182,258 users have contributed to 42,215 threads and 254,736 posts.
In the past 24 hours, we have 2 new thread(s), 23 new post(s) and 44 new user(s).
Hi,
It's been months I'm using VE pro and cubase on 2 separate computers using the same template in cubase with a Vsti VE pro connected to Ve pro server on the secund computer.
In this cubase session VE Pro loads automatically an instance (full orchestra) but I found out today that I don't see it in the available slaves.
Now I'm trying to create a new cubase session but Ve pro can't connect to Ve pro slave (I tried name and ip). I got error 32.
What is happening?
Thx
Now I'm trying to create a new cubase session but Ve pro can't connect to Ve pro slave (I tried name and ip). I got error 32.
I'm not sure; but, I can give you an example of something that happens here, Cubase on the master machine using the VST3 version of VE Pro. Cubase sees my x64 VE Pro server where it's present in every case. When the slave machine is in x64 kernel, Cubase fails to see the 32-bit server until I quit Cubase, quit the VE Pro 32-bit server and reopen it. I think it's a flaw of Cubase and VST3.
I found the least confusing way for me to manage VE Pro connecting as slave/server is to save metaframes and load VE Pro before launching Cubase; when I'm ready to quit Cubase I decouple VE Pro from it and save the .cpr that way, saving VE Pro as projects separately. For one thing Cubase takes a LOT longer to load a project when it has to load VE Pro projects as part of its project.