Re: Audio no longer feasible with vanilla Ubuntu + Studio packages (?)
On Mon, Oct 11, 2010 at 1:36 PM, Ronan Jouchet wrote: > > Howdy, > > 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! > Ronan > > 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. -- -Brian David -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: Audio no longer feasible with vanilla Ubuntu + Studio packages (?)
On 10/11/2010 09:34 PM, Scott Lavender wrote: > I believe the reason for the change is rooted in Debian Bug #507248: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507248 > > And I think the thrust was that someone did not like enabling priorities in > a system wide manner and security vulnerability associated. > > This is also why we should be asked to give the user -rt priority when > installing JACK now. > > ScottL Ah, good to know. I thought it had something to do with sticking every single config file in .d directories that is very common these days. Best, Jeremy -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: Audio no longer feasible with vanilla Ubuntu + Studio packages (?)
On Mon, Oct 11, 2010 at 2:03 PM, Jeremy Jongepier wrote: > On 10/11/2010 08:36 PM, Ronan Jouchet wrote: > > > a. is audio.conf new to jack2? > > No, it's new as of Lucid. The origin of this change is in Debian. > > > b. why this change? > > Ask the Debian packagers. Probably because it complies better with > conventions. Don't ask me which conventions, don't have the faintest clue > ;) > > > Best, > > Jeremy > > I believe the reason for the change is rooted in Debian Bug #507248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507248 And I think the thrust was that someone did not like enabling priorities in a system wide manner and security vulnerability associated. This is also why we should be asked to give the user -rt priority when installing JACK now. ScottL -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: Audio no longer feasible with vanilla Ubuntu + Studio packages (?)
On Mon, Oct 11, 2010 at 3:03 PM, Jeremy Jongepier wrote: > On 10/11/2010 08:36 PM, Ronan Jouchet wrote: > > On Mon, Oct 11, 2010 at 2:09 PM, Brian David 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 > > > > Howdy, > > > > 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? > > No, it's new as of Lucid. The origin of this change is in Debian. > > > b. why this change? > > Ask the Debian packagers. Probably because it complies better with > conventions. Don't ask me which conventions, don't have the faintest clue > ;) > > > c. should we leave limits.conf alone now? > > > > Make your changes in /etc/security/limits.d/audio.conf to prevent any > future problems. > > > 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? > > Yes, concerns all cards. It's a complete rewrite afaik. > > > e. is adding the user to the "disk" group still required? > > No idea, haven't used/tested the new Juju stack yet, afaik this is not > necessary anymore. But then it wasn't required with the old stack > either, you'd better use the audio or video groups for that. > > > 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? > > > > modprobing and chmodding isn't necessary at all when you use the Ubuntu > Studio Controls or add the raw1394 module to your /etc/modules and > create a /etc/udev/rules.d/50-raw-firewire-permissions.rules manually. > > > Thanks everybody for your grrreat help! > > Ronan > > > > Best, > > Jeremy > > -- > Ubuntu-Studio-devel mailing list > Ubuntu-Studio-devel@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel > one thing i do to trouble shoot my firewire interface is run sudo qjackctl. if JACK starts as root, then i know i need to look at the permissions and groups, and go from there. i have had decent luck just adding myself to the audio and video groups, and looking at https://help.ubuntu.com/community/Firewire . i have a presonus firepod. -- MH http://www.myspace.com/mikeholstein http://opensourcemusician.libsyn.com/ -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: Audio no longer feasible with vanilla Ubuntu + Studio packages (?)
On 10/11/2010 08:36 PM, Ronan Jouchet wrote: > On Mon, Oct 11, 2010 at 2:09 PM, Brian David 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 > > Howdy, > > 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? No, it's new as of Lucid. The origin of this change is in Debian. > b. why this change? Ask the Debian packagers. Probably because it complies better with conventions. Don't ask me which conventions, don't have the faintest clue ;) > c. should we leave limits.conf alone now? > Make your changes in /etc/security/limits.d/audio.conf to prevent any future problems. > 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? Yes, concerns all cards. It's a complete rewrite afaik. > e. is adding the user to the "disk" group still required? No idea, haven't used/tested the new Juju stack yet, afaik this is not necessary anymore. But then it wasn't required with the old stack either, you'd better use the audio or video groups for that. > 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? > modprobing and chmodding isn't necessary at all when you use the Ubuntu Studio Controls or add the raw1394 module to your /etc/modules and create a /etc/udev/rules.d/50-raw-firewire-permissions.rules manually. > Thanks everybody for your grrreat help! > Ronan > Best, Jeremy -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: Audio no longer feasible with vanilla Ubuntu + Studio packages (?)
On Mon, Oct 11, 2010 at 2:09 PM, Brian David 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 Howdy, 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! Ronan -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: Audio no longer feasible with vanilla Ubuntu + Studio packages (?)
On Sat, Oct 9, 2010 at 2:31 PM, Ronan Jouchet wrote: > On 10/08/2010 12:14 AM, Brian David wrote: > > Hi Brian, > > Yes I tried disabling NetworkManager (by unchecking nm in the Startup > options, completely disabling it at logon) > I also tried disabling compiz, it didn't help. > > Anything else I should try? Thanks! > > 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 -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: Audio no longer feasible with vanilla Ubuntu + Studio packages (?)
Le 09/10/2010 21:31, Ronan Jouchet a écrit : > > Anything else I should try? Thanks! > > Did you had your username to "audio" group ? Toine -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: Audio no longer feasible with vanilla Ubuntu + Studio packages (?)
On 10/08/2010 12:14 AM, Brian David wrote: > On Thu, Oct 7, 2010 at 10:38 PM, Ronan Jouchet > > > > - Studio "installed" from ubuntu-desktop iso + ubuntustudio-audio > > metapackage is a disaster. Mountains of xruns even when doubling the > > latencies reached with no xruns on a studio install. While this has > > always led to a non-optimal result, it used to work and was good > enough > > for many (like ttoine and I), with the advantage to stay close from a > > standard ubuntu install. > > Have you tried disabling Network Manager applet while running audio (by > right-clicking on the app and turning of networking)? You can then turn > it back on once you are finished recording. If that works, it would > mean you would not be able to have your Internet connection while > running JACK. > > I have in the past had no problems with Network Manager on one version > of Ubuntu, only to find that it caused a lot of trouble on the next release. > -- > -Brian David Hi Brian, Yes I tried disabling NetworkManager (by unchecking nm in the Startup options, completely disabling it at logon) I also tried disabling compiz, it didn't help. Anything else I should try? Thanks! -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: Audio no longer feasible with vanilla Ubuntu + Studio packages (?)
On Thu, Oct 7, 2010 at 10:38 PM, Ronan Jouchet wrote: > I forgot to mention I used the -lowlatency in both cases. > > On 10/07/2010 11:36 PM, Ronan Jouchet wrote: > > Hi, > > > > Today I did some ISO testing and here are the results: > > > > - Studio installed from ubuntustudio-alternate iso works fine. > > > > - Studio "installed" from ubuntu-desktop iso + ubuntustudio-audio > > metapackage is a disaster. Mountains of xruns even when doubling the > > latencies reached with no xruns on a studio install. While this has > > always led to a non-optimal result, it used to work and was good enough > > for many (like ttoine and I), with the advantage to stay close from a > > standard ubuntu install. > > Note: I did the usual setup in groups and limits.conf. > > > > Did I miss something or did something really change a lot between 10.04 > > and 10.10, making ubuntu+ubustu-metapackages a non-option? > > I like Ubuntu's package selection! I like the new font and desktop > > polish! I like having a standard install! I like network-manager even if > > it means losing 1ms latency! > > > > Thanks for your help :) > > > > -- ronj - http://ronj.bandcamp.com > > Have you tried disabling Network Manager applet while running audio (by right-clicking on the app and turning of networking)? You can then turn it back on once you are finished recording. If that works, it would mean you would not be able to have your Internet connection while running JACK. I have in the past had no problems with Network Manager on one version of Ubuntu, only to find that it caused a lot of trouble on the next release. -- -Brian David -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: Audio no longer feasible with vanilla Ubuntu + Studio packages (?)
I forgot to mention I used the -lowlatency in both cases. On 10/07/2010 11:36 PM, Ronan Jouchet wrote: > Hi, > > Today I did some ISO testing and here are the results: > > - Studio installed from ubuntustudio-alternate iso works fine. > > - Studio "installed" from ubuntu-desktop iso + ubuntustudio-audio > metapackage is a disaster. Mountains of xruns even when doubling the > latencies reached with no xruns on a studio install. While this has > always led to a non-optimal result, it used to work and was good enough > for many (like ttoine and I), with the advantage to stay close from a > standard ubuntu install. > Note: I did the usual setup in groups and limits.conf. > > Did I miss something or did something really change a lot between 10.04 > and 10.10, making ubuntu+ubustu-metapackages a non-option? > I like Ubuntu's package selection! I like the new font and desktop > polish! I like having a standard install! I like network-manager even if > it means losing 1ms latency! > > Thanks for your help :) > > -- ronj - http://ronj.bandcamp.com -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Audio no longer feasible with vanilla Ubuntu + Studio packages (?)
Hi, Today I did some ISO testing and here are the results: - Studio installed from ubuntustudio-alternate iso works fine. - Studio "installed" from ubuntu-desktop iso + ubuntustudio-audio metapackage is a disaster. Mountains of xruns even when doubling the latencies reached with no xruns on a studio install. While this has always led to a non-optimal result, it used to work and was good enough for many (like ttoine and I), with the advantage to stay close from a standard ubuntu install. Note: I did the usual setup in groups and limits.conf. Did I miss something or did something really change a lot between 10.04 and 10.10, making ubuntu+ubustu-metapackages a non-option? I like Ubuntu's package selection! I like the new font and desktop polish! I like having a standard install! I like network-manager even if it means losing 1ms latency! Thanks for your help :) -- ronj - http://ronj.bandcamp.com -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
