Hi again! First, thank you for your answers, they have been very useful. But I'm gonna bother you again with a newbie question.
How do you gate flow, both control / audio?
I think max has a gate or so object. Writing a patch which treats a number of cases in different ways I was in a bad need of a gate-like object with for example an output selector inlet and an input inlet gated to one of N outlets according to the current value of the output selector.
I solved this by [pack]ing the incoming message with the output selector in front and then [route]ing it (and in case the selector was a symbol stripping the list selector added by [pack] before routing).
Regarding audio streams I find gating them by means of [~* 1] / [~* 0] multipliers too awkward, as a few N gated streams would clutter your patch with ~ N^2+3*N control connections needed to send 0 or 1 factor for each multiplier and them sum the outputs. But here I could use [switch~] (or derek's [switcheroo]) and subpatches with the plus of performance gain.
I could write some gate-like subpatches but first I would like to know if there is an usual way of doing the above which I'm missing, or some adequate external, specially for the control part.
Thank you again. Regards, Carlos
How do you gate flow, both control / audio?
for data spigot for audio switch~ (but you know that)!
patrick
----- Original Message ----- From: "Carlos Pita" carlosjosepita@yahoo.com.ar To: pd-list@iem.at Sent: Wednesday, April 20, 2005 2:10 PM Subject: [PD] Gating
Hi again! First, thank you for your answers, they have been very useful. But I'm gonna bother you again with a newbie question.
I think max has a gate or so object. Writing a patch which treats a number of cases in different ways I was in a bad need of a gate-like object with for example an output selector inlet and an input inlet gated to one of N outlets according to the current value of the output selector.
I solved this by [pack]ing the incoming message with the output selector in front and then [route]ing it (and in case the selector was a symbol stripping the list selector added by [pack] before routing).
Regarding audio streams I find gating them by means of [~* 1] / [~* 0] multipliers too awkward, as a few N gated streams would clutter your patch with ~ N^2+3*N control connections needed to send 0 or 1 factor for each multiplier and them sum the outputs. But here I could use [switch~] (or derek's [switcheroo]) and subpatches with the plus of performance gain.
I could write some gate-like subpatches but first I would like to know if there is an usual way of doing the above which I'm missing, or some adequate external, specially for the control part.
Thank you again. Regards, Carlos
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
for data spigot
I tried spigot but it readily clutters the patch too, it's not as different as using 1/0 multipliers for audio. You must send 0/1 to the cold inlet according to your output selector which amounts to n^2 connections (from each selector to 0 or 1 for each spigot), plus n*2 from each 0/1 to its spigot, plus n to combine spigots outputs. It's ok for simple cases (are multipliers are) but to gate 4+ control streams could be awkward.
Hi again! First, thank you for your answers, they have been very useful. But I'm gonna bother you again with a newbie question.
I think max has a gate or so object. Writing a patch which treats a number of cases in different ways I was in a bad need of a gate-like object with for example an output selector inlet and an input inlet gated to one of N outlets according to the current value of the output selector.
I solved this by [pack]ing the incoming message with the output selector in front and then [route]ing it (and in case the selector was a symbol stripping the list selector added by [pack] before routing).
Regarding audio streams I find gating them by means of [~* 1] / [~* 0] multipliers too awkward, as a few N gated streams would clutter your patch with ~ N^2+3*N control connections needed to send 0 or 1 factor for each multiplier and them sum the outputs. But here I could use [switch~] (or derek's [switcheroo]) and subpatches with the plus of performance gain.
I could write some gate-like subpatches but first I would like to know if there is an usual way of doing the above which I'm missing, or some adequate external, specially for the control part.
Thank you again. Regards, Carlos
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
hi carlos
maybe zexys [demux],[demux~] and [mux~] are what you are looking for.
roman
---- Original Message ----- From: "Carlos Pita" carlosjosepita@yahoo.com.ar To: pd-list@iem.at Sent: Wednesday, April 20, 2005 8:28 PM Subject: Re: [PD] Gating
for data spigot
I tried spigot but it readily clutters the patch too, it's not as different as using 1/0 multipliers for audio. You must send 0/1 to the cold inlet according to your output selector which amounts to n^2 connections (from each selector to 0 or 1 for each spigot), plus n*2 from each 0/1 to its spigot, plus n to combine spigots outputs. It's ok for simple cases (are multipliers are) but to gate 4+ control streams could be awkward.
Hi again! First, thank you for your answers, they have been very useful. But I'm gonna bother you again with a newbie question.
I think max has a gate or so object. Writing a patch which treats a number of cases in different ways I was in a bad need of a gate-like object with for example an output selector inlet and an input inlet gated to one of N outlets according to the current value of the output selector.
I solved this by [pack]ing the incoming message with the output selector in front and then [route]ing it (and in case the selector was a symbol stripping the list selector added by [pack] before routing).
Regarding audio streams I find gating them by means of [~* 1] / [~* 0] multipliers too awkward, as a few N gated streams would clutter your patch with ~ N^2+3*N control connections needed to send 0 or 1 factor for each multiplier and them sum the outputs. But here I could use [switch~] (or derek's [switcheroo]) and subpatches with the plus of performance gain.
I could write some gate-like subpatches but first I would like to know if there is an usual way of doing the above which I'm missing, or some adequate external, specially for the control part.
Thank you again. Regards, Carlos
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
Yes, thank you. In combination with zexy's [index] they will do it having symbols as output selectors. I've been also looking at [pyext]. It's great for quickly implementing control objects that are better expressed programmatically and for which performance is not critical (so C/C++ is not a sine qua non).
hi carlos
maybe zexys [demux],[demux~] and [mux~] are what you are looking for.
roman
---- Original Message ----- From: "Carlos Pita" carlosjosepita@yahoo.com.ar To: pd-list@iem.at Sent: Wednesday, April 20, 2005 8:28 PM Subject: Re: [PD] Gating
for data spigot
I tried spigot but it readily clutters the patch too, it's not as different as using 1/0 multipliers for audio. You must send 0/1 to the cold inlet according to your output selector which amounts to n^2 connections (from each selector to 0 or 1 for each spigot), plus n*2 from each 0/1 to its spigot, plus n to combine spigots outputs. It's ok for simple cases (are multipliers are) but to gate 4+ control streams could be awkward.
Hi again! First, thank you for your answers, they have been very useful. But I'm gonna bother you again with a newbie question.
I think max has a gate or so object. Writing a patch which treats a number of cases in different ways I was in a bad need of a gate-like object with for example an output selector inlet and an input inlet gated to one of N outlets according to the current value of the output selector.
I solved this by [pack]ing the incoming message with the output selector in front and then [route]ing it (and in case the selector was a symbol stripping the list selector added by [pack] before routing).
Regarding audio streams I find gating them by means of [~* 1] / [~* 0] multipliers too awkward, as a few N gated streams would clutter your patch with ~ N^2+3*N control connections needed to send 0 or 1 factor for each multiplier and them sum the outputs. But here I could use [switch~] (or derek's [switcheroo]) and subpatches with the plus of performance gain.
I could write some gate-like subpatches but first I would like to know if there is an usual way of doing the above which I'm missing, or some adequate external, specially for the control part.
Thank you again. Regards, Carlos
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
- not REALLY important*
hi :-( i downloaded zexy-NT-1.3 from pd.iem.at and i still cannot create [mux 1 2 3 4]. what am i doing wrong?
roman
maybe zexys [demux],[demux~] and [mux~] are what you are looking
for.
btw there is a [mux] too... (just for completeness)
mfg.a.sd IOhannes
I think zexy has no [mux] object.
ftp://ftp.iem.at/pd/Externals/ZEXY/README.html
Perhaps it belongs to another externals library. At least it's not included in pd-externals debian (testing) package, which is a fairly complete collection.
Regards, Carlos
- not REALLY important*
hi :-( i downloaded zexy-NT-1.3 from pd.iem.at and i still cannot create [mux 1 2 3 4]. what am i doing wrong?
roman
maybe zexys [demux],[demux~] and [mux~] are what you are looking
for.
btw there is a [mux] too... (just for completeness)
mfg.a.sd IOhannes
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Carlos Pita wrote:
I think zexy has no [mux] object.
well, _i_ know that zexy has a [mux] object.
ftp://ftp.iem.at/pd/Externals/ZEXY/README.html
outdated
Perhaps it belongs to another externals library. At least it's not included in pd-externals debian (testing) package, which is a fairly complete collection.
but obviously outdated.
i recently restructered zexy (and changed the version number to 2.0) and this one includes [mux]. currently only in the CVS though...
probably i'll put together some binaries within the next days.
mfg.a.dast IOhannes
Carlos Pita wrote:
for data spigot
I tried spigot but it readily clutters the patch too, it's not as different as using 1/0 multipliers for audio. You must
if you are experiencing such problems, you should seriously rethink your strategy of patching.
try to modularize your patches, and you might see great wonders of how smooth and simple they can become without using any super-dooper-all-in-one (external) objects.
mfg.adr IOhannes
-
Carlos Pita -
IOhannes m zmoelnig -
patrick -
Roman Haefeli