Slashdot Mirror
Goodbye Apple, Hello Music Production On Ubuntu
Adam Wrzeski notes a piece up at Create Digital Music by musician Kim Cascone (artist's bio) on switching from Apple to Linux for audio production: "The [Apple] computer functioned as both sound design studio and stage instrument. I worked this way for ten years, faithfully following the upgrade path set forth by Apple and the various developers of the software I used. Continually upgrading required a substantial financial commitment on my part. ... I loaded up my Dell with a selection of Linux audio applications and brought it with me on tour as an emergency backup to my tottering PowerBook. The Mini 9 could play back four tracks of 24-bit/96 kHz audio with effects — not bad for a netbook. The solution to my financial constraint became clear, and I bought a refurbished Dell Studio 15, installed Ubuntu on it, and set it up for sound production and business administration. The total cost was around $600 for the laptop plus a donation to a software developer — a far cry from the $3000 price tag and weeks of my time it would have cost me to stay locked-in to Apple. After a couple of months of solid use, I have had no problems with my laptop or Ubuntu. Both have performed flawlessly, remaining stable and reliable."
Well, Apple DO encourage it...
nice to see a person that has the right tool for the job. BTW you wern't locked into Apple, you were locked into the software developers choice of OS and hardware.
There was an unknown error in the submission.
I see why you posted as AC. The point of the article is he is a fairly well established musician breaking away from a well established platform for the music industry. I actually find it interesting, considering that a few years ago you often had to go through hell just to get anything to come out of the sound card using linux.
I'm all for open-source, but trying to do any music production on linux has been a headache to say the least. I'm more than willing to give it another shot, but I've had very little if any problems on my mac. Actually, all the problems came from it being a "hackintosh" Mac OS X was designed for audio unlike other OS's. Between it's ultra-low latency audio subsytem and the industry standard Audio Units plugin archetecture, it'll take a hell of alot for Linux to beat that. Plus Logic owns any program I've ever tried and I can only run it on a mac. As much as I love open-source anything, I spent too much time just trying to figure out Linux technical issues and not enough time actually recording. If there were less competing standards on the platform and less buggy software I'd probably be running a Linux DAW right now. Until then I'm more than happy with my "Mac".
So what? I'm not trying to troll here (well, maybe a little) but honestly, who cares?
This whole mentality of "Us against the world" is kinda amusing to me. I guess it's because I'm not a developer, or something, I dunno.
But this is one artist saying "Software X is/was expensive, so I'm using a different and free solution." Ok, great, good for her. So now what?
Sent from your iPad.
Anyone who believes this has never tried to record and mix multitrack audio on Linux
Audio support is fine. Music making support OTOH is abysmal. The article correctly points out that sound recording, editing and mixing is fine on Linux. The heavyweight music creation tools just don't exist and many of the top-end hardware interfaces simply don't have Linux drivers.
Squirrel!
I agree with the premise of this article: Linux is a perfectly good platform for digital audio creation and editing. It might even be better than a Mac, depending on how you weigh different pros and cons. But I unfortunately don't really feel I learned much from this article about why Linux is a good choice. All the apps he mentioned (Audacity, Ardour, etc.) are available for both platforms. And his reasons for switching, like the lack of a tree view in the OS X finder, strike me as weirdly trivial and not music related.
As someone who's done some published research on audio latency/jitter issues in a former life, I'm also somewhat annoyed by how much these sorts of articles focus on tech like JACK and low-latency kernel patches. This used to be a huge issue, but I suspect it shouldn't be nearly as high up anyone's priority list as it used to be--- back in the 2.4.x. series kernels, when the default kernel's clock tick used 10ms granularity and scheduling was flaky, it made a much bigger difference. Today, I suspect this sort of behind-the-scenes performance is only infrequently the bottleneck in anyone's audio performance; when I see actual glitches in performances, they can often be fixed by much more boring scheduling tweaks like "nice -19" on the processes that are bottlenecks in the audio path, or finding bugs in how you're setting up your callbacks.
In any case, these days I see JACK as useful mainly for being a reasonably well supported audio-app-interconnection bus; as he says, the Core Audio of the Linux world. But that doesn't make it hugely unique either.
So I guess I'm in the weird position where I agree with the article's conclusions, and some of its specific points, but overall if I didn't already agree with it, this article wouldn't have sold me on why Linux is great for audio editing. Sorry. :/
10 PRINT CHR$(205.5+RND(1)); : GOTO 10
I've been using this for quite some time now. anyone else?
Warning, the above comment may contain sarcasm. Don't say I didn't warn you.
I actually find it interesting, considering that a few years ago you often had to go through hell just to get anything to come out of the sound card using linux.
On the other hand, many still do have trouble getting anything to get out of their sound card on Linux. I agree that the story is "interesting," but those of us serious Linux users will have to admit that the audio situation here is far from ideal, to put it positively. Alsa.... pulse.... awful. Compound this with the noticeable lack of good software and drivers for audio production equipment, and I will have to admit that the vast majority of professional audio people are much better of staying with Apple at the moment.
This author takes full ownership and responsibility for the unpopular opinions outlined above.
If you're looking for a great alternative to expensive, bloated audio applications, check out Reaper. It's made from the guy who originally wrote Winamp. The licensing is very friendly and only costs $60 (discounted license). They're very responsive to user feedback and add features constantly (updates usually arrive every 2 weeks). I've used other tools in the past like Reason and Cubase, but ended up ditching them in favor of Reaper. Its built-in effects are quite good and it supports DX and VST plugin formats. Unfortunately it is only supported on Windows (32 and 64bit) and Mac OSX at the moment however
Seems like some enterprising individual could start putting together cheaper-than-dirt Ubuntu-based music machines by buying Dell Studio laptops (with Microsoft license rebate, naturally) and preloading everything necessary.
The complaint from non-geeks about Linux is you have to do it yourself. If you didn't have to do it yourself, and it really was that cheap, it becomes a lot more interesting.
Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
This dude is not exactly producing musical scores using his Ubuntu rig. I mean, seriously... go check out some of the stuff on his store and you'll see why (examples):
Reaching Dark Stations
Recorded in Regina, Saskatchewan in 2007 at the Neutral Ground Gallery:::industrial factory sounds filtered through a turbine jet engine::Play loud, play often:::Statistically Improbable Phrases
30 minutes of sputtering modems and hacked sparking mainframes; the sound of technology gone awry mixed with submariner dark station dronescapes; briny chains scraping against the hulls of rusted ships. Recorded live in Paris at Instant Chavires
In short, he doesn't need the type of precision and accuracy provided by higher-end hardware and/or custom interfaces and plugins that one would need for 'serious' music (yes, I went there), so he can get away with using Ubuntu. After all, it's just 'bleepy shit' anyway.
Kim mentions the use of free audio production software, such as Audacity, as substitutes for commercial offerings. While an Audacity user is more than welcome to dive into the code base and make needed improvements, not every user has the time and/or ability to do such. In my estimation, neither Audacity 1.3.7 nor Audacity 1.2.6 are stable enough to be considered "professional-quality" software. I am not trying to insult the developers and their abilities -- they have a complex project on their hands. But Audacity's graphical interface has serious and repeatable bugs; Audacity's sound export facilities reliably adds spurious noise to sound. I admire Kim's decision to use Ubuntu as an audio workstation, but I don't think Kim has been forthcoming about sacrifices in software quality that a user must make to do so. Kim can easily translate most audio programming done in Max/MSP (the commercial environment he has worked with extensively) to the public domain environment "pd" -- but as an experienced user of both systems there are more functionality loses than gains moving from the commercial Max/MSP/Jitter environment to pd (Pure Data).
If the cost of an Apple system and the higher cost of outfitting it with professional quality audio production and performance software are bankrupting a musician, then I can see the logic of using an Ubuntu system at this time. Otherwise, I still believe the adage "you get what you pay for" applies. However, I believe with effort from open source audio developers an Ubuntu audio workstation with both cost and quality advantages is more than possible. The bugs I am seeing in Audacity today remind me of the bugs I saw in the comparable commercial application "Peak" ten years ago.
The heavyweight music creation tools don't exist because a) there's not much of a market for them on Linux because; b) Audio support is most definitely not fine.
I have had nothing but a NIGHTMARE with sound in Ubuntu forcing me to go through hell to find the problem at each upgrade. And each upgrade from 8.04 (to 8.10 and now 9.04) have caused me to have to figure out why I get NO SOUND each time. Unfortunately each of the 3 versions caused a different problem so it wasn't as simple as just replicating what I did previously to resolve the issue.
Many people have problems with sound in Linux. The situation is certainly less than ideal. However, on most computers, sound in Linux works flawlessly. If you have problem with sound in Linux, you are part of the exception, rather than the rule.
You could buy a used (aka EBAY, craigs list, apple.com) macbook (which would blow the doors off of the mini) to replace your 5-7 year old powerbook for about $700. It would (or at least should) include the latest iLife bits. You'd be way ahead. Linux is a helluvalot better than OSX for stuff like databases and web servers, but there is no way that video or audio applications (or most any desktop app) are anywhere close. I used linux exclusively on my notebooks from 98-06 and I can tell you about 1000s of hours wasted (although I enjoyed it) getting everything to run. With OSX everything just runs. Plus, using the media apps is a breeze.
Suppose you were an idiot. And suppose you were a member of congress. But then I repeat myself. -- Mark Twain
I wish the article's server hadn't been slashdotted, because I would love to know which professional digital audio adapter he's using, where he got the drivers, and whether he uses jack or not.
Every time a new Ubuntu studio comes out, I install it on a PC workstation in my studio to see if finally I can use Linux for digital music production, and every time I am disappointed by the way Linux talks to my audio gear. In Windows, I can use ASIO or WDM drivers and get professional-quality results, low latency, etc in Reaper. Apple uses SoundDriver for Logic. But Linux? All I've been able to find is jack, and for a professional, it doesn't do jack. There always seems to be problems with my MIDI gear, too, but that's gotten better in the past year.
Still, Reaper, using its ReMote technology allows me to offload certain things on to a Linux box via ethernet, such as rendering and effects processing, and that's a huge help, allowing me to use more real-time effects on more tracks. And, of course, my Linux box is absolutely key for streaming samples and other stored data to my digital audio workstation.
But using Linux as a main machine for music production? Not yet as of February. I plan on reading this article, though, as soon as you slashdotters give the server a breather, to find out what this guy's doing. Maybe it's finally time. I may not yet be ready to give up my Mac Pro and custom-built windows workstation for music production yet, but I look forward to being able to use Linux on a music project, start-to-finish.
You are welcome on my lawn.
...you must be kiddin'!
First of all, Linux is not the guilty one for not providing software for musicians. It is the developers of the software, like Apple, Steinberg, Propellerheads and Native Instruments, to name a few big ones.
Second, without all that Software. And I mean specifically that software, it is literally impossible to create the wanted sound on a Linux platform.
My setup is nearly 100% software (with a set of MIDI devices and a powerful sound card), and includes Cubase, Reason, Reaktor, Absynth, DR-008, and pretty much every Software from Native Instruments. And that is only the base. You also have to add a ton of specific plug-ins. E.g. for reverbs using impulse responses, or very specific filters to create the sound of a vintage synth.
You can not ever possibly recreate this under Linux, without it becoming a main platform for music production, so that those companies port their software. Which of course is a vicious circle.
But if Steinberg alone would port their VST platform Cubase onto Linux (Don't tell me about using it in Wine. I tried it. For real songs with dozens of tracks. It's a total joke. And I don't even mean the latency.), the circle could be broken.
So please stop with your dreamy dreams from wannabe professional musicians telling me how they were able to create a simple four-track audio song with some amateur FX plugged in. Because it has nothing to do with even my semi-professional work.
P.S.: I may sound angrier than I am. In fact I really *really* wish I could help with some big thing, like persuade Steinberg.
Any sufficiently advanced intelligence is indistinguishable from stupidity.
I blogged about it and submitted the patches to the ALSA tree. It should hit mainline eventually (I'm not sure how often they sync up with ALSA).
I'm the editor of CDM and also run our servers. (apparently not terribly well, though I am in the middle of a migration to a new server config -- should've, uh, waited on this story!)
I'd like to get more data on hardware, too, and I'm curious what's been giving you trouble. I regularly see various problems on all three platforms, though I agree Linux is probably the least familiar and needs information dissemination most urgently (at least for music production).
While I'm waiting and restarting Apache (cough), some of the things folks are claiming here seem to be misinformed. That's not necessarily their fault; it illustrates that better documentation is needed, and simply pointing people to audio-centric distros I think is not enough.
For driver support -- RME fills the pro audio gap nicely if you're looking at the high end; they're the ones that are really doing it right. You'll also have good luck with any class-compliant USB audio interface. I'm getting good results out of a Cakewalk SPS-25 (basically equivalent to an Edirol UA-25). FireWire support is greatly improved, and you can check there at ffado.org. Most internal chipsets are also well-supported by ALSA - not a high-end option, true, but it means you can mix something on the road listening to the headphone jack without having to muck about with something like ASIO4ALL on PC.
Software: it's true there isn't much in the way of Linux-*only* software, but not that you don't have choices. Renoise and energyXT now both run natively, Renoise being a huge deal to fans of trackers. And many Windows apps can run better under WINE, with ALSA, WINEASIO, and JACK, than they do on Windows. That's the reason Native Instruments software can run on the MUSE Receptor, specialized hardware that runs Linux and WINE under the hood. It's solid enough that it winds up being preferable for people to buy that hardware over a laptop - yes, even over a Mac laptop. You probably won't get that kind of reliability out of a Linux setup out of the box, really, regardless of distro. But if you can set it up in a way that will be rock-solid, that could be worth the time for people.
I think that's the bottom line: a lot of people would be happy to invest a little extra time and effort to get an open system running. The problem is, they don't know how. The responses here demonstrate that people aren't aware of what some of their choices are, or have had (understandable) frustration because the distros ship out-of-box in a way that doesn't quite work, and there's not much clear documentation to tell you how to fix it.
ALSA isn't perfect, but neither is Core Audio, let alone ASIO. ALSA combined with JACK can be an exceptionally-terrific audio system for these applications.
So, I can make you a deal - I will put more of that information online, *and* fix our servers, too, so you can actually read it. ;)
I just finished recording and producing a jazz album using Project CCRMA hosted on Fedora. The recording through to the final mastering were all done using linux. Having read his article I was surprised to find he hadn't mastered his production using Jamin which, when used in combination with Ardour and Jack, gives the type of control over the production process I've not seen duplicated using a Mac (Windows is not capable at all in this regard). I suppose though that is the workflow he is used to.
The innovation is what it means to the production process. There is no mixdown to a 24bit 44.1Khz stereo track prior to mastering and you can render your tracks through the mastering software into the final tracks and tweak automation artifacts instead of compromising by using equalisation. Sure you still equalise but you end up doing less as you can refer back to the master if there is a problem and fix it there. Plus you have better control over (audio gain) compression to reduce transients and maintain dynamic range in the final product.
The bands that listen to my recording are amazed at the results (well my recording techniques *ahem* do play some part :-) and some asked me if it was done on analogue equipment - which is quite a compliment. The thing is sure, it's not perfect and sometimes frustrating because the your hardware is often pushed to it's limit, you find bugs you have to adjust your work flow around but simply put I don't think the capability *exists* anywhere else.
I've been using it since 2003 and have seen the foundation laid down by Alsa and Jack projects continually refined. Often the criticism is made that 'linux copies this or that' but after comparing it to existing processes it seems to me that audio production under Linux is on the leading edge of technology as the framework for innovation in music production.
My ism, it's full of beliefs.