jmmmp

in Pure Data it is possible to set the name of send/receive variables to each gui object, thus saving lots of time in connecting with extra objects. Is there such a feature in max?

I found the pattr object, but it doesn't do the same, e.g. it doesn't allow to link with several gui objects.

in Pure Data it is possible to set the name of send/receive variables to each gui object, thus saving lots of time in connecting with extra objects. Is there such a feature in max?
I found the pattr object, but it doesn't do the same, e.g. it doesn't allow to link with several gui objects.

object-internal-sendreceive

perhaps you can do it via thispatcher object (scripting) , first of all you need to give JS name (inside inspector) for each ui that u want to access

edit : then check help file for thispatcher how to access your objects

yeah . pvar is even more appropriate here !

Thank you all, that was a good suggestion. But nevertheless an instance of pvar is always necessary before each receiver - in the end one saves one object by not using "send", but has to use a "receive"-like object. Also, max doesn't allow me to have several objects with the same scripting name.

I'll try it this way. But this gave me the thought of, instead of having too many variables around, to try to put all these variables in a central place in the patch, so that they're easy to manage. Do you know any type of such a management system?

pattr still sounds good to me for the variable storage. If you post a representative slice of your patch, and people will be better able to advise you.

If you put objects in parameter mode (live.objects are already in parameter mode), you'll be able to see them when you view the "Parameters" window. You can change their names there if you're looking to rename things en masse. Drop an autopattr in and you have bidirectional communication; you can use pattrhub, pattr, and pattrforward to do that.

Alternatively, the sw object lets you link multiple controls with the same value without feedback problems, though it may not be what you're looking for in this case.

If you put objects in parameter mode (live.objects are already in parameter mode), you'll be able to see them when you view the "Parameters" window.  You can change their names there if you're looking to rename things en masse.  Drop an autopattr in and you have bidirectional communication; you can use pattrhub, pattr, and pattrforward to do that.

Alternatively, the sw object lets you link multiple controls with the same value without feedback problems, though it may not be what you're looking for in this case.


Thanks for your replies. I don't have a specific patch to show, it's more of a general concept I was thinking of - on one side to try to save on sends/receives and patching time, and on the other hand to have a central place where all these variables are accessible; ideally with one object that automatically knows how many variables exist, and can go through them. But as it seems such an object doesn't exist, so I'll stick to the traditional method, and keep track of my variables, trying not to repeat any names.

you'll probably prefer things like pattrstorage, autopattr etc. The Pd-style built-in option of send/receive for GUI objects has no real equivalent in Max, alas.

object internal send/receive