Seems like can be used for tracking with some fidling with alignment afterwards, but for live vibes it’s a no go… There’s lots of 8+ channel usb audio interfaces that can operate with just a few milliseconds latency, so hopefully they can optimize this eventually…
2 Likes
Can I just use the plugin and route audio separately? I already have all the physical inputs so I don’t really need to stream over USB. I just want the convenience of the plugin.
1 Like
I did spend some tome with OB 1.15 in Win10 Cubase 9 last night. I’m using and Innnerclock SyncGen2 and the latency is 3115!!! samples to play in sync with my other midii gear and VSTi’s
This is totally unusable, without OB in midi only mode, it’s 882 samples
I’m also using my RYTM and A4 via the analogue outs (though OB would have been really nice to break out 4 channels)
Currently 1.15 is NOT usable for me. I don’t want to fiddle around, or record.
I just want stuff to be tight, realtime and instantly available, without recording or rendering or enabling/restraining delay compensation.
I would also welcome a midi control version of OB as well.
Only an enhanced midi connection, NO USB Audio, so the performance stays identical as when the RYTM is configured as midi only (non OB mode)
OB Is nice when sitting behind a macbook, with the Rytm as sounddevice. But it just pulls the realtime performance down of more complex setups.
So a midi only version of OB please, WITHOUT any audio or sequencer clock syncing.
1 Like
i have latency issue too when i recording from AR
i change from clock to song position and seem work very nice,i continue to do some test but at the moment this setup give me nice records
motu ultralite mk3 buffer 256 (i think for most of you is high but for me is good)
ob buffer 128
win 10
overbridges point is to produce zero latency. have you something like the cpu sapping izotope plugins effecting anything?
… the best way to run overbridge is to run it dry, no effects in daw… then you can add them after, i know this doesnt help you but i find overbridge absolutely spot on. the only issue i have ever had syncing is when ive forgotten ive got izotopes mastering plugins running. try uninstalling and adding over bridge again perhaps
1 Like
There is no debate that OB causes about 30ms latency. Even Elektron acknowledges that. Of course, that does not matter if both of these conditions are true: a) You are working in a DAW with PDC. b) You are not playing an instrument.
I would be willing to bet a LARGE sum of money that ALL of the people who are not bothered by OB’s latency do not play their Elektron instruments, and instead they “type” in their music using Elektron’s buttons. Before I get yelled at, there is NOTHING wrong with that, and it does not make their art less worthy. I would also be willing to bet an equally LARGE sum of money that ALL the people who DO play their Elektron instruments are bothered by OB’s latency. There’s no way a musician (in the classic sense - y’all know what I mean) would not be bothered by OB’s latency.
6 Likes
Fair point
1 Like
Yep just give me OB midi only, without the ASIO soundcard part.
This needs to be able to be turned off. OB is jow holding back the latency of my whole setup
Not sure how windows handles multiple audio interfaces but on a mac I’ve tricked OB into much lower latency by combining it as an audio interface with my regular interface into an aggregate device, then setting my interface to 96000 sample rate and enableing drift correction(resampling) of the rytm in the agg device setup. This was quite awhile ago so I don’t rememmber the figure but it was much lower than 30ms…
Never thought i would suggest a Virus TI feature for overbridge.
But that “live” button that reduces latency from 77 ms to 5 ms is really helping a lot.
i’m sure we would all accept some compromises like disabled features in that mode to get latency down to max 2x 5 ms while recording live.
anything above is really hard to work with.
(and not even disabling the RYTM plugin does help, as ableton still keeps the latency with disabled plugins.)
if sync/clock is the problem i would happily accept not to be able to use the rytm’s sequencer in that mode, but only use it as a synth/sampler.
hi,
im having the issue, i use overbridge, its cool, and timimng is very solid.
my problem is that when i want to use the internal sequencer with eurorack gear, which itself goes through my interface, it has another latency, so that adds up and is again out of sync.
would be cool if i had a global delay compensation for the cv track in overbridge.
Could you please describe what means “combining it as an audio interface with my regular interface into an aggregate device” ?
1 Like
On a Mac there’s an app called audio midi setup in /applications/Utilities. Open it and you should see your available audio interfaces, if not go to the window menu and select audio. On the bottom click the + icon and select create aggregate device. Next you choose your devices by checking the box on the left, all of the in/out of the devices you select will be combined into one virtual audio interface with the sum total of all combined in/out. The one you choose first will be inputs/outputs 1->however many the device has, the next device you choose will have its in/out numbered appropriately after that. I choose my audio interface first so it’s in/out numbers appear as normal, and then I choose Rytm and its in/out will be the last ones in the aggregate. There will be a picture of the combined interfaces showing there in/outs and if you want you can click them and give them custom names. To get the low latency and just because I prefer I set my audio interface to 96k, but this does use a lot of cpu. Where it says clock source set it to the audio interface. For overbridge device check the drift correction box. Double click aggregate device on the left to give it a name.
Now when you in an app you can choose the agg device as your audio interface and all the interfaces in/out plus the overbridge in/out will be available… 
2 Likes
Hmm, no its not. Overbridge only adds to latency. Then it uses the plugin to delay all of the other stuff in your sequencer so it has the same lateny as what the elektron device gives you.
So its a synchronization tool, but it adds latency.
This is a very very important difference and the reason overbridge is useless to me.
2 Likes
Overbridge definitely adds way too much latency to be used in a music production setting. Probably works well for mixing, or if you only use sequencers and never play an instrument.
You can get the plugins to report 0 samples latency by disabling all the outputs/inputs in the Overbridge Control Panel, and using the analog outputs on the units.
The problem is that this has a major bug that has been left unfixed for multiple versions now: the kernel sometimes gets stuck in a 100% CPU loop, with the following message being logged thousands of times every millisecond:
PGDevice::rtsProcessIsocIn_Elektron numFrames(48) != numAudioFrames(0)
I really hope this bug can be fixed.
3 Likes
You definitely don’t want to use an aggregate device! It adds lots of latency
1 Like
Im new to OB (but had my elektrons for 1-2 years), been reading the thread cause I haven’t been able to completely setup AK-AR-OB so im gathering info
I was thinking, if you are only playing your elektrons, can’t you start recording and monitor your playing through the machines’ headphone outputs? There won’t be latency in the headphones out
Focusrite has zero latency live monitoring.
You just mute tracks in DAW and send audio directly through card.
Latency of lowest common denominator.
@safetyofobjects, that’s a good idea(!), but I also like to use an outboard Kush Tweaker compressor, plugins, etc., and I really value playing through it live. The immediacy of results gives me ideas that I would not have if applying effects after the fact.
It seems like this is an issue that would be fairly easy to solve: using Overbridge not as a sound card, but as a controller.
@Purusha, really? Do you have a source for that, from what I could find it’s either “up to 300ms” or the sum of all devices latency. If it’s LCD that would mean lcd([10, 30]) = 30 samples, while lcd([10, 31]) = 310 samples, which seems odd.