Message to "set" a ghostbox or change an object on the fly
Every now and then this comes across my mind. Is it possible to change an object with a message. For example i have a [cycle~] and i actually want it to be a [phasor~] I know this can all be done with [this.patcher] and js but it would be nice to change it with a simple message.
----------begin_max5_patcher---------- 605.3ocwV98aaCBDG+YGo7+.x8kUorJarcR71S6efIMsGmplHlKIrZCQF7V5 p19aeGfc9cUS6bZUTfvwE368gyG9ggCBBmoVC5PxGHeiDD7.ZIvYyZInyPPX EacQIS6bLrPUUARS3n1IMvZiahupp.yRgbAoTbGPvepIuaVigHjZCv3jYJyR RgRJgBCvIFE5CPzrJ.mZ80aVwRA5gpQ5V1zNqxlJUioDLNYD0YdtRZzheCVi wza1XeEyTXEy2qwcyGgoSxv4IYQ11XmyjwXK41cWLIpGW77oZAqLbmsWH618 3NqBtyU0re79rPms+LbfsG6Fc1HsBzZ1B3XjtPgeX7EfgXCi+twiU0fFODXF gRtSDRScQXdhsMpsYa3sOBiOIBiuIKOKd5jtI8+Ay8q.+VDFtc8NAiSl3vZV riwQ9touDFSOAioWVFWbeQI7zPNO0m.M9MixzwdJS8TdZ+R43K.k0E0hUFBG vMFqMnLpQjVaR3WbXNqozPli1w3IhPwuGbZ7Zj7R8kF70In9Gi5Otlew457G gqlc459URdMvZTtCjYtmanSG2uXM8+HeEYDtDGiU6kWtHApeDRQepKfNFRiN SPQ8UOG6GD0WWPkrwUM6mch5pOak0dgKI7i1lq9hsEjbuExsG.YunbWVe3aP 3VJ6DGfdspotnam80ywZmaiNNnMBoqd6NNgmu640RAmCx8dIfJAekRHMsBIY JlwZS3hrcIXpV2nihhQu.UGeNpN+4JZ5Dunmj5DMMeyndQzomkpSdtptWzV9 EQZsHjl5Jp2lE3Fchb4gCvt+A.BQH9J -----------end_max5_patcher-----------
(after i made the example) Ok, it’s not that much of a hassle but it’ll save some objects plus when you change layout you wouldn’t have to update the positions ofcourse this can also be js’d but that is too much trouble (at least for me now)
You can do this with poly~ now. Check out the DynamicPoly subpatch in the poly~ helpfile for more details. Hope that helps.
Thanks for your suggestion but that was not really what i meant because you would still need to have a patch for each object object (plus additional ins/outs) and so forth which is too much of a hassle :)
(Or am i missing something here?)
"patchername cycle~.mxe" didn’t work
how do you intend to use this? If you use this in performance you will get clicks as the DSP chain will be interrupted when inserting new audio objects… poly~ is definitely a good way of approaching this for live purposes. I am afraid there is no way around patching, yet ;)
Ehhmmm, you definetely got a point there but it’s something that occurs every time i’m in lazy-mode and fooling around with a new patch and it doesn’t really have a clear goal. That’s when i’d like to have a way to change stuff fast(er). Nevermind, i think i’ll just create some abstractions for this since the applications are limited but all in all it didn’t seem that illogical to already exist in a hidden message somehow/where.