Automation to change plugin preset

[massimosammi]

Hello there,
is there a way to automate the change of preset (factory or user) for a plugin? For example, let's say I have Proverb on an aux track and I want to change from a hall preset to a room preset, and draw that change as automation in the sequence window. I saw that it's possible to change the parameters of a preset (time, damp, mix etc.) but I can't find a way to switch to another preset.
Thanks in advance!!

[Tritonemusic]

You can do that with "Automation Snapshot."

[massimosammi]

Thanks Tritonemusic!
I tried but for some reason it doesn't work. I followed literally all the step in the manual at page 802, but still it doesn't change the preset.
Any idea of what could that be?

[Tritonemusic]

First, make sure that Automation ("Auto") is enabled in the plug-in window (select "Play"). Place the Playback Wiper at the point you want the change, select the new preset, then take a snapshot from your plug-in window. Try setting it to "From counter to chunk end." It should change at that point. I tried it a few minutes ago, and it worked for me.

If you've already done that, I'm not sure what the issue could be.

[MIDI Life Crisis]

Alternately, you could instantiate two instances with the individual preset in each. Then use automation to mute and activate each at will.


Sent from my iPhone using Tapatalk

[Shooshie]

Thanks Tritonemusic!
I tried but for some reason it doesn't work. I followed literally all the step in the manual at page 802, but still it doesn't change the preset.
Any idea of what could that be?

Have you been to Automation Setup and selected "All" for controller and data types types? It may be only recording the basic pan, volume, expression, etc. You've got to be sure it's recording the parameters of plugins. In Automation Setup, you look around till you find what allows that to be recorded (sorry; it's not open right now, and that's a dialog I hardly ever look at), then be sure you apply it globally and locally to all tracks.

Also, be careful about your Snapshot parameters. Be sure you're not overwriting other things, and that each snapshot you do writes to the end of the sequence or to the end of the selection. You can take a snapshot of before and after (at) the change point, have one write back to the beginning and the 2nd one writes to the end, or whatever is appropriate for that situation in your mix.

It SHOULD work, but there are many ways to make it NOT work. Just look carefully at what you're setting, and don't hit OK until you've read all the settings and are sure you're doing the right thing. Once you figure it out, the rest will be fast.

That said, I realize I haven't used snapshots on plugins in a long time. There may be a bug I haven't seen. But I'd be willing to bet that it works.

Shooshie

[massimosammi]

Thanks so much Shooshie! I'll pay attention to all of that and let you know if it works.


Best,
Massi


- Late 2011 8,2 MacBook Pro, 2.4 GHz Intel Core i7, 16GB RAM, OS 10.10.2, 480GB Mercury EXTREME Pro 6G SSD OS Drive, 480GB OWC Mercury Electra 3G SSD - Optical Bay Sample Drive, DP 8.07, MachFive 3.2.1, VEPro 5, Vienna MIRPro

[dpg4macman]

Alternately, you could instantiate two instances with the individual preset in each. Then use automation to mute and activate each at will.


Sent from my iPhone using Tapatalk

I second that

[MIDI Life Crisis]

Alternately, you could instantiate two instances with the individual preset in each. Then use automation to mute and activate each at will.


Sent from my iPhone using Tapatalk

I second that

Probably gives you even more flexibility.