Re: [Jack-Devel] Multi-user desktop integration

On Sun, Nov 2, 2014 at 11:59 AM, Cédric Schieli <[hidden]> wrote:

>
> 3. hack Jack to allow bypassing the whole thing
> I've chosen 3, the formers do no really reserve anything anyway as the
> buses are not connected to each other. By passing the
> JACK_NO_AUDIO_RESERVATION environment variable I can now disable the
> audio_acquire/audio_release callbacks.
>

basically, jack1 :)


>
> The first solution that comes to mind is to make this system-wide server
> run in promiscuous mode, so I've exported JACK_PROMISCUOUS_SERVER globally
> (in /etc/environment). Problem: for this to work, the server and every
> single Jack application (including the pulse-jack bridge) must be running
> with a 0000 umask, which sounds a bit scary to me.
>

should not be the case. should be fixed if it is the case.


> So I've hacked a little enhancement to the promiscuous mode which makes it
> possible to pass the name or gid of a group through the
> JACK_PROMISCUOUS_SERVER variable. In that case, the sockets, shared memory
> segments and semaphores have their permissions tightened so only members of
> that group will get access to them. More importantly, it is not needed
> anymore to fiddle with the umask, even if no group is given.
>

sounds like an improvement.


> With that in place, and after having changed the default PulseAudio
> configuration (/etc/pulse/default.pa) to statically load the pulse-jack
> bridge, each user session has its shiny desktop sounds working, and every
> user is able to run Jack applications whenever they want.
>

multi-user JACK is not something i'm particularly interested in but perhaps
other people will feel differently.

i'm also fairly sure that the ALSA loopback device is a better method for
Pulse<=>JACK interaction than the pulse JACK sink/sources.

1414948007.23198_0.ltw:2, <CAFa_cK=vzNt3Q4=CvpHf=CkZ4WB6E3SU6KZx493c=aEQoEBtog at mail dot gmail dot com>