Could I add Midi Time Code to the feature request please? I would like to drive LightAct from a midi timecode source (as opposed to ArtNet timecode). I am then assuming if I can drive the master LightAct server with Midi Timecode, then other servers would automatically be synced by the LightAct syc protocol?
FYI, Midi Time code can be generated from a number of sources and we use an all software setup including Reaper for programming a time coded show on the MA Console - below is a video of how to setup a simple rig for programming using Midi Time code. I’m assuming the same Reaper and Midi Loop back rig would work with LightAct…
Thank you as always and now I’m off to look at the exciting Notch integration
the Mif4 device connects to the computer via USB. Windows installs the necessary device drivers at it appears as a Windows MIDI device. As far as I know, Windows maintains the list of MIDI devices on the machine, same as other devices (like sound cards, displays, mouse etc).
What this device does is take Audio Time code (LTC) and convert into MIDI TC (it does other stuff, but this is the feature of interest). If you want read about LTC Linear timecode - Wikipedia As best as I understand from some basic research MIDI TC is a protocol supported by MIDI Messages which is also a time code signal. I assume this would be similar to the Artnet Time code protocol you have already implemented in LightAct
Also, this utility loopMIDI | Tobias Erichsen creates a virtual MIDI device which can be used to send MIDI TC from a generator (like Reaper) to an application looking for MIDI TC like Grand MA on PC or (hopefully) in this case LightAct. So, I don’t think you need to have the Mif4 device to make MIDI TC work - you can use the Reaper + LoopMidi rig to test. But I’m always happy to help test if you needed
Please note, this feature hasn’t gone through our standard testing procedures yet, so if you encounter any issues, please let me know. There is also a whole bunch of (very beta) projector autoblend functionalities .
Thank you that would be great. My suggestion is to have a “time out” stop parameter - that way we can configure a system to distinguish the difference between a stopped timecode clock and an drop out or millisecond interruption in the signal
thank you as always