Vienna Symphonic Library Forum
Forum Statistics

182,262 users have contributed to 42,216 threads and 254,737 posts.

In the past 24 hours, we have 3 new thread(s), 22 new post(s) and 40 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Cubase 10 Real-Time peaks/dropouts with VEP instrument tracks connected to a slave

  • Cubase 10 Real-Time peaks/dropouts with VEP instrument tracks connected to a slave

    S
    S

    I and other folks over at the vi-control forum are having some strange random real-time peaks and dropouts by record enabling and playback Vienna Ensemble Pro 6 instrument tracks in new Cubase 10 connected to a slave. The peak meter ranges are going from around 10% to 100%, very unstable, jerking up and down during playback of a very light project, never mind if those tracks have anything to play or not, it peaks as long as they are record enabled.

    With VEP buffer set to 2, real-time peak jumps are small enough not to cause the dropouts, but they are there. But as soon as I change the buffer to 1, it starts to jump full scale, from very a minimum (as I have only one track loaded in the project) to a full tilt, totally random. However, there is no such behavior on Cubase 9.5 with either buffer setting.

    Loading the same library in VEP locally on the master PC doesn't introduce any problems with C10, only via Ethernet, streaming from a slave. Tried with two different slaves and have the same issue with both. 

    I lost days troubleshooting to finally go back to Cubase 9.5 as there are no such problems with the previous version. 

    LatencyMon doesn't show the problem. I tried many things, both vep vst3 and vst2, AG on/off, fresh win install, different video drivers (AMD), pref rebuild (this introduced even more peaks), couldn't find anything locally related to the problem.

    Despite an obvious difference in performance between C10 and C9.5, it was sudgested to me to make a thread here as well in case there is something you guys can do.

     

    Thank you.
  • G
    G

    You didn't mention Wi-Fi... Do you have Wi-Fi concurrently enabled on your DAW?  Is your Wi-Fi set to be the same network range as your Ethernet Ports?  If so, that will cause strange dropouts just like the ones you're describing.
  • A
    A

    COuld you please explain what does it mean WIFI to be the same network range?

    My Wifi is 10.20.11.102 and this my DAW on a MAC but for VEP my LAN is 10.255.255.7

    Is this THE SAME range or not?

    Please tel me more WHAT is the infulence of the WiFi network. Unfortunatelly I have to often cracles they appear I do not know why but after some time and I believe soemthing is wrong here. I am desperate - now it works well but then it can stop/
  • G
    G

    Possibly they are...   We need to check your SUBNET MASK in order to confirm.  

    If these computers also have a Subnet Mask of 255.0.0.0, then yes, your LAN and WIFI are on the same logical network - 10.x.x.x.  (this may also be the case if one of your computers or interfaces has a different subnet  mask)

    If your Subnet Mask is 255.255.255.0, then they are not on the same network, they are on two different logical networks: 10.20.11.x and 10.255.255.x

    The dropouts and crackles you hear may be an indication that your network buffer has been overrun... packets are either being dropped, or spending too long in the Network buffer to be delivered to your Audio Application on time.

    From my own experience with Mac computers, it appears to me that OSX creates a separate data buffer for each logical network I create within my computer.   This means that my DAW<>Slave network data is isolated from my DAW<><WIFI traffic (within my DAW).   This is good - audio is clear and everything works very well.

    If I put everything on one logical network, then it sounds like the traffic coming in over WIFI is causing my network data buffer to overrun.  This is bad - sometimes a single instrument plays okay, but the more I load it up the worse the dropouts and crackles get.

    OH, one other thought comes to mind... something else that can go wrong - your Ethernet ports might be set to Auto-Sense - meaning they will decide if they are going to run at Gigabit Ethernet, or 100b TX.  This happened to me once because either cats or geckos, or cats chasing geckos in my studio.  Upshot of it all was that my ethernet cable was damaged and one of my Macs kept changing it's mind about running at 1000Mbps or 100Mbps.   That cause a lot of crackles and dropouts!   I found it better to manually configure my Ethernet ports to 1000baseT and static addresses.   That way it works or it doesn't. It's easier to figure out the cause of the problem this way.