[Mod 11.8.2.1] Getting midi timecode from an external source

[Prometheus]

Hello,

I'm doing some testing in order to trigger cues from an external timcode source. My source is a Rosendahl mif 4( http://www.rosendahl-studiotechnik.de/mif4.html), an USB timecode device. I followed all the steps described in the manual, but I am not able to get this to work. I added a screenshot of my "Cue Control" configuration as an attachment. When I use the "Test MIDI Input..." button, I can correctly read the incoming midi timecode. However, I am unable to trigger cues with it, and the timecode does not appear in the VU meter area.

MTC_SCS.PNG (29.3 KiB) Viewed 876 times

However, when I use an internal timecode generator, the timecode does appear in the VU meter aera, and I am able to trigger cues with it. I am also able to transmit the internally generated timecode to my mif 4 when I configure it under "Control Send" as a midi output device for timecode.

Am I missing some necessary configuration? SCS and the mif 4 are clearly talking to each other, and communication is possible in both directions. This should exclude drivers as the source of the problem.

[Mike Daniell]

A log file will have been created and saved in a folder named "SCS Logs" under "Documents", and the name of the file includes a time-stamp indicating when the log started. Please email the log file from that test or a similar test to support@showcuesystems.com.

[mountainhighmusic]

I'm having exactly the same issue with 11.8.2 Platinum. Did this get resolved at all?

[Mike Daniell]

I don't have any record of having received that log file, so perhaps you could email me the log file from a run in which you have tried this.

[Mike Daniell]

Mod applied in SCS 11.8.2.1. The problem was caused by the device not send MTC Full Frame messages, only Quarter Frame messages. SCS now accepts MTC without Full Frame messages.

[Prometheus]

I just installed the newest version of SCS and I can confirm that I can now receive timecode properly from my Rosendahl mif 4. Thank you for resolving the issue.