Bug with GoToCue 0 over riding virtual faders by reloading them with a different cue which causes black outs.

Hello, I have found a bug and would like to report it. I am working in Multiple Cue lists on a Nomad, sometimes much to my chagrin when I press Back on one Fader to go to it's Cue 0 and Play on another Fader before the move is finished - That Cue I expect to load instead of loading I get a black out because the Fader I pressed Back to get to Cue 0 on Loads into both the Faders. I was just reading through the manual and was reading about [Go To Cue 0] & [Load] and as soon as I tried it instead of going to Cue 0 on my Cues 900/1 and 901/1 it loaded Cue 1/1- I took a screen shot. You can see Cue List 900 and 901 Fader is blank on the Cue List Index, on the Fader page you can see they have both been replaced by Cue 1/1 and in the Fader list you can see it says the Cue's are still assigned to the Faders I assigned them to. 



Parents Reply Children
  • Hey ! We're still unable to replicate this particular issue. Would you be willing to give us a call to walk us through this? I've created notification number 300854078 for your particular issue. If you could, please give us a call at 800-688-4116 and ask for tech support. Once through to support, anybody on our team will be able to help you out!

    Alternatively, if you encounter this issue again, press [Displays]+[Record] (this puts a flag in the logs...visually, nothing will happen) as soon as you notice something strange happen, then export logs and send them our way!

    Sorry this has been a tricky one to track down!

  • ETC_Logs_PC_Offline_02262020_210802.zip

    Hello again, I am able to replicate the bug any time :P I have this log file for you, I hope it contains some info that helps. These log files in particular are from my computer at home that I use to practice EOS on.

Related