pattr object for multiple used patches

5 posts / 0 new
Last post
Phatline
Offline
Joined: 11/08/2009
pattr object for multiple used patches

Hi, i have programmed this device:
http://www.phatline.at/m4l/NochSimpler1.amxd
It uses the pattr object to save a string with the liveset (a path to a folder on my harddisc, where i have samples...) The device work great if I use one Instance, but when I put this device on a few miditracks in my Ableton set, then it dont save the path with the Liveset.
So how do I name a Max4Live "pattr" object, or which Attributs I have to set?
I simply want to multiple use this patch. I dont want 7 patches for 7 miditracks, with 7 differnt "pattr" names- any Idea?

mchenetz's picture
mchenetz
Offline
Joined: 09/17/2009

I am not a pattr expert by any means. But, I think the problem may rest in the fact that you named the pattrstorage. This would create the same json file for all instances. I think, if you leave the name out, after, "pattrstorage" then it is supposed to create a semi-random name. The other thing you can do is prepend the --- before the name and see if that makes it a unique instance.

Phatline
Offline
Joined: 11/08/2009

solved.

the pattrstorage object is useless.
the --- bevore a name is also useless ofcouse- Ableton dont save any data (it seems that ableotn not regonizes the object when a --- is in front of the pattr .

but when i dont give the pattr object a name -only type "pattr" - then like you said, a random name is given - and now the clue: when i load multiple patches in my setup then the pattr objects getting new random names :-) - so givin no names is the best way!

mchenetz's picture
mchenetz
Offline
Joined: 09/17/2009

Yeah, I figured the no name thing would work... It does state that in the docs, that none of us ever read. :-)

Phatline
Offline
Joined: 11/08/2009

i read the docs... but most of the time I dont understand them, because of the English Language...
And then is the problem -> what works with MAX and in the other side what works with MAX4LIVE --- they are often much differnt... so things like loadbang, loadmess, send receive... that are things that works well with MAX not so with MAX4LIVE... but in the DOCs doesnt is documenteted that they make troubles... so nothing is really sure... so a small trouble, that could solved with the docs can take you 7 ours of Trial and Error - because of "you read the docs, follwed them, and error with them" yep the doc take me much time of my live haha