I am actually having trouble with the TR1000 and Omniclock - does not seem to push it back or forwards with the plugin. I note there are Four USB MIDI Output channels though (TR1000 / TR1000 CTRL / MIDI 1 and MIDI 2) so maybe it’s an error on my behalf as I have not spend any time with this machine yet.
Yeah got it timed dead on with the TR1000 delay sync anyhow (as well as my hardware clock). Just odd how I cant do it in the plugin but looks like its problem with my setup
Chiming in here quickly, I own Rapid Flow and we built Omniclock. I will try to answer questions as they come up. Omniclock does compensate for plugins that add additional latency. Say if you add an EQ with linear phase to your master and the plugin reports it s latency to the DAW correctly, our clock will stay where you set it. Tested yesterday with Fabfilter. Sorry the info you got was not correct, have to inform my team
Do you somehow ensure that the operating system schedules the MIDI output with similar priority as audio, or is it subject to the same lower priority scheduling as DAW midi output that leads to jitter and other timing delays?
This is a good question. I can say when I use the Nome, any audio I record in, I turn off keep latency. May just have to record both ways to see. But if you try it with keep latency off and the audio is ahead of the grid, you will probably have your answer.
I just checked my session and I have keep latency on. However one quirk about how I work, is I monitor everything through live and my soundcard in real-time so what I hear is what I get. Not sure how this would be if I were monitoring off my mixer…
This is a little tricky to explain and also entails some of our IP, but what I can share is that our MIDI clock is so stable and locked in, that if your CPU hangs and stutters, when it comes back, our clock will still be in sync! As such it is more stable than any standard MIDI clock I have used in the past from any DAW I own.
Really! Try it, just lower your buffer till your CPU is overwhelmed. Even if audio drops out and your DAW hangs, when it plays again our clock will still be in sync. I know it sounds crazy but it works. I was honestly pretty amazed when I found this behaviour on the Alpha tests.
Thanks for reply - I mean in response to the specific question…
‘Do you somehow ensure that the operating system schedules the MIDI output with similar priority as audio, or is it subject to the same lower priority scheduling as DAW midi output that leads to jitter and other timing delays?’
I’m running it through a MiOxl currently and not getting sub sample jitter results ?
Ive no idea about the techical aspects of the plug in but it def fixed timings of my op-xy and rytm and the jitter is pretty much non existent on each device
Will keep my ACME and multiclock but its def worth a look if you dont have the cash for hardware clock and certainly a try with the trial period
does that mean that there is jitter but it realigns all the time? thats what ableton does already, right?
i can sync perfectly in the broader sense. it just jumps around
edit: do you mean the external stuff with “system”?