Throw~ /Catch~ equivalent in Max?
Hi
I am following a tutorial on Youtube but it's PD and I am trying to recreate the patch in Max. What is the equivalent for the PD throw~ and catch~ objects?
send and receive. because non-MSP send and receive will also forward signal connections.
for the technical difference between send and send~ allow me that i am pointing you to the forum search.
i looked at the pd helpfiles for both and i suspect there are minor differences anyway.
if you need to rename the throw~, then you have to use [forward] in max.
if you stick to the send~/receive~ (with the tilde '~' symbol, similar to the original throw~, as this is the normal way to delineate between signal-handling and regular objects), you don't need to worry about using [forward], you can use the 'set' message like with other named contexts in max:
technically, aren"t tapin~ and tapout~ somewhat closer analogs to throw~ and catch~ ?
i could be wrong, but this article seems to imply they're more like send~/receive~:
https://hvc.berlin/Puredata/puredata-send-receive/
(maybe there's a delay introduced somehow we're not aware of, but it's true i'm not actually familiar with PD anymore, apologies in advance if i misunderstood)
(also, wasn't trying to contradict Roman 😅
but felt maybe there might be a simpler answer to try first.)
send~... i first wrote that... but later changed my post to the non-MSP objects, because the pd helpfile confused me lots about the differences among the pd objects. :)
maybe the best advice is always to point out that there are mostly no 100% identical objects, which means that you have to make your own abstractions and check stuff carefully, message by message.
"technically, aren"t tapin~ and tapout~ somewhat closer analogs to throw~ and catch~ ?"
pd´s tapping buffer is delwrite~ i think.
well, actually it is quite different, too.
I used send~ and receive~in the end. That worked. The PD tutorial also used delwrite and delread for a buffer which I replaced by tapin~amd tapout~