On Mon, Oct 11, 2010 at 1:36 PM, Ronan Jouchet <span dir="ltr"><<a href="mailto:ronan@jouchet.fr">ronan@jouchet.fr</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><br>
</div>Howdy,<br>
<br>
TToine: yes I added myself to the audio group (that's what "the usual<br>
setup in groups" meant in my extremely imprecise original mail :P )<br>
<br>
Brian, yay! You're right these settings were in<br>
/etc/security/limits.d/audio.conf (thanks to jackd2's dpkg install<br>
procedure, am I right?) but I also added them manually in<br>
/etc/security/limits.conf . Seems to work fine after restoring<br>
limits.conf. And sorry if the following questions have already been<br>
answered, but:<br>
a. is audio.conf new to jack2?<br>
b. why this change?<br>
c. should we leave limits.conf alone now?<br>
<br>
I am using an Edirol FA-66. And while we're at it, now seems a good<br>
time to empty my bag of related questions:<br>
d. I read about changes in the firewire stack (different kinds of<br>
/dev beasts used now). Do they concern all firewire cards, and what is<br>
their impact?<br>
e. is adding the user to the "disk" group still required?<br>
f. under lucid, in order to get jack to start I often had to modprobe<br>
raw1394 && chmod a+rw /dev/raw1394 . Under Maverick I no longer need<br>
this, is this thanks to the new firewire stack, some kind of new auto<br>
setup, or the powerz of keyboard cat playing during a full moon night?<br>
<br>
Thanks everybody for your grrreat help!<br>
<font color="#888888">Ronan<br>
</font><div><div></div><div class="h5"><br clear="all"></div></div></blockquote></div><br>Looks like all your questions got answered. I will say that I use a firewire device myself (a Firepod) and while it does work out of the box in Maverick, I found it did not work well i.e. lots of x-runs. However, when I used Ubuntu Studio Controls to adjust firewire priveleges, it worked much better. I would not use Ubuntu Studio Controls for anything else, though, as it still modifies limits.conf, and as this discussion has pointed out, that is no longer the right file.<br>
-- <br>-Brian David<br>