On Wed, December 12, 2012 10:36 pm, Paul Davis wrote: > no. JACK by default only allows connections from clients started by the > same UID that started the server. > I ran into the same problem the other day when trying to connect to a running jack session from a different user on a different DISPLAY (terminal session) on the same host. I looked at using netjack for the connection but neither the master or the slave could see each other which could just be user error on my part. Just checking now and it seems that "promiscuous" mode was intended for this use case. Hard to find an example for this online though. Google doesn't through up anything obvious and the FAQ doesn't have anything either. Can't see anything in the MAN page either. > > On Wed, Dec 12, 2012 at 3:09 AM, david <gnome@xxxxxxxxxxxxx> wrote: > >> On 12/11/2012 02:11 PM, Harry van Haaren wrote: >> >>> On Wed, Dec 12, 2012 at 12:05 AM, Grant <emailgrant@xxxxxxxxx >>> <mailto:emailgrant@xxxxxxxxx>> wrote: >>> >>> Is this something that might be integrated into a jack release? >>> Would it be worth filing a bug? >>> >>> >>> I'm afraid I don't understand exactly what you're asking. >>> <jokes> And no I don't see it being integrated </jokes> >>> >>> Running JACK as a system wide daemon has downsides, and is a pretty >>> niche use case. I don't >>> see it becoming the standard as GStreamer / Phonon / PulseAudio and a >>> variety of other frameworks >>> already try to run a daemonized audio server. And I remove all of them >>> from my installs when I can :) >>> >>> Since its only advanced users that will ever want to do this, I think >>> the config files fix above is fine. >>> My two cents, -Harry >>> >> >> Well, if you automatically have every user a member of the audio group, >> can't they all use JACK? >> -- Patrick Shirkey Boost Hardware Ltd _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
