19 Nov
2002
19 Nov
'02
12:05 a.m.
greetings all,
i recently put together a new debian box (unstable with 2.4.19+ll),
installed jack from cvs, installed freqtweak 0.4.5, ssm from cvs, pd
from cvs, etc. and tried to get them to play together and have had no
success.
i start jack as follows:
wazowski:/home/jcw# jackd -d alsa -d hw
jackd 0.40.1
Copyright 2001-2002 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
loading driver ..
creating alsa driver ... hw|1024|2|48000|swmon
starting engine
everything seems to be ok. then i launch freqtweak and get the
following:
wazowski:/home/jcw# freqtweak -i none,none -n ft
JACK error: cannot connect input port: none -> _pcm:playback_18
JACK error: cannot connect output port: ft:in_1 -> alsa_pcm:playback_1
JACK error: cannot connect input port: none -> %
JACK error: cannot connect output port: -> alsa_pcm:playback_2
i have no idea what to make of this. once freqtweak is running, i can't
get alsa_pcm:playback_1, etc. as options. also, ssm just segfaults if i
try to connect it to jack at all. pure data just kills all audio.
i am running alsa rc5 with an rme9652 and an emu10k1. all of my apps
work perfectly without jack.
does anyone have a clue or suggestion? i hope that i have just done
something silly and someone will be able to point out the error in my
ways.
thank you for your time.
j.c.w.
--
WITH GORILLA GONE,
WILL THERE
BE HOPE
FOR MAN?
- ishmael
19 Nov
19 Nov
6:35 a.m.
On Mon, Nov 18, 2002 at 09:59:34 -0600, j.c.w. wrote:
greetings all,
wazowski:/home/jcw# freqtweak -i none,none -n ft
JACK error: cannot connect input port: none -> _pcm:playback_18
JACK error: cannot connect output port: ft:in_1 -> alsa_pcm:playback_1
JACK error: cannot connect input port: none -> %
JACK error: cannot connect output port: -> alsa_pcm:playback_2
i have no idea what to make of this. once freqtweak is running, i can't
get alsa_pcm:playback_1, etc. as options. also, ssm just segfaults if i
try to connect it to jack at all. pure data just kills all audio.
i am running alsa rc5 with an rme9652 and an emu10k1. all of my apps
work perfectly without jack.
does anyone have a clue or suggestion? i hope that i have just done
something silly and someone will be able to point out the error in my
ways.
Did you rebuild all your apps after you built jack last? It sounds like
there is a version problem between the two. Unfortunatly, until recently
jack did not use proper unix library versioning.
- Steve
10:41 a.m.
yes, i rebuilt everything from scratch _after_ i rebuilt jack. that's
what has me so confused. i track the jack-dev list and haven't seen
anyone with a similar situation, so i am at a bit of a loss...
of course, i am assuming that freqtweak et al have caught up with the
most recent jack changes, but i thought that the occurences of
"playback" and "capture" would indicate that they had.
any further thoughts?
j.c.w.
Steve Harris wrote:
On Mon, Nov 18, 2002 at 09:59:34 -0600, j.c.w. wrote:
greetings all,
wazowski:/home/jcw# freqtweak -i none,none -n ft
JACK error: cannot connect input port: none -> _pcm:playback_18
JACK error: cannot connect output port: ft:in_1 -> alsa_pcm:playback_1
JACK error: cannot connect input port: none -> %
JACK error: cannot connect output port: -> alsa_pcm:playback_2
i have no idea what to make of this. once freqtweak is running, i can't
get alsa_pcm:playback_1, etc. as options. also, ssm just segfaults if i
try to connect it to jack at all. pure data just kills all audio.
i am running alsa rc5 with an rme9652 and an emu10k1. all of my apps
work perfectly without jack.
does anyone have a clue or suggestion? i hope that i have just done
something silly and someone will be able to point out the error in my
ways.
Did you rebuild all your apps after you built jack last? It sounds like
there is a version problem between the two. Unfortunatly, until recently
jack did not use proper unix library versioning.
- Steve
12:44 p.m.
j.c.w. wrote on Tue, 19-Nov-2002:
yes, i rebuilt everything from scratch _after_ i
rebuilt jack. that's
what has me so confused. i track the jack-dev list and haven't seen
anyone with a similar situation, so i am at a bit of a loss...
Are you sure that there is no other older jackd or libjack.so* that
could be picked up at runtime exists on your system?
of course, i am assuming that freqtweak et al have
caught up with the
most recent jack changes, but i thought that the occurences of
"playback" and "capture" would indicate that they had.
freqtweak should be alright if you are using 0.4.5 or CVS.
>>greetings all,
>>wazowski:/home/jcw# freqtweak -i none,none -n ft
>>JACK error: cannot connect input port: none -> _pcm:playback_18
>>JACK error: cannot connect output port: ft:in_1 -> alsa_pcm:playback_1
>>JACK error: cannot connect input port: none -> %
>>JACK error: cannot connect output port: -> alsa_pcm:playback_2
This is a frightening output ;} Definitely looks like some
sort of jackd/libjack mismatch with all the messed up portname
strings.
jlc
3 p.m.
um...yeah...about that...
that was it. old libs will get ya every time kiddies... thanks a
million! you saved me (i'm guessing) about 10 hours of digging around
before i would have come to my senses...
party on...
j.c.w.
Jesse Chappell wrote:
j.c.w. wrote on Tue, 19-Nov-2002:
yes, i rebuilt everything from scratch _after_ i
rebuilt jack. that's
what has me so confused. i track the jack-dev list and haven't seen
anyone with a similar situation, so i am at a bit of a loss...
Are you sure that there is no other older jackd or libjack.so* that
could be picked up at runtime exists on your system?
of course, i am assuming that freqtweak et al
have caught up with the
most recent jack changes, but i thought that the occurences of
"playback" and "capture" would indicate that they had.
freqtweak should be alright if you are using 0.4.5 or CVS.
>>greetings all,
>>wazowski:/home/jcw# freqtweak -i none,none -n ft
>>JACK error: cannot connect input port: none -> _pcm:playback_18
>>JACK error: cannot connect output port: ft:in_1 -> alsa_pcm:playback_1
>>JACK error: cannot connect input port: none -> %
>>JACK error: cannot connect output port: -> alsa_pcm:playback_2
This is a frightening output ;} Definitely looks like some
sort of jackd/libjack mismatch with all the messed up portname
strings.
jlc
8068
days inactive
8069
days old
linux-audio-user@lists.linuxaudio.org
4 comments
3 participants
participants (3)
-
j.c.w. -
Jesse Chappell -
Steve Harris