4 Nov
2005
4 Nov
'05
7:05 a.m.
Hi there.
I'm not a linux-guru but I'm trying to build my own audio system
taking some pieces from A/Demudi and Sid,and compiling some others from
source.My main goal is to learn as much as I can and get an audio system
working with only the components that I need.
I take the last kernel from Demudi:2.6.13-1-multimedia-386 and
jackd-0.100.0-4 from sid.
Compiled ardour,muse,zynaddsubfx,qsampler-linuxsampler,hydrogen,and some
others,and everything works really well.
I'm impressed how "stable" can be the "unstable" side of
Debian.
The subject of this message is the output of qjackctl when I launch
jackd with :
/usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p256 -n2
or
/usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p256 -n2
*But it works fine*,I can record and playback at realtime processing
with very good results.
This advice doesn't appears when launch jackd from commandline:
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.
My machine:
P IV 2.6 Mhz
1 Gb ddr
Terratec DMX6 Fire soundcard
Is there something that I have to do to avoid this error?I would like
to know why this happens.
I'd googled about it and find many cases where jack was stoped,but
this is not the mine.
Thanks in advance.
Saludos.
Cheers.
-- Carlos.
4 Nov
4 Nov
8:50 a.m.
New subject: [linux-audio-user] cannot write to jackstart sync pipe 4 (Bad file descriptor)
Carlos Pino wrote:
...
The subject of this message is the output of qjackctl when I launch
jackd with :
/usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p256 -n2
or
/usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p256 -n2
*But it works fine*,I can record and playback at realtime processing
with very good results.
This advice doesn't appears when launch jackd from commandline:
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.
My machine:
P IV 2.6 Mhz
1 Gb ddr
Terratec DMX6 Fire soundcard
interesting. i have the same situation: syncpipe error starting with
qjackctl but it works fine. no error starting jackd from commandline.
i'm on a fedora core 3 planet-ccrma laptop, with an rme multiface.
kernel 2.6.12-0.21.rdt.rhfc3.ccrma. jack 0.99.36. qjackctl 0.2.15.
i don't know what's going on either.
-p
1:35 p.m.
New subject: [linux-audio-user] cannot write to jackstart sync pipe 4 (Bad file descriptor)
On Fri, 04 Nov 2005 12:05:36 +0100
Carlos Pino <pinojazz(a)gmail.com> wrote:
The subject of this message is the output of
qjackctl when I launch
jackd with :
/usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p256 -n2
Weird. jackstart should only ever be used when you tell qjackctl to do
it. See the setup tab -> server path. Make sure it's just "jackd" there.
Flo
--
Palimm Palimm!
http://tapas.affenbande.org
1:47 p.m.
New subject: [linux-audio-user] cannot write to jackstart sync pipe 4 (Bad file descriptor)
Florian Schmidt wrote:
On Fri, 04 Nov 2005 12:05:36 +0100
Carlos Pino <pinojazz(a)gmail.com> wrote:
dunno about carlos, but mine is set to "jackd" -- i still get the error.
note that jackd IS starting fine, but we ALSO get the jackstart sync
pipe error message. yeah... it's wierd.
-p
The subject of this message is the output of
qjackctl when I launch
jackd with :
/usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p256 -n2
Weird. jackstart should only ever be used when you tell qjackctl to do
it. See the setup tab -> server path. Make sure it's just "jackd" there.
2:43 p.m.
New subject: [linux-audio-user] cannot write to jackstart sync pipe 4 (Bad file descriptor)
On Fri, 04 Nov 2005 12:48:22 -0500
Peter Lutek <plutek(a)infinity.net> wrote:
dunno about carlos, but mine is set to "jackd" -- i still get the error.
note that jackd IS starting fine, but we ALSO get the jackstart sync
pipe error message. yeah... it's wierd.
maybe it's a qjackctl bug. hmm..
flo
--
Palimm Palimm!
http://tapas.affenbande.org
The subject of this message is the output of qjackctl
when I launch
jackd with :
/usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p256 -n2
Weird. jackstart should only ever be used when you tell qjackctl to do
it. See the setup tab -> server path. Make sure it's just "jackd" there.
3:06 p.m.
New subject: [linux-audio-user] cannot write to jackstart sync pipe 4 (Bad file descriptor)
Florian Schmidt wrote:
On Fri, 04 Nov 2005 12:48:22 -0500
Peter Lutek <plutek(a)infinity.net> wrote:
dunno about carlos, but mine is set to "jackd" -- i still get the error.
note that jackd IS starting fine, but we ALSO get the jackstart sync
pipe error message. yeah... it's wierd.
maybe it's a qjackctl bug. hmm..
Maybe.
IMO this error is pretty innocuous. It is only issued if jackd is built
with ./configure --enable-capabilities, which does not make sense
anymore for the 2.6 kernel line.
Apparentely the error is due to some mishap with the pipe file
descriptors that the jackstart launcher proccess uses to communicate
with the actual jackd process. Which are simply not used if you don't
use jackstart. However, jackd still tries to access the pipe if built
with capabilities enabled.
Maybe, it only happens when you tell qjackctl to capture the jackd
standard output into its own messages window, and those pipe/file
descriptors get loose (because it is assumed to be file descriptors
number 4 and 5, coincidentally right after the standard ones).
Just a though. Not sure.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
The subject of this message is the output of qjackctl
when I launch
jackd with :
/usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p256 -n2
Weird. jackstart should only ever be used when you tell qjackctl to do
it. See the setup tab -> server path. Make sure it's just "jackd"
there.
5 Nov
5 Nov
7:16 a.m.
New subject: [linux-audio-user] cannot write to jackstart sync pipe 4 (Bad file descriptor)
On Friday 04 November 2005 11:05, Carlos Pino was like:
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.
This isn't an error message.
--
cheers,
tim hall
http://glastonburymusic.org.uk/tim
9:55 a.m.
New subject: [linux-audio-user] cannot write to jackstart sync pipe 4 (Bad file descriptor)
tim hall wrote:
On Friday 04 November 2005 11:05, Carlos Pino was
like:
Of course.
http://music.columbia.edu/pipermail/linux-audio-user/2005-November/028256.h…
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.
This isn't an error message.
* This advice doesn't appears when launch jackd
from commandline:*
7 Nov
7 Nov
5:36 a.m.
New subject: [linux-audio-user] cannot write to jackstart sync pipe 4 (Bad file descriptor)
On Saturday 05 November 2005 13:55, Carlos Pino was like:
Duh, sorry, I really should read the subject line sometimes. ;)
--
cheers,
tim hall
http://glastonburymusic.org.uk/tim
This isn't
an error message.
Of course.
6806
days inactive
6809
days old
linux-audio-user@lists.linuxaudio.org
8 comments
5 participants
participants (5)
-
Carlos Pino -
Florian Schmidt -
Peter Lutek -
Rui Nuno Capela -
tim hall