When I open existing projects in either 32 or 64 Cubase, that have a mixture of regular and jbridged Nebulas, whatever server I have running determines which Nebula project presets are remembered.
IOW 64 bit server launched before starting Cubase = all the Neb 64 bit presets are there. Neb 32 bit shows up init. 32 bit server launched before starting Cubase = all Neb 32 bit presets show up, but all Neb 64 bit presets are init.
Don't launch server before Cubase = all existing project presets show up fine.
This happens in 32 or 64 bit Cubase jbridged either direction. MAGIC numbers in XML files match (dll folder and server folder XMLs).
Any ideas what I might be doing wrong? I'd like to be able to use this upgrade on all my old projects, per all the previous Neb 3 Pro upgrades.
yes, remember that the OLD library was 32 bits only. Download eq from the current library (just an example) and tell me if they are fixed
edit: check that you don't have multiple nebula3 dll copies in your computer. Anyway it's possible your old projects can't work using the new server feature for somewhat reason. If you used ALTERNATIVEDATAPATH or similar things in your nebula xml, they should replicated in nebulaserverwin.xml and nebulaserverwin64.xml
As much as I'd like my old projects to work with the server version, being that jBridge isn't Giancarlo's responsibility and was a workaround to begin with, I don't think he should be expected to ensure compatibility.
woeischris and Raynorshyn. We have here Jbridge but not Cubase, we could try with Reaper. I just need to know if you are loading Nebula Client x86 and Nebula Client x64 (Jbridged to x86) at the same time in the same project with a Nebula Server online (in local mode as well)
Enrique Silveti. Acustica Audio customer and technical support.