Audio no longer feasible with vanilla Ubuntu + Studio packages (?)

Ronan Jouchet ronan at
Mon Oct 11 19:36:57 BST 2010

On Mon, Oct 11, 2010 at 2:09 PM, Brian David <beejunk at> wrote:
> Also, you should not be using limits.conf anymore.  JACK will create
> /etc/security/limits.d/audio.conf, and that is the one that should be used
> to adjust settings.  I think it might cause trouble if these settings are
> listed in both limits.conf and audio.conf
> What kind of interface are you using?
> -- Brian David


TToine: yes I added myself to the audio group (that's what "the usual
setup in groups" meant in my extremely imprecise original mail :P )

Brian, yay! You're right these settings were in
/etc/security/limits.d/audio.conf (thanks to jackd2's dpkg install
procedure, am I right?) but I also added them manually in
/etc/security/limits.conf . Seems to work fine after restoring
limits.conf. And sorry if the following questions have already been
answered, but:
 a. is audio.conf new to jack2?
 b. why this change?
 c. should we leave limits.conf alone now?

I am using an Edirol FA-66. And while we're at it, now seems a good
time to empty my bag of related questions:
 d. I read about changes in the firewire stack (different kinds of
/dev beasts used now). Do they concern all firewire cards, and what is
their impact?
 e. is adding the user to the "disk" group still required?
 f. under lucid, in order to get jack to start I often had to modprobe
raw1394 && chmod a+rw /dev/raw1394 . Under Maverick I no longer need
this, is this thanks to the new firewire stack, some kind of new auto
setup, or the powerz of keyboard cat playing during a full moon night?

Thanks everybody for your grrreat help!

More information about the Ubuntu-Studio-devel mailing list