On Sat, 24 Jan 2004, Kjetil Svalastog Matheussen wrote:
k_jack~ is an external to get sound in and out from jack clients.
Example:
[k_jack~ freqtweak]
...will give you an object with two signal inlets and two signal outlets, if a jack-client containing the name freqtweak is running.
It requires at least PD 0.37.
v0.0.1->v0.0.2: -Support for pure_data_1. And also pure_data_2/3/etc. if pd is compiled up with support for more than two simultaniously running pd sessions. -Only connect ports once.
How about combining this with my jackx connection query externals into a jackcontrol external lib. I still want to add a jacktransport external to my jackx lib eventually.( When I understand how the jacktransport works :) )
Gerard http://www.xs4all.nl/~gml they should also be in the sourceforge CVS
On Sat, 24 Jan 2004, Kjetil Svalastog Matheussen wrote:
k_jack~ is an external to get sound in and out from jack clients.
Example:
[k_jack~ freqtweak]
...will give you an object with two signal inlets and two signal outlets, if a jack-client containing the name freqtweak is running.
It requires at least PD 0.37.
v0.0.1->v0.0.2: -Support for pure_data_1. And also pure_data_2/3/etc. if pd is compiled up with support for more than two simultaniously running pd sessions. -Only connect ports once.
--
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
Do you mean making the two externals into one file? Doesn't that mean you have to start pd with the -lib flag and the name of the file? Whats the advantage?
On Sun, 25 Jan 2004 gml@xs4all.nl wrote:
How about combining this with my jackx connection query externals into a jackcontrol external lib. I still want to add a jacktransport external to my jackx lib eventually.( When I understand how the jacktransport works :) )
Gerard http://www.xs4all.nl/~gml they should also be in the sourceforge CVS
On Sat, 24 Jan 2004, Kjetil Svalastog Matheussen wrote:
k_jack~ is an external to get sound in and out from jack clients.
Example:
[k_jack~ freqtweak]
...will give you an object with two signal inlets and two signal outlets, if a jack-client containing the name freqtweak is running.
It requires at least PD 0.37.
v0.0.1->v0.0.2: -Support for pure_data_1. And also pure_data_2/3/etc. if pd is compiled up with support for more than two simultaniously running pd sessions. -Only connect ports once.
--
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
I was thinking of making it into one lib, yes. The advantage would be that all jack externals are in one place. It could also be as seperate externals collected in one directory for the sources and one for the help-patches. Another thing is to have them al start with the same name. Mainly it is about userfriendlyness and to avoid double developments.
Gerard
Do you mean making the two externals into one file? Doesn't that mean you have to start pd with the -lib flag and the name of the file? Whats the advantage?
On Sun, 25 Jan 2004 gml@xs4all.nl wrote:
How about combining this with my jackx connection query externals into a jackcontrol external lib. I still want to add a jacktransport external to my jackx lib eventually.( When I understand how the jacktransport works :) )
Gerard http://www.xs4all.nl/~gml they should also be in the sourceforge CVS
On Sat, 24 Jan 2004, Kjetil Svalastog Matheussen wrote:
k_jack~ is an external to get sound in and out from jack clients.
Example:
[k_jack~ freqtweak]
...will give you an object with two signal inlets and two signal outlets, if a jack-client containing the name freqtweak is running.
It requires at least PD 0.37.
v0.0.1->v0.0.2: -Support for pure_data_1. And also pure_data_2/3/etc. if pd is
compiled up
with support for more than two simultaniously running pd sessions. -Only connect ports once.
--
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
On Sun, 25 Jan 2004 gml@xs4all.nl wrote:
I was thinking of making it into one lib, yes. The advantage would be that all jack externals are in one place. It could also be as seperate externals collected in one directory for the sources and one for the help-patches. Another thing is to have them al start with the same name. Mainly it is about userfriendlyness and to avoid double developments.
Yes, but k_jack~ and jackx does quite seperate tasks (doesn't they?). Allthough they both can be used to connect jack clients, they do it in different ways. k_jack~ makes a new jack port for each inlet or outlet, while jackx just connects allready existing ports.
And regarding making it a lib, I don't think its very userfriendly to let the user add "-lib <filename>" to the commandline when starting pd.
But it would be nice with an external that automaticly behave like k_jack~ when needed, and jackx when needed: That is when the external only connects two allready existing jack ports, to create some kind of super jack patch bay external. But I don't really see how to do that in practice.
Gerard
Do you mean making the two externals into one file? Doesn't that mean you have to start pd with the -lib flag and the name of the file? Whats the advantage?
On Sun, 25 Jan 2004 gml@xs4all.nl wrote:
How about combining this with my jackx connection query externals into a jackcontrol external lib. I still want to add a jacktransport external to my jackx lib eventually.( When I understand how the jacktransport works :) )
Gerard http://www.xs4all.nl/~gml they should also be in the sourceforge CVS
On Sat, 24 Jan 2004, Kjetil Svalastog Matheussen wrote:
k_jack~ is an external to get sound in and out from jack clients.
Example:
[k_jack~ freqtweak]
...will give you an object with two signal inlets and two signal outlets, if a jack-client containing the name freqtweak is running.
It requires at least PD 0.37.
v0.0.1->v0.0.2: -Support for pure_data_1. And also pure_data_2/3/etc. if pd is
compiled up
with support for more than two simultaniously running pd sessions. -Only connect ports once.
--
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
-
gml＠xs4all.nl -
Kjetil Svalastog Matheussen