Dynamic synchronization of sevarl mc.function
Hello, I am new to this forum, so please be clement. I don't like to be reductionist, but for reasons I hope you understand, I have chosen to simplify my question by giving a simplified example that clearly illustrates my problem.
I have a patch with three identical mc.function objects (same range and domain), each with two channels. Every time I modify one of these, the remaining objects must show the same curve for their respective channels, so that if I modify the curve of channel 2 of “funcA,” the same curve is faithfully reproduced in channel 2 of ‘funcB’ and “FuncC.” It's a sort of virtual link. I'm trying with a pair of sends and receives, but I'm not sure what the right formula is to send as a list to the various func. At the same time, I don't think I'm that comfortable using pattr. I've been advised to use a buffer to record the curves each time, but the original patch is already quite heavy and I don't want to complicate it further.
If it helps to understand the context of the general problem, the patch containing mc.function is loaded by poly~. I'm sure there's an easy way to handle this, but I don't know why I ended up in a loop of unnecessary complications that I can't get out of. Thanks in advance.
Basically you want multiple [mc.function] to all always show the same functions, right?
You can use the copy and paste messages, although my implementation will also make all [mc.function] to display the same channel, which might not be desirable.
The pattr option doesn't have this flaw:
and you can always add @invisible 1 to make your [pattr] to hide from [pattrstorage] if needed.
Yo! my man! That's exactly what I need!
Until now, I've completely ignored the use of copy-paste messages. Although the pattr version seems to be quite elegant and convenient, at the moment I'm forced to choose the first option. The reason is that pattr doesn't work for me: as mentioned, the patch containing (a single) mc.function is loaded by a poly~ object (designed to dynamically load various patches via patchername, hence the need to resolve the narrow issue internally within the patch). The requirement, therefore, is to have the same envelope for all poly~ items that load this patch, which is easily achieved using your first suggestion. In this case, pattr does not seem to work. But that is a different story.
I don't see why the pattr option wouldn't work in your case:
Something must be wrong with my general patch, maybe. I tried using @invisible 1 but something is probably conflicting. In any case, thank you very much for your help.
my bad, just tried again and pattr works fine as well