Vienna Symphonic Library Forum
Forum Statistics

194,395 users have contributed to 42,918 threads and 257,959 posts.

In the past 24 hours, we have 4 new thread(s), 6 new post(s) and 83 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VEP7 (v1120 / v1056) OT-SINE Crashes Randomly

  • VEP7 (v1120 / v1056) OT-SINE Crashes Randomly

    J
    J

    Hi there everyone,

    I was wondering if anyone else is experiencing v1120 (latest update) crashing regularly for no apparent reason?

    I've managed to reduce how often it crashes by uninstalling / re-installing from scratch.  But it is still crashing a few times a day.

    This is happening on my studio workstation PC (Windows10 Pro, dual-CPU, 256GB DDR4 RAM).   I'm loading about 180GB of sample libraries from SSD in to a VEP7 template that I created back in May 2020 and have used without problems with VEP7 version 1056.   v1120 is the first version for which VEP7 has crashed.  Previous versions up to v1056 (the last version) were very very stable.

    So I guess the question is:  What has VSL introduced with v1120 to make it unstable.

     

    Thanks for any help,

    Jon
  • PaulP
    VSL Team
    PaulP
    last edited
    last edited

    Hi Jon,

    Thanks for reporting!

    Are you sending in the crash reports you get, with your email and a short explanation? Reproduction steps will always be helpful in such cases, and of course you can also contact us directly: support@vsl.co.at

    Here's the changelog of VE Pro, feel free to roll back to previous versions, build 1056 is also available in our downloads archive.

    Best,
    Paul

    Paul Kopf Product Manager VSL
  • J
    J

    Many thanks Paul.

    I've been playing around with v1120 and then v1056 on a spare PC, and have narrowed down the cause.   It actually appears to be OT's SINE, when loading up an ARK library.     I can now make VEP7 crash predictably: the ARK5 library appears to crash VEP7 (v1120 and v1056) whenever it tries to load the Strings Section (but only after the SINE window has been expanded / made larger by dragging the bottom right corner of the SINE window).   

    I have just tried loading the ARK5 Strings Section in to SINE (v1.0.8) in VEP7 v1056 on my main studio workstation PC Following the same approach as before, and again VEP7 has crashed.      However, when loading the String Section in to a standalone SINE (not running in VEP7), then it is fine and doesn't crash.

    So, to conclude I am guessing that there is something being triggered in VEP7 by SINE, when loading the Strings Section, which ultimately crashes SINE and then crashes VEP7.

     

    I have also tried loading ARK5 in to SINE (v1.0.8) on a couple of our Dell servers which run VEP7 v1056, and  VEP7 has also crashed on those machines.

     

    I'm away for the next couple of days, but will try gain to make it crash when I'm back in the studio - just in case today was a fluke day !!

     

    Wishing you and the team a very Happy New Year,

    Jon
  • PaulP
    VSL Team
    PaulP
    last edited
    last edited

    Hi Jon, 

    Thanks for the update. Feel free to inform my colleagues at OT as well 😉.  

    Best, 
    Paul

    Paul Kopf Product Manager VSL
  • C
    C
    last edited
    last edited

    @Jon@ShoutingProduction said:

    This is happening on my studio workstation PC (Windows10 Pro, dual-CPU, 256GB DDR4 RAM).   I'm loading about 180GB of sample libraries from SSD in to a VEP7 template that I created back in May 2020 and have used without problems with VEP7 version 1056.   v1120 is the first version for which VEP7 has crashed.  Previous versions up to v1056 (the last version) were very very stable.



    Hi Jon,
    I've a very off topic question to ask you - If you pull up resource monitor on your dual CPU machine do you see the CPU load spread over cores in both of your CPUs?

    The reason I ask is that VE Pro on my HP z640 dual-CPU with 256GB only ever uses a single processor. I'm hoping that it's some configuration of the system or just a VE Pro setting.

    Thanks,

    Roger