Am 23.05.2013 15:32, schrieb Len Ovens: > > On Thu, May 23, 2013 12:21 am, Hartmut Noack wrote: >> Am 23.05.2013 06:17, schrieb Len Ovens: > > >>>> It should be easier to disable PA to a near-removed status though.... >>> >>> Unload module-jackdbus-detect: >>> pactl unload-module module-jackdbus-detect >>> >>> PA still takes up memory, but uses almost no cpu without that module. >> >> The CPU-load would be tolerable, the problem is, what PA+dbus do at >> startup. Is there a way to blacklist interfaces? Some command like : "PA >> do not touch that device!"? > > Yes, run pavucontrol, select the last tab (configuration?) select the card > you want PA to leave alone and turn it's "profile" to OFF.
Thanks for the hint, I did not know that. Sadly it looks, like the problem resides deeper in the bowels of dbus: the problem prevails, only KDE spits out "device is not available" messages.... Anyway: thanks again! with every shot in the dark we draw nearer a real solution or as Spock puts it: "Once you have eliminated the impossible, whatever remains, however improbable, must be the truth." ;-) > Counter > intuitively, I turn off the cards Jack is not going to want to use as I > have found that the PA-jack bridge links the two cards. In other words, if > PA uses the internal HDA (mine does not do good low latency due to HW > problems) and Jack is using my USB IF, the problems I would have with the > HDA, show up on the USB. The PA-Jack bridge forces PA to try to do the > same latency as jack. > > I am not sure if that is clear. The thing to remember is that they do > interact when bridged. This is not really a bug any more than the fact > that a trailer will affect the way your car drives. > > -- 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