Linked by Thom Holwerda on Fri 22nd Jul 2005 19:05 UTC, submitted by Jono Bacon
Linux This article discusses audio production on Linux. The author identifies two problems: integration and usability. "I am convinced the the problems discussed here have readily available solutions, but I think opening some dialog with the providers of different parts of the stack needs to happen to allow the solution to develop."
Permalink for comment 8105
To read all comments associated with this story, please click here.
Has he even tried jack?
by Ringheims Auto on Sat 23rd Jul 2005 16:30 UTC
Ringheims Auto
Member since:
2005-07-23

The integration issue is proportionate throughout the entire system. If I plug in a USB sound card, I want all of my applications to make use of it.

Doesn't this already happen as long as the card is supported?

but if you have a complex card with 10 ins and 10 outs and multiple recording modes, you need an application to manage this.

I think exactly this is handled very good in jack. See to the right of this screenshot, there's a full patchbay:
http://ardour.org/img/main-screenshot-big.png

You can certainly control levels with the ALSA mixer, but it will not allow you to deal with the many other options for the card.

This of course depends on how well the card is supported by alsa. The ones who are can make for a very nice recording system afaik.

As with setting up RT-kernel, jack and all, I recommend one of the pre-configured distros like planet ccrma.

Each of these modes of practise can be reasonably implemented in sensible defaults throughout the entire application. This not only applies to effects, but to other areas. Some ideas: [his ideas]

These ideas are pretty good.

As for "integration" I don't know, to me it seems he hasn't really used GNU/Linux THAT much for audio, cause there's really just jack to worry about, and once you've got that in tune the rest is really as straightforward as any system. Jack is also analogue and simple once you discover what it is and can do.

He mentions Cubase, and that's more of an application designed to emulate hardware than taking advantage of the computer as such. That might be why he's doubtful, cause this is not the case for jack and it's client apps. But that doesn't mean it's harder. Me I learned most of my audioknowledge via the computer, and in many cases I find Cubase, Nuendo and such harder to use than jack/etc because of this.

If I can't use it, how is someone with no knowledge of audio recording supposed to use it?

Seriously, if you can't use Ardour I doubt you can consider yourself competent of judging these tools. Ardour operates very much exactly as other similiar apps. I suspect he's looking more for nice graphics then actually where buttons are located, streamline'ism etc.

It's just that I'm using Nuendo nowadays because of an assignement, and many times problems arises where the solution would be pretty easy to solve with Ardour/jack because of it's concept and design. Nuendo might be easier at first, but once you get to a realistic session it might come short and you have to make unclean solutions to solve them.

I agree with him on having more good presets/templates and having things more ready setup. There should also absolutely have been some kind of session-saving system for all jack-apps simultaneously, so that if you use fx seq24, hydrogen and specimen through jack, you could save all of them in one go.

Reply Score: 1