• Date
    Chris78307
  • Date
  • Replies 2 replies
  • Subscribers 77 subscribers
  • Views 59 views
  • Users 0 members are here

Feature Request - Timecode outside of a single Mosaic Project

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

Parents

  • Interesting request, Chris. As you've identified, an implementation of this would be quite involved and seems to me a relatively niche use case. I think the best approach here would be to implement a network-based timecode. We have an internal feature request for that already, and I'll add this thread to it. Would that work for you?

  • in reply to jack neill

    I can't speak for how niche it would be.  But, I know that a recent large project deployed dozens of RIO-A's to account for this need.... add to that dozens of Audio-over-IP interfaces.... They dropped north of $100k to deal with this need.  

    Network based timecode might be an appropriate middle ground!  Admittedly, I haven't done too much research in this area... so, I don't know all of the Pros and Cons of something like ArtNet Timecode.  But, in concept, that seems right.

    We frequently deploy Dante Virtual Soundcard on computers to allow them to receive a Dante stream as timecode... then, expose that stream to the internal software (show control and media servers).  This keeps that device in-sync with its buddies.  Might not be a perfect example/solution.... but, that's how we've been handling it with computers that run playback software.  Perhaps, that sparks an idea related to dedicated playback hardware, such as the MSC-X.

    Thanks for giving it a thought!

Reply
  • in reply to jack neill

    I can't speak for how niche it would be.  But, I know that a recent large project deployed dozens of RIO-A's to account for this need.... add to that dozens of Audio-over-IP interfaces.... They dropped north of $100k to deal with this need.  

    Network based timecode might be an appropriate middle ground!  Admittedly, I haven't done too much research in this area... so, I don't know all of the Pros and Cons of something like ArtNet Timecode.  But, in concept, that seems right.

    We frequently deploy Dante Virtual Soundcard on computers to allow them to receive a Dante stream as timecode... then, expose that stream to the internal software (show control and media servers).  This keeps that device in-sync with its buddies.  Might not be a perfect example/solution.... but, that's how we've been handling it with computers that run playback software.  Perhaps, that sparks an idea related to dedicated playback hardware, such as the MSC-X.

    Thanks for giving it a thought!

Children
No Data
Related

www.etcconnect.com