[PD] PD 0.36-0 and Jack 0.61.0 doesn't work?
Frank Barknecht
fbar at footils.org
Sat Mar 22 08:40:45 CET 2003
Hallo,
Larry Troxler hat gesagt: // Larry Troxler wrote:
> At least, after I start Jack, then start PD, then run qjackconnect (which, BTW
> did _not_ need to be recompiled to use with this Jack snapshot I got - the
> Planet CCRMA binary works fine!), I see that the Jack PD clients (two of
> them- one for each channel I suppose) have been connected to the the JACK
> alsa clients. So it seems that PD does indeed connect itself on startup. Is
> there a way to disable this?
Not currently, that's why I disabled jack_connect in s_linux.c at
all.
> Certainly I don't want it to connect to the soundcard through Jack,
> because if that were the case, there would be no point in using Jack
> at all. Perhaps I am missing some understanding about the Jack
> concept.
Well, something *must* connect to the soundcard in the end, otherwise
no sound would be produced.
> Is there a way to make more Jack clients avalable to PD, so that one audio
> output for example, goes to the DAC, and another one goes to an audio
> recorder? If so, (1) how is this specified on the PD command line,
$ pd -jack -channel 12
or
$ pd -jack -inchannels 4 -outchannels 2
After that, you probably have a lot of jack_connect to do.
> and (2) how would you decide from PD, which jack client audio input
> or output you want to connect to, in a given box? (For example, dac~
> just takes a number of signal inputs equal to the number of output
> channels - how would you tell PD which Jack client the DAC stream
> should be sent to?)
dac~ takes the ids of output channels. So it works like this:
[dac~ 1] ==> pure_data_0:output0
[dac~ 2 4] ==> pure_data_0:output1, pure_data_0:output3
...
ciao
--
Frank Barknecht _ ______footils.org__
More information about the Pd-list
mailing list