200,670 users have contributed to 43,206 threads and 259,115 posts.
In the past 24 hours, we have 4 new thread(s), 13 new post(s) and 77 new user(s).
I did mention this once in another thread in passing, but it is now starting to be an issue for me.
If I have 32 bit and 64 bit instances of VE Pro on my slave PC, and then close the song down on the master PC, the 64 bit VE Pro closes down, but the 32 bit one always remains open, it never closes down. Is this a general issue with the 32 bit VE pro, or is this something unique to my setup here?
I'm using VE Pro V4.17846 in Windows 7
Hi andyjh,
I assume that you are using VE PRO SERVERS (32 bit and 64 bit) on your slave machine. Servers always need to be closed manually. Or are you talking about stand-alone VE PRO instances (which also need to be closed manually, of course)?
Or is this about the VE PRO GUIs?
The more information you can give us, the better. It´s also a good idea to use the latest updates [:)]
Best,
Paul
Hello,
It is the 32-bit VE Pro window including everything loaded into it that does not close down. I'm not expecting the servers to close down, as I know that they dont, but when I close a Cubase song on the master, the 64-bit VE Pro closes on the slave but the 32-bit stays on screen, so I have to go to the 32 bit server and close the active instances there.
It seems this is only happening with two of my Cubase songs, I cannot recreate it from scratch. It looks like the offending songs have 2 entries for the 32-bit server (only 1 should be there, as it only opens 1), which is probably what is making it leave the 32 bit VE Pro open. I have finished these 2 songs now, so I'll see if it happens again.
I will now update to 4.1.8008 versions, as I never update anything whilst I am in the middle of a song
