10 Nov
2005
10 Nov
'05
10:17 a.m.
Hi all,
I wondered if anyone could help me. I'm having problems starting JACK
from Qjackctl. I'm running a current PlanetCCRMA FC3 setup, and my
soundcard is an RME DIGI9636.
I have appended the output which I get in Qjackctl's "messages". Does
anyone have any ideas?
Thanks
Michael Nelson
--
14:01:12.797 Patchbay deactivated.
14:01:13.655 Statistics reset.
14:01:13.801 MIDI connection graph change.
14:01:14.134 MIDI connection change.
14:01:14.135 MIDI connection graph change.
14:12:44.803 Startup script...
14:12:44.803 artsshell -q terminate
14:12:45.267 Startup script terminated with exit status=256.
14:12:45.327 JACK is starting...
14:12:45.328 /usr/bin/jackd -v -R -dalsa -dhw:1,0 -r48000 -p512 -n2
14:12:45.338 JACK was started with PID=20739 (0x5103).
cannot write to jackstart sync pipe 4 (Bad file descriptor)
jackd: wait for startup process exit failed
getting driver descriptor from /usr/lib/jack/jack_oss.so
getting driver descriptor from /usr/lib/jack/jack_dummy.so
getting driver descriptor from /usr/lib/jack/jack_alsa.so
jackd 0.99.36
Copyright 2001-2003 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.
server `default' registered
cannot lock down memory for jackd (Cannot allocate memory)
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:1,0|hw:1,0|512|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:1
configuring for 48000Hz, period = 512 frames, buffer = 2 periods
nperiods = 2 for capture
nperiods = 2 for playback
registered builtin port type 32 bit float mono audio
required capabilities not available
capabilities: =
new client: alsa_pcm, id = 1 type 1 @ 0x805aa68 fd = -1
new buffer size 512
JACK: unable to mlock() port buffers: Cannot allocate memory
registered port alsa_pcm:capture_1, offset = 2048
registered port alsa_pcm:capture_2, offset = 4096
registered port alsa_pcm:capture_3, offset = 6144
registered port alsa_pcm:capture_4, offset = 8192
registered port alsa_pcm:capture_5, offset = 10240
registered port alsa_pcm:capture_6, offset = 12288
registered port alsa_pcm:capture_7, offset = 14336
registered port alsa_pcm:capture_8, offset = 16384
registered port alsa_pcm:capture_9, offset = 18432
registered port alsa_pcm:capture_10, offset = 20480
registered port alsa_pcm:capture_11, offset = 22528
registered port alsa_pcm:capture_12, offset = 24576
registered port alsa_pcm:capture_13, offset = 26624
registered port alsa_pcm:capture_14, offset = 28672
registered port alsa_pcm:capture_15, offset = 30720
registered port alsa_pcm:capture_16, offset = 32768
registered port alsa_pcm:capture_17, offset = 34816
registered port alsa_pcm:capture_18, offset = 36864
registered port alsa_pcm:playback_1, offset = 0
registered port alsa_pcm:playback_2, offset = 0
registered port alsa_pcm:playback_3, offset = 0
registered port alsa_pcm:playback_4, offset = 0
registered port alsa_pcm:playback_5, offset = 0
registered port alsa_pcm:playback_6, offset = 0
registered port alsa_pcm:playback_7, offset = 0
registered port alsa_pcm:playback_8, offset = 0
registered port alsa_pcm:playback_9, offset = 0
registered port alsa_pcm:playback_10, offset = 0
registered port alsa_pcm:playback_11, offset = 0
registered port alsa_pcm:playback_12, offset = 0
registered port alsa_pcm:playback_13, offset = 0
registered port alsa_pcm:playback_14, offset = 0
registered port alsa_pcm:playback_15, offset = 0
registered port alsa_pcm:playback_16, offset = 0
registered port alsa_pcm:playback_17, offset = 0
registered port alsa_pcm:playback_18, offset = 0
++ jack_rechain_graph():
client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
jack_create_thread: error -1 switching current thread to rt for
inheritance: Unknown error 4294967295
cannot start watchdog thread
cannot load driver module alsa
starting server engine shutdown
14:12:47.397 Could not connect to JACK server as client.
could not attach as JACK client (server has exited)
stopping driver
14:12:47.710 JACK was stopped successfully.
--
10 Nov
10 Nov
10:38 a.m.
On Thu, 2005-11-10 at 14:17 +0000, Michael T D Nelson wrote:
Hi all,
I wondered if anyone could help me. I'm having problems starting JACK
from Qjackctl. I'm running a current PlanetCCRMA FC3 setup, and my
soundcard is an RME DIGI9636.
I have appended the output which I get in Qjackctl's "messages". Does
anyone have any ideas?
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.
--p
10:50 a.m.
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.
It was working fine until a couple of weeks ago, when this started to
happen. I would have posted sooner, but I've been pretty busy.
Thanks
Michael
11:22 a.m.
On Thu, 2005-11-10 at 14:50 +0000, Michael T D Nelson wrote:
Paul Davis wrote:
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?
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.
11:58 a.m.
Paul Davis wrote:
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.
No solution yet, though...
Thanks,
Michael
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. 
1:03 p.m.
Michael T D Nelson wrote:
Paul Davis wrote:
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. 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
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. 
1:31 p.m.
Peter Lutek wrote:
Michael T D Nelson wrote:
Have you tried whether switching off standard output capture on
qjackctl/setup/options makes any difference on that "jackstart sync
pipe" issue?
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
Paul Davis wrote:
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. 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 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?
2:26 p.m.
Rui Nuno Capela wrote:
Have you tried whether switching off standard output
capture on
qjackctl/setup/options makes any difference on that "jackstart sync
pipe" issue?
I have now! :o)
But no, it doesn't make a difference. All that happens now is that JACK
tries to start, and then stops, without the messages between.
As I mentioned elsewhere in this thread, turning off the real-time
option allows JACK to start. But I am seeing a lot of XRUNs, which I
didn't see before. Previously, JACK would run RT-enabled, with only
occasional XRUNs.
My machine is a P3 700MHz box, with over 600Mb of RAM and an RME
DIGI9636. It is running an up-to-date PlanetCCRMA FC3 distribution.
I believe I am using fairly conservative settings for JACK:
/usr/bin/jackd -v -R -dalsa -dhw:1,0 -r48000 -p512 -n2
Regards
Michael
2:52 p.m.
On Thu, 2005-11-10 at 18:26 +0000, Michael T D Nelson wrote:
Rui Nuno Capela wrote:
i just remembered something.
this has happened to me twice so far. something in some package update
(i don't know which package) can mess up the /etc/modules.conf file. the
result is that the required kernel module for realtime-lsm does not
load. i had to go in to the file with emacs, delete the "realtime" line
and reenter it by hand (it ends up with binary characters present in the
line, invisible to the naked eye).
i discovered this by looking at /var/log/messages, and also by noting
that "realtime" doesn't show up in lsmod's output.
i wish i could spare the time to find out which package cause(s|d) this,
but i can't.
--p
Have you tried whether switching off standard
output capture on
qjackctl/setup/options makes any difference on that "jackstart sync
pipe" issue?
I have now! :o)
But no, it doesn't make a difference. All that happens now is that JACK
tries to start, and then stops, without the messages between.
3:08 p.m.
Michael T D Nelson wrote:
Rui Nuno Capela wrote:
> Have you tried whether switching off standard output capture on
> qjackctl/setup/options makes any difference on that "jackstart sync
> pipe" issue?
My last answer may have been confused.
I have had another problem starting Jack, which I have a workaround for.
Just the last time I tried it, I believe that was stopping me.
Now, after clearing up that problem - by removing
/var/lib/jack/tmp/jack-500/default/jack-ack-fifo* files, and rebooting,
I found that jack will start as well as it always did, waith the
original settings.
However, I was fully aware of this problem, and it wasn't happening
earlier - it's a different error message (which I didn't spot this time,
because I was suppressing stdout...)
Anyway, my system is working fine, but I am not aware of anything that I
have done differently this time. I tried all of the same things before.
Thanks
Michael
3:34 p.m.
Rui Nuno Capela wrote:
Peter Lutek wrote:
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
Michael T D Nelson wrote:
Have you tried whether switching off standard output capture on
qjackctl/setup/options makes any difference on that "jackstart sync
pipe" issue? Paul Davis wrote:
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. 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 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.
11 Nov
11 Nov
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?
7:55 a.m.
Carlos Pino wrote:
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.
Again, I believe the "cannot write to jackstart sync pipe 4 (Bad file
descriptor)" message is nothing to worry about. And as it seems from the
results above it just confirms my suspicion. If you're sticking with a
2.6 kernel, just don't configure jackd with --enable-capabilities and
you're off the hook ;)
Cheers.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
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?
12:33 p.m.
Rui Nuno Capela escribió:
Again, I believe the "cannot write to jackstart sync pipe 4 (Bad file
descriptor)" message is nothing to worry about. And as it seems from
the results above it just confirms my suspicion. If you're sticking
with a 2.6 kernel, just don't configure jackd with
--enable-capabilities and you're off the hook ;)
Cheers.
Yeah,you are right .I complied jackd as you say and the "cannot write
to jackstart sync pipe 4 (Bad file descriptor)" message doesn't
appears anymore.Now the problem is with ardour,that doesn't want to
start after thhis compilation.
Here is the output :
supertux@sid:~$ ardour
Ardour/GTK 0.99
(built using 0.604.3 with libardour 0.901.2 and GCC version 4.0.2
(Debian 4.0.2-2))
Copyright (C) 1999-2005 Paul Davis
Some portions Copyright (C) Steve Harris, Ari Johnson, Brett Viren, Joel
Baker
Ardour no ofrece ningn tipo de garantï¿ 1/2
not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Este software es gratuito.Usted puede distribuirlo
under certain conditions; see the source for copying conditions.
Loading UI configuration file /etc/ardour/ardour_ui.rc
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.
`default' server already active
ardour: [ERROR]: Unable to connect to JACK server
ardour: [ERROR]: Could not connect to JACK server as "ardour"
ardour: [ERROR]: No se pudo conectar a JACK con el nombre "ardour"
I also compiled alsa-driver-1.0.10-rc3,but the problem come after the
compilation of jackd.
Any hint?
Thank you very much.
Saludos
Cheers
-- Carlos.
12:51 p.m.
On Fri, 2005-11-11 at 17:33 +0100, Carlos Pino wrote:
Yeah,you are right .I complied jackd as you say and
the "cannot write
to jackstart sync pipe 4 (Bad file descriptor)" message doesn't
appears anymore.Now the problem is with ardour,that doesn't want to
start after thhis compilation.
Here is the output :
my guess is that you have just committed the cardinal sin of setting up
your system so that there are two versions of JACK installed. you
started one, and ardour is trying to start the other. i wish we could
detect this situation and report it more accurately, but we don't know
how to right now. you should never ever have more than 1 JACK install on
a machine unless you are confident that you know everything there is to
know about JACK, and perhaps not even then.
when you recompiled JACK, did you remove the old version first? what
--prefix= argument did you give configure?
--p
13 Nov
13 Nov
10:55 a.m.
Hi,sorry about the delay of the answer,I'd been very busy.
First of all tank you very much for interesting in my message,I
couldn't imagine to have a response from the main developer of one of
the best things made for Linux-Audio,and excuse my english.
I'm very newbie in this kind of linux tasks,and try to learn as
much as I can.
I'm trying to build my own audio-system and compile only the more
ussual apps for me;Ardour and Jack are the main core of this.By now I
take the Demudi kernel till I learn to compile my own,and compile with
succes Ardour and some other apps.Before try to compile jack I installed
it from Sid and everythings works fine but the message that shows at
the window messages, that doesn't have influence with the normal
function of jackd.
Paul Davis escribió:
On Fri, 2005-11-11 at 17:33 +0100, Carlos Pino wrote:
Ok it will be present in the future.
Yeah,you are right .I complied jackd as you say
and the "cannot write
to jackstart sync pipe 4 (Bad file descriptor)" message doesn't
appears anymore.Now the problem is with ardour,that doesn't want to
start after thhis compilation.
Here is the output :
my guess is that you have just committed the cardinal sin of setting up
your system so that there are two versions of JACK installed.you
started one, and ardour is trying to start the other. i wish we could
detect this situation and report it more accurately, but we don't know
how to right now. you should never ever have more than 1 JACK install on
a machine unless you are confident that you know everything there is to
know about JACK, and perhaps not even then.
when you recompiled JACK, did you remove the old
version first?
I did many things in the procces and probably no.At the second time I
remove all about jack and try again.But if I remove the compilation
installed and do an apt-get install jackd,everything goes back to the
fine working but the "cannot write to jackstart sync pipe 4 (Bad file
descriptor)" message return.
what
--prefix= argument did you give configure?
First I did --prefix=/usr and later leave blank to use the default
settings
Now I'm at the begin again,I removed all the jack staff and have the
source code to try to compile.I will read more about this and see what
happens.
--p
Again thank you very much for your interest.
Saludos from Spain
Cheers
-- Carlos.
15 Nov
15 Nov
8:33 a.m.
New subject: [linux-audio-user] Musix - Rosegarden - no sound - Please Help
Hi.
I am a musician with some experience in studio work
I can work without problems with: solfege - ardour - Resound
but with Rosegarden i can't hear nothing
audio or midi
I use Musix 0.30
Thanks in advance.
10 Nov
10 Nov
12:51 p.m.
On Thu, 10 Nov 2005 14:17:35 +0000
Michael T D Nelson <m_nels(a)gmx.net> wrote:
jack_create_thread: error -1 switching current thread
to rt for
inheritance: Unknown error 4294967295
cannot start watchdog thread
Just a guess:
Uncheck the realtime option in qjackctl's setupdialog or setup either
- the realtime_lsm
or
- rtlimits
Have fun,
Flo
--
Palimm Palimm!
http://tapas.affenbande.org
1:05 p.m.
Florian Schmidt wrote:
On Thu, 10 Nov 2005 14:17:35 +0000
Michael T D Nelson <m_nels(a)gmx.net> wrote:
Thanks. Well, if I uncheck the realtime opton, JACK will now start. But
it worked fine up until a couple of weeks ago.
I don't think that it coincided with any changes which I made, but I'll
have to check that. I think I may have upgraded my kernel at some point
(but only to a newer CCRMA kernel).
Maybe it's time to reboot into thwe older kernel and see if the problem
goes away...
jack_create_thread: error -1 switching current
thread to rt for
inheritance: Unknown error 4294967295
cannot start watchdog thread
Just a guess:
Uncheck the realtime option in qjackctl's setupdialog or setup either
- the realtime_lsm
or
- rtlimits
Well, if this turns out to be the problem, then I'll have to learn how
to set one of these up I guess.
Thanks
Michael
3 p.m.
On Thursday 10 November 2005 17:05, Michael T D Nelson wrote:
Florian Schmidt wrote:
Hi Michael. Would you check out.
rpm -q rtirq
and
rpm -q rtload
These two packages should have been installed when you installed
planetccrma-core with apt-get install planetcccrma-core , and the
accompanying low latency kernel with apt-get install planetccrma-core-edge .
These two packages "rtirq" and "rtload" are responsible for realtime
working
with planetccrma kernels. All the best. Nigel.
On Thu, 10 Nov 2005 14:17:35 +0000
Michael T D Nelson <m_nels(a)gmx.net> wrote:
Thanks. Well, if I uncheck the realtime opton, JACK will now start. But
it worked fine up until a couple of weeks ago.
I don't think that it coincided with any changes which I made, but I'll
have to check that. I think I may have upgraded my kernel at some point
(but only to a newer CCRMA kernel).
Maybe it's time to reboot into thwe older kernel and see if the problem
goes away...
jack_create_thread: error -1 switching current
thread to rt for
inheritance: Unknown error 4294967295
cannot start watchdog thread
Just a guess:
Uncheck the realtime option in qjackctl's setupdialog or setup either
- the realtime_lsm
or
- rtlimits
Well, if this turns out to be the problem, then I'll have to learn how
to set one of these up I guess.
Thanks
Michael
4:08 p.m.
Nigel Henry wrote:
Hi Michael. Would you check out.
rpm -q rtirq
and
rpm -q rtload
# rpm -q rtirq
rtirq-20050620-1.rhfc3.ccrma
# rpm -q rtload
rtload-0.0.2-1.rhfc3.ccrma
I'm not sure what I'm looking for. Did you just want me to check whether
the packages are installed? Or are the versions significant?
I should point out that (as I have said elsewhere in this thread) my
problem now seems to be resolved, although I do not yet know why!
Thanks
Michael
4:30 p.m.
On Thursday 10 November 2005 20:08, Michael T D Nelson wrote:
Nigel Henry wrote:
Hi Michael. Mainly to check that the packages were installed, but I'm glad
you've got the problem fixed. Nigel.
Hi Michael. Would you check out.
rpm -q rtirq
and
rpm -q rtload
# rpm -q rtirq
rtirq-20050620-1.rhfc3.ccrma
# rpm -q rtload
rtload-0.0.2-1.rhfc3.ccrma
I'm not sure what I'm looking for. Did you just want me to check whether
the packages are installed? Or are the versions significant?
I should point out that (as I have said elsewhere in this thread) my
problem now seems to be resolved, although I do not yet know why!
Thanks
Michael 
3:06 p.m.
On Thu, 2005-11-10 at 14:17 +0000, Michael T D Nelson wrote:
jack_create_thread: error -1 switching current thread
to rt for
inheritance: Unknown error 4294967295
I am having the same problem on a customer's machine. JACK starts OK
but the client gets this error. Never was able to find the solution.
Check the archives, it looks like no one has ever been able to figure
out what this "error -1 switching current thread to rt" problem is.
I think it has something to do with JACK being compiled for capabilities
on a non-capabilities enabled kernel, or something.
Lee
3:15 p.m.
On Thu, 2005-11-10 at 14:17 +0000, Michael T D Nelson wrote:
jack_create_thread: error -1 switching current thread
to rt for
inheritance: Unknown error 4294967295
cannot start watchdog thread
Hmm, was the code that generated this error message ripped out of JACK
recently? I just grepped my source tree and there's no occurence of
"jack_create_thread", "switching current thread to rt", or
"inheritance"
whatsoever. There is a "jack_client_create_thread" however.
So maybe the problem is a mismatch between client and server JACK
versions? Maybe your upgrade pulled in an older version of JACK.
Lee
6950
days inactive
6955
days old
linux-audio-user@lists.linuxaudio.org
23 comments
9 participants
participants (9)
-
Carlos Pino -
Florian Schmidt -
Lee Revell -
Michael T D Nelson -
Nigel Henry -
Paul Davis -
Peter Lutek -
roy -
Rui Nuno Capela