The 15 second delay-bug seems to be gone.
Good work!
Jochen
194,188 users have contributed to 42,912 threads and 257,929 posts.
In the past 24 hours, we have 1 new thread(s), 14 new post(s) and 89 new user(s).
This one seems to now load for me in Logic 9, whereas the non beta gave me an AU error when loading. Played with it for awhile and seems stable but not really pressure tested yet.
While I've been in contact with Paul directly, I wanted to publicly acknowledge the hard work of the VSL team in listening to our concerns. Since I updated to the 4604 beta the crashes of the 32-server upon loading have stopped, and I no longer have issues with the LASS scripts as I detailed in the earlier threads http://community.vsl.co.at/forums/t/23261.aspx and http://community.vsl.co.at/forums/t/22729.aspx.
While I haven't yet upgraded to 4657 I just wanted to send my thanks to Martin, Karel, Paul and the rest of the team.
Cheers - Brett
The new build performs sluggishly on my system.
Mac Pro 8-Core 2,88 Ghz
14GB ram
Logic 9
A single 64-Bit instance with 16 instruments loaded and a setting of 4 Threads will report a CPU usage between 30% and 40% when idle and will go above 50% when playing some instruments.
OS X Acitivity Monitor shows a CPU usage of about 182% when idle and approaches 300% when playing instruments. It also shows 27 threads.
The interface is very sluggish to the point, that it is a chore to drag instruments around.
The last stable version was a smoother interface experience for me.
My project became increasingly harder to work with, but after restarting the computer it works smoothly now. 0% CPU usage when idle.
@Johannet said:
The new build performs sluggishly on my system.
Mac Pro 8-Core 2,88 Ghz
14GB ram
Logic 9
A single 64-Bit instance with 16 instruments loaded and a setting of 4 Threads will report a CPU usage between 30% and 40% when idle and will go above 50% when playing some instruments.
OS X Acitivity Monitor shows a CPU usage of about 182% when idle and approaches 300% when playing instruments. It also shows 27 threads.
The interface is very sluggish to the point, that it is a chore to drag instruments around.
The last stable version was a smoother interface experience for me.
Now, where I solved the Program Change problem, I would like to use the VST3 version of VE Pro with multiple MIDI and audio ports. But if I set number of audio channels above exactly 94, then Cubase 5.1 crashes. Either right when creating the VE instance or at least if I enable all audio ports (only the first two are enabled by default).
It is really odd, the limit seems to be exactly 94 audio channels. If I keep the setting at 94 or below, all works great. Setting 96 or more will make the system unusable - crashes all the time. It is easy to reproduce the problem on my system. Even a new empty Cubase project and a single empty instance of VE Pro (VST3) will reproduce the crash.
Not sure whether this is a Cubase or a VE Pro issue. Anyone else having this problem?
PS: Is it advisable to minimize the number of VE Pro instances, or is the overhead per instance negligible?
System: Vista 64, Cubase 5.1 (32 bit), VE Pro 4657
Best regards,
Peter