[Mod 11.8.2.1] Getting midi timecode from an external source
Posted: Sun May 05, 2019 6:31 pm
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.
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.
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.
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.