Vienna Symphonic Library Forum
Forum Statistics

194,206 users have contributed to 42,912 threads and 257,931 posts.

In the past 24 hours, we have 1 new thread(s), 15 new post(s) and 87 new user(s).

  • How to roll back to 4416 VEP (from beta 4657)

    I have noticed I get quite a few more pops/clicks with 4657 over 4416.   Is there a trick to rolling back to 4416?  Or just simply run the exe for 4416?

    Thanks for your input.

    Rob

    (running PC/ duo quad - main and Daw x64 - buffers all set to '2x' - motu card latency - 2408 mk3 - set to 512 samples - still pops.   probably time for an i7 on the main daw.)


  • Uninstall, re-boot, re-install old version.

    Just in case you haven't, before you roll back try setting the Priority of VE pro back to normal in Task Manager, and see if that solves the problem.

    DG


  • Hey DG - thanks and nice idea on the check.   When you say 'task manager' - do you mean x64's task manager / 'update speed'?   I checked that and it is now set to 'normal' (on all PCs - main and slaves).  Perhaps change from there?


  • Rob, I've lost count on which number public beta we are on now, but you should right click the desktop toolbar (on all machines where there is a VE Pro server), choose Task Manager, right click VE Pro, click Priority and check that it is set to normal. If it already is, then roll back. If it isn't, set it and try again. You will need to do this every time you boot up (although it is possible to set it to be automatic).

    DG


  • Hey DG - I hope you are on the payroll at VSL.  :)   Doing as you say I found out everthing is set to 'High' ('set priority' in task mgr) - set them to 'normal' and the CPU meter in Nuendo seems to be jumping around a lot less.

    I'll watch it over the next few days.  Thanks again my friend for you help.

    (anyway to set this to be 'automatic'?)


  • Next update will have the priority restored by default. Sorry about that.

  • Great Karel - makes a difference on this system.  Thanks again DG for the suggestion.


  • Hey Karel - might have been mentioned on a thread but I would suggest that when closing a metaframe --  that if NOTHING has changed the 'prompt' to SAVE not come up.   Small thing - just my opinion.


  • The (main) reason we have removed this - is that the compare functionality is rather slow, especially when involving some slow-saving 3rd-party instruments like Kontakt.