Vienna Symphonic Library Forum
Forum Statistics

188,678 users have contributed to 42,622 threads and 256,578 posts.

In the past 24 hours, we have 4 new thread(s), 29 new post(s) and 44 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Tempo Changes causes audio pop with VEP slave instruments
  • C
    C
    Sorry I don't know how to do this beyond the 2 buffers. Can you explain more?
  • A
    A
    When/where did PLAY state that it supported real-time bounce only, DG?
  • D
    D
    last edited
    last edited

    @aptmusic said:

    When/where did PLAY state that it supported real-time bounce only, DG?

    This was in the early days, before I deleted it from my system, and my life. Probably around the same time that Buck Rodgers was telling everyone that PLAY Pro was a much better Networking solution than VE Pro.  [;)]

    DG
  • F
    F
    Did anyone come up with any solutions or answers with this? It is happening to me right now. 100BPM tempo change and Play (HS) pops. If I remove the tempo change or slide the midi just past it it is fine. Obmit
  • C
    C

    Any word on that? I am experiencing this issue as well and it is quite bad!
  • C
    C

    my [Cubsse 5.5.3] projects have extensive tempo changes... I conform the timeline to the music so even where there is a 'steady beat' there are many actual changes. I have not seen this, including with Play instances. Now, my usage of Play is pretty minimal.

    I use Jumbo Frames, 9000 in the network settings. If yu have smaller frames you could try that.
  • G
    G

    I have the same issue, but with LASS loaded in Kontakt 5 inside VE Pro. During ramp tempo changes in Cubase, the audio sounds very distorted, almost like it is using the wrong sample rate.
  • K
    K

    How does LASS behave when loaded directly in Cubase while ramping like this? I was never able to reproduce this problem here.
  • T
    T
    I've had a similar problem with 'looping points' when using instances of NI's Maschine in VEP and piped through /slaved to Ableton Live. If I have, say a 16 bar loop set in Live every time it reaches the beginning of a new loop the audio glitches for that first beat from the Maschines in VEP. The only solution I've found is to set the VEP Plug-in instance latency set to 'None', which raises the CPU level in Ableton to about the same as if the Maschine instances were in Live (which defeats the point of using VSP really). Is there possibly some sort of tempo/loop/sync issue here? (Maschine's play nicely when directly inside Ableton Live) Cheers, Alan
  • J
    J

    Hopefully I can bring this topic back to the top here..

    I have 2 Mac Pro Slaves, and 1 Master Mac Pro.  VEPro 5, DP7.24, 10.6.8, Dual Quads.

     I don't do a lot of tempo changes often, but I have this project now where it calls for it.  I'm using Native Instruments Electric Piano at the moment.  And I have a tempo change from 112bpm to 113 to 114 over about 2 measures.  The EP is going through a Delay, but that doesn't matter.  It happens regardless to what plugin I have on it.

    So when it goes over the tempo change there's a quick POP.  And it actually gets carried through the delay plugin.. so that tells me that it is popping before reaching DP?  

    However, the intersting thing is that if I move the EP patch over to my other Mac Pro.  It doesn't pop during the tempo changes.  I've had this happen to me a few times with the same Mac Pro in Kontakt.  Popping over a tempo change, and moving that patch to the other computer solved the problem.

    The only issue is that I have my EP licensed to 1 Mac pro.. not the other, so I'm running it in Demo mode right now.  I'm currently trying to figure out how to swap activations.. But still.. whats up with this??  Why is one machine handling the tempo change correctly, while the other isn't?  And it seems to be only very specific patches?  very odd..

    Just seeing if anyone came up with a solution for this..  

    Raising the buffer isn't a good solution for me, since 1) It's hard to play  .. and 2) DP7 hasn't properly compensated the latency, therefore it gets off the higher the buffer.  Also, i'm not pushing my computer too hard.. it should handle 256.

    Many Thanks!!

    ~J