Rodrigo

So I've started using autopattr to do macro-type morphing of presets, and I've run into a massive problem, because every adjustable parameter in my patch (and there's tons of them) is named for MIDI-learn reasons.

I started playing with autopattr/pattrstorage thinking that the tickboxes in the window lets you select what parameters to control from there, but that doesn't appear to be the case. (What are those tickboxes for?)

So I stored a default preset, and one preset to morph to, but it's morphing every single parameter in my app.

Is there a way to exclude named parameters from autopattr?

If not, does that mean I need to connect a cable to every single thing I want to control in my patch?

So I stored a default preset, and one preset to morph to, but it's morphing every single parameter in my app. 

Is there a way to exclude named parameters from autopattr? 

If not, does that mean I need to connect a cable to every single thing I want to control in my patch?


excluding-named-parameters-from-autopattr

I just started trying to connect the parameters I wanted to control using pattr but I can only use one per object?

I have waaaaaay too many objects to connect everything to the exclude outlet of autopattr, so is there a way to connect what I want to control to a single thing (and still be able to interpolate things).

Maybe in that case is best to use pattrhub and pattr objects instead autopattr, so you can choose your specific parameters and not automatically...not sure if it suits your purposes...

Wouldn't I need one pattr object per object I want to control still? It's probably over 50 objects I want to control... and more down the line.

Autopattr would be perfect if I didn't already have scripting names in place for midi-learn type stuff.

Wouldn't I need one pattr object per object I want to control still? It's probably over 50 objects I want to control... and more down the line. 

Autopattr would be perfect if I didn't already have scripting names in place for midi-learn type stuff.


can you use the "subscribe" and "unsubscribe" commands to [pattrstorage]?

If it works, you may lose your stored settings...changing the structure seems to do that.

And yes, what are those tickboxes for, if not to select/deselect?

Not sure how the subscribe stuff is supposed to work. Documentation isn't very clear/good in that regard.

If I made a pattrstorage with @subscribemode 1 and send it a message "subscribe named_parameter", then double click it, it doesn't show up as one of the things to control.

Sending "getsubscriptionlist" tells me "subscriptionlist named_parameter" but I don't what I'm supposed to do with that information.

Not sure how the subscribe stuff is supposed to work. Documentation isn't very clear/good in that regard. 

Sending "getsubscriptionlist" tells me "subscriptionlist named_parameter" but I don't what I'm supposed to do with that information.


It looks like subscribe is working now. Not sure why it wasn't the other day. I hate these kind of objects where you can't 'see' the stuff that's happening..

Nope, I take that back. Even with pattrstorage in subscribe mode, it saves seemingly random parameters.

Can anyone take a look at this and see if I've set it up correctly?

that looks right to me ... am I missing something what is happening exactly? unsubscribed objects are still getting their states stored?

you also can send a [active myScriptingName 0] to the [pattrstorage] object.

you also can send a [active myScriptingName 0] to the [pattrstorage] object.
perhaps this helps.

Yeah unsubscribed stuff is still getting stored. Not all of them though. I haven't figured out the rhyme or reason to it. I even set up some print objects to make sure I wasn't imagining stuff.

@lee, are you saying to send that for every named object I don't want to control? Or are you saying literally send that message (myScriptingName).

Ok I understand what you meant now. Basically making everything inactive. The problem is that everything is named, so that would be a huge list. I'd also need to keep adding things to it every time I add new objects etc...

I've just made an individual pattr object for each parameter I want to control. Tedious as shit, but at least it shouldn't randomly save/store stuff.

Ok having pattrs for everything is working groovy, but now I'm back to square one (in terms of the problem) as I now want to have two sets of presets that interpolate.

Can't have two pattrstorage's with their own pattrs, and the subscribe thing seems to not do anything. Making (and maintaining!!) a list of inactive object is not an option at all.

How can you have multiple sets of preset interpolation in the same patch?

Ok having pattrs for everything is working groovy, but now I'm back to square one (in terms of the problem) as I now want to have two sets of presets that interpolate. 

Can't have two pattrstorage's with their own pattrs, and the subscribe thing seems to not do anything. Making (and maintaining!!) a list of inactive object is not an option at all. 

How can you have multiple sets of preset interpolation in the same patch?


Right, I understood 'subscribe' to mean you could subscribe to named objects, not named pattrs.

That would do the trick, I just need to redo all the bits for that to work.

Is there a way to store/keep the interpolation mapping settings? If I change the subscribe mode I'll lose all my table/interpolation data.

Right, I understood 'subscribe' to mean you could subscribe to named objects, not named pattrs. 

That would do the trick, I just need to redo all the bits for that to work. 

Is there a way to store/keep the interpolation mapping settings? If I change the subscribe mode I'll lose all my table/interpolation data.


I'm a little confused about what exactly you are trying to do in terms of your last question...

If you want to disable some clients *while* recalling data for others, *and* have the option to chose which arbitrarily, then I don't think the un/subscribe method will really solve your problem. You may be better served by looking at the "active" attribute as mentioned above - it is possible to un/activate entire patchers if that is any use. Check the pattrstorage help 'scope' tab (in Max

I'm a little confused about what exactly you are trying to do in terms of your last question... 

If you want to disable some clients  *while* recalling data for others, *and* have the option to chose which arbitrarily, then I don't think the un/subscribe method will really solve your problem. You may be better served by looking at the "active" attribute as mentioned above - it is possible to un/activate entire patchers if that is any use. Check the pattrstorage help 'scope' tab (in Max
 6 at least)...


Nothing that fancy. I have two main sections of my patch. I want to have presets for each section, and be able to interpolate between those presets (independently).

Everything I tried (before) would either grab every named object (everything in my patch is named for MIDI-learn) or just one set of items (that had pattrs connected).

This subscribe mode with named pattrs seems like it will do the trick.

Nothing that fancy. I have two main sections of my patch. I want to have presets for each section, and be able to interpolate between those presets (independently). 

Everything I tried (before) would either grab every named object (everything in my patch is named for MIDI-learn) or just one set of items (that had pattrs connected). 

This subscribe mode with named pattrs seems like it will do the trick.


Ok. From that description it sound like you're sorted then... Cool.

Sorry to bump this old thread but I had the same issue - how to exclude parameters from autopattr.

The answer seems to be connect parameters to the centre left output.

Fingers crossed I think this is working!


I connect the second left outlet from autopattr to exclude the object, which seems to exclude the object from pattrstorage ( verified when i double click it). However when i recall presets the object is still included.

Am i missing something or is this a bug ?

I connect the second left outlet from autopattr to exclude the object, which seems to exclude the object from pattrstorage ( verified when i double click it). However when i recall presets the object is still included. 

Excluding named parameters from autopattr?