Forums > Max For Live

Strange behaviour with pattr / autopattr & liveset

December 8, 2011 | 2:05 pm

Hi there,
using abstractions in my device, I put an autopattr in each of them and a couple of pattr stuff for all non Live objects too.

At the higher level, I put:
– autopattr @autorestore 0
– pattrstorage @outputmode 1 @savemode 2 @autorestore 0

I checked for the parameter mode to be enabled for all my stuff.

If I save my device as a preset, it works all fine.
If I drag’n’drop it from a track to another one… it works!
If I copy paste (command C & V) the device to another track, it DOESN’T work >>> WEIRD STUFF.
If I save the liveset without saving the device as a preset, it DOESN’T work.

What did I miss …?

December 8, 2011 | 4:29 pm

I didn’t explain correctly … and made a mistrake
With abstractions, ALL is ok.

I’m using bpatchers ….
Here is what I did:

main patcher)- autopattr + pattrstorage
/– subpatcher- autopattr + many bpatchers all with autopattr inside


It is "like if" bpatchers gave problems.
But at the top level in the client window of the pattrstorage, I have ALL my hierarchy etc.
But still nothing save with my liveset…

December 8, 2011 | 5:34 pm

oh… and greedy didn’t help :-(

December 8, 2011 | 6:01 pm

Quote from the M4L documentation

The autopattr object cannot be used to batch-register objects with the Parameter system.
You need to use individual pattr objects for this purpose.

December 8, 2011 | 6:05 pm

broc, you make me rtfm and it was deserved :p
I can really deal with that but.. I have to say, this proof of concept work no?

btw, I guess it is a side effect that stuck me…

I’ll use pattr.

(many thanks)

December 8, 2011 | 6:33 pm

@broc: no prob now.
still something strange.
pattr with parameter mode enable to 1 should expose parameters to Live (I mean, I should be able to modulate parameters which have a type like float, int..

it doesn’t happen :-(

Viewing 6 posts - 1 through 6 (of 6 total)

Forums > Max For Live