It's free, but only available for Image-Line customers: If anyone wants to test it, here's a copy. Whether it's VST hosts, racks, whatever else. I'd really love to have this work, or just find another solution for some really simple parameter automation.
#Plogue bidule blogspot how to
In my case, this occurs with Minihost Modular, which seems to be the slickest and easiest option to automate plugin parameters I've found so far (even if I still haven't figured out how to use a simple LFO with them yet). I'm using foobar v1.6.14 and v9.0 of the plugin. Meanwhile, the 32-bit equivalent works with the old foo_vst plugin. Unfortunately, as in sveakul's case, certain 64-bit plugins give an "Unrecoverable playback error: VST refused audio stream format" error. I e, the brain becomes unreliable if the comparison of two sounds are more than 10-15 seconds apart. I experienced significant lag of a couple of seconds even with just one VST in the chain compared to the VST 2.4 immediate response as outlined above, but perhaps this is unavoidable? For "play" of a track this is not such a big deal, it's with interaction, such as changing a parameter where the lag between trying different settings becomes more of a problem, due to the brain's need to use working memory to make reliable detailed comparison of auditory signals. Thank you for the reply and for the update! It would be fabulous if you can create a work around by keeping a persistent process. The current solution can indeed get nasty with multiple VST effects in the chain. I can probably work around them by keeping a persistent process. These are due to startup of VST host process per DSP instance. Quote from: Peter on 11:40:41 Sorry about the stupid regression with missing popup for simple effects, fixed just now in 0.8.
0 kommentar(er)
