Vienna Symphonic Library Forum
Forum Statistics

200,887 users have contributed to 43,216 threads and 259,147 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. Automatic Delay comp
  • V
    V

    This is a miracle or it should be? :)

    ***

    [URL=http://xmages.net/i/3225089][IMG]http://xmages.net/storage/10/1/0/b/6/upload/c6fbc269.jpg[/IMG][/URL]

    ***

    Cubase 6, VE PRO 5 on slave comp. Without insert effects (clean). ASIO - 6 ms (RME AIO). Delay compensation on ( [URL=http://xmages.net/i/3225093][IMG]http://xmages.net/storage/10/1/0/0/e/upload/9992c090.jpg[/IMG][/URL] ).
  • T
    T

    I did the same experiment in Pro Tools 9HD (44.1kHz 24bit Session) on Snow Leopard w/VEP 5 (9735) ... here's what I found:

    Buffers:          Sample Delay from MIDI Source (samples)

    4 Buffers :          2 Samples

    3 Buffers:           2 Samples

    2 Buffers:       256 Samples

    1 Buffer:             2 Samples

    0 Buffers:           2 Samples

    VSL - comments on setup?  
  • K
    K

    I just verified and fixed this issue. Current version of VE Pro 5 always processes at 4 buffers latency when set to 2 & 3 buffers and doesn't compensate the latency correctly. A new update will arrive tomorrow or possibly the day after. Sorry for the inconvenience.
  • V
    V

    Yes! Now correct compensation for all buffers set! [Y]
  • S
    S

    No, not here: automatic latency compensation is NOT working with Logic (9.1.5) and the actual VEPro 5.0.9753
  • S
    S

    to be more precise: latency compensation does not work at all, the only setup without latency is "none"....
  • K
    K

    Logic doesn't always update latency compensation as it should. Usually a start/stop of the Logic transport makes it work. This is something we can't change unfortunately.
  • S
    S

    Sorry, Karel, but this cannot be true. Start/stop commands do not change it - even a reload of the song or a reboot of Logic doesn´t make a difference. Latency Compensation simply does NOT work. And: it DID work BEFORE the upgrade.

    Oh - and of course I checked "Enable PlugIn Latency Compensation" in the prefs....
  • K
    K

    Please check your Logic settings. Preferences -> Audio -> General -> Plug-in Latency. Make sure Compensation is set to All there. I've just verified the latency compensation in Logic just to be sure and it works perfectly.
  • S
    S

    Sorry I should have mentioned even this option: in Logic, delay compensation is (and always was) set to "all". 

    Latency compensation in VEPro 5 does not work. 
  • K
    K

    How exactly do you verify that it doesn't work?
  • S
    S

    by having a percussiontrack playing via VEPro together with another one inside Logic.

    But meanwhile a funny thing occured: while I was doing normal composing/arranging work and occasionally changing the VEPro buffer size from time to time to check if the bug still occurs, suddenly latency compensation worked fine. I then tried all buffer sizes - all worked like expected. 

    Maybe the problem has to do with Logic´s "low latency"-mode, to which I switched several times - though the problem occured in "normal latency"-mode, too. It is my normal process to work that way, and before the update to 5, there was no latency problem when switching. Maybe you should do a little research in this direction.
  • S
    S
    I have a major issue with Latency comp too Cubase 6.03 just downloaded latest build of vepro 5 sending via vepro input plugin from C6 on 1 macbook pro to another macbook pro running latest vepro 32 bit server load 3 instances of waves L316 - really high latency on this plug makes it easy to hear straight away - on 1 path second path is fed from same inputs and feeding same outputs as the first so in effect parallel with no plugin inserted returning to C6 as an instrument etc result: obvious delay WITHIN VEpro even thou the little counter is showing about 20000 samples as delay so this is issue does not appear to be about bad reporting to the daw it seems that latency comp within vep is not working at all