Currently, Linear Time Code (LTC) or MIDI Time Code (MTC) enter the "system" via a RIO-A or an MSC-X (Mk 3).
In either instance, that timecode stream is bound to the Project, since the hardware is bound to the project.
I'd LOVE to have the timecode stream available outside the project - available to other Mosaic hardware, running other projects.
In the ideal scenario, LTC would hit the input of a RIO-A and now be available as a timecode stream to any Mosaic Controller running any project that is within the visible network.
- It could be a "multicast subscription" model, similar to Dante.... or any sACN Universe
- It could be secured via a passcode, if necessary.
- If truly necessary, it could have an offset variable to account for latency.
I understand this is quite different than how the stack is handling LTC at the moment.
However, we're investing a lot of effort and money in infrastructure to distribute the timecode to separate devices spread across a given facility. And really, they're often referencing the same clock(s).
CRaZy additional requests....
- a small display on the RIO-A hardware or MSC-X hardware showing a running clock
- implementation of other network-based timecode protocol - such as ArtNet Timecode and/or PTP
Thanks!
/Chris