Are these problems also present in 32 bit environment? Unfortunately, as you said, there is not much what Nebula Set-ups can do here - it works the same way in 32 and 64 bit environment.Grim wrote:I am having a recurring problem when using set-ups to create different instances of Nebula.
I believe this is a problem specific to Cubase and the way in which it recognises plugs. I'm sure this is not any fault or bug with Neb setups but just wondering if anyone might have experienced the same thing and worked out exactly the cause or possible workarounds.
I first had the problem in a big way when trying to switch from 32bit to 64bit Cubase. My projects would open with wrong Neb instances and init (as obviously they couldn't find the correct preset). This was despite them being created with exactly the same names. I ended up bridging 32bit Neb to open old plugs and creating new names for 64bit and I gradually moved all instances across to 64bit only.
However despite now only having the 64bit instances I am finding that every time I use Neb Setups to update the library of an instance, something changes and if I open a project with that particular instance previously inserted, a different instance is loading. To further confuse the situation, it doesn't seem to do this with all instances!
Obviously this is an annoyance as I never know if re-opened projects are missing processing without opening all my Nebs.
Maybe you could make a test with Reaper, to be sure if it is Cubase only problem. I am not sure, but I think there is some kind of every VST plugin - maybe DAW is confusing instances because they all have the same id !?! Just speculating!
Maybe Giancarlo has some ideas ?