Direkt zum Inhalt

Change to the way moving a vst from engine to daw works

Posted

Not sure if this is possible at all, but if it is, I'd love to see it implemented.

I have a couple of vst and au that only allow one instance to be loaded. The main one I use all the time is the vst/au control plugging that controls my access virus hardware synth.

The main issue is that only one instance is allowed at a time. It seems the move from engine to daw/drone, loads the plugin in the drone and configures it before unloading the plugin from the engine. On the virus, that causes the plugin to fail. The only way I can move the vst is to save the patch, unload the plugin from the engine/instrument track. then load it as a new vst in the drone. Lastly loading the patch I'd forgotton to save in step one ;)

Is there anyway the migrate function could be changed to unload the plugin before loading it in the drone?


Do., 01.12.2016 - 08:15 Permalink

This would make sense indeed, also for not using twice the memory during the transition. 

I'll have to check. If it's a simple rearrangement of code lines, it'll be a quick fix. Can't make a promise.

So., 11.12.2016 - 21:19 Permalink

Just checked the source code and it's already unloading the plugin before loding it in the DAW.

Maybe it's happening faster than the plugin can deal with?

So., 11.12.2016 - 22:12 Permalink

I'll try it again as I havent used that feature for 'years' due to it never working with the virus, maybe youve changed it since I tried it last

Mo., 19.12.2016 - 00:20 Permalink

havent been able to test it with the vst, but didn't work with the au. In fact got a different result with the current version of synfire. In synfire it seemed to do its job, the virus device seemed to get unloaded and then reloaded in synfire (very quick). However shortly after, Live crashed before I could switch to it.