Ubuntu Studio 9.10 - First Look

Since my old Acer has been on it's last legs for months now, I haven't had a working Linux computer for some time.  The Acer's video card finally gave out, so I had to use an external monitor, which Ubuntu didn't support on the SIS graphics chip.  (SIS's fault - they won't release the code)

So when I got my new (used) Dell Inspiron B130, I was anxious to try out Studio on it.  I had wiped the drive and did an OEM install of XP Home via the recovery partion, so I had a nice, clean drive to work with, 20gig bigger than the Acer. 

Since I didn't have any DVD-RWs around, and I am notoriously impatient, I dowloaded the ISO image of Ubuntu 9.10 (Karmic Koala) Live CD.   Install was a snap.  It ran quickly and easily, using it's own easy-to-use partitioning software.  I gave it a 25gig slice, and soon it was humming along with it's sleek new Gnome 2.28 desktop.  The Dell (unfortunatly) has the same klunky Broadcom 4318 wireless card as the Acer (at least I have a spare) so I had to add the BC43 driver (on the CD) and the fw-cutter driver (download).   I knew this from the Acer, and  was ready, having already downloaded them to a flashdrive. I didn't have to jump through any hoops, though, like with Hardy and Intrepid. Install the packages and boom - working ever since.  (on Intrepid it would work sometimes, not work sometimes) A run of the Upgrade Manager to get the latest and greatest, and we're all set.

Surprise #1 - Grub2 - Since my wife uses my laptop from time to time, I like to make Windows the default OS.  In the past this was done by editing a small text file called menu.lst in the GRUB directory.  Except Karmic ships with Grub2, and there is no menu.lst file.  There is a grub.cfg file, which you are warned everywhere in BIG RED LETTERS never to edit.  Ever.  Seems Grub2 dynamically configures the config file when you make changes.  There are a couple of ways to make the change.  One involves downloading the Startup Manager package, which gives you a nice, pretty GUI to do it.  Very un-Linuxy.  The other is to edit etc/default/grub and change the number in Default=O.  You have to figure out which number to put by counting your entries on the startup menu.  Mine was 5.

That done, I wanted to get right to work.  Installing Ubuntu Studio was a snap: open the Synaptic Package Manager > Repositories window and enabling the additional repositories.  Reload.  Search for "studio".  Click on ubuntustudio-desktop, ubuntustudio-audio, ubuntustudio-graphics, ubuntustudio-video.  Click "Mark."  Click "Apply."   Watch Criminal Minds while it does it's thing.

So, how does it do it's thing?  Excellent.  I had some guitar parts to record for the record, so I started with Ardour, the awesome DAW program.  First, launch JACK to connect to the soundcard, then Ardour. Once I had started a project, imported a soundfile and set up the JACK connections, it was time to go.  The system worked flawlessly for recording and editing.  I didn't have to change any setting on the soundcard mixer to duplex, and multitracking worked perfectly. (was was working off an imported wav file produced in Audacity.)  I was able to easily save the new track as a wav.  Ardour did hang while exporting it as an mp3, but I think that was more a processor-heat thing.  (the Dell gets pretty warm)  I let it cool for awhile and was able to complete that export.

The real test was using Audacity.  Although Audacity uses a lot less processor and memory overhead than Ardour, I would be working with projects that had 10-15 tracks running at once while recording. Time to plug in the portable and load a project. (I had been working in Audacity all along because of the Acer issues; there is no Ardour port for Windows)

Surprise #2 - Native NTFS read/write support. I didn't have to tweak Karmic at all to use the portable. (Previous versions required an additional package.  Take that, Apple.)  Audacity easily opened the project files that I had created in a Windows installation without skipping a beat. 

I was able to load up a project and import the wav I had made in Ardour easily.  A little mixing, and then export it to mp3.  Done.

Next was a song I needed a new acoustic track for.  I use a Behringer Xenex 802 into the mic-in on the computer.  One limitation of Audacity is that it doesn't duplex very well, so you usually can't hear what you're recording.  I was tracking acoustic, so I really didn't care, but that's something they need to work on.

The system performed well, however - no latency even with 11 tracks going out and 1 coming in, and TweetDeck running in the background. 

Conclusion: All in all a great experience so far.  I know there have been issues with 9.10 on a lot of boxes, mainly with upgrades from Jaunty and with certain video cards.  So far I've had only one minor hiccup, and I've worked the system pretty well.  Multitrack recording on a three-year-old budget laptop is pretty intensive stuff.  The only thing left to do is see how the video editors fare.


  1. Glad it worked so well for you. Maybe I should have tried the same method as you (live install, then build studio afterward) but with the exception of Mandriva Powerpack 2008 no lixux distro I've installed has ever managed to connect to a repository for downloads & updates. With my first successful Ubuntu studio install (where I failed to select the components I wanted installed) it repeatedly failed to connect to the repositories: had it done so I'd have added in the other studio components just like you did. I suspect it's to do with ipv6 - Orange have not enabled the protocol, and all modern distros automatically assume use of ipv6 now.

    Have you tried LiLo instead?

    BTW I hadn't realised that Ubuntu (and presumably some of the other distros) couldn't access NTFS drives. Sabayon (as you know, my long time favourite) has been able to do this as standard for a long time.

    As for duplex from Audacity, I'm not sure what the answer is. It had really bad latency issues under W2000, but works great under XP. Not a problem if you're recording in the normal way, micing up, but a problem if you're recording from a modeler. A few recordings I've made, I've played the guitar through a processor going direct into the computer, and had nothing but an un-amplified electric guitar to follow. It worked much better than I expected, but it's not my favourite. I'm hoping that with the trademark 60 I can use the amp as a monitor and use the DI out for recording, so it'll work like a sansamp. The processor does have true stereo outputs, so I could run 1 to the PC and one to an amp.

    Anyway, glad it's working well for you.

  2. i was wondering if you knew what cause this errorr message to pop up with recording

    i'm new to this and can't seem to find an answer

    Latency Correction setting has caused the recorded audio to be hidden before zero.
    Audacity has brought it back to start at zero.
    You may have to use the Time Shift Tool (<---> or F5) to drag the track to the right place.


  3. Typically that means that there is too much latency (delay) in your recording source. Audacity is trying to compensate, but the delay is so much, it has to "push" the recording back that it starts before the zero mark.

    You can try a couple of things. Be sure that you have the right type of card selected in Edit=> Preferences=> Audio I/O. (If you have a 16 bit card, be sure that is selected.)

    Also, you can disable the "Software Playthrough" function. And increase latency. I think the default is 100. You can bump it to 250 or 300 and give it a whirl.

    If you still have issues, it would be helpful to know something about your system; type, OS, version of Audacity, speed, memory, soundcard, etc...


Post a Comment

Popular Posts