Vienna Symphonic Library Forum
Forum Statistics

200,452 users have contributed to 43,198 threads and 259,085 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. In the past - higher ASIO buffers settings took care of pops/crackles...but now new issues

  • In the past - higher ASIO buffers settings took care of pops/crackles...but now new issues

    R
    R

    Is anyone else noticing that NOW (with VEPRO and VIPRO - latest builds) that higher ASIO buffer settings cause a whole new set of issues?  i.e. drop outs, stuttering, etc.

    In the past on export or final mix I would increase the asio buffer setting to 1024 or even twice that to remove any pops/crackles - now if I go above 512 (to 1024) - I get the described above.

    I have always left the 'buffers' on the VEP server at 2x's and close all GUI's.

    My problem is if I leave ASIO at 512 for final mix (becuase of mix plug ins, etc.) - I'll get CPU spikes.   Anyone find a workable solution?

    Again - I have only now had this issue with the new VIPRO and latest build of VEPRO.  I would hate to go back to the old player and earlier VEPRO builds - really LOVE the new VIPRO features!

    Thanks for your input.

    (all my preferences are set at 2 threads/per instance on the two i7's and 1 thread on the two duo quad puters.)
  • G
    G
    Yes, much to my horror, I've just discovered this is the case (mac latest Cubase)...as I went to bounce the individual parts playing in VEP to audio I've discovered there's glitching everywhere.. This needs to be fixed as an emergency priority...it's just ruined my gig for me..not what i paid for.
  • R
    R

    I am getting through my deliverables today but freezing a bunch of VEPRE instances.  Not desired but gets my project out the door.   Thanks VSL for any input you can be on this.

    Rob
  • K
    K

    If this occurs only with Cubase as master host and VI Pro hosted in VE Pro, the issue is already solved for the next update, which should be released in a couple of days.
  • P
    P

    Ok I'm guessing that this is the problem I'm having with spikes and glitching since updating to 6853. I was thinking it was Kontakt but perhaps not.

    Refer to this thread.   http://community.vsl.co.at/forums/t/26583.aspx

    Today I'm going to go back a version of VEPro and I''l report back.

    Yesterday I was using a session with only one instance of Kontakt (Artvista Piano) and nothing else. So just one instrument streming from the slave.

    Drop outs all day long.

    Driving me crazy.
  • P
    P

    Hi Karel, no it's not just Cubase. Check out the posts on this thread.

    http://community.vsl.co.at/forums/p/26583/175224.aspx#175224

    These drop outs are affecting a group of us now.

    Any ideas?
  • R
    R

    I am on Cubendo - assume it will be the same?
  • G
    G
    Correct, just worked that out myself by loading some of the patches into VI instead of VI Pro.... that fix can't come soon enough for me! Can we just clarify that it is indeed VI Pro for the others with the problem? Just load the patches into VI and see...fixed the glitches and pops immediately for me..(I'm using latest VEP to host VI and VI Pro) with latest Cubase mac in Leopard
  • K
    K

    This has been fixed in the upcoming update. Using the VST2 version of VE Pro probably avoids the problem, so if you can't wait, that's a temporary option.
  • J
    J

    Karel, is that a previous version than the latest official release (as in 6844 and earlier)? 

    Thanks,

    JB
  • G
    G
    last edited
    last edited

    @Karel said:

    This has been fixed in the upcoming update. Using the VST2 version of VE Pro probably avoids the problem, so if you can't wait, that's a temporary option.

    So putting the vst3 offline should do it? EDIT. Tested. It seems that Vienna Ensemble Pro VST3 is indeed the culprit here. I put it offline and reconnected the VST2 to an existing metaframe and project hosted on our MacBook Pro. The problem with this of course is that the VST3 and VST2 are completely different identifiers to Cubase and as such there's zero recall for projects saved using the VST3 (the default when both are present in the system) This means the only useful way to get correct playback is to manually load the metaframe and project and reconnect EVERYTHING which is an enormous pain and obviously is the opposite of convenient. Could that fix come a little sooner please?
  • K
    K

    We're in the testing phase for the update, so should be soon. Thank you for your patience.
  • R
    R

    Thanks Karel for keeping us updated on the update :)

    Few bugs aside - this really is brilliant software.  Good luck on getting this sorted out.
  • P
    P
    I've also had some stuttering, pops and crackles,,,, never had before?? I'm running PT's 8.0.4 ,, W7,64,, and all latest updates??!! Its not consistent, but annoying none the less! Any hope of the upgrade fixing the PT's prob?? Thanks,,,,,,,,, Mike
  • M
    M

     Just to bump really...

    We're looking forward to:

    - less stuttering and performance issues

    - VE (Pro/Non-Pro) integration

    I believe about a month ago this was supposed to be there 'in three weeks' (wait for newsletter). Not to sound impatient, though obviously, I am!

    Cheers,

    MSpape