• State Not Answered
  • Date
    Sabr Hemming
  • Date
  • Replies 7 replies
  • Subscribers 185 subscribers
  • Views 5617 views
  • Users 0 members are here

Snapshots in Cues on an Eos Client

Greetings

Well I have just finished programming a show. The designer likes to light the show mainly with the moving lights so I try and use a new Preset page for every scene to try and keep track of what I'm using where.. This particular show had 5 scenes in Part 1 and 5 in Part 2 so a lot of pages to scroll if your in the wrong place! Before the first Dress I made a load of Snapshots and linked them to the Cues so they would change my Preset page and a few other things when we reached a new scene.

Trouble was every time a Snapshot fired nothing happened (or so i thought). When the Dress was finished I returned to the control room to find our RPU (which is the Master) to have direct selects open across it's displays. I realised of course that my Snapshots had been firing on the Master and not the Client. 

Any way to change this behaviour? I only want them to fire on the Console I'm working at and they would be removed once the show was open. Hope I'm missing something here ^_^

Thoughts appreciated.

Sabr

Parents Reply Children
  • 0 in reply to luke.delwiche

    Thanks Luke

    That is a good work around but, shouldn't Snapshots fire on the console they are created? I think there should be at least a way of determining which User a Snapshot Execute command will trigger on. Otherwise, this does kind of make the Execute Snapshot command useless in a multi-console system where the programming console is not the Master. It seems a shame to have a function that will only work properly with the console in a specific configuration, if indeed that is the case. 

    Sabr

  • 0 in reply to Sabr Hemming

    Have you tried running the show with the RPU as primary and the console as backup rather then client? 

  • 0 in reply to usesafesets

    This behavior is changing shortly.  Currently, the snap is recalled on the device that triggers the snapshot (in this case, as it was an execute command, it is being triggered on the current master).   This will change to the snap being executed on the device that calls the cue, regardless.

    Just as an FYI.  Snapshots have no knowledge, nor should they really, of what device they were stored from.  This introduces a world of hurt when the devices on the network are swapped, not reset to the same IP address or not given the same name.

    :-)

    a

     

  • 0 in reply to usesafesets

    The config we are running with at the moment is RPU master and an Eos Console running as the backup, these both live relatively peaceful lives in our control room. We have a second Eos Console that we use in the auditorium as the programming console. This console has a hard life, in and out of storage every day. So we like to run this console as a client and spare it the extra responsibility of tracking backup. I'm not saying the thing can't handle it but, simply having that luxury makes it seem foolish not to run in that configuration.

    I'm doing the show in question this evening so I'll have a little go on the Backup and see what happens.

    Sabr.

  • 0 in reply to Sabr Hemming

    Hi Anne

    Cheers for that, I should refresh the page before I make my reply...

    Glad to see it's making a change, seemed to be just what I was looking for and then...bugger! I take your point about User ownership I can see now how that would cause some serious problems! 

    Much appreciated

    Sabr.

Related

www.etcconnect.com