Re: alsa, jack output issue
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"
... ;)?
Again, regarding to Jack2 there is a small chance that it's related to
D-Bus and regarding to the issue, the thread is about, he needs to
switch the CPU freq scaling to performance, since ondemand is asking for
trouble and I suspect, that the latency is much to small. Besides it
would be better to use "period/buffer: 3", assumed the card is able to
do it, but the period/buffer isn't related to any of the issues, it's
just better to use 2 when ever possible. If he wouldn't be in the group
audio, he couldn't start Jack1 in RT mode.
Regards,
Ralf
Reply to: