Backup, and LTC

I don't think the way that timecode currently is implemented works well in a backup system, but perhaps I am thinking about it incorrectly.

Equipment
Roadhog fullboar 4
PC running Hog 4 pc (With LTC Widget)
DP8000

The Roadhog, and Hog PC are both running a server, and are assigned to #1.

My problem is that, I can only assign 1 timecode source to the cuelist.

So, if my main console fails, timecode cues stop being played back, until I go into my backup, and change the timecode source to the widget plugged into the pc.

Is there a way to set this up to have it work better?

Thanks,
Josh
Parents
  • The macro is a good idea, and I don't know why I didn't think of it.
    While I would prefer an automatic option. This would be acceptable.

    As for cable worries.
    I run separate cables from FOH to backstage, or I run a rapid spanning tree switch, which allows for multiple runs backstage, in case one fails.

    Or if that isn't possible, I will place an additional backup backstage, next to the ethernet hub. Once again, with a separate cable run.

    For The FOH truss, I never run a single DMX cable to the truss, usually 1 per type, or 8 fixtures max.

    Once again, never allowing for a single cable to kill the entire show.

    Then again, I run tours, so redundancy is key.
Reply
  • The macro is a good idea, and I don't know why I didn't think of it.
    While I would prefer an automatic option. This would be acceptable.

    As for cable worries.
    I run separate cables from FOH to backstage, or I run a rapid spanning tree switch, which allows for multiple runs backstage, in case one fails.

    Or if that isn't possible, I will place an additional backup backstage, next to the ethernet hub. Once again, with a separate cable run.

    For The FOH truss, I never run a single DMX cable to the truss, usually 1 per type, or 8 fixtures max.

    Once again, never allowing for a single cable to kill the entire show.

    Then again, I run tours, so redundancy is key.
Children
No Data