Hello Paul;

on master: Xp service Pack 2_/Intel Core 2 Quad Q6600 @2.40Ghz

on salve : xp service pack2_/pentium 4 3.00Ghz

Thanks again

as soon as I have time, I reinstall the last version to try to find other information

best regards

Dup

Hi, my name is Carsten. This Thread is very interesting. I have exactly the same Probs with the new Release of Ensemble pro 4536.

My config:

Master:

Intel Core Duo Quad 8200 4 x 2.33 GHz 4 Gigs

Cubase 5.1

Windows 7 64 Bit Professional

Gigabit ethernet

(runs fine)

but the Slave:

Intel Dualcore T2300 2 x 2.0 GHz 3 Gigs

Gigabit ethernet

Vista home 32 bit service pack 2

no other Plugins in Ensemble Pro

It is the same. With the "old" version all works fine but the new Version crashes

at the slave.

I looked at the Logfile an the last loaded Modul of the Startup-Process of Ensemble Pro was the WTSAPI32.dll which is part of the Terminalservices of Windows, which is lokated in the windows/system32/folder.

I hope i could help with my Informations Its up to you :-) Vienna

Greetinxxx from Munich

Carsten

Thanks for your feedback Carsten.  I'm having a similar problem on XP64. 

Paul, you mentioned the to me (in the LASS thread) that the crashes experienced with the latest build were XP64 related (XP64 being an unsupported OS) despite the previous build not exhibiting this behaviour.  However it seems that the problem might be more widespread on PCs.

Carsten and Dup, if you are interested my experiences with the issue are outlined in the following thread.

http://community.vsl.co.at/forums/t/23110.aspx?PageIndex=3

Brett

Hi

Same problem here after trying build 4536 :

Cubase 5.01

Open project with Ensemble Pro on slave (build 4536)

VSL string instruments taking up around 3GB ram.

All instruments load but at the end of loading VSL slave closes down/crashes  (no error messages)

I reinstalled build 4416 on the slave and the samples/instruments all loaded fine and was able to continue working on project as usual.

Slave PC: winXP SP3 32bit.

same problem here, crashes after loading is complete. Im on Cubase 4. Reverted back to first build fixed my problem.

@calculus said:

Hi

Same problem here after trying build 4536 :

Cubase 5.01

Open project with Ensemble Pro on slave (build 4536)

VSL string instruments taking up around 3GB ram.

All instruments load but at the end of loading VSL slave closes down/crashes  (no error messages)

I reinstalled build 4416 on the slave and the samples/instruments all loaded fine and was able to continue working on project as usual.

Slave PC: winXP SP3 32bit.

 If you are loading 3GB, then you will be running out of memory, if you are runiing XP32bit.

DG

 If you are loading 3GB, then you will be running out of memory, if you are runiing XP32bit.

DG

I know exactly how much memory this particular template takes up and the limit of the 3GB switch (in my case 3.25GB). This template has not crashed once on the previous build even though it is pushing memory to the limit (3gb in size). The only time VE pro slave has crashed is with the latest version.

Regards

@calculus said:

 

 If you are loading 3GB, then you will be running out of memory, if you are runiing XP32bit.

DG

I know exactly how much memory this particular template takes up and the limit of the 3GB switch (in my case 3.25GB). This template has not crashed once on the previous build even though it is pushing memory to the limit (3gb in size). The only time VE pro slave has crashed is with the latest version.

Regards

However, have you checked that the newest build doesn't use more memory than the previous one? Probably not, but worth eliminating.

DG

You're right I didn't check. When I get finished with this particular piece I will reload latest build and check the memory usage on the slave. I really hope it isn't crashing due to memory as I was kinda holding out from building a win7 64bit slave just yet. I will keep on using the previous build though....if it aint broke.

@Andreas Waldetoft said:

same problem here, crashes after loading is complete. Im on Cubase 4. Reverted back to first build fixed my problem.

Hi, How much memory were you using?. 32bit or 64bit?

Hi,

just to let you know: We´re listening and currently fixing this bug!

Thanks for your patience!

Best,

Paul

Thats great news and thanks for the confirmation.