A really odd one. This is booting with the 64-bit kernel, on a slave. C5.5 will see VE Pro 64 server every time. It fails to see the 32-bit server the first time, I have to quit both Cubase and that server and it works the second time. Maybe the new build will sort this?
-
Cubase 5.5 needs a dry run to see VE Pro 32-bit server
-
Well, I tried the new build last night (5814 was quite stable here); didn't solve this in any way. It may be Cubase 5.5, which has some issues with VST3, all over the place. Actually I think this issue is new since C5.5.
VE Pro did this with the new version last night: it quit during a metaframe save, which invalidated that file, '0 kb' now. Fortunately I have the instances saved as project frames with little changes since 'save as metaframe'.
I found that the 32-bit server needs this dry run with the slave in x86 kernel also. The workaround takes an extra minute, to open an empty project to 'not' see the server, quit both apps and 2nd time works, so it's no big deal, but a small annoyance.
-
VE Pro did this with the new version last night: it quit during a metaframe save, which invalidated that file, '0 kb' now. Fortunately I have the instances saved as project frames with little changes since 'save as metaframe'.
It just quit on you without any user interaction?
-
Yes. All I did was save metaframe (I would expect trouble somewhat if I clicked on the GUI during...). it was a stable metaframe and a stable cubase project until this build.
on this slave machine:
OSX.6.4
MacPro 8 core 2.93 ghz, 24 GB
Loaded were: Kontakt 3.5, Kore 2.1, Vienna Instruments
with Vienna Suite and IK Multimedia in inserts and send busses (V. Suite and VI are latest builds)
2 instances of 32-bit VE Pro server.
the system as a whole was nowhere near maxing RAM or page outs, ca. 6 GB, and user + system CPU was maybe 20%
dedicated machine with no extraneous drivers in background