This topic contains 3 replies, has 3 voices, and was last updated by Profile photo of Nick.home Nick.home 6 months, 2 weeks ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #105748
    Profile photo of Nick.home

    If you can can someone explain. If not is there a chance of seeing in the future the possibility of the system reading timecode and being able to program scene changes to react to different time points?

    Profile photo of Scotchy

    Could that be achieved through MidiTimeCode? We use Pro Tools with SMPTE and MTC broadcasting various commands. The system responds to many MIDI commands….

    You must be logged in to view attached files.
    Profile photo of Nicola A&H
    Nicola A&H

    Hi Nick,

    What timecode format do you use, and what device is generating the timecode?
    We found that most shows these days tend to run a show control system like Qlab or similar, and fire program changes or other messages to devices on the network (including dLive), rather than distributing timecode. But we’re always interested in other uses, applications or requirements.

    Profile photo of Nick.home

    Hi Nicola

    We run a multi Qlab setup which the main control system outputs Midi Timecode. The subsequent systems all sync to this. Until recently we have been running the show on a GLD with firing the scene changes via midi from Qlab. We have just upgraded to a DLive S5000 and DM32. The show runs in each setup for a month before it’s completely changed. When programming the lighting console it is able to save each cue to the timecode signal live which really speeds up the programming session. Whereas with the sound we have to create each scene on the desk then again on Qlab and manually assign the time stamps.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.