Hi list,
just discovered that Pd's jack audio ouput ports are numbered from zero onwards. Is this very intentional? Can't seem to think of any other software that does it, and system ports such as soundcard ports seem to be numbered from 1 onwards, making it easy to tip over the off-by-one error (have movie dialoge come out of the sub woofer perhaps).
Thanks for all oppinions! P
- IOhannes m zmölnig zmoelnig@iem.at [2020-12-18 20:52]:
On 12/18/20 8:40 PM, Peter P. wrote:
Hi list,
just discovered that Pd's jack audio ouput ports are numbered from zero onwards. Is this very intentional?
it's been on my todo-list for ages to fix this.
Great, good to hear! Thanks IO! P
On 12/18/20 9:06 PM, Peter P. wrote:
- IOhannes m zmölnig zmoelnig@iem.at [2020-12-18 20:52]:
On 12/18/20 8:40 PM, Peter P. wrote:
Hi list,
just discovered that Pd's jack audio ouput ports are numbered from zero onwards. Is this very intentional?
it's been on my todo-list for ages to fix this.
Great, good to hear! Thanks IO!
while fixing the issue is trivial, i wonder what's the best way to proceed. simply changing the port-names from "input0" to "input1" will probably break all existing auto connection-setups (e.g. qjackctl patchbays).
currently they will do something like: "puredata:output1 -> system:capture_0"
if we just renumber the ports, this will *certainly* introduce off-by-one errors (e.g. have movie dialoge come out of the sub woofer).
so we probably should name the ports slightly different, so that "output0" becomes "output_1".
(the ALSA backend of jack uses underscores as a separator; but Ardour (somewhat canonical) uses spaces - though i'd rather avoid that)
what do you think.
famdsr IOhannes
- IOhannes m zmölnig zmoelnig@iem.at [2020-12-18 21:16]:
On 12/18/20 9:06 PM, Peter P. wrote:
- IOhannes m zmölnig zmoelnig@iem.at [2020-12-18 20:52]:
On 12/18/20 8:40 PM, Peter P. wrote:
Hi list,
just discovered that Pd's jack audio ouput ports are numbered from zero onwards. Is this very intentional?
it's been on my todo-list for ages to fix this.
Great, good to hear! Thanks IO!
while fixing the issue is trivial, i wonder what's the best way to proceed. simply changing the port-names from "input0" to "input1" will probably break all existing auto connection-setups (e.g. qjackctl patchbays).
currently they will do something like: "puredata:output1 -> system:capture_0"
if we just renumber the ports, this will *certainly* introduce off-by-one errors (e.g. have movie dialoge come out of the sub woofer).
so we probably should name the ports slightly different, so that "output0" becomes "output_1".
Elegantly circumnavigating the above issue I find.
(the ALSA backend of jack uses underscores as a separator; but Ardour (somewhat canonical) uses spaces - though i'd rather avoid that)
I'd recommend underscores as they are easier to put as command line flags for eg. jack_capture or jack_connect.
cheersz, P
-
IOhannes m zmölnig -
Peter P.