federico77

I was trying to build an external using rnbo which uses

sampling techniques accessing a buffer (referencing to the one on the main patcher as usual). Until I stay in the rnbo environment everything is ok, but after I try to export (succesfully) the patch as external (on Mac), there is no way (at least from what I am able to see) to create a reference to the same buffer as before. 

Groovy.jpg

I was trying to build an external using rnbo which uses
sampling techniques accessing a buffer (referencing to the one on the main patcher as usual). Until I stay in the rnbo environment everything is ok, but after I try to export (succesfully) the patch as external (on Mac), there is no way (at least from what I am able to see) to create a reference to the same buffer as before. 
What I am missing ? 
All the best to you, 



Dear friends, 
I was trying to build an external using rnbo which uses
sampling techniques accessing a buffer (referencing to the one on ... 

exporting-as-max-externals-which-make-use-of-buffer~

We're working on updating the documentation to improve the visibility of this information but, if you export a max external from a rnbo patcher that has a buffer in it that is "external", your exported max object should now have an attribute with the same name as the rnbo buffer. This lets you map that rnbo buffer to any max buffer by name. So, to achieve the same mapping as I assume you're expecting, you'd want to do "groovy~ @demon demon"

I believe buffer in rnbo defaults to external, but you can make sure by saying 

Hey Federico,

We're working on updating the documentation to improve the visibility of this information but, if you export a max external from a rnbo patcher that has a buffer in it that is "external", your exported max object should now have an attribute with the same name as the rnbo buffer. This lets you map that rnbo buffer to any max buffer by name. So, to achieve the same mapping as I assume you're expecting, you'd want to do "groovy~ @demon demon"

I believe buffer in rnbo defaults to external, but you can make sure by saying @external 1

Many thanks for your kind and precise response. 

One more thing, sorry for the stubborness :-). 

Even if I exported my object with "Write MC wrapper" checked, and the object indeed shows its multichannel properties, I am encountering difficulties on how to deal with messages. 

For instance, using attributes (like rate, Loopstart and so on) in order to pass arguments to my groovy instance, using dedicated messages like "deviate $1 $2" and so on.

For now this is the only way I've found to make it work. Not a big deal but using mc.target solves this issue. Maybe, you know more hidden tricks then I do (sure you do .-))

groovy-help.png

for your invaluable support. Happy Patching.

Dear Alex, 
Many thanks for your kind and precise response. 
Everything is working nicely now. 
One more thing, sorry for the stubborness :-). 
Even if I exported my object with "Write MC wrapper" checked, and the object indeed shows its multichannel properties, I am encountering difficulties on how to deal with messages. 
For instance, using attributes (like rate, Loopstart and so on) in order to pass arguments to my groovy instance, using dedicated messages like "deviate $1 $2" and so on.
For now this is the only way I've found to make it work. Not a big deal but using mc.target solves this issue. Maybe, you know more hidden tricks then I do (sure you do .-))
All the best to you and, thanks again 

 for your invaluable support. Happy Patching. 

Exporting as max externals which make use of buffer~