Vienna Symphonic Library Forum
Forum Statistics

174,401 users have contributed to 41,834 threads and 252,997 posts.

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

  • Pro Tools 10 and VE Pro 5 delay compensation

    So Pro Tools 10 and Vienna Ensemble Pro 5 both have delay compensation... should we activate delay compensation in both of them or just one of them? I'm a bit confused.

  • Bump! :)

  • You'll want latency compensation enabled in both to keep everything synchronized.


  • has the issue between VEPro and PT been resolved...where the PT delay comp engine has to be disengaged at times to sync things accurately? pls advise. thanks

    EDIT:...found answer...yes it still does. does makin' the pluin inactive then active again accomplish this also?


  • What?! That's the first I've heard of this problem, but I've only just started testing VE Pro and Pro Tools 10, so havn't had much experience with them yet. Your comment is scaring me though, is anyone else out there getting the same sync problems?

  • hi i've been trying to figure out how to get rep and pt 10 back in sync again , can someone give me a step by step guide to jump starting the latency to sync (null) again please many thanks whats the latest on this being fixed is it an avid issue , VSL of a mixture of both , any info please Matt

  • AFAIK delay compensation in PT10 is not complete, Avid added proper latency notifications in a later SDK, which is used in PT11.


  • Ah - Kool. But how do I get it working in pt 10 ? ( I am an hd user and won't be changing anything in future ) M

  • You'll have to talk to Avid.


  • Martin, could you plz explain a bit more about what you are talking about.  PT10 upgrade was quite expensive, and delay compensation was implemented before this version.  Would be good to hear VSL's perspective on this.  At the very least, in order to know what information to follow up with Avid.

    I have been experiencing some strange timing delays using VEPro 5 and PT 10 - but not really until I added MirPro and used it as a plugin in PT10.  Have not been able to find out what the problem really is... I sent tech support (VSL) a session (and a crash report), but never heard back anything from anyone.

    Thanks for any light you can shed on this. 

    - Greg


  • ... anything....?

    - Greg


  • Nope written twice to support. But it seems to be a perculiar issue for us non tech guys. To be honest I don't understand what it is but I know the 2 programs don't sync properly.

  • mafiacondon:   I saw above that you asked whether it was an Avid issue, a VSL issue, or both.....  I contacted VSL support several (like 3+....) weeks ago as I was having crazy timing issues - I had recently purchased MirPro24 and was using it in PT10 as a plugin.  Tracks would be in sync, then not in sync.... reboot.... in sync... then out -- very maddening, and very hard to get work done.  Support asked for a session, which I gave them and I also sent a crash report.  Very uncharacteristically for VSL, I have heard nothing back -- must have gone down a rabbit hole.... :-)

    From Martin's comments above, re: that latency comp was somehow not fully working properly in PT10 (but was with another SDK which was used for PT11) seems to verify that there IS a latency issue that VSL is aware of... but that it is an Avid issue.  However, as it seems to be affecting VePro, doesn't that also make it a VSL issue?  Seems to me that it does.  Telling us PT users to 'contact Avid' seems like a finger-pointing excersize to me.   :-)  That is why I posted originally - to get some more information and/or clarification from Martin about the issue.

    So Martin, if you could plz expand further on what you know about this, it would be greatly appreciated!

    Thanks.

    - Greg


  • The latency problem is caused by the pt frame work of plugin ie rtas aax not sending the correct information about the extra latency VEP is introducing with its buffer system. Therefore vsl can only wait till avid address this as they cannot alter rtas or aax architecture. However there has been posts around forums saying there is a trick of bypassing then resuming the plug in that knocks the latency back in. Mostly I am trying to find out about.

  • The issue with latency compensation in PT10 can be demonstrated by the following procedure: 1. Create a project with one instrument track and one midi track. 2. Add some midi events on the instrument track (steady beats). Copy the events to the midi track. 3. Set midi track to output to the instrument of track 1. 4. Verify that events play double (in time). 5. Add a plugin with latency on track 1, such as MIR Pro. 6. start playback again. Tracks should now flam. The above happens in PT10. In PT11 it works alright.

  • OK, I'll check that out.  But, I just noticed that VIPro2 was updated about 8 days ago, and saw this: 

    •   Fixed: Incorrect latency compensation when disabling MIRx


       This might explain the timing issues I was having before this - I was switching over from using MIRx to MirPro.


      - Greg



  • last edited
    last edited

    Hey Martin, [:)]

    I haven't installed my copy of PT11 yet, but in v10 it works for me if I uncheck the second and third boxes in;
    Preferences/Midi - Delay Compensation for External Devices.

    I don't think it's a bug, but we need to see an update in which PT can tell the difference between midi tracks for internal vs external devices.

    Maybe this is a remnant from an ancient version, when the developers presumed that all midi in a session was intended for external sources.

    @MS said:

    The issue with latency compensation in PT10 can be demonstrated by the following procedure: 1. Create a project with one instrument track and one midi track. 2. Add some midi events on the instrument track (steady beats). Copy the events to the midi track. 3. Set midi track to output to the instrument of track 1. 4. Verify that events play double (in time). 5. Add a plugin with latency on track 1, such as MIR Pro. 6. start playback again. Tracks should now flam. The above happens in PT10. In PT11 it works alright.