Hello,
I was testing MTC generation from REAPER for a project and found that while MTC per-se (F1...) was transmitted as it should, the SYSEX message (F0 7F 7F 01 60 00 00 00 F7) that is sent when one hits the rewind button for example, is not transmitted at the time the rewind button is pressed but only at the time the PLAY button is clicked. This does not affect REAPER, but it creates dis-synchronization between REAPER clock (which shows a 0:00:00:00 resulting of the rewind request) when the receiving program clock still shows the time at which the rewind button was hit (0:00:30:28 for example).
I believe the SYSEX message that sets the full clock should or could be sent at the time the rewind button (or any other full time generating action) is clicked on.
-Patrick
I was testing MTC generation from REAPER for a project and found that while MTC per-se (F1...) was transmitted as it should, the SYSEX message (F0 7F 7F 01 60 00 00 00 F7) that is sent when one hits the rewind button for example, is not transmitted at the time the rewind button is pressed but only at the time the PLAY button is clicked. This does not affect REAPER, but it creates dis-synchronization between REAPER clock (which shows a 0:00:00:00 resulting of the rewind request) when the receiving program clock still shows the time at which the rewind button was hit (0:00:30:28 for example).
I believe the SYSEX message that sets the full clock should or could be sent at the time the rewind button (or any other full time generating action) is clicked on.
-Patrick
SYSEX & MTC transmission from REAPER
Aucun commentaire:
Enregistrer un commentaire