Vienna Symphonic Library Forum
Forum Statistics

180,746 users have contributed to 42,140 threads and 254,362 posts.

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

  • Weird Latency Problem Solved

    I wanted to post this in case anyone else has this problem. It occurs when combining Vienna libraries with other libraries, at least on Sonar (now Cakewalk/Bandlab). The problem, which affects both Vienna and Synchron libs, is that they lag behind the other libraries' instruments. I could not figure out a way to solve it, until I posted it on the Cakewalk forum, and the resident DAW Genius, scook, responded. Cakewalk has a way to set the timing of a midi inst. ahead or back by a specified amount. This turned out to be -10 in my case. You do it on the track imspector, which has all kinds of controls on it, pan, velovity etc. I never knew what the timing one was for, but I do now. The best part is, it doesn't affect the notes in staff view, they still display correctly (unlike using the slide function, which messes them up).

    I don't know how many folks use Cakewalk/Sonar here, maybe not many, but this could affect other DAWS as well, so maybe it might be applicable. It solves a problem which has plagued me for years. Like most of this stuff, it's so simple, once you know the trick. No more using inferior sounds, now, I can use Vienna's great sounds whenever I want! Wonderful!


  • Hi,

    you can do the same with Cubase on purpose. But the default value is 0.
    Is there a reason Cakewalk sets a different default value then zero as track delay?

    Best, Ben


    Ben@VSL | IT & Product Specialist
  • I figured you could. Probably any DAW. The deafult value in CW is zero, I was not clear about that. I initially set Synchron strings to -10, but have found I need to set it even lower. Also now I have found East West stuff sometimes needs it. Generally, strings need the most. 

    One problem, however: if you set the first inst's that are playing as the piece begins, you won't hear any sound, because their start is, well before the piece begins, if that makes any sense. So you would need to offset everything by say one bar. So this whole thing is more complicated than I thought. Guess I flunked midi 101...


  • Strange... Cubase calculates the latency compensation all by its own. No need for me to tweak it. To make sure the legato transitions happen in time I start the second note a little too early. Even no problems when combining real recordings with virtual instruments.

    Ben@VSL | IT & Product Specialist
  • I was using Reaper for awhile, and I don't recall having this problem. So it may in fact be due to Cakewalk not adjusting for the latency. but I think I'll figure it out eventually. If not, I may have to switch to another DAW. That is problematic, because I have not found one that will work well for my particular workflow. that includes cubase.


  •  

    Well, often the DAW has in the preference menu a setup for "Latency compensation on/off" you should find it, and check the status. Even better reading the Manual section of your DAW describing it, so you get very useful and accurate explanation of the way your DAW manage latency.


  • Thanks fatis12, I am checking into that, although so far I haven't found such a setting. But I asked a question on the Cakewalk forum and am waiting for a response.