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

Re: alsa, jack output issue



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

Reply to: