An Intro To Editing Audio On Linux
W-9z writes "Ars is running a guide to editing audio under Linux that I think is a great read for anyone trying to
find new ways to flex that Linux muscle. There are some outstanding FOSS tools out there. They look at Ardour, Audacity, and SND. The author talks a bit about why Linux is a
superior platform for this kind of work: 'FOSS software is, almost by definition, a work in process. If Ardour doesn't have a feature I need, I can code it myself. With this
possibility, the software no longer defines what I can do -- it's just a point of departure.' It's an interesting companion to the /. discussion of video editing earlier this year."
Wow, I never knew Linux was so good for that kind of thing. In fact, I might just stop using SONAR (Windows) and switch to Linux.
I guess that means that the 1% market share just got a bit bigger.
I usually don't turn to linux for day to day tools, but I have to admit, it is pretty good for editing large audio. Tools are lacking, but its pretty stable doing.
"FOSS software is, almost by definition, a work in process. If Ardour doesn't have a feature I need, I can code it myself."
But, what if you aren't a coder?
On proprietary platforms, eventually you'll run into "you can't do that." On open platforms, you'll run into "you have to learn more to do that."
That applies to so much more than just audio programs.
-Charles
Learning HOW to think is more important than learning WHAT to think.
Unless, of course, you don't know how to code it yourself, either because you don't have the technical know-how or the willingness to invest time investigating and learning how it works.
This is becoming a pet peeve of mine when people espouse the benefits of FOSS; it only applies to tech-geeks. Great, programmers can do things with it that they can't do with closed-source. Now how about everyone else?
An intro to getting your goddamn sound card to work on linux?
It's only superior if you have the ability to code the feature you need. There's a huge assumption there that someone who is skilled at using a DAW is even inclined to code new features for an application. Personally speaking, I lack the skills to approach that, so a superior platform is one that lets me do what I want without having to code the feature. That's not to discount the value of being able to do that, but really, most modern DAW's are extensible in some way or another (be it via VST, or some API). Having said that, Audacity rocks!
look, i love open source software as much as the next man, and it's price really goes with my poor musician ethic, but to be honest, as the man said it's a work in progress. Configuring a number of audio programs to run togehter, such as a drum machine and a synth or sampler, through jack and rosegarden is a royal pain in the arse.And musicians don't want to code new bits to their software, they just want it to work. so for now i'll still keep that windows box that doesn't go anywhere near the net....gotta love reason and acid pro...and keep this freebsd box for the net
My brother owns a recording studio, and Linux wouldn't compete in that arena. For a home studio, these apps + a SB Audigy are fine, but no talented band, producer, editor or mastering engineer will look twice. The midlevel sound cards don't approach the quality and power of the high end (even rotools HD) vehicles.
For me, I want to see Linux drivers adapted for the high end hardware. Windows isn't an issue as most high end studio apps offload the processing to the hardware. The software is just a window to what the hardware is doing in the recording.
If you're just mixing tracks for a garage demo, this software looks great. I paid a fortune 3 years ago for Win32 software that didn't approach this level. I see great things ahead as hardware gets better.
For now, though, the SB cards don't offer the best input quality. I can tell the difference in noise floor, transparency, and soundprint signature. When I've listened to demos, I can pinpoint quality gear versus prosumer gear.
In the end though, a 4track tape is enough if you have talent. Most bands don't.
ProTools is industry standard, period. No FOSS is going to conquer their market share. In fact, outside of the /. crowd, this will remain small. Lack of hardware support for most popular interfaces will doom it so, not to mention Linux's inflexibilities to the average user.
A blog like any other.
I don't know about the author of this article, but I am certainly NOT an audio engineer, so I could not "code it myself". In fact, most end users probably aren't even developers. And even if you are a developer, you will have to spend a good deal of time getting intimate with the architecture and framework of the application. Sure, you can hire somebody to code something up for you, but that's not the same as doing it yourself. If you're going to pay somebody to change something, why not request a feature from the author and give him a "donation" in return?
On the other hand, many audio editing tools have some kind of relatively simple, well-defined plugin architecture, so if you have the skills it is quite possible to write your own plugin (or modify someone else's). Even many closed source solutions have an open plugin architecture, so I don't really see the necessity of having the main application open (though it doesn't hurt). So, in essence, I don't really how Linux is a "superior platform" for audio editing. Yes, it encourages open source software, but a lot of the software is available for Windows (i.e. Audacity, but it doesn't look like the other two have been ported).
The platform shouldn't matter; it's the applications, stupid! Once again, use the right tool for the job. If Audacity on Linux works for you, fine. If CoolEdit on Windows works for you, fine. If something else on another platform gets the job done, more power to you.
"What's insane is the pro proprietary companies charge prices in the four figures just for some of their software alone. Can't be justified when you have the same abilities free."
$1000 is a drop in the bucket for most professional studios whose bread and butter work utilizes these tools. Photoshop is expensive but with the amount I make using teh software, it's nothing. if you're looking to purchase this software to goof off and do some amature stuff, then I can see you having a problem with the price. If you're a professional, these licenses are nothing in the overall scheme of things.
IMO, Ardour is my least favorite but has the brightest future.
I know 2 Pro studios that made the switch from Pro Tools and both were financially unstable. Pro Tools still reigns supreme for me for the moment.
The 4 figures for software is worth it when the $150/hour mastering engineer spends 2 days at the studio and works with what he knows. The 2 studios I know running Ardour have released relatively mediocre sounding albums that had great content. I can tell they didn't have a good engineer handling the mastering.
Remember, $2500/album pays off Pro Tools in 8 weeks. Many bands and engineers are familiar with Pro Tools, which is a huge selling point.
An engineer friend of mine just recorded 80 tracks of audio simultaneously using protools (dual G5 mac)...over an hour solid. It was a large live event with no second chances, and it went without a hitch.
I think one huge advantage of the commercial apps is the associated hardware. The DACs and off board procs do far more than a single workstation could do, and unfortunately open source hardware can't really be free. For big tasks, professional recording is much more than software.
There may be a way to cluster some slave workstations or something to provide the required horsepower, but some time-sensitive situations are going to require that such a system be very, very stable.
Well, the article itself touches on a few of my reasons. Ardour, specifially, is very "Linuxy" in its interface layout and design, reminding me in many ways of the old Dos version of 3D Studio. It definitely looks like a programmer-designed UI, it's very stark and bare-bones, and things are never quite where you expect them to be. It's clearly a Cubase/Logic inspired design and layout, but without the years of fine-tuning those have had to get to their current states. I prefer Ableton's more unorthodox approach anyway, but that's just me
The other is, as always, hardware support. Getting less important now in some ways, for some uses (I use quite a lot of virtual instruments, so not a huge deal for me) the lack of hardware DSP support is a killer. Proprietary developers are to blame here, in fairness, but it's still a problem.
Probably most importantly for me is the real killer, and I suspect the reason most audio folks won't move to Linux for some time to come (and coincidentally the reason so many of them use Apple machines): we don't want the software to get in the way of the creation of music any more than it has to. At the moment, many parts of Linux are unhelpfully complicated, especially to non-technical people.
A final thought, based on the quote from the article repeated in the summary:
Quite apart from ignoring the fact that almost every major audio app can use various forms of plugin, which have relatively easy to obtain SDKs, and that various generic programmable plugins (like MaxDSP) exist for which one can do the same, it ignores maybe the most obvious point of all: not all musicians are programmers.
Game dev and music blog
Link please?
Here is a quote from Jules on Sep 29th, 2005
"Yeah, there's a few things not done in the linux port yet - audio and file choosers are amongst them.
(actually, I think those might be the only major things still missing from the linux port.. sorry if they happen to be the exact things you need!)
Haven't got a timeline for doing them, I just fit things in when I get the time to do it, but they'll happen eventually."
Two major likely reasons:
1) FOSS people tend to be Linux people. Many of them are highly idealistic, hence why they opt to do FOSS. That idealism leads to sometimes a fanatical level of hatred for Windows. That means that they aren't very inclined to port to Windows. However it also usually mean a severe lack of knowledge about Windows. Windows IS different than Linux and unless you cop out and use Cygwin, there's some porting work a head of you to make a Linux app in to a Windows app.
2) Competition. Often, FOSS tools liek this are written because there isn't something else that does what they do. For audio at least, there are tools that do all these do and a whole lot more. They do cost money, but they are out there. It's easy to shine when there's nobody to compete against. Much harder to go up against a polished, well maintained commercial product and look as good.
This is one of those areas where Linux frustrates me the most. I would not use Windows at all if the audio/midi apps for linux were more mature. Ardour for example is great if all you want to do is multitrack audio, but even in this area it does not come close to say Cubase or Sonar. For example Ardour does not feature hitpoint detection, non-destuctive time stretching, audio warping, groove templates, offline per-clip effects, track freezing and on and on. MIDS is coming but who knows how many years that will take. I'd add it, but I'm not a good programmer and dont have the time. The features it does have work great but it still doesnt really compare to the commercial offerings. VST support.. This is a joke. Last time I checked there were three or four different alternatives for linux here, all using wine and all have dead for at least a year.. MIDI? Linux has some good midi apps which still dont have near the features of the windows ones. Some of these, namely Rosegarden and Muse, even have audio track support but these features are so primitive that they are nearly useless and really Ardour is the better choice here.. But someone will then say but Linux has Jack and you can hook together whatever apps you want. Jack is sort of like Rewire on steroids. So you load Qjackctl which is a nice app for connecting Linux audio apps. Ok. So you load up Muse for its midi capabilities, maybe load up some soft-synths in it, maybe the ones you want to are plugins for Muse, but probably not so you load up two or three external soft-synths and route muses midi output to those one at a time, then you hook the output of those soft synths into ardour via jack. So now there are 5 programs loaded, took you 30 minutes to load and connect everything. You make some changes to the patches in the soft-synths, write some midi tracks in muse and then record a bit of it into ardour. Then think gee I'd like to save my song so I can unload all these programs and do something else with my computer. So you save in muse, save in both synths, save your hookups in qjackctl, save your session in ardour, write a little note so you remember everything you need to do to load your song again. This takes you another 30 minutes.. But really whats more likely to happen is: you will hook everything up and one of the crappy soft synths will crash before you have a chance to save everything and take out the other audio apps forcing you to start over or your whole computer will crash because you were using the realtime-lsm patch to make the thing responsive. Or you will close Ardour before disconnecting it from muse and muse will crash. etc etc. There are nice proposals like LASH, formerly LADCCA which would let all Lash compliant apps be saved in their current states and then reloaded that way but most programs dont use LASH. Not to mention the time it takes to get all there programs and a proper kernel compiled and downloaded if you are not using some pre-made solution like CCRMA, Demudi or Studio to go. Many distro have these apps as packages, but something is always out of date. I have been watching Linux audio grow for years and years and really its going to take years more before all of the features I listed above exist in a single app. With Cubase I open one app with synthesis, sampling, Midi and Audio editing under one roof. When Im finished I save and close, done. I am a huge Linux fan, but I really hate Linux audio. Maybe next year.. Ardour really is awesome though..
I do audio professionally and I'm also a programmer. In my home, I have 2 Windows machines, a Linux server, and an iBook. I do use Audacity from time to time because it does a few things better than even the high-priced editors. As I've told many people, Audacity will open damn near anything...I also frequently use Supercollider, which is a stellar synthesis/dsp programming language that runs natively on OSX, but has been ported to Linux and Windows. However, most of the Linux audio projects are not stable enough to get real work done. I try them from time to time, and some things are getting better, but it's just really not there yet. There's nothing that really stacks up to any of the big 3 sequencers or to Pro Tools. That, combined with the fact that it's very difficult to find professional-grade audio cards that even work with Linux currently make it a lackluster platform for doing any sort of serious audio work. You can make write the best audio software, but if I have to use a shitty soundblaster, I'm not even going to consider it...
ZuluPad, the wiki notepad on crack
At the Dutch Electronic Arts Festival (DEAF) I attended a session with Paul Davis, author of Ardour DAW, and he was using RME Multiface.. Hardly a shitty soundblaster, I'd say, although I do think he coded the alsa driver himself.
RME cards are well supported under Linux w/ ALSA and they definitely fall into a superior category...