11 Nov
2005
11 Nov
'05
7:31 a.m.
Hi everyone,
Peter Lutek escribió:
hmm... seems to make it go away, but is that just because the error
message is no longer being echoed to the message window? when i start
qjackctl from a terminal window, i don't any messages in the terminal
about jack status anyway, so it's hard to tell.
-p
If this can be usefull,here is the window messages output of
qjackctl before an after change the "Capture standard output" option,and
the shell output of jackd with the same config that qjackctl.
*Before*
11:36:08.520 Patchbay deactivated.
11:36:08.570 Statistics reset.
11:36:08.687 MIDI connection graph change.
11:36:08.801 MIDI connection change.
11:36:09.004 MIDI connection change.
11:36:46.241 Startup script...
11:36:46.241 artsshell -q terminate
sh: artsshell: command not found
11:36:46.461 Startup script terminated with exit status=32512.
11:36:46.461 JACK is starting...
11:36:46.462 /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p256 -n2
11:36:46.466 JACK was started with PID=3592 (0xe08).
cannot write to jackstart sync pipe 4 (Bad file descriptor)
jackd: wait for startup process exit failed
jackd 0.100.0
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:0|hw:0|256|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 256 frames, buffer = 2 periods
nperiods = 2 for capture
nperiods = 2 for playback
11:36:48.665 Server configuration saved to "/home/supertux/.jackdrc".
11:36:48.668 Statistics reset.
11:36:48.690 Client activated.
11:36:48.693 Audio connection change.
11:36:48.701 Audio connection graph change.
*
After *
11:34:32.194 Patchbay deactivated.
11:34:32.245 Statistics reset.
11:34:32.360 MIDI connection graph change.
11:34:32.475 MIDI connection change.
11:34:32.678 MIDI connection change.
11:34:46.166 Startup script...
11:34:46.166 artsshell -q terminate
sh: artsshell: command not found
11:34:46.384 Startup script terminated with exit status=32512.
11:34:46.384 JACK is starting...
11:34:46.385 /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p256 -n2
11:34:46.407 JACK was started with PID=3566 (0xdee).
11:34:48.538 Server configuration saved to "/home/supertux/.jackdrc".
11:34:48.539 Statistics reset.
11:34:48.557 Client activated.
11:34:48.558 Audio connection change.
11:34:48.568 Audio connection graph change
*Shell*
supertux@sid:~$ /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p256 -n2
jackd 0.100.0
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:0|hw:0|256|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 256 frames, buffer = 2 periods
nperiods = 2 for capture
nperiods = 2 for playback
I have this working on a Pentium IV 2.6 ,1gb ddr,terratec dmx6 fire
(ice1712) running Debian Sid and the A/Demudi kernel 2.6.13-1-multimedia.
Still learning how to compile my own :p .
Saludos
Cheers
-- Carlos.
Rui Nuno Capela wrote:
> Peter Lutek wrote:
>
>> Michael T D Nelson wrote:
>>
>>> Paul Davis wrote:
>>>
>>>> On Thu, 2005-11-10 at 14:50 +0000, Michael T D Nelson wrote:
>>>>
>>>>> Paul Davis wrote:
>>>>
>>>>
>>>>
>>>>
>>>
>>>>>> go to the qjackctl setup dialog and make sure that the command
>>>>>> to start
>>>>>> jack is "jackd" and not "jackstart".
"jackstart" is purely for 2.4-
>>>>>> kernel based systems and should not be used on a 2.6-kernel
based
>>>>>> system.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Thanks for the prompt reply, but it's set to "jackd"
already.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> well then something is very confused. your error messages included a
>>>> line about not being able to write to the jackstart sync pipe.
>>>>
>>>> did you install jackd as a normal CCRMA package?
>>>
>>>
>>>
>>>
>>>
>>> Yep. And it was working fine until a couple of weeks ago. I don't
>>> think I have done anything untoward.
>>>
>>> The only software which I compile from source is completely
>>> unrelated to audio (things like OpenVPN, mainly for work).
>>>
>>> I have just noticed a recent thread on this list (started by Carlos
>>> Pino) with a very similar sounding problem.
>>>
>> yes... i was in on that thread. i get the jackstart sync pipe error
>> message when starting jackd with qjackctl, however it does start
>> fine despite the error.
>
The same for me.
when starting jackd with the same parameters, but from
the
commandline, i do not get the jackstart sync pipe error message.
perhaps it's a qjackctl bug?
-p
Have you tried whether switching off standard output capture on
qjackctl/setup/options makes any difference on that "jackstart sync
pipe" issue?