At this point I should be Googling what distinguishes a client vs a server. I have decent pc skills but this one has me.enriquesilveti wrote: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)
Firstly, I don't know how to know if I'm in local mode on the server.
Lately I have been running them both in one project. Not my usual way but it works well for some circumstances. Depending on which version of Cubase I open one of these doubled projects in - the non-native Neb will open automatically in Jbridge and work just fine. V.480.
If I open X86 server first only the X86 Nebulas remember the project preset. The X64 * up init, but I can still get to the library.
If I open X64 server first only the X64 Nebulas remember the project preset. The X86 * up init, but I can still get to the library.
This happens the same way no matter which Cubase I open after launching the server.
64 server = 64 Nebs good, either version of Cubase whether the Neb 64 is native or jbridged in Cubase 32.
32 server = X86Nebs all remember. No go for the 64.
I would love to be able to take advantage of these new and upcoming benefits that the server will support.
I am concerned that a workaround is to use server as a bridge and leaving One Only Neb Reverb on the PC as I have used hundreds of instances of 32 and CoreII64 Nebs in the 2 Cubases and I can't afford to toss that.
Thanks for all your help.
Nebula sound, and community, is certainly worth the effort.