December 15, 2007

Audio in Linux is awesome

I’ve got some poorly recorded MP3s of people speaking. I want to try to make them a little easier to hear. In Windows I’d reach for Sound Forge. How about in Linux?

  1. Search Google for “sound forge equivalent for Linux.”
  2. Find several references to “Wave Forge.”
  3. Find “Wave Forge” hasn’t been updated this century. Move on.
  4. Decide to try Audacity because it’s in the back of your head, and Ardour because you found a bunch of links to it somewhere.
  5. yum install audacity ardour. That was easy.
  6. Run Ardour. Tells you it needs JACK. WTF is a JACK? Move on.
  7. Run Audacity. Loads. GUI looks a little silly compared to Sound Forge, but it looks functional enough.
  8. Try to load the MP3 file. Get told this version doesn’t have MP3 support.
  9. Fish around for something to decode an MP3 to a WAV file. Feel bad about considering installing xmms just because you remember how to do this with WinAmp. Rejoice when you find lame --decode.
  10. Load the WAV in Audacity. Looks good.
  11. Hit the play button. Get told there’s an error in sound output.
  12. Check sound preferences. Note that there are no available playback devices.
  13. Read around for a while about JACK. See references to jackd. Eventually realize that this is something you need to run yourself, as your own user.
  14. Run jackd. Get told that it can’t open the hardware device, presumably because other things (Amarok, Flash) are using it.
  15. Find the correct invocation to run jackd which is something like jackd -d alsa -d default (-d twice, WTF).
  16. jackd seems to keep running. Cross fingers, run Ardour. It opens.
  17. Look at the Ardour interface. Decide that (1) it’s not what I want, and (2) dear god that is ugly. Is that Tk? Motif? Holy hell. Run away.
  18. Open Audacity back up for the shit of it. Lo, there is some sort of JACK playback device now. Select it, hit OK.
  19. Click play button in Audacity. Error with sound card.
  20. Go into settings, change record device from OSS to JACK. (But I’m not recording?) Click play button in Audacity. Sound comes out! Rejoice.
  21. Select a section, figure out how to zoom in. Click play. Get an error telling you it can’t play.
  22. Try playing different selections, no selections. Keep getting the same error.
  23. Restart Audacity. Same error.
  24. Restart jackd. Restart Audacity. Same error.
  25. Read about qjackctl being very helpful. yum install qjackctl. That was easy.
  26. Run it. Not sure what I’m looking at. Says JACK is started. Try to turn on logging. Tells me I have to restart something. Whatever.
  27. Restart Audacity. Hit play. Same error.
  28. strace jackd. Hit play in Audacity. No activity.
  29. Stop jackd and tell qjackctl to start it. Get a pretty incomprehensible error message in its “log.”
  30. Realize that it’s bitching because it’s trying to start it with real-time priority, which it presumably doesn’t have permission to do.
  31. Read “The simplest, and least-secure way to provide real-time privileges is running jackd as root. This has the disadvantage of also requiring all of JACK clients to run as root.” Yeah, no.
  32. Google around a bit, find out about /etc/security/limits.conf. Find some lines in there referring to @jackuser.
  33. Try to usermod -a -G jackuser myuser. Fails, presumably because my user is in LDAP (but the group is in /etc/group).
  34. vigr, add myself to the jackuser group by hand.
  35. Don’t want to restart my X session to get new groups. Figure I need to log in from scratch to get new limits. Fuck it, ssh localhost.
  36. Run qjackctl. Tell it to start jackd. Works. Rejoice.
  37. Run Audacity. Hit play. It works!
  38. Stop. Hit play again. It still works!
  39. Stop. Make a selection. Play the selection. Holy shit it played the selection!

Really not very much work at all. And Audacity only crashed, like, three or four times while I was using it! (Mostly when hitting the play button to play the section I was working on. I can’t remember if jackd exited too.)

I can’t wait for PulseAudio. I’m sure that will make all of this even easier.

Oh, but in the end, I just ended up using sox and normalize in a script to do my MP3s in a batch…

Comments (59)

  1. December 17, 2007
    Anonymous said...


  2. December 17, 2007
    rj ryan said...

    In Windows, you’d reach for your pirated copy of soundforge..

  3. December 17, 2007
    Will said...

    Dripping with sarcasm…just the way i like a post. Stuff like this is the reason I gave up on Ubuntu after a day.

  4. December 17, 2007
    WalterSear said...

    Linux for audio, is for people who are more into Linux than Audio.

  5. December 17, 2007
    Lol said...

    aptitude install audacity ardour

    oh wait, that not debian based distro, too bad

  6. December 17, 2007
    Samium Gromoff said...

    When doing “Linux for audio”, why not use a multimedia-oriented distribution?

    That is, if you want a targeted QA, there’s a place where you can get it from.

    There are, at least:


    And if you’re using a Debian-based distro, you can just add the debian-multimedia package source, and it’s very likely to just work.

    (That includes Ubuntu.)

  7. December 17, 2007
    steve said...

    While I’ve been using Linux since the beginning, these people advising multimedia Linux are not on this planet. You’re advising that someone should wipe their whole machine and install a complete new operating system just to tidy up some sound files. Please, recognise when your love of Linux is making you say stupid things, and stop doing it.

  8. December 17, 2007
    Mike McNally said...

    You’re dumb.

  9. December 17, 2007
    David said...

    Use a multimedia-oriented distribution? That means reinstalling the entire OS. That would add a lot of steps to the 37 listed here. No thanks…

  10. December 17, 2007
    she said...

    This is a GREAT post

    People flame at you but they should realize that if YOU have a problem (a somewhat advanced user), anyone that is less “advanced” will have a LOT MORE problems.

    Using a “multimedia oriented” distribution is NO solution. How many windows are there? Right. And how many different Linux distributions? Right.

    Every distribution must be PERFECT at a given task. Or, if not PERFECT; at least “good enough”.

    Reread the above and then ask yourself is it is “good enough” or not.

    If you think it is good enough, I just laugh at you!

    It sucks. Linux must do better.

  11. December 17, 2007
    kb said...

    > In Windows, you’d reach for your pirated copy of soundforge..

    Or Audacity for Windows, because even if it’s a freaking Open Source tool that’s way, WAY off everything that a productive user would want (a: see the GIMP for other references on this topic, b: it’s astounding how wrong you can get a sample editor even 15 years after Cool Edit), you can start it and it even pretends it works. Might be because it runs atop an operating system that deserves this name.

  12. December 17, 2007
    Matt said...

    Debian versions handle package dependencies much better in my humbling experience. I did give up on redhats a long time ago though.

    For linux – with great power comes great responsibility :) At the end of the day you were able to find documentation and get it working that’s cool.

    In regards to “Use a multimedia-oriented distribution?” some how you have a linux system now but have not installed some key audio software… well then if you’re in a pinch you could boot up a CD-distro that would allow you to edit the file. dynebolic is one. No need to install ‘anything’ just pop in a cd and if you’re lucky and your hardware is supported then you’re good to go. If not then you’ve wasted 15 minutes downloading the cd and trying it.

  13. December 17, 2007
    docatomic said...

    No, no, no! Install the multimedia-oriented distribution on one of your _other_ boxes… that is the more convenient way to do it. If you still insist about being less convenient, then install a removable hard drive tray and use multiple drives on the same box. Or if you somehow want more masochism in your life, then add more partitions to your poor lonesome lil’ existing hard drive and install XOSL, or some other wonderful boot-manager program. Or finally, just go all-out twenty-first-century on the bling thing and run *all* of your OSes in VMs – works great on those shiny new multi-core platforms, right, kiddies?

    Or perhaps best of all, simply have enough smarts to choose a fully-functional distribution to begin with.

  14. December 17, 2007
    Loic said...

    Well linux sounds is crap i agree…

    But there is something called Pulse Audio that isn’t present natively in most distributions…Too bad because it’s freaking useful.
    in few word, it will do what most people would want. If something is asking for sounds it will give it. But it will never lock the sounds so flash and only flash can output sounds. It manage the sounds streams…So if something ask for will see alsa but if someone want jack…it will see jack..and thats like that for all the sounds driver…

    And the funny thing with pulse audio is that it let you control the volume of every stream. So you could say flash is muted whatever flash does… while everything else is high etc.

    But yes, if you don’t have pulse audio it’s crap because linux does have to much sounds mixer/driver whatever we call them. And they aren’t very friend together so thats why the big mama pulse audio is great.

  15. December 18, 2007
    timeywimey said...

    You can get crossover office and run soundforge 7 in it and it works totally fine. Xover office is 60 bucks but it sure beats having to deal with windows stress. I will try it with wine but I know that it will work in wine becuase xover is based on wine, just with alot of management added onto it and alot more support and it is easy. Alsa works and sound is great. I even got the antares and autotune to work on it as well. Try this and you will be able to relax! Good luck! ;-)

  16. December 18, 2007
    russellnation said...

    you don’t have to reinstall the whole operating system to get a multimedia baseddistro. infact it can be as easy as (in ubuntu) adding the ubuntu studio repository then in synaptic (or terminal with apt-get or aptitude) install the ubuntu-studio-audio package (or whatever its name is can’t remember) and while your at it install the ubuntu studio theme its a cool dark grey theme that looks sweet. as for other distros … your on your own. and jokosher sucks too or at least i cant figure out how to do much of anything on it but haven’t messed with it that much.

  17. December 18, 2007
    russellnation said...

    …you*re …
    sorry don’t drop the grammer hammer on me.

  18. December 18, 2007
    Razee Marikar said...

    What you’ve done is something like installing a cut down version of Windows without drivers, and get all freeware to do your work. Its more like installing Windows 95, trying to get a driver for your new sound card, trying to install some sound editor and do the work. Install a major linux version, like Debian 4.0. It contains almost everything you want, including a Windows emulator (wine), with which you can revert to Windows software if native software doesn’t work. Even if you buy it, its cheap compared to Windows. And the good news is, you don’t have to buy it. You can use it for free – freedom and free of cost!

  19. December 18, 2007
    Pavel said...

    Your post is written from the position that you already know and have what software you need under Windows and you don’t under Linux. That’s a really really unfair comparison.

    For me, editing an mp3 under windows would involve: googling for “mp3 editing windows” or something equivalent, testing all free version, figuring out they are not good enough, finding Sound Forge, finding the correct torrent, downloading it, figuring out it’s corrupted, downloading a better one, figuring out all controls…… All that can’t be fewer steps.

  20. December 18, 2007
    mattperry said...

    me@ubuntu:~/Music$ sudo apt-get install audacity && audacity your_crappy_music.mp3

    Wow. That was really hard.

  21. December 18, 2007
    tom said...

    A funny, if only slightly atypical account. Wait’ll you try to get some nice TTF fonts in there! Yet I would not trade my Ubuntu desktop for anything else out there. And my sound system rocks!

  22. December 18, 2007
    Fred said...

    You’re an idiot, keep using Windows then, nobody’s forcing you to change or anything.

  23. December 18, 2007
    James said...

    In a sense this is an allegory. I’ve never had this exact problem but it reminds me of several problems I’ve had using OS software in the past. It’s the main reason I stick with a commercial operating system (OS X) and keep the command line OS tools handy (fink).

  24. December 18, 2007
    Patrick Hall said...

    Thanks for posting this.

    SO true. It seems to me that audio is the last place in the Linux/FOSS world where the situation is so hopelessly balkanized and confusing that the only people who manage to do it are alpha alpha alpha geeks. And those are the people who will then turn around and smite down the newbies with acronyms. (Even the insults are condescending.)

    I remember buying a copy of Linux Magazine (or was it Linux Journal?) with a cover story about Linux audio. There was a diagram about ALSA, JACKDUP, and OMGWTFBBQ, the latest astonishing Linux sound libraries, that looked exactly like the rat’s nest that it is.

    Maybe it’s possible for Linux audio to be reliable; I’ve been using Linux since 1999 and I’ve yet to come across a distro that has reliable audio, ever.

  25. December 18, 2007
    Conrad Parker said...


    I completely agree with you and most comments; it shouldn’t be necessary to go fidling with JACK to just go edit a sound file, and software should just work without crashing.

    I’m the lead developer of Sweep, a sound editor for Linux that works somewhat similarly to Sound Forge. It’s been available in basically in its current form since 2003, and has been developed with these goals in mind.

    Please try it, and I’ll be glad to hear your criticism (good or bad :-)

  26. December 18, 2007
    root said...

    apt-get install ubuntu-studio

  27. December 18, 2007
    Ryan said...

    Don’t use an OS that sucks at things you want to do. If you’ve committed yourself to an OS that doesn’t meet your needs, tough shit. That includes Windows (although lots of people don’t realize there are alternatives).

  28. December 18, 2007
    Ryan said...

    (BTW, I categorize each Linux distribution as its own OS, so by the above comment, I meant you should have picked a more suitable distribution, like Ubuntu, off the bat, or, if you couldn’t find one and just love dealing with malware, gone with Windows.)

  29. December 18, 2007
    Simon Edwards said...

    Which distro and hardware are you using? because that doesn’t resemble my experience. I just open audacity, load the mp3 file, do what I have to do and then export it as mp3 again. No mess, no fuss. I’m on Kubuntu 7.10.

  30. December 18, 2007
    Anonymous Coward said...

    He, the article pretty much sums up my sound experience. That’s the reason I removed jackd after two days of fiddling around. It is just not worth the time.

  31. December 18, 2007
    K said...

    I installed the latest Fedora, and my audio doesn’t work either. No error messages, there is a device installed, I can control the mixer and the volume… Except, all remains _dead_ silent. Second time in 10 years I installed Linux. I expected it would just work by now. I’d love to use it for everything but obviously can’t.

  32. December 18, 2007
    ChaOS said...

    You’re article is pretty good, however, there are easier ways.

    Assuming your running ubuntu just install Automatix2 and then check off mp3 support. Open amarok and have fun.

  33. December 18, 2007
    tgies said...

    Linux doesn’t really have audio yet sorry dude we’re working on the problem and hope to have it all fixed up within fifteen years

  34. December 18, 2007
    Anonymous said...

    That sounds very familiar. I have dual installation with Gutsy, and it’s stuff like that, that keeps me using Vista 99% of the time. Heck, in 2007 end-user should *never* have to touch the command line.

  35. December 18, 2007
    Mikey said...

    I discovered that you’d never get an answer to a problem from Linux Gurus by asking. You have to troll in order for someone to help you with a Linux problem.
    For example, I didn’t know how to find files by contents and the man pages were way too confusing. What did I do? I knew from experience that if I just asked, I’d be told to read the man pages even though it was too hard for me.
    Instead, I did what works. Trolling. By stating that Linux sucked because it was so hard to find a file compared to Windows, I got every self-described Linux Guru around the world coming to my aid. They gave me examples after examples of different ways to do it. All this in order to prove to everyone that Linux was better.
    * ion has quit IRC (Ping timeout)
    brings a tear to my eye… :’) so true..
    So if you’re starting out Linux, I advise you to use the same method as I did to get help. Start the sentence with “Linux is gay because it can’t do XXX like Windows can”. You will have PhDs running to tell you how to solve your problems.
    this person must be a kindred spirit of mine

  36. December 18, 2007
    BT said...

    Pavel is right… this isn’t a fair comparison. If you googled for a windows app you’d have a much harder time, imo. You have to experiment with various freeware and potential malware. You’d probably introduce some spyware. You’d have a VERY difficult time removing all of the software you’d be testing with all the orphaned dll’s and registry entries. Testing applications is a disaster on windows machines.

    Jack is mainly used for extremely low latency recording. It’s actually a much better implementation than windows asio drivers. Jack allows you to route various audio streams, it’s a very powerful application. Unfortunately, until Ardour 2.0 comes out multitrack recording in linux will be a black art. I’ve had a great deal of difficulty getting my asio devices in windows working with reasonable latency levels without crackling… with jack I have no such issue.

    It’s unfortunate you didn’t try Rezound first because that should work well out of the box… and it’s not ugly.

  37. December 18, 2007
    philibertperusse said...

    In Windows I would have used Audacity and it would have worked fine after simple installation. The only thing not there is LAME for MP3 encoding only (Audacity manages the decoding somehow without LAME). In fact, I used Audacity quite a lot and find it quite convenient for a free audio tool.

  38. December 18, 2007
    George said...

    I think many of you are missing the point of this article.

    The point is that Linux is NOT ready for public consumption. ANY distribution of Linux you choose, it’s not ready for the masses.

    There seems to be this push by the hardcore Linux users to install _insert favorite Linux distro here_ on your mom’s PC to replace Windows and all of her Windows problems will go away.

    Yeah, right.

    This post detailed the ordeal of trying to do something that SHOULD BE relatively simple, but is unnecessarily complex, by an above average user who knows what they are doing. Imagine and end user going through this.

    I had a similar experience trying to get a wireless network card working under Fedora 5. It took all weekend, and when it finally did work, it would lock up the system entirely if WEP or WPA was turned on. I gave up, and haven’t touched Linux since.

    I’m not a typical user. I’ve been a network engineer for over over a decade. I remember setting IRQ and memory address settings by jumper on network cards, and then manually tweaking the DOS drivers to match those settings, rinsing and repeating until you could find a combination that actually worked. (And even that was easier than doing the most basic things in Linux.)

    The point is, I know what I’m doing, and I wouldn’t touch Linux with a ten foot pole. Linux is no where near ready for mass consumption.

    Just because some of you enjoy digging into all of the esoteric little corners of your operating system just to get it to work, and the feelings of superiority you get doing so, doesn’t mean your preferred system is right for everyone.

    Linux is for the super geeks who want a computer for the sake of getting it to work. It is not for people who want to get stuff done.


  39. December 18, 2007
    Bon said...

    This is an apt, and typical, description of the hurdles for broadening the appeal of linux. I tried several flavors of Linux on my kids laptop and finally found one that was “relatively” straightforward to install, use, get wireless, DVD capability, etc… Generally, Linux just aint there yet (but almost – stuff like Linux Mint, etc… are just about there).

  40. December 18, 2007
    Brianary said...

    Why not “Audio on computers is awesome” or “Audio on digital hardware is awesome” or “Audio on new software is awesome” or “Audio on unfamiliar software is awesome”?
    Your experience wasn’t the same on EVERY distro, was it?

  41. December 18, 2007
    Anonymous said...

    The quality of packaging for your distro can make a really big difference. For example, when I installed ardour under Ubuntu, it installed jackd as a dependency, and then Just Worked because the Ubuntu jackd package installs it in a working configuration. It is really terrible looking, though.

  42. December 18, 2007
    Johannes Eva said...

    Great, great review!
    I had exactly the same experience, many, many hours trying around, but at the end nothing functionned.
    More, my sound card has some nois when recording under linux that it hasn’t on windows, audacity functions better under windows, doesn(t crash all the time.
    I’ll probably have to go back to windows, as my printer refuses to work, too.
    It’s so sad we will never have a great OS operating system…

  43. December 18, 2007
    porker said...

    Audacity has never given me a problem. Yes, you must have lame, and that must be installed manually due to the fact that it deals with a restricted format, but that brings the steps down significantly.

    1. aptitude install lame audacity
    2. open file in audacity
    3. edit
    4. export

    I’ve never had Audacity crash, even with 8+ instances.

  44. December 18, 2007
    Aminorex said...

    You’re painting with a broad brush here. I understand that the distribution of Linux which you were using had crappy audio support. I sympathize. I’ve tried Vista for example, and it sucks hard vacuum; I always had trouble when I ran Red Hat. Now I use Debian or Ubuntu on everything, and I don’t have problems like these any more. Likewise, when I need Windows, I use a trusty, efficient, uncrapped Windows 2000, if the hardware is supported, or XP otherwise.

  45. December 18, 2007
    Justin said...

    Linux == Fuck with it until it works.

  46. December 18, 2007
    Aaron said...

    Yes, It’s tough to get audio working right in Linux. However, I took the time to get JACK and ALSA working correctly in getting LinuxSampler installed under UbuntuStudio. In the end, I’ve got a reasonable software audio sampler for no cost other than the few hours of time invested. For some decent quality in a home studio, this not a bad investment of time.

  47. December 18, 2007
    nalf38 said...

    If you’re looking for something that functions a lot like SoundForge, then ReZound would have been a better bet for you. I used SoundForge religiously for audio editing, though I haven’t used it since SoundForge 5.

    Also, do you absolutely need JACK? ReZound works very well with PulseAudio, too.

  48. December 18, 2007
    JMC said...


  49. December 18, 2007
    JMC said...

    it is YOUR opinion that linux desktop is not ready for the masses. in my experience, this is not the case, at least, windows, bsd, or osx is no more or less ready than any of the others. some things that are extremely simple in linux (package management, permissions, administration) are ridiculous in another (windows, namely). you pick one instance where YOU could not get an MP3 to open (which i’ve never personally experienced) and use that as an indicator of the OS, as a whole. that would be like me stating that windows is a worthless platform simply because notepad has a buffer size limit.

  50. December 18, 2007
    Applegates said...

    I personally have not had this much trouble with Linux audio, and I use Fedora Core 8 (I have also used ubuntu, debian, mandrake, suse and a few others, but i prefer Fedora). I have never used Audacity however so maybe that has something to do with it, but in my experience, All I’ve ever needed to play an MP3 is to install Jack, pulseaudio, xmms and the mp3 codecs and it all runs sweet. In my experience yum install jackit will install Jack and the dependencies it needs to make it run without a hitch. Of course you may need alsa to actually hear the sound, but usually this is installed when you install the multimedia components of Fedora. To be short, I think Linux as a Desktop OS is more than ready for those prepared to give it a go and to learn how to use it, And while you can’t play every game designed for windows in Linux (I’ve not tried Cedeaga so whether i’d have more luck with that than with WINE i’m not sure) I don’t think that rules it out as viable OS. Windows has it’s own set of problems that you have to deal with and if you want to use it as your primary OS then so be it, but at the end of the day your choice of OS does not matter. What matters is that your choice of OS does what you want it to do, and for me Linux does what i want it to do. A survey of Linux users recently (want to find it? google it) said that most Linux users use Windows as well as Linux as per their needs, so the argument of Linux vs Windows is irrelevant in the end. For me, and in my experience, Linux audio works fine, is relatively easy to get working if your sound hardware is supported, and only requires around 5 or 6 packages which can be installed easily with Yum and Apt without much configuration required.

  51. December 18, 2007
    Anonymous said...

    pebkac pebkac

  52. December 19, 2007
    ... said...

    In steps 11 and 12, a sound daemon like esd or pulseaudio may have been blocking audacity from using alsa. Closing audacity and shutting down the sound daemon might have allowed audacity to use alsa, which would have made steps 13 through 36 unnecessary.

    Nice finale with the sox and normalize solution. The command line rocks. Even with the 39 step process you outlined, you probably spent less time with the script than you would have if you had edited each file individually.

  53. December 20, 2007
    Chris Lees said...

    pebaasc (Problem Exists Between Audacity And Sound Card). Go to the Sound control panel in Gnome, turn off Software Sound Mixing. It will work fine now.

  54. December 20, 2007
    darkness said...

    @Chris Lees: no esd here (setting was unchecked). Presumably Audacity couldn’t grab the ALSA hardware devices because Amarok and/or Flash had them open.

  55. December 21, 2007
    anthony said...

    Linux is a PITA unless you get a distro specific to what you want to accomplish. Had you been using Ubuntu Studio you would have been fine. A more accurate statement: Audio in YOUR SPECIFIC LINUX DISTRIBUTION sucks. Its not a problem with “the linux” its a problem with your linux distro.

  56. December 21, 2007
    Joe said...

    People are tools. “Don’t use an OS that doesn’t work for you.” “If you can’t figure it out, go back to Windows.” Blah Blah Blah Blah.

    Problems like these are typical on a linux box unless you want to run the bare minimum of software that comes on the disc. Seriously, try to do anything out of the ordinary becomes a true pain in the ass.

    I love Linux, and I’ve been using it for years, but every fucking time, it’s the same shit. Library version issues, conflicts, missing software you didn’t know existed..

    I can always figure it out, but it always annoys me that I had to.

    It’s like, shit. It’s almost 2008. Let’s get a fucking move-on here! Fortunately, I believe distributions such as Ubuntu have and will continue to do good things in the future.

  57. January 7, 2008
    darkfader said...

    thank you so much for the laugh.

    an irix user.

  58. February 7, 2008
    ClayOgre said...

    I have not had much luck with Linux sound either. And all I want to do is to simply record sound from the microphone, something that is a breeze under Windoze. Everybody is talking about Ubuntu. The problem is that Ubuntu is just as bad, if not worse. I have tried many different versions of Ubuntu, on TWO different computers, one of which, a System 76, was purchased with Ubuntu pre-installed….and it STILL didn’t work, crashed six times in the first hour. Other distros install and run on this computer, but not the one that it supposedly came with. Right now it is running ZenWalk 5.0, which works just fine, except for less than stellar sound quality, playback is kinda staticky and as usual, I have not been able to get anything recorded from the microphone. Guess I will just have to do sound on Windows and use Linux for everything else.

  59. December 2, 2008
    roger said...

    Note that if you google for ‘windows mp3 editor’ it comes up with audacity for windows.

    As a funny side note, if you google for ‘linux mp3 editor’ it comes up with the audacity for windows page. LOL.