An alternative way would be to put the devices in a rack with different settings and switch between them with the chain selector. However, having multiple instances of the devices would consume more resources.

I think that pattrstorage works only for single devices. But you could have an additional device on the track to control/switch the presets of the other devices. So the track preset would be implemented as a combination of individual device presets.

but wait, how to get a control of live devices presets in m4l? i couldn’t find any info about it.. it seems very simple idea what i want to do.. just change for example, effect rack preset from one to another whit click of one button, cos switching between them with the chain selector is way too CPU hungry

is there any way to do it with M4L device? or is this not implemented in API features yet?

Why don’t you just save all the effect presets as separate devices in a rack, and use the API to move the chain selector. That should amount to the same thing, not use much extra CPU, and will allow for crossfading

At a guess – you need to set up a pattr to store a blob, then construct a list of all the parameters you want to save, probbaly something like live.path value = parameter value pairs.

I dont beleive there is any way to do this more directly.

The other headache you will have is having stored all of those parameters in this way you are going to find it rather hard to track path changes should that be needed. If a user moves a device, then its path will change and there your parameter snapshot will be invalid as quite likely another device will now be at the same path, or no device at all.

Path tracking will be a complete pain and probably a huge resource hog for large number of parameter paths, so perhaps an altternative may be to save the list of device names along with the paths and paremeters an then just use the list of device names to validate against the current list of device names before applying the parameters as this should give you a reasonably indication of an incompatible device change.

BTW – If you dont have any kind of validation, then you could run risk of setting parameters to values that might be rather hazardous to you ears and sound system :)

Also you cant access devices inside racks, therefor3e you will not be able to recall their parameters, only the parameters for the rack knobs (which may be sufficient).

BTW – using hidden multi-sliders may be a good approach to simplifiy some of it as well, but I havnt tried this.

I’ve created a device that will probably do what you need. It allows you to assign a single knob to 8 different parameters of a single device, and have different reaction curves for each one of those 8 parameters. Its similar to macro mapping, but with more possibilities (e.g. it gives more fluency than just assigning a lo and hi value: everything is mapped via x/y).

I am trying to get this stuff together to release this weekend, but if your interested, pm me and I’ll send you a version that you can mess with prior to releasing the "dumb" version.

Attachments:

Try this out….I don’t have time to test it completely right now, but I’ve been using it for a couple of months and it works fine. Its part of a much larger patch, but I’d planned on releasing it standalone as I think people might dig it. I’m currently rethinking about how I’m going to deal with devices, so it may change drastically soon.

Since I ripped it out of a larger patch, I had to add a few things to the js that are normally provided by other scripts in the larger patch. Let me know if its what your after, and if so, I can ammend the js so that it is a little more transparent.

As it is, it should generate a list of devices upon instantiation. If you change things in your set, you’ll have to reset the plugin by hitting refresh. This can also mess with your assignments. If you have a static Live set, though, it should restore values between load states. Also, it may give you some clues on how to get pattr working for you in your own patches.

Attachments:

As it is, it should generate a list of devices upon instantiation. If you change things in your set, you’ll have to reset the plugin by hitting refresh. This can also mess with your assignments. If you have a static Live set, though, it should restore values between load states. Also, it may give you some clues on how to get pattr working for you in your own patches.
[url=http://www.royalapollo.com/]usa casino bonus[/url]
[url=http://www.jackpotcapital.com/]Accepting US players[/url]