Presets vs. automation in SX2

[cptgone]

Just insert an automation point at the beginning of the song (even make it change to a different program and back again

Of course, why didn't I think of that! That should do the trick.

Thanks a million, everyone, all great replies here!

[cptgone]

So Korg have provided a way to change a parameter in a "hardware fashion" but no way for the plugin (or controller) to send the complete state of the plugin as sysex like most hardware would, to be recorded?

I CAN send a snapshot from the controller.

But not from the plug-in itself AFAIK.

relaying MIDI automation to VST parameter changes

That sounds cool - maybe I should have a look at the Cubase MIDI Transformer.

[cold c]

So Korg have provided a way to change a parameter in a "hardware fashion" but no way for the plugin (or controller) to send the complete state of the plugin as sysex like most hardware would, to be recorded?

I CAN send a snapshot from the controller.

But not from the plug-in itself AFAIK.

Interesting but as you said that wouldn't solve your problem (if the controller has different values to the one in the plugin).

relaying MIDI automation to VST parameter changes

That sounds cool - maybe I should have a look at the Cubase MIDI Transformer.

To clarify, I wasn't referring to the MIDI transformer at all but to a useful property of certain plugins-

Some plugins have built in MIDI automation for their parameters (like your Korg plug.)

(For example, some of these plugins may use CCs to control a parameter.)

Some of these plugins allow this MIDI automation (from whatever source) to be picked up by the host as standard VST parameter automation (with the "W" button enabled), so instead of just recording MIDI automation, the host can record the VST parameter automation at the same time.

The advantage of this is that the MIDI automation can be deleted (because the VST parameter automation was recorded with the "W" button), but much more importantly, that the VST parameter automation that is generated allows rewinding to any point in the track without requiring any "snapshot" or similar to revert to the original state of the plugin patch.

To test if your MS-20 plug does this, simply route your controller to the plugin in the normal way, enable the "R" and "W" automation buttons for that plugin, press play (not record), move the knobs on the hardware controller (not the GUI), stop playback, disable the "W" button but leave the "R" button enabled, rewind and attempt to playback the automation.

If SX recorded the automation (if the knobs move on the GUI or if the VST automation lanes have a * next to the name) that is the method of automation you should use (instead of recording sysex) as it will allow the parameter values to automatically revert to the original values when you rewind your track.

I hope that made some sense.

[ahja]

Simple Program Change, isn't it?

[cold c]

Simple Program Change, isn't it?

Only if the program change "forgets" the state of the patch when going forwards/backwards through the presets.

If the plugin is correctly implemented it shouldn't forget its state.

However, I wouldn't be surprised if they implemented it like that.

[cptgone]

wow cold c, you're a fountain of knowledge! i'll try the automation bit - sounds like the best solution if it works.

edit: and it DOES! hurray!
thanks!

[cold c]

I just downloaded the demo, it looks like changing the patch up and down forgets the state of the patch unless "write prog" is clicked so that method as mentioned by Rozzer and ahja should work fine.

I tried recording the VST automation with the "W" button by assigning a MIDI CC to it but that didn't work, so if it works perhaps it only works from the hardware controller?

Anyway glad you got it working.