Re: alsa, jack output issue

[Ralf Mardorf <ralf.mardorf@alice-dsl.net>]

On Wed, 2013-01-30 at 11:24 +0100, Ralf Mardorf wrote:
> On Wed, 2013-01-30 at 11:10 +0100, Raffaele Morelli wrote:
> > 2013/1/30 Ralf Mardorf <ralf.mardorf@alice-dsl.net>
> >         On Wed, 2013-01-30 at 07:31 +0100, Raffaele Morelli wrote:
> >         >
> >         > 2013/1/29 dAgeCKo <dagecko@free.fr>
> >         >         Le 29/01/2013 19:48, Ralf Mardorf a écrit :
> >         >
> >         >                 On Tue, 29 Jan 2013 19:37:38 +0100, dAgeCKo
> >         >                 <dagecko@free.fr> wrote:
> >         >                         Yes jack1 because jack2 never wants
> >         to start
> >         >                         for some reasons.
> >         >
> >         >                 If you started jack2 by QjackCtl, than there
> >         might be
> >         >                 a dbus issue.
> >         >                 QjackCtl > Setup... > Misc > [ ] Enable
> >         D-Bus
> >         >                 interface
> >         >                 If I start jack2 by QjackCtl, I unchek, aka
> >         disable
> >         >                 D-Bus interface.
> >         >
> >         >
> >         >         If I remember well, the error message was something
> >         about that
> >         >         the soundcard was already in use.
> >         >         I will try this. But do you think this could solve
> >         the
> >         >         problem ?
> >         >
> >         >
> >         > It's a permission problem then, post the output of pstree
> >         before and
> >         > after jackd refuses to start.
> >         > Are you in the audio group?
> >         
> >         If this would be the issue, then why can he start Jack1
> >         with ...
> >         
> >         "driver: alsa
> >         RT with default priority
> >         samples/period: 128
> >         sampling freq: 96000
> >         period/buffer: 3
> >         max numb of ports: 128
> >         count-down: 500
> >         dither: none
> >         audio: duplex
> >         input device: hw:0
> >         output device: hw:0
> >         late start: 2 seconds"
> >         
> >         ... ;)?
> > 
> > 
> > simple, just because the other app/daemon takes control over hw:0
> > Ralf you are also on LAU mailing list, you should have learned
> > something there about ;-)
> > 
> > 
> > -r
> 
> I'm confused. It's possible to start Jack1 with real-time priority, when
> another app captured the device, even, when the user isn't in the group
> audio?  I experienced that when an app captures the device, that Jack
> can't be started anymore, but the OP can run Jack1. Can you send a link,
> where such a situation ever was a thread at LAU?
> 
> Don't get me wrong, it might be possible that this could happen, I
> simply missed, that this ever happened.
> 
> Regards,
> Ralf

It might be possible that Jack2 was installed, when he wasn't in the
group audio, we never will know, but now he can start Jack1 with
real-time, so I've doubts. IMO he is in the group audio.