Using an obscure 32bit plugin (JuceOPLVsti), so I'm not sure if this is a problem with its coding or if I'm missing something re: how bitbridge handles presets.
 
Using Sonar X3 x64, I can't seem to get my custom parameters in this VST instrument to "stick" between sessions. When I open the VST the dotted-line dropdown menu at the top lists a handful of hard-coded default presets. If I hold Shift when I open the plugin I can access and save custom presets from bitbridge's. But even if I save and load from this list, it doesn't use the custom settings, it just loads whatever hard-coded preset I had selected last before saving the custom preset. It also does this when I first open the project. I've tried playing with saved FXP and FXB files too, but there seems to be no way to keep my custom settings when I reload the project.
 
I have run into this problem on a few other synths and effects, though I can get most to remember settings just fine. If it is indeed a bug in the plugin, is there a work around? For example, a way to dump all of the current parameters to automation envelopes?

You can freeze the track and then drag (shift-drag to lock horizontal) the audio to a new track.  At least that way you preserve your midi by unfreezing the instrument track.  Just mute one or the other depending to avoid doubling.  If you have any sends on the instrument track, you would need to set them up on the new audio track in order to hear the send effects.