User: Password:
|
|
Subscribe / Log in / New account

Why is JACK difficult to setup?

Why is JACK difficult to setup?

Posted Jun 24, 2005 8:11 UTC (Fri) by pkolloch (subscriber, #21709)
Parent article: 64 Studio - creative and native

The author mentions that JACK adoption is hindered by its complexity. That
strikes me as odd. Is the general use case (just playing sound files and
mixing concurrent sound streams, just like esd and arts do) so hard to
setup? What makes JACK that complicated?


(Log in to post comments)

Why is JACK difficult to setup?

Posted Jun 24, 2005 8:41 UTC (Fri) by dhj (guest, #4655) [Link]

I don't think JACK is difficult to use once you know how it works, but
from a general user point of view it appears complicated - take a look at
the qjackctl settings dialogue.

Jack will rarely "just work" with a standard distribution - a low-latency
patched kernel is practically essential - and the flexibility available
with routing adds additional complexity. It also requires a fixed sample
rate to be set on the interface. In a non-music-creation context, you
might have a Flash game with a 22KHz soundtrack and a CD playing at
44.1KHz simultaneously, for example.

For these reasons, I don't think any of the mainstream distributions
support Jack as their primary sound server. Arguably, Jack is overkill for
a general-purpose desktop where the only need for a sound server is to
connect multiple stereo streams (of various sample rates) to a single
sound chipset. But for a distribution like 64 Studio, it's a critical
component.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds