Cue List not responding - ETC ION

Hello, 

Im working as part of the LX team, in a venue. 

we've had a tour come through, and have had an odd bug happen. 

For example, we'd {go to cue 0.1} 

Press {Go} once or twice, then the {Go} Button would stop responding. 

To get the cue list going again, we {Load} the next cue, then everything responds as it should. 

 

This is something over never come across before, but the company in question have reported the issue has happened before. 

(Different desks in each venue, using house desks, not touring a desk) 

 

Does anyone know why this happens? anything that could cause it? 

and especially anything to stop it happening. 

(for information, our console is running V2.5.2) 

 

 

Thanks! 

  • how did those irresponsive Go's manifest? nothing happened on stage, but the console showed stuff happenening? nothing on stage, nothing on screen? nothing on stage, the cue started but stopped immediately after starting?
  • So, I pressed Go, Nothing happened on stage or on screen.
  • Hello NFoulis,

     

    a few things can be checked here. One could first try elimnating a hardware failure,

    by going to the Shell->Settings->Maintenance->Facepanel Test, and push the

    GO Button in many different methods: fast, slow, repeatly fast, and make sure

    the reaction on the monitor display is reacting the same as what is being physically pressed.
    If there are differences/failures here, then the hardware button needs to be further examined.  

     

    If the facepanel test completes with no problems, then ist possible that the cue list

    is simply being removed from that GO Button Playback - especially since "Load"ing

    the cuelist back to the playback got the Go Button working again.

    A snapshot or macro that is attached to a Cue, can cause when the Cue is executed

    with a GO, that then the playback is cleared of its Cue List, and the Go Button doesn't cause any

    change of the state on the stage. You can always check the showfile where this happens,

    and see if there are any snapshots or macros that clear the playback faders.     

  • Hello Corey

    Im not able to test hardware at this moment, as I'm mid show.
    But will look at that post show.

    Its not a macro or snapshot, as there are none linked to the cues,
    and it doesn't do it every time.
    Since my original post, Ive narrowed down the situation it seems to happen in.

    we've gone out of the cue stack, between performances, (after at least an hour)
    then after going into one of the show cues. i.e. 0.1.
    If you press {Go} after jumping into the stack by pressing {go to cue}
    the stack doesn't respond to Go, unless a cue is loaded.

    (there is no issues jumping straight back into the cue list after running it all the way through)

    the company have also reported this happened to them on a different console, in a different venue.
    and as our ION has not done this before, it would lead me to believe its not a hardware issue.

    Neil
  • Hi Neil,

    Gotocue only outputs that Cue, but does not load the cue list to a playback.
    So its normal that if a cue list is not on a playback and you execute Gotocue 3/1 that cue 3/1 will be outputted but cuelist 3 is not put on an empty playback.
  • Hi Corey,

    thanks for that.
    Gotocue is something I use quite a lot, to load the correct cue, which also, usually, loads the list into playback.
    Would this only work if there is only one cue list in the desk?

    Neil
  • Only cuelists that are loaded to a Fader can be played back. If your cuelist is loaded somewhere, GoToCue will use that fader, if it's not loaded yet, it has to get loaded somewhere.
Related