Vienna Symphonic Library Forum
Forum Statistics

183,385 users have contributed to 42,295 threads and 255,061 posts.

In the past 24 hours, we have 2 new thread(s), 10 new post(s) and 52 new user(s).

  • This issue has been fixed for the next update. We'll do our best to release it as soon as possible. Apologies for the inconvenience.


  • FANTASTIC news.  I have been reporting this problem for a long time saying that I did not believe this ever happend in VE PRO 4.  I am glad the "PLAY" folks were able to consistant ly show the problem.

    Now if you can fix my multiple instances of Halion 4.x VE PRO would be flawless for me.

    Thanks for the fix....I can't wait to get it.


  • This is very awesome news indeed :) Thank you very much :)


  • I have this issue as well. I have just set up a slave machine i7 processor with Win7 Pro and am only running Kontakt 5 instruments in VEPro5. My host machine is a Mac Pro with Logic 9. I can't even get so far as to steam audio. I created a metaframe containing a handful of instances. I can load the metaframe just fine. But now, the application (VEPRO5 server) operates very slowly and hangs. Selecting different instances from the main server window or trying to Alt/Tab through instances either takes several minutes (yes minutes) or simply causes the machine to freeze. I'm glad to hear that a solution is in the works but I am basically stymied at this point.

  • The solution only applies to the crashes when starting/stopping the audio engine with Play in the project, but may extrapolate to the strange hangs as well. Just to avoid potential disappointments.


  • I hope that this fix actually fixes my Kontakt hangs, as I stated before that this did not happen at all in VE PRO 4.


  • I have updated the title of this forum post to better describe the initial problem that has been resolved. Hopefully this will also fix the problems you others are having, if not, hopefully those problems have come to light now that support has read these posts as they do seem very similar.

    EDIT:

    Removed my previous statement.

    Thanks once again everyone for helping solve this problem :D


  • Support would be me for this particular case. The support case is not closed. I just replied in this thread instead because I knew it was you :).


  • Ah thanks for the clarification Karel :)


  • Sorry, im a bit restless Karel :) Do you know anything about a potential release date?

    Got 2 weeks of vacation comming up and would love to be able to use this time to make some music :)


  • Some larger changes are currently being tested, which prevents an immediate release, but we're doing our best to get it out there as soon as possible. I'm sorry for the inconvenience.


  • :(  i think small fixes and fast pushes rather than large fixes and slow pushes are better for everyone.

    Where do i sign up for a beta test?  ;)  And a small feature request, make sure there is a crash log if the program hangs/crashes for any reason in the future :)

    Anywho, thanks for the update :)


  • Any news on the update?

    Its been over 1 month since i first reported the error.

    Best regards Øivind.


  • Hi Ã˜ivind,

    It´s in the pipeline, should be out in the first days of next week!

    Thanks for your patience, 

    Paul


    Paul Kopf Product Manager VSL
  • Super, thanks for the update!


  • Hi I have this exact same error (VEPro 5 using Play 3.0.37 (and Pro Tools 10.2 under Windows 7 64 bit) stops responsding (white screen) very often when startip/stoping playback. I have to restart the VE Pro server (which has crashed and disappeared it seems) and reload my instance. This is happening only with VE Pro 64 bit server (working fine with 32 bit version). I have the latest VE Pro version (5.1.10988) and this is issue is still present.

  • I notice there was nothing realted to this issue in the .10988 changelog.

  • Could you send an e-mail for me to ? That way we can get to the bottom of this, because so far I haven't been able to reproduce this behavior. Thanks.


  • Still the same problem here, tho i havent been able to crash it on my slave yet, but the one on my main computer crashed after 10 minutes of normal music making.  So it triggering on the audio engine on/off might have been fixed but the underlying problem seems to be there still.

    Edit: going to leave it going over night and see what happens.

    Edit 2: ops, there the one on my main computer crashed again, by clicking on the audio engine on/off button. The slave server is still working tho, seems like its pretty stable at the moment.


  • last edited
    last edited

    @Karel said:

    Could you send an e-mail for me to ? That way we can get to the bottom of this, because so far I haven't been able to reproduce this behavior. Thanks.

    Email sent, thanks !