Well, as a generally accepted view of simply writing songs from a
musical perspective, it's considered good practise to write the tune
from beginning to end first, then start work on polishing it. If
you're recording live, that is straight audio recording, then we're
well served in that regard with Ardour, Qtractor, and few others. Once
your recording is done, then it would be a fairly simple matter to
open one of your previously built templates, and assign your ports.
A possible use case:
You've got the guitar out and laid down a track or 2, managed to to
wake up the drummer, and after 78 takes, got something near a well
timed set of drum tracks. The bass player has got back from the
vegetarian food shop, and added his line. So you have say 12 tracks
all recorded, and ready to be polished. There are some good hosts in
Linux for lv2, and ladspa plugins, like ingen, for instance. It can
open templates you've built yourself, so you open the one named
"simple song". Now you have a dedicated plugin host, to which you port
your dozen tracks. (use sends for instance, in each track). Ardour,
for example, is terrific for "quick" recording. Simply "port up" (the
real man's terminology for setting up), and hit the red button. Ardour
remembers what you are ported to, so if you build a little 12 track
"instant" template, for example, with a basic "instant" plugin
template set in Ingen, you simply open Ingen, load the template, then
open Ardour, and load the template, and voila, you're ready to roll.
Like any working environment, setting up is important. Taking the time
to build templates for use pays dividends, as you can open your "core"
plugin set in an app like ingen, then add or subtract per project
according to need. You only need to build templates once, and then you
have an "instant" set to work with. And of course, you can build a lot
of them. In linux we have another massive advantage in multiple
workspaces, and i consider this feature essential when handling lots
of plugins, etc.. I have 8 workspaces, and i fly between them with a
pair of keybindings. So in this use case, i would have Ardour editor
in workspace 1, Ardour mixer in workspace 2, and the plugins in
workspace 3, and possibly 4.
I can say that spreading a working environment out like this is a vast
improvement over trying to handle a sequencer, and what seems like
constantly breeding plugins all in one window, or at a max 2. In my
win days when i wrote for ads, it was a nightmare trying to shift the
focus all the time between so many windows open, even over 2 monitors.
Add to that the image you were trying to write to, and the frustration
builds fairly easily, particularly when you're operating to a tight
time limit. I seemed to spend more time changing GUI focus than i did
No such limitation in Linux, and it works so well, i'd never ever go back.
You'll need to devote some time to setup your DAW like this, and
probably ask a few questions along the way, but for reward in terms of
daily workflow satisfaction, i can say i'm in front by a long way, and
get a LOT more work done for less effort.
Thinking out of the commercially driven box is the key here, but as a
user in a linux audio environment, imho, you're more likely to enjoy
writing and working with music, for a far longer period of time.
On Sun, Dec 20, 2009 at 11:51 AM, Louigi Verona wrote:
Linux-audio-dev mailing list