Hi
I'd like to have a |throw~ channelX| where X is an integer (say 1-8) controlled from a number box. It doesn't seem to be possible, but I hope I'm wrong.
Any input appreciated.
hi,
this should do it..
(num) | [makefilename channel%d] | [set $1( | [throw~ channel0]
greetings,
xof
info@kristoflauwers.domainepublic.net
http://kristoflauwers.domainepublic.net http://myspace.com/xofxof
At 08:58 p.m. 3/08/2008, you wrote:
Hi
I'd like to have a |throw~ channelX| where X is an integer (say 1-8) controlled from a number box. It doesn't seem to be possible, but I hope I'm wrong.
Any input appreciated.
-- peace, love & harmony Atte
http://atte.dk | http://myspace.com/attejensen http://anagrammer.dk | http://modlys.dk
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
since pd-0.40 $-variables don't have to be at the beginning of a symbol anymore, so
(num) | [set channel$1( | [throw~ channelX]
should work, too. marius.
kristof lauwers wrote:
hi,
this should do it..
(num) | [makefilename channel%d] | [set $1( | [throw~ channel0]
greetings,
xof
info@kristoflauwers.domainepublic.net
http://kristoflauwers.domainepublic.net http://myspace.com/xofxof
At 08:58 p.m. 3/08/2008, you wrote:
Hi
I'd like to have a |throw~ channelX| where X is an integer (say 1-8) controlled from a number box. It doesn't seem to be possible, but I hope I'm wrong.
Any input appreciated.
-- peace, love & harmony Atte
http://atte.dk | http://myspace.com/attejensen http://anagrammer.dk | http://modlys.dk
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
Hallo, marius schebella hat gesagt: // marius schebella wrote:
since pd-0.40 $-variables don't have to be at the beginning of a symbol anymore, so
(num) | [set channel$1( | [throw~ channelX]
or use [set $1-channel( as in the years before. ;)
A small hint: If you don't want to have a default channel to send to, you can use an abstraction with a [throw~ $0-dummy] in it and an unconnected [catch~ $0-dummy] as well to get rid of the warnings about "error throw~ 1001-dummy: no matching catch~". I used this approach for "schusslig 1.7 beta".
Or use a global [catch~ DUMMY] but make sure you really only have one!
Ciao
Frank
marius schebella wrote:
(num) | [set channel$1( | [throw~ channelX]
Where is this set-ability documented? Now I'd like to do kinda the same with dac~, but that doesn't work:
[set 4( | [dac~ 1]
Naturally a bit more elaborate in real life, bit the idea is to have an abstraction output to some channel in dac based on creation arguments...
What's different about dac~ compared to throw~, where can I read about it, and how can I do what I'm trying to (set the channel of dac~)?
On 05/08/2008, at 8.27, Atte André Jensen wrote:
marius schebella wrote:
(num) | [set channel$1( | [throw~ channelX]
Where is this set-ability documented?
in the help patch. if you right-click a throw~ object you can choose
"help" which will get you to the help-patch of the throw~ object-class.
Atte André Jensen wrote:
marius schebella wrote:
(num) | [set channel$1( | [throw~ channelX]
Where is this set-ability documented?
Should be in the help patch for throw~, otherwise file a bug report.
Help patches can be accessed for each object using the right-click context menu.
Note that setting a throw~ could lead to clicks if you do it while non-zero signal is playing, better to pan smoothly between the outputs.
Now I'd like to do kinda the same with dac~, but that doesn't work:
[set 4( | [dac~ 1]
Naturally a bit more elaborate in real life, bit the idea is to have an abstraction output to some channel in dac based on creation arguments...
use lots of:
[catch~ dac~1] | -- in one topmost patch [dac~ 1]
with:
[inlet~] [inlet] | / -- abstraction "mydac~.pd" [throw~ dac~$1]
What's different about dac~ compared to throw~, where can I read about it, and how can I do what I'm trying to (set the channel of dac~)?
about 8 characters ; pd source code ; probably not possible
Claude
Claude Heiland-Allen wrote:
Should be in the help patch for throw~, otherwise file a bug report.
Thanks everyone for the input, I've got something to work with. I now realize my question came out all wrong, I'm perfectly aware of the difference between dac~ and throw~, I was just wondering if there's a greater logic behind the fact that throw~ accepts set messages? Can anything general be said about which objects accepts set-messages?
Is that clearer?
Atte André Jensen wrote:
Claude Heiland-Allen wrote:
Should be in the help patch for throw~, otherwise file a bug report.
Thanks everyone for the input, I've got something to work with. I now realize my question came out all wrong, I'm perfectly aware of the difference between dac~ and throw~, I was just wondering if there's a greater logic behind the fact that throw~ accepts set messages? Can anything general be said about which objects accepts set-messages?
no. which messages an object supports is entirely up to the object itself. even though Pd's code has rudimentary implementation of an object-oriented inheritance concept, this is only used in a few special cases.
there are 3 ways to find out which objects accept a "set" message:
- read the help-patch
- read the source
- send a "set" message to the object and see what it does
fgmasdr IOhannes'
Atte André Jensen wrote:
Where is this set-ability documented? Now I'd like to do kinda the same with dac~, but that doesn't work:
[set 4( | [dac~ 1]
Naturally a bit more elaborate in real life, bit the idea is to have an abstraction output to some channel in dac based on creation arguments...
try the attached patch.. note, you can put the [r~]-[dac~] block anywhere, it doesn't have to be in the same patch.
What's different about dac~ compared to throw~, where can I read about it, and how can I do what I'm trying to (set the channel of dac~)?
[dac~] is for connecting to the soundcard - best practise is probably to have only one [dac~] object in your whole patch of patches, because then you can do nice things like have a master volume control.
[throw~] and [catch~] on the other hand are for routing signals.
imagine the [dac~] as your master mixing desk and P/A, and [throw~] and [catch~] (and [r~] and [s~]) as audio signal cables connecting your various bits of gear.
kristof lauwers wrote:
(num) | [makefilename channel%d] | [set $1( | [throw~ channel0]
Thanks, that works great. Must read up on stuff to understand...
-
Atte André Jensen -
Claude Heiland-Allen -
Damian Stewart -
Frank Barknecht -
IOhannes m zmoelnig -
kristof lauwers -
marius schebella -
Steffen Juul