I asked the same thing. But maybe again this is one of those obvious questions that needs to be repeated. This kind of stuff IS very annoying, especially when it seems to be with a singular DAW software, maybe even a singular computer. But my life became so much easier (and more productive) after spending time to learn Reaper. Huge liberation. Either way, keep us posted about this, and good luck.
Yes...I've checked in the cold light of day & I'm certain that my setup is correct.
Just out of interest...I notice with Reaper that before messing with Neb instances even with the different names as installed the Nebula3 Reverb saved in 32bit will open Nebula3CoreII64 in 64 bit.
It's a little annoying that I was still up & desperately trying to fix this at 4 in the morning when it was a bug of some kind but there you go....I should have tested another DAW earlier.
It's really not the end of the world...unless Acustica has any great ideas to fix this I plan to bridge the 32bits so I can open existing projects, but also have the 64bits with tweaked naming so I can start using the 64bit vs.
My "Magic" Id's are actuall different between 32 & 64 bit as this was how they installed, but it was my understanding there is a hard coded ID that the DAW uses & this "magic" one was more for Nebulas own reference.
I tried changing one to match but still no go.
Just to confuse things further I should perhaps mention that there are also Neb Server (exe) xml files in Nebtemprepositry/server & on these the 32 & 64 magic ID matches & they are both the same as my 32 bit instance xmls.
Just tried this and even with Neb3 pro setup only installed (no server update) Cubase doesn't replace 32 bit with 64 bit....Reaper does though I did need to change the name to match this time.
I'm stumped....would appreciate it if Giancarlo could confirm absolutely that the 1.3.492 or 1.3.504 IDs are the same for 32 & 64 bit or if anyone else can let me know if they have this working on Steinberg host.
This is a long shot, since it seems to be a Steinberg issue and not totally a Nebula issue.... Have you tried installing ONLY the 64bit version of Nebual and ensuring that the dll and xml names are identical to the 32bit? Maybe if it has no choice it will load correctly...?