Feature Request: Firing Scenes via Timcode MTC

dLive dLive Feature Suggestions
1

Hi all,

dLive has an excellent scene management system but the ability to launch snapshots via MTC Timecode is something I would really need to have. I do understand that this is possible via Qlab software but I would not like to add another weak link to a big production. All the major touring pop&rock shows are running on LTC. As there is no physical LTC/XLR connection, using MIDI over TCP would be an acceptable solution for this. Converting the LTC coming from stage to MTC using something like Rosendahl MIF4 is fine.

I’m sure this has been requested before, and I do hope it’s coming on the next software update.

Thank you!

Screen-Shot-2019-06-14-at-12.24.08-AM.png
Screen-Shot-2019-06-14-at-12.24.08-AM.png834Ă—544 21.4 KB

2

Hi Pertu,

Thanks for the suggestion, we’ve certainly added it to the feature request list. As we mentioned before off ticket, (just repeating here for others to see) you can automate a lot of this using a program such as qLab or Show Control. But it would be nice to have such functionality in with the console.

Appreciate you taking the time to get in touch.

3

Hi,

I do agree with Perttu on this and would like to see this kind of feature in the near future. Any ideas when could this be possible?

Thanks!

  • Niko Laasonen
4

The need for MTC is still there. I’m really hoping to get this in the V2 Software. PLEASE.

5

100% agree with Perttu. Midi is great but when a show is running on timecode I don’t want to add a laptop and an interface just to convert from tc to midi. TC also has the benefit of putting out a continous stream from which every device can pick as many “points” to make recalls as it needs. Not having a timecode option holds dlive back in my opinion.

We also need a simple way to disable listening to incoming midi (or tc if that happens). Preferebly via softkey. Thanks!

6

Hi all,

Back in 2020, I posted here about the need for MTC (MIDI Timecode) support to trigger Scenes in dLive. I’m still hoping to see this added — and I know I’m not alone :slight_smile:

As dLive continues to expand in touring and theatre applications, timecode integration is becoming essential. I’d like to ask the global dLive community to support these requests and help show Allen & Heath there’s strong demand for them.

Feature Requests:

• Trigger Scenes via MTC

For fully automated shows, this is a must. QLab and workarounds exist, but native support would be far more reliable.

• Trigger Actions via MTC

Imagine the power of combining Actions with MTC: firing FX changes, channel mutes, MIDI messages — all locked to timecode.

• Capture Time (Timecode Stamp Scenes or Actions)

During rehearsals, let us “capture” the current MTC time to create cue points. This would speed up programming massively.

Why MTC?

LTC is still the backbone of most large-scale touring rigs, but MTC over TCP is a solid compromise given dLive’s architecture. External LTC-to-MTC converters like Rosendahl MIF4 are common and easy to integrate.

I truly believe that MTC support would push dLive even further into the mid-sized Theatre and Touring automation world — without adding external software layers or complexity.

If you agree, please comment below!

P.S. I’ve added my old mockup image for laughs.

IMG_0625
IMG_06252796Ă—1290 394 KB

Best,

Perttu Korteniemi

FOH Engineer & Production Manager – Haloo Helsinki!

9 Likes
7

I would also love to have a native LTC/MTC option instead of having to rely on external solutions.

2 Likes
8

Big +1 but it should be native LTC. MTC has zero advantages, and would mean having either a converter or a midi integration with playback system. Native LTC is ideal.

4 Likes
9

I agree LTC is my preference too over MTC. Much simpler.

1 Like
10

+1.

Bands track rig is already rolling LTC for lighting guys. I have LTC pass through our desk to be distributed via Dante for media servers and an analog out at FOH for their desk. Would be nice to just natively read it!

1 Like
11

+1

LTC, not MTC. No reason you can’t just have a page similar to Talckback to designate the source and the decode takes a fraction of processing compared to any of the new UltraFX engines.

Some observations from doing this on other shows (with dLive and custom TC software):

  • You need the ability to specify a +/- offset from received, either in frames or time (yes, you have to project a - time offset). I’ve seen different source cause delays in TC that throw an entire show off, especially if MTC was anywhere in the path.
  • LTC instead of MTC any day. MTC has a minimum of 4 messages to establish location and is nowhere near as robust as LTC. As noted elsewhere, we also dropped LTC on Dante and distributed it everywhere.
  • Enable/Disable for LTC, with appropriate LED indications on soft keys. The last thing you want is the console recalling scenes while you are updating the show!
  • How do you handle time jumping backwards? I ran into it in rehearsals for long numbers. I haven’t used the SSL side, but we implemented it as “Key Scenes” (like key frames), such that a timecode start that wasn’t within X seconds of the next key scene (aka, song start) jumped to the last known key scene in time order and did a quick roll-forward.
  • LTC display (and GREEN vs RED for enabled/disabled) on-screen.
2 Likes
12

Hi everyone,

Thanks for the passionate discussion – it’s great to see how many of us care about timecode integration on dLive. Just to clarify, my original intention was never to create an MTC vs. LTC debate. Quite the opposite – We simply need dLive to support timecode natively, and I have to agree with most of you: LTC is the way to go.

I was kind of hoping that MTC would be easier (read quicker) to get implemented.

Please keep the comments, upvotes, and ideas coming in the this thread – the more voices, the better chance we get real implementation:

Let’s show A&H that the demand is real! :slight_smile:

1 Like
13

I do agree with this Request. I would vote for both LTC/MTC as anyway in the soft a LTC will be converted in MTC to speak with the Soft inside the desk.

I use now a LTC going in the monitor rack, entering in Dante to my Qlab fireing midi cues thru midi over ip…
this is way too much failure points. it could be all inside the desk !
can’t wait to have an update with that feature.

many functions could be triggered by L/MTC as

  • Scenes
  • Actions
  • Automations (this is a bigger deal I know)
  • …

please think of making a timeline editing view of the TC events !

1 Like