after cuda fix I'll check this metaplug issue. It's maybe related withau porting. For sure metaplug is not doing all things an host is supposed to do, it's an early development. Just think to jbridge and the time required for fixng all issues with all possible plug-ins!
I hadn't gotten the chance to try it before it stopped working for you all, but a question: Isn't this the same thing as using a crossover type plugin or M/S encoder and just routing those into programs?
ok, let's wait for them a bit, maybe they need to fix some little detail and refine little things. At the moment it's the only host with this strange behaviour, I don't think it's related with our code (vst protocol is not very documented, but it's the first time I hear about a frequency rate issue at preset initialization). All they need is to set frequency rate before calling setchunk.
You could help me a bit, put <DL> 6 </DL> in your Nebula3 Reverb.xml, and attatch here the log file.