• Date
    tommulliner
  • Date
  • Replies 2 replies
  • Subscribers 185 subscribers
  • Views 6184 views
  • Users 0 members are here

Show Control and recording cue timing

Hello All,

I was having a play today with show control (for the first time) and I can't seem to get my head around it. Following information from the Show Control manual I managed to set up 8 cues and create an event list with timed events for each cue recorded from live the first starting at time 00:00:00, the next at 00:00:12 etc etc.

What I'm trying to get my head around is how to play back the list of cues with their timed triggering. The only way I can currently get them to play back is by manually enabling the 'Internal' clock. I tired programming that command into a macro and attaching the macro to cue, but is there another way of getting the event list to trigger in a cue?

Any help would be much apreciated, a rough step by step would amazing!

Many Thanks.

Parents

  • Timecode event lists are usually used when there's an external clock that you need to synchronise with - eg video or audio tracks.

    The internal timecode clock is generally intended for test purposes, when you want to check the show but don't have the real timecode source available.

    As Hans said, the internal timecode clock can be started/stopped manually or via Macros.

    tommulliner said:
    ...the first starting at time 00:00:00...

    As a point of style it is generally not a good idea to have anything happen at Timecode 00:00:00.00.

    When using timecode you always want a short section of "preroll", where timecode is passing but nothing is due to happen yet.

    This preroll serves two purposes:

    • It allows the operator to see that timecode is spinning by before anything is due to happen.
      - And fix it if it's not spinning, eg by plugging the cable back in!
    • It allows the console time to perform the initial clock sync.

    While MIDI Timecode and the internal timecode source are capable of reliably sending timecode 00:00:00.00 (as they don't have to sync), SMPTE/EBU LTC and some other forms of timecode take some time to send what time it is, so will always miss the 00:00:00.00 (unless you start from 23:59:xx and roll over).

Reply

  • Timecode event lists are usually used when there's an external clock that you need to synchronise with - eg video or audio tracks.

    The internal timecode clock is generally intended for test purposes, when you want to check the show but don't have the real timecode source available.

    As Hans said, the internal timecode clock can be started/stopped manually or via Macros.

    tommulliner said:
    ...the first starting at time 00:00:00...

    As a point of style it is generally not a good idea to have anything happen at Timecode 00:00:00.00.

    When using timecode you always want a short section of "preroll", where timecode is passing but nothing is due to happen yet.

    This preroll serves two purposes:

    • It allows the operator to see that timecode is spinning by before anything is due to happen.
      - And fix it if it's not spinning, eg by plugging the cable back in!
    • It allows the console time to perform the initial clock sync.

    While MIDI Timecode and the internal timecode source are capable of reliably sending timecode 00:00:00.00 (as they don't have to sync), SMPTE/EBU LTC and some other forms of timecode take some time to send what time it is, so will always miss the 00:00:00.00 (unless you start from 23:59:xx and roll over).

Children
No Data
Related

www.etcconnect.com