How to fix Overbridge Latency

[@weinbob]

Nice! Your production quality (use of video examples) is really good! Good teaching video-I hate those snap, popples and cracks…

[@subliminalsequences]

Thanks!

[@OtoMeskhy]

Thanks for the nice tips! Did you do any tests with changing Plugin buffer size property in Overbridge standalone app settings? Depending on it, the VST gets some crazy latency (60+ms for 265...)

[@ZozillaThaGreat]

How do you handle the offset when boucning from overbridge and other vst'i's Vst'i are sample aligbned vbut overbidge being ot's own thing , recording ofsset in my settings (studio one) doesn't do anything .... i don't understand why ... any clue ? Great video by the way ....

[@kosmicdriver]

Thanks, never saw this error before. Really helpful

[@subliminalsequences]

Glad it did the trick!

[@GeorgeLocke]

My limited OB experience with bitwig has been strange because the OB audio comes in a good 300 ms _early_. Bitwig tries to account for plugin and hardware latency like Ableton, but this is pretty annoying.

[@azimpradhan]

Doing the step of opening the stand alone digitone app and setting the sample rate and buffer size there was not necessary. That only sets the sample rate and buffer size for when you are using the stand alone app. The digitone vst plugin only looks at the buffer size and sample rate configured in your DAW.

[@subliminalsequences]

Appreciate the insight and that does make sense. Have you found any additional tips for dealing with OB latency?

[@azimpradhan]

Other than the ones you mentioned: - make sure that your overbridge device does not have any input/output/sync turned on in the ableton midi sync options. Also in your device, make sure it is set to overbridge mode. Doing that makes it work quite well for me.

[@muchomacho79]

@@subliminalsequences Just skip overbridge altogether and adjust track delay in audio config settings in Ableton. While I was initially stoked on OB I now look at it as a novelty.

[@HelicopterRidesForCommunists]

@@muchomacho79 it’s not, and that introduces more latency than correctly using OB.

[@HelicopterRidesForCommunists]

@@subliminalsequences Tip 1: driver error compensation between your audio interface and Ableton. Tip 2: use Ableton’s external instrument plug-ins to route audio/midi through instead of the regular midi track + audio in. Tip 3: use “lighter” effects - hover your mouse over them to see how much latency they introduce and try to use ones with 0ms. Tip 4: set it to “in” instead of “auto” and perhaps even try using an audio interface with direct monitoring capabilities.

[@HelicopterRidesForCommunists]

Hey there thanks for the video. Heres a few tips I like to add. You should follow Ableton’s guide for driver error compensation for your audio interface. Also, and I don’t see enough people doing this so I’m trying to spread the word, you should be using Ableton’s external instrument plug-ins to route Overbridge/ audio/ midi through. It has far less latency. It also gives you an extra gain knob and you can put audio effects right on that midi track which is convenient especially when using macros.

[@subliminalsequences]

Hey! Thanks for sharing that. I will have to test that out. I haven't used Overbridge in a hot minute but I will try the external plugin trick. Thanks for stopping by!

[@HelicopterRidesForCommunists]

@@subliminalsequences Sure no problem man. Yeah give it a try. I hope my instructions/ description was clear enough.

[@GeorgeLocke]

Nice B roll lol

[@subliminalsequences]

thanks ;)