Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Forum Jump  
Options
Go to last post
Posted on Mon, Oct 12 2009 16:58
by michael_12374
Joined on Wed, Feb 09 2005, Posts 26

This is what I already wrote earlier in a thread:

-------------------------

Thanks for this new update, guys!


However, VE Pro crashed when I do the following:

1. VE Pro and Cubase are running and connected to each other, in VE Pro a VI is loaded.

2. I save and close Cubase (decouple mode off), close VE Pro completely.

3. Restart VE Pro Server (32-bit), restart Cubase and load that saved project file.

4. Now, Cubase tries to connect to VE Pro and VE Pro crashes.

Important: This does not occur when the last instance of VE Pro is still running! And I don't know if it is a new problem, which came with the update because I have not tried that before...

-------------------------

Any workarounds or solutions?





Gigabyte Mainboard, Intel P35 Chipset
Intel Core2Quad Q9300
Gigabit LAN
ATI HD 3470
Windows XP 64
Cubase 4
Posted on Mon, Oct 12 2009 17:17
by DG
Joined on Wed, May 12 2004, Posts 8608

This is a well known bug with Vienna Ensemble, and has been around for years. Steinberg needs to fix it, but they haven't so far. FWIW I think that this doesn't happen with Cubase 5, but for C4 and Nuendo users that is no consolation.

DG

Nuendo 6.03, 4.3
2 x Intel Xeon x5675 3.07GHz Hex Core
48GB RAM
Windows 7 (x64)Pro
RME Multiface II
Intensity
ATI HD5400 series graphics card
Posted on Mon, Oct 12 2009 18:03
by michael_12374
Joined on Wed, Feb 09 2005, Posts 26

What a shame! I haven't heard of this problem and would have thought twice before buying VE Pro under this circumstances.

But if there is a solution please let me know!

Best,

Justus

Gigabyte Mainboard, Intel P35 Chipset
Intel Core2Quad Q9300
Gigabit LAN
ATI HD 3470
Windows XP 64
Cubase 4
Posted on Mon, Oct 12 2009 19:00
by DG
Joined on Wed, May 12 2004, Posts 8608
michael_12374 wrote:

What a shame! I haven't heard of this problem and would have thought twice before buying VE Pro under this circumstances.

But if there is a solution please let me know!

Best,

Justus

 

The solution is easy. Don't close Cubase and then re-open it.

DG

Nuendo 6.03, 4.3
2 x Intel Xeon x5675 3.07GHz Hex Core
48GB RAM
Windows 7 (x64)Pro
RME Multiface II
Intensity
ATI HD5400 series graphics card
Posted on Mon, Oct 12 2009 20:02
by michael_12374
Joined on Wed, Feb 09 2005, Posts 26

And saving and loading the VEPRO instance seperately from Cubase should do it as well.

Gigabyte Mainboard, Intel P35 Chipset
Intel Core2Quad Q9300
Gigabit LAN
ATI HD 3470
Windows XP 64
Cubase 4
Posted on Mon, Oct 12 2009 20:13
by brett
Joined on Fri, Aug 19 2005, Australia, Posts 87

DG, I have the same problem as michael_12374 and have posted already here - http://community.vsl.co.at/forums/t/23110.aspx

However, this problem wasn't in the first build.  Could you explain your work around, because it crashes here on the first cubase load (ie I don't have to closing and re-opening Cubase).  Besides, if this happens everytime you load Cubase it defeats the purpose of Preserve.  Here is my comment and repro from the earlier thread...

>>>>>>

However, VEP still crashes when loading a saved project.  I've done
some more testing though and only the 32-bit server crashes, not the
64-bit version and this occurs whether I'm connected using the VST2 or
VST3 version of the plugin.  Nothing has to be loaded into the VEP
plugin - it can be empty.  Also, the crashes to the 32-bit server only
occur when 'connected' to the Cubase.  If I've disconnected (preserved) prior to saving the project then it will load without crashing. 

>>>>>>

AND

>>>>>>

Thanks Karel for your reply.  I'm using xp64 and cubase4 on a PC, with VEP only on my local computer.  No slaves.

Load VEP server 32-bit.

Load Cubase4

Open a new Cubase project

Instantiate a single VEP from the VST instruments rack

'Connect' to localhost [32] (new)  - I'm not naming the preserved
session which means the VEP instance is connected to the host and not preserved

Save the project

Close the project

Re-open the project = crash! (exception in vienna ensemble pro.exe)

In contrast...

Load VEP server 32-bit.

Load Cubase4

Open a new Cubase project

Instantiate a single VEP from the VST instruments rack

'Connect' to localhost [32] (new) and either name the instance (automatically preserving it) or don't name but then preserve.

Save the project

Close the project

Re-open the project = No worries.

[edit - however, if you shutdown the VEP 32-bit server, or delete
that preserved instance of VEP, after closing the cubase project, and
then re-open the project, this will force VEP to load with the project and cause a crash similar to the first example above]

(Also, the problems with cc-instensive patches like the legato LASS patches is not fixed here - I've detailed this in the LASS thread)

Thanks Karel - Brett

>>>>>>>

Posted on Mon, Oct 12 2009 21:00
by DG
Joined on Wed, May 12 2004, Posts 8608

I don't get any crashes when closing and opening a project. It's only when closing and opening Nuendo. The crash has nothing to do with VE Pro, as it is caused by the vsldaemon.

DG

Nuendo 6.03, 4.3
2 x Intel Xeon x5675 3.07GHz Hex Core
48GB RAM
Windows 7 (x64)Pro
RME Multiface II
Intensity
ATI HD5400 series graphics card
Posted on Tue, Oct 13 2009 13:49
by michael_12374
Joined on Wed, Feb 09 2005, Posts 26

OK, I did a little bit of testing and these are the results:

- 64-bit version of VEPRO server works (as already mentioned)

- 32-bit version only works with preserved instances and only when they are named exactly as they were in your Cubase project. Alternatively you can save a metaframe for each Cubase project.

- It's even possible to open an empty instance (named correctly, s.a.) and choose "Load plugin data" which will load all the VE PRO data Cubase has saved with the project.

Gigabyte Mainboard, Intel P35 Chipset
Intel Core2Quad Q9300
Gigabit LAN
ATI HD 3470
Windows XP 64
Cubase 4
You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.