bugs in MaxMSP 5(.0.6)
Mar 11, 2009 at 4:27pm
bugs in MaxMSP 5(.0.6)
I’ve recently noticed several bugs related with both MaxMSP 5 in general, but some particular ones which have only occurred in the latest release MaxMSP 5.0.6..
The first of them is an issue related with the multiSider object, that is usually declared as an unexistent object. When you load it from a new ordinary object it tends not to load properly. If you make it from your GUI it loads always properly. But when you Re-open the patches, the object is not usually recognized (sometimes it is, but normally I have some problems with it). I’ve experienced this in my laptop, and reported to a fried, who told me that this happened also in his computer, so I think that this might be a bug.
Another thing, is the preset object, which tends not to save all the info in the patch properly, which leads to problems in recalling values.. I know pattr tends to work much better, but for noobs like me preset is simply much better..
hope to have helped the community of this awesome app to grow
Mar 11, 2009 at 4:54pm
There’s no reason that pattr has to be difficult for beginners – in my workshops, I teach it very early on with no troubles. And you can now use the preset object WITH pattr, which is even easier.
1. for each UI object whose values you want to save, open the Inspector and type a unique name (e.g. dial_1) into the “Scripting Name” column.
2. add a pattrstorage object to your patch and give it a name (e.g. mypresets)
3. add an autopattr object to your patch.
That’s it. It’s done. If you’d like to use the preset object to manage presets, you have to exert yourself just once more.
4. add a preset object to your patch, select it, and then open the object’s Inspector and type the name you gave the pattrstorage object (in the example above, it was “mypresets”) into the “pattrstorage” value column.
The preset object is now in charge of your pattr-ized Max patch.
Now, that didn’t hurt a bit, did it?
Mar 11, 2009 at 5:30pm
I maybe get conflicts only when using preset isolated – it may need the pattr to work properly (something that I didn’t know, so it might not be a bug at all, althogh the preset object was supposed to work properly alone)..
Also, if anyone knows something about the multislider issues that I’ve posted, please say something
Mar 11, 2009 at 5:52pm
Give us some steps to follow and what you’re expecting to see.
Mar 11, 2009 at 6:09pm
it is happening me the following:
when I have huge patches and use preset object, not all the info is stored (solution: use pattr or even pattr+preset)..
then, about multislider:
1a, when I post a new ordinary object, and tipe there the name of the multislider, sometimes (not always), there’s nothing loaded as an object and there is even an error message in the console referring that there is not an object with that name (even when the name is typed correctly).. this is used to happen mostly in the 5.0.6
1b, then when I load the object by the GUI, it usually loads properly
2 – when the patch with a multislider is loaded properly, and I re-open MaxMSP, sometimes (not always), I get an un-identified object in the Max GUI (like the are of the patch with a box and the name of object inside with some lines)
Mar 11, 2009 at 6:45pm
Maybe something is wrong with your install. Do you see any errors about multiple files with the same name?
I would try an uninstalling and reinstalling MaxMSP. If you need more help, please write in to support@
Mar 11, 2009 at 10:56pm
Have you by any chance saved a Max patch called multislider.maxpat?
Mar 12, 2009 at 7:53am
You must be logged in to reply to this topic.