[linux-audio-user] jack question
j.c.w.
jcwjcw at qwest.net
Tue Nov 19 14:01:01 EST 2002
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
>
>
>
>
More information about the Linux-audio-user
mailing list