Re: debian wheezy vs pulseaudio vs jackdbus

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, October 30, 2012 4:51 pm, Patrick Shirkey wrote:
>
> On Tue, October 30, 2012 4:26 pm, Raffaele Morelli wrote:
>> 2012/10/30 Patrick Shirkey <pshirkey@xxxxxxxxxxxxxxxxx>
>>
>>>
>>> On Tue, October 30, 2012 10:11 am, Len Ovens wrote:
>>> >
>>> > On Mon, October 29, 2012 2:45 pm, Patrick Shirkey wrote:
>>> >> On Tue, October 30, 2012 8:35 am, Patrick Shirkey wrote:
>>> >>> Hi,
>>> >>>
>>> >>> Does anyone know whats going on with pulseaudio-module-jackdbus in
>>> >>> Debian
>>> >>> Wheezy?
>>> >>>
>>> >>> On my system the jackdbus module doesn't exist in the repos and the
>>> >>> result
>>> >>> is that pulseaudio doesn't play nice with jack.
>>> >>>
>>> >>> I can see that jackd2 was compiled with dbus support so not sure
>>> what's
>>> >>> going on with the missing pulse module.
>>> >>>
>>> >>
>>> >> I can see with pacmd list-modules that module-jackdbus-connect is
>>> loaded
>>> >> so the module must be compiled into pulse directly.
>>> >>
>>> >> So any thoughts on why the module is not kicking in?
>>> >
>>> > On ubuntu (which normally uses debian src packages), The module name
>>> is
>>> > module-jackdbus-detect. I don't think I have seen a module called
>>> > module-jackdbus-connect even on the pulse site.
>>> >
>>> http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modules#JACK_Connectivity
>>> >
>>>
>>> You got the gist...
>>>
>>> > Even if jackd comes with dbus support, it can be started without. so
>>> use
>>> > ps x or similar to check that the running app is jackdbus and not
>>> jackd.
>>>
>>> There is no jackdbus on debian wheezy, just "jackd" or "jackd2".
>>
>>
>> jackdbus is in debian wheezy and it comes with jackd2 package.
>>
>> http://packages.debian.org/search?suite=wheezy&arch=any&mode=path&searchon=contents&keywords=jackdbus
>>
>
> You're correct. When I looked yesterday I had jackd and jackd2. Today I
> have jackd and jackdbus instead.
>
> No wonder people get confused about how to get this stuff working.
>
> What possible reason is there to have jackd and jackd2 *or* jackd and
> jackdbus ?
>
> The former must be for jack1 package and the later for the jack2 package
> but why would there even be a jackd2 option for the jack1 package? It's
> completely redundant.
>
> And why isn't a jackd2 option installed with the jack2 package?
>

So, If I tell jackqtl to use jackdbus I get a message saying:

----
jackdbus should be auto-executed by D-Bus message bus daemon.
If you want to run it manually anyway, specify "auto" as only parameter
----

The obvious question is where do you specify "auto" as the only parameter?
I tried adding it to qjackctl but it doesn't work there.

This process was being worked on at least three years ago. What happened?
Did everyone just get bored of testing stuff or something?




--
Patrick Shirkey
Boost Hardware Ltd
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user


[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux