VEP crashes when I quit DP with one project. DP is fine.

[belkina]

This project is fine in DP, but why does VEP crash when I quit DP every time?

[belkina]

Sometimes when I have used DP for for other projects, when I go to quite VEP (after it is empty) it crashes as well. I have sent in many of the crash reports already.

[Bross]

What version of DP? and What version of Vienna ensemble? And what mac OS?

I had that problem. Then i converted to iLok and allot went away. With DP 11.23 it happened .

I love Vienna! and could not make a living without Vienna Ensemble as i have two mac Pro's and balance library. It handles allot of instances and memory better than DP does. OR cubase. Since no one is updating me with support ticket i am going to try updating PACE and Ilock software.

I have a feeling with running old E-Licencer version 6.5 Ensemble and Ilock version that when older version updated it trashed my conversion to ilok Vienna VST or its authentication. But what do i really know. I got try some things my entire DAW is down and DP crashes when i open Vienna Ensemble. So my current projects are on hold. And since i use two macs with Vienna pro server open one my entire studio is down. I may sound pushy but when you got a Film gig there is no waiting for answers. You get fired. In a perfect world we would have millions of dollars to purchase huge Time Machine 120TB external drives. But i don't have that. I have a backup of my 18TB System drive over a week ago but then it takes time to update all my software again and authenticate at vendors with non Ilock VST plugins. They think you are pirating when you switch CPU's.

Thanks for you reply! I need help and more ideas to try. Like how to see what versions of vienna software is using ilok and what is using E-Licencer. And where Vienna VST's are so i can remove them and reinstall.

[belkina]

@Bross said:

What version of DP? and What version of Vienna ensemble? And what mac OS?

I had that problem. Then i converted to iLok and allot went away. With DP 11.23 it happened .

I love Vienna! and could not make a living without Vienna Ensemble as i have two mac Pro's and balance library. It handles allot of instances and memory better than DP does. OR cubase. Since no one is updating me with support ticket i am going to try updating PACE and Ilock software.

I have a feeling with running old E-Licencer version 6.5 Ensemble and Ilock version that when older version updated it trashed my conversion to ilok Vienna VST or its authentication. But what do i really know. I got try some things my entire DAW is down and DP crashes when i open Vienna Ensemble. So my current projects are on hold. And since i use two macs with Vienna pro server open one my entire studio is down. I may sound pushy but when you got a Film gig there is no waiting for answers. You get fired. In a perfect world we would have millions of dollars to purchase huge Time Machine 120TB external drives. But i don't have that. I have a backup of my 18TB System drive over a week ago but then it takes time to update all my software again and authenticate at vendors with non Ilock VST plugins. They think you are pirating when you switch CPU's.

Thanks for you reply! I need help and more ideas to try. Like how to see what versions of vienna software is using ilok and what is using E-Licencer. And where Vienna VST's are so i can remove them and reinstall.

VEP latest version, DP likewise, Windows 10.

[belkina]

No help from VSL??? I've sent in the crash report many, many times now, still no help or answer???

[Ben]

@belkina I can't find any mail this year from you in our inbox. You should have gotten a response mail with a Case-number, if you post this number I can check the status.

Please note that this is a user-forum and not a support forum. The only official support is via mail to support@vsl.co.at

Also, responses often take longer during weekends.

[belkina]

When VEP crashes it brings up this crash notice. And I reply "Crash on Quit" under Tell us more. Sometimes I also add my email, but never had any answer.

[Ben]

This is not a mail to support, and you will not recieve any support by adding a message there.

All crashes of VSL programs, even if being caused by 3rd party plugins, get sent to a monitoring server.
Only if something sticks out it gets manually checked (like a lot of similar crashes), and in this case the messages will be read and you might get contacted for further troubleshooting or a beta build.

But as long as you are the only one experiencing this kind of crash we can not find your message since there are too many reports and data unless you contact us via mail and add your SystemID. While you are at it it's also a good idea to create a support file in the Vienna Assistant and attach it as well.