JellyJonas
New member
So, after having put S1 on the shelf and returned to Nuendo for a couple of projects I decided to go back and see if I could figure out why S1 was out of sync with my video player (Video Sync Pro 6).
Turns out that S1 sends 10 byte MIDI Universal Real-Time SysEx messages which are always 2 frames off (ahead) from the actual playhead location in the DAW when pressing transport stop. It doesn't matter if you do it by pressing space bar, clicking with your mouse or using a controller like the FaderPort, as soon as you hit stop S1 will send the Sysex end message and this message will include an incorrect TC.
I will of course talk to S1 support about this but holy cow, this is a BIG problem and please be aware of it all of you. Not sure how/if this affects Embedded MTC MIDI broadcast but might be good to double check.
Please check attached picture.
Jonas
Turns out that S1 sends 10 byte MIDI Universal Real-Time SysEx messages which are always 2 frames off (ahead) from the actual playhead location in the DAW when pressing transport stop. It doesn't matter if you do it by pressing space bar, clicking with your mouse or using a controller like the FaderPort, as soon as you hit stop S1 will send the Sysex end message and this message will include an incorrect TC.
I will of course talk to S1 support about this but holy cow, this is a BIG problem and please be aware of it all of you. Not sure how/if this affects Embedded MTC MIDI broadcast but might be good to double check.
Please check attached picture.
Jonas
