Here are my results:
So that’s what I mean by just a little late: don’t notice it if the metronome’s off but when it’s on you can hear that little bit there. I would normally take that and drag it 6 pixels to the left.
The only DAW I have that this doesn’t happen in is Luna (which isn’t yet a great DAW for composing in…excellent for mixing though).
Pritty much the same as yours by the looks of it
How strange for Luna to be bang on ( not tried it myself though) turns this into abit of conundrum , that said is it because Luna auto quantises after recording or ?
Doesn’t matter what buffer size I set, maybe raise ticket ?
on the face of it looks correct therefore can be deceiving until zoom in to see that its not
Ya…the reason I’m not overly bothered by this is because it’s no worse than trying to line up a hardware MPC with MIDI sync…you gotta futz with the compensation settings down to decimal milliseconds and at best you can get it to right where Overbridge already is. So I’ve gotten used to recording and dragging.
I’m not gonna raise a ticket. I tried that already with a previous issue and got…questionable treatment from the support staff. And trust me, I was being nothing but polite and agreeable.
I don’t use overbridge that much and I have a midi card that transmits the clock to all my instruments, so my experience is not comparable to yours, but I noticed one thing, until a few months ago with the “pattern” option and -50ms the tracks were quite aligned, since live 12.1 came out something has changed and I got to -70ms… maybe it’s better that they don’t do anything 
i dont know if its relevant but because elektron devices run at 48k i switch ableton to 48k … it might not be clever / correct thing… just a guess that it might help… (well, digitakt samples are 48k )
but i dont sync internal ableton midi / triggering with external devices… i typically keep my hardware work seperate to ableton stuff noodles .
Yes fair enough just thought usb handles midi/audio better so therefore wasn’t expecting it to be off , should be bang on
Can’t be anything to do with abelton updates since if was the case would have effected the snow as well , still records bang on to grid audio over usb
Projects always 48k , have since established though that it’s the same for others so will just crack on enjoy it for what it is rather than what it isn’t doing , although still wouldn’t mind this looked into by the devs as misalignment across the board it seems so could be tweaked within the os
Anyhow all that aside , really loving the plugin for making patches , other fixes etc , appreciated !
Still wondering, as it seems the release notes only focus on added features for (new) devices.
You gotta roll with whatever fuzzier model of safety/stability here you’re comfortable with, there were no firmware updates for them needed to match the new version of OB.
The application/engine was likely improved, we wouldn’t have any baseline to compare performance to… but at least it’d be an easier downgrade if you encountered any issues.
Thanks, the downgrade option indeed is a safety net (for as long as OB supports the MacOS / Windows used).
I do understand no OS update is needed (or even available) for the OG-series of devices. But as OB is developed, possibly incorporating features in the OS of the newer devices, I’m wondering if those dependencies could break or interfere with the ‘older’ integrations.
So I’m wondering about the application / platform architecture, if this are (partially) separated in-app process?
Caveat- I don’t work for Elektron so these are assumptions based on the piecemeal memories of how OB works at a lower level, my model may be inaccurate.
Elektron (please correct me anyone if this is inaccurate) licenses their USB audio driver for use with their multiple embedded platforms and may have some say over bugfixes for general-purpose computer USB chipsets + their embedded platforms) and to optimize the OB streaming feature improvements / performance, developing OB on top of the stable / predictable driver.
If their changes in driver and OB software are primarily surrounding newer platforms, it is unlikely that an obvious regression would miss testing. Not impossible, but fairly unlikely. As well, if they are not writing the raw USB driver I would imagine that this sees a lot of adoption that would help with many clients potentially reporting concerns with any stable build.
Often there are updates to tool libraries, and between builds of the USB Driver or OB, it is possible that milder performance benefits could occur as well. I also haven’t really checked how often the USB driver gets updated with each release vs other OB components. Perhaps the driver is necessarily updated with with each release, but I haven’t spent any time verifying this.
In the end, if things are working fine as is, it’s unnecessary to chase illusory benefits through upgrading. Do I compulsively do so anyway, beyond a delay for any firmware updates to devices? Yes 
To more directly answer your question-
Some components will be shared, some components will be unique to whatever platform is being fixed. I imagine the common shared components will be stabler than more unique aspects, the new Takt 2/Tone 2 configuration may be a superset of them…
This is one of those things that people need to build their own models around to gauge risk levels they’re interested in, “are they separate or shared architectures” is both yes and no depending on area of the code 
Not 0 risk, but fairly low as far as these things go.
I don’t recall hearing complaints about regressions due solely to newer versions of OB that weren’t also paired with large enough changes to device firmware, though someone might also have different experiences there to offer.
Does that make sense, so far as my understanding goes?
I have a solution here for the (very) slight sync fuzziness on Live. Keep in mind I just started using Live a month ago so everyone else probably already knows this!
First go to the bottom-right corner of the app and click the down-arrow beside the mixer icon. Turn on Track Options.
Then adjust the Track Delay control until your drums line up with the metronome. You can do it in milliseconds (the yellow “ms” button) or, if you press it, you can do it in samples (blue “Smp” button).
Lines up perfectly now and never have to think about it again. No “recording-and-sliding” chores.
Nice, thanks for that!
