Midi Note Chase doesn't work correctly (?) with negative time offset
Here's my deal: I make additional recorded tracks (synths, backing vocals) for my band to play along with. The drummer has an Alesis DM5 in his setup, so I send him a click by playing notes on his drum machine (which go to his monitor, rather than the mains).
Because of MIDI latency, if I don't do any correction, the clicks coming out of his drum machine are about 6-7ms late, compared to the (audio) clicks coming from Sonar's metronome. Or more importantly, 6-7ms behind any additional percussion tracks that Sonar might be playing via VSTs or frozen versions of same. Either way, it's enough latency that it screws with him.
If I push the click notes backwards in time (either with the Time +/- dials in the pattern editor, or the Time offset value for the track), I can get the click sounds coming out of the DM5 to be nicely sync'd up with the audio tracks. However, doing so annoyingly cuts off the first note whenever I start playback, assuming I'm starting at a measure boundary -- he hears " 234 1234 1234", which is less than ideal. Understandable, since the shifted '1' note happens before the Now time in this case, but still.
I'd think that the new Midi Note Chase thing in the 2017.01 would handle this -- the shifted note has a 240 tick duration, so it's still 'playing' at the measure boundary if it's only been shifted back 12 ticks or so -- but it doesn't.
I'll note that if I manually take all the notes on the click track and nudge them backwards so that they're no longer directly on the beats, then the Midi Note Chase thing correctly handles that. I hear the first beat, even though the Note On occurred before the Now time. But that's messy as hell compared to just entering a single offset value in the track properties.
It'd be nice if Midi Note Chase took the track Time Offset value into consideration.