I need to send a bang through the OSC protocol. Is there a way to tell max not to evaluate a "bang" message?
let me explain what my small problem is,
sending "/x/y bang" evidently works fine, but what i need is "/x/y $1" and feed it a bang message.
tried converting to string, symbol, etc.. but max always seems to evaluate it as a standard bang.
i have no way to change the receiving patch to convert another kind of input to a bang (which would be more convenient, i agree).
thanks for any help and/or suggestions!
posts like these used to get a reply very quickly on the old max list, i guess no one comes to the forum..
well i’ve found my answer somewhere else and i’m posting it in case someone wants to know: there is apparently no way to tell max not to evaluate a bang message..
this is done very easily in PD sending a "foo bang" message, so i guess i’m just gonna translate my patch to PD.
this is actually pretty clever but it isn’t what i need. for many reasons i will not list here, i need $1 to be changed to "bang" inside a preformatted message box (/x/y $1).
thanks for replying though, i feel less alone! ;)
yeah, this is good in most situations but i really need that $1 in that preformatted message! ;)
i could probably use a workaround in the line of what you proposed, but i’m the stubborn kind and like my patches with less boxes.
since PD can do it so effortlessly, why can’t max? i don’t get it.. maybe i’m missing a bigger issue linked to the inward working of PD vs Max?
It does what you want.
brilliant! works like a charm.
Log in to reply
C74 IN YOUR INBOX
C74 RSS Feed | © Copyright Cycling '74 | Terms & Conditions
Let us tell you about notable Max projects, obscure facts, and creative media artists of all kinds.