Making Studio work with more than one DE
zettberlin at linuxuse.de
Thu May 23 07:21:47 UTC 2013
Am 23.05.2013 06:17, schrieb Len Ovens:
> On Wed, May 22, 2013 3:52 pm, Hartmut Noack wrote:
>>>> For what kind of professional audio, graphic, photographers and video
>>>> creation tool is pulseaudio useful ;)?
>>> Broadcast. It is good for remote content transport as suggested by the
>>> EBU. They do not talk about pulseaudio specifically, but the methods
>>> do suggest can at this time only be done that way.
>>> Pulseaudio is also good for use with client show and tell... the client
>>> comes in and says, "I saw this thing on U tube..." I understand you have
>>> had trouble with PA... Not that long ago it did have many problems. But
>>> this time, I would say that a PA->jack bridge is easier to set up and
>>> than ALSA loop backs. Also many of the MP3 players or CD playing SW do
>>> play well with Jack. (I don't know any)
>> That is my experience too. Once jack is started and the
>> pulse-jack-bridge runs, all audio-trouble is gone. Any sane
>> audio-application supports either Jack or PA automatically. And I cannot
>> see, that the PA-bridge increases the rate of xruns(as of now I have
>> zero of them while experimenting with Guitarix and Qtractor and watching
>> YT-videos as well (*videos *with* audio that is...).
>> 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!"?
More information about the Ubuntu-Studio-devel