Windows tools for Midi clock offset negative/positive

[AudioBabble]

I need a tool that can do negative and positive MIDI clock offset, particularly negative in my current use-case.

I'm trying to send clock out from my DAW, via my interface out into a hardware sampler (which unfortunately doesn't have its own offset).

I use Reaper DAW and that has a clock offset -- it will take a negative value, but actually any value less than 0 does nothing. Plus, it's in milliseconds which is far from ideal.

The ideal would be a percentage value, or a tempo-linked value, like 1/64 -- so that no matter what the BPM, the offset will adjust accordingly.

I realize that negative offset takes a bit of thought since the first beat can't be offset negatively, but surely the second and subsequent beats can?

So.. I think I'm looking for a standalone windows app to which I can feed MIDI clock via a loopMIDI driver (or maybe the app has its own driver), which then sends out the adjusted clock value via my interface to the sampler... is there such a thing?

So.. to recap: 1. MIDI clock offset negative & positive, 2. "tempo" not "time" based offset, 3. (icing on the cake) fractional translation of MIDI clock, e.g. 1/2 time, x2, etc

Programming-wise, I don't imagine this is terribly complicated stuff so the question really is whether anybody thought these are useful enough features to make an app for.. MIdI's been around so long it may even be something fairly old.

Be interested to hear any suggestions, cheers

[BertKoor]

How are you so sure it's Clock messages, and not plain note on/off messages that need time travel?
Asking since you're sending midi to a sampler, not a sequencer.

Another thought: fix the Audio stream coming out of the sampler instead of the Midi stream. Or adjust the rest in Reaper via a common bus.
This all sounds like hardware latency compensation.

[lfm]

There's a JS script in Reaper Delay/time_adjustment where you can set this in ms+samples for a track.
This give Reaper info that this is plugin latency to compensate for and places audio accordingly.

I used it to line up external gear so that audio came on the right spot as recorded.

I think this means that daw has to delay midi clock as well accordingly, but never tested that.
If daw does not do that any pdc would ruin sync with external gear, if clock still sent clock on the grid but everything else delayed.

In Cakewalk/Sonar you just set offset in ticks for midi itself. But not sure if midi clock is is affected.

Otherwise I only know of MTC(midi time code) that many hosts support and offset can be set this way.

Otherwise my questions is the same as BertKoor, why clock?

[AudioBabble]

Thanks for the replies -- I should probably define my situation a bit better:

It's a Korg ES-1 "sampler" I'm trying to control, but you could just as easily call it a sequencer since what I'm actually doing is triggering a sequenced pattern on it. The Korg does not respond to MTC at all, since it's just designed to trigger patterns, hence my initial idea that Midi clock is what i need.

The pattern is a "shaker" sample -- therefore in actual fact the transient of the sample is a good 25ms later than the start of the sample, which makes it sound "late" in practice.

I'm actually using it as a metronome to play drums to -- i know it might sound a bit convoluted (as in why not just use the metronome in Reaper?), but it really works for me on a variety of levels.

I read somewhere that the offset for midi clock in Reaper can only respond down to -20ms -- I have yet to test this, it may well get me close enough.

However, the Time Adjustment Delay JS effect mentioned by @lfm above would be a viable alternative since it seems to respond to any value, negative or positive.

In my case I might have to go a bit old-school however and actually make a MIDI click track in my project -- that way I can trigger the shaker sample via MIDI note out instead of starting a pattern via MIDI clock.

Thanks for the help, I think I'm on the right track now!

[lfm]

Also remember how Reaper works and realtime monitoring.
- if no plugin latency at all, the delay on source will be one asio buffer on output
- if having a single plugin reporting 1 sample delay, it will be two asio buffers on output adding to roundtrip
But a recorded clip will be placed properly.
- then if having more plugins reporting latency lets say more than one asio buffer total, it will be 3 asio buffers delay realtime to out to monitor.

So this can be useful how to proceed if getting longer delays that wanted.

First thing I discovered using Reaper 2010, my 128 samples buffer for guitar was too large not to feel delay. So had to go down to 64 samples buffer to get decent delay.

[AudioBabble]

That's a good point! Mind you, if I choose to direct monitor via my interface, it's not going to be problem, still I'll probably just end up experimenting with JS delay plugin until it "sounds" right.

I seem to get away with 128 for guitar purposes usually, I have it at 64 for drumming though (and mix down to stems beforehand to avoid plugin congestion)... apparently reaper tells me this is 5.6ms total. I'm running the live audio output of my roland kit at the same time as Superior Drummer VST and together they make a very nice live kit!

[lfm]

I have a similar setup with Yamaha DTX700 and Addictive drums or the module itself.
I will be happy the day I play as tight as when 5 ms becomes a problem.

[digitallysane]

I guess you'd be able to do that with either Loomer Architect or Synergy MIDI Tracker.

[maanga]

If you are using a USB midi, try connecting to a different USB port that is on another bus or try increasing the USB speed to 128 khz or more and test.
Regards.