gbravetti

Is there any difference in terms of performance/reliability on connecting objects using cables vs Send and Receive objects?

wired-vs-wireless

The main difference seems to be the order of operations : with right to left order or trigger, you can easily control the order, but it gets difficult with send / receive. I think I read somewhere that data is delivered to s / r pairs using the order of creation of the objects in the patch.

Thanks, I was worried about cpu usage or reliability.

In older versions I remember that using S and R objects to connect objects to the Preset object´s include - exclude didn't work. Do you know if that works on Max 7?

The send/receive with preset doesn't work. You could try [pattr] and [pattrstorage] to avoid any cable connections.

If you don't like that, and have to connect stuff to [preset], to avoid having a visual mess with lots of cables, you could change the opacity of the cables' color, to barely see them.

Personally, I've gotten several strange results when using the send~ and receive~-objects. One time I got totally twisted values (from a line object, I believe), and another time my signal got amped up significantly. Has anyone gotten similar problems?

@Jonas Mangussen - If you are have more than one [send~] with the same name, the [receive~] will output the sum of the signals. Maybe this happened to your patches?

Not impossible, in fact I used it inside a poly~, so I guess that means sends are a bit sketchy to use. I'll keep it in mind for the next time I need the objects.

Not so sketchy as its desired in some cases, like the synth I've made. The common practice seems to be, when the new poly voice is created, using thispoly to find its index & give the send~ a unique name.

Not so sketchy as its desired in some cases, like the synth I've made.  The common practice seems to be, when the new poly voice is created, using thispoly to find its index & give the send~ a unique name.


For abstractions (and poly abstractions) just use the #0 argument to make send/send~ receive/receive~ local: [send~ #0FooBar]. No need to look for the voice index. Max will replace #0 with a unique identifier.

That's amazing! Thanks a lot, guys! I'll definitely try this out later.

"For abstractions (and poly abstractions) just use the #0 argument to make send/send~ receive/receive~ local: [send~ #0FooBar]. No need to look for the voice index. Max will replace #0 with a unique identifier."

wired vs wireless?