You need to be more specific as to the problem. In general, nebulatemprepository is created on the C drive by default. Inside this folder is another called acustica. Copy that to Cubases vst folder or have Cubase point to it with its vst path settings. Open Nebula in Cubase. This will create a ser file in the nebulatemprepository. You need to upload this here in your user area. You will recieve the licence. Download libraries from the user area or 3rd party ones and install. HTH
It seems you are installing both 32 and 64 bit versions. This could be confusing things. I would uninstall everything then start again. Install the 32bit version. Then folow my directions in my first post. By default its installed to C:/nebulatemprepository (not into any program or x86 program folders). If you want to install the 64bit version, create a folder called nebulatemprepositoryx64 under the first one and instal it there. Thats what I did anyways. You can have Cubase point to any vst path in its settings. In Cubase its: Devices/plug-in information/vst2 plugin paths.
Hi all. I'm using Win7 x64, Cubase x86 and Neb Pro 32bit via jbridge. It's going quite well. So tell me please, is there an advantage to using Neb*64* via jbridge in 32bit host? I mean, it's not like I am going to need more then 4gb RAM for a single neb program/instance so is there something else I should know about? Perhaps a performance gain?
I believe jBridge will let you use memory outside of the host. If all you are using is one instance of Nebula then I do not think it will make any difference unless you are also using alot of samples and that one instance may put you over the top. I think the better thing is to render tracks using Nebula. jBridge is a great tool though and also very cheap. Neal