External Q List Problems/other issues

I am in production (we've been open for 3 weeks) of a show and am using 2 cue lists.

List 1/ is my master, and 2/ triggers my video cues via a program called Keystroke, which is set up to hit spacebar (go trigger on video program--Watchout) when channel 751 (add1001) is at full (after .2 secs 751 returns to 0, and next time it hits 100 triggers video go again).

The list is linked to my Master list, and has worked without problems until this past sunday.  That's when the things went crazy.

!. When I turned on my facepanel (Ion is client to server), only one screen was recognized, I had to go into the shell and reactivate it for it to work (not a huge problem, but it happened again today), also needing to recalibrate my touchscreen whenever this happens.

2.  When I scrolled through list 2/ during my channel check (for video check) the values of ch 751 stayed at zero (video fail),

--I ended up manually running video for the show Sunday

3. Today, the electricians were able to get things working via iphone rfr but when i started up my ion, same symptoms (1 screen and no love from list 2/)

The strange thing about this all is I saved sat. afternoon, had a good show sat night, and reloaded my save file from Sat when I was having problems on Sunday.

Today I loaded the save file from 2 saves ago, and it seemed to solve my problems with list 2/.

Any Ideas what is going wrong here (I also went to q out and 0 in my troubleshooting to no avail)?

We are running 1.9.8

Thanks.

 

 

Parents
  • So list 2 (video list) no longer triggers channel 751 at all?  If you go into blind and next/last through the list does list 2 still contain any information?

    I've seen the occasional HTP issue where a primary will prevent a client from taking channels below their home state (i.e. a moving light is held at pan/tilt 0 straight down) and if you try to pan/tilt the light to a "negative" angle the master's higher level prevents this... but i've always been able to recover by logging out and logging back in...

Reply
  • So list 2 (video list) no longer triggers channel 751 at all?  If you go into blind and next/last through the list does list 2 still contain any information?

    I've seen the occasional HTP issue where a primary will prevent a client from taking channels below their home state (i.e. a moving light is held at pan/tilt 0 straight down) and if you try to pan/tilt the light to a "negative" angle the master's higher level prevents this... but i've always been able to recover by logging out and logging back in...

Children
  • I do two things at channel check daily:

    1.  On fader wing (while in q1/0.3) go through my 2nd list....Upon successful completion of that, I usually run through the actual q's (after resetting to 2/0) (q1/32-1/37)

    and it has been problem free for 3 weeks.

    When I do it now, the channel level info in my tombstone changes colors, but the value stays at 0, but the level stays at 0.

    ....And I just loaded my bad show file to try and replicate the problem and it is suddenly working again.  Thinking software related.

  • MichaelMax said:

    When I do it now, the channel level info in my tombstone changes colors, but the value stays at 0, but the level stays at 0.

     

    Hi Michael,

    What color does the channel level information change when this doesn't work?  

     

    Regarding your other questions:

    1. If the console was moved from one location to another, or powered up with a loose connection, it can sometimes default back to one screen.  Using the External Monitor Arrangement tool will allow you to re-enable that second monitor.

    2. See above. Channel level information is very helpful, and gives us a starting point for finding the control source.

    3. How did the iRFR bring up the Keystroke channel (channel check, address check, go to cue, etc...)?  Also, what kind of monitors are hooked up to the Ion console?

    Go to Cue Out and Go to Cue 0 take out a lot of data, but submasters may not be impacted, as well as things controlled by the Capture function.

     

  • Hans,

    1.  Yes, the console was powered down (unplugged) sat between shows, but I have had to reset my monitors every time I've powered up since.

    2. Blue to Green

    3. I imagine in ch check mode 751 @ f, as I initially thought it was keystroke that was malfunctioning.

    All the sliders were at 0, but I reloaded the show when things started going funky sunday (from the browser).  Would assume that should reset any fader info.

    Typically I just use go to q 0 during my daily check,

    Like I said before, as I reloaded the "bad" file after the show last night, it seemed to work fine again.  and when I was pressing "go" on the fader module it would advance to the next q, but nothing would happen on the console.

    Thanks,
    MM

  • As I just turned on my ION faceplate, I once again had to activate my 2nd monitor. 

    Turned faceplate off again to see what happens, as I restart both monitors are active.

    Furthermore, my video channel (751) in q list 2/ is operating as programmed.

    I believe that the level for said channel would be yellow in my tombstone if it were captured by a fader.

    Could this be a communication issue between the ION and server?

  • Hi Michael,

    Hmm... The monitor issues you're experiencing do seem odd.  

    Would you be able to send in two sets of logs -- once after you've successfully configured your monitors and launched into the show, and then a second time after the console reboots and doesn't bring back the second monitor.  We'd also want to know the make and model of your monitors.  -- Go ahead and send those in to hans <dot> hinrichsen <at> etcconnect <dot> com.

     

    Indeed, the level would have been yellow if controlled by a submaster.  If this happens again, check out About to see what the source is for the channel -- it will specify cue and cue list of control. See below:

     

    This most likely isn't a communication issue between Ion and RPU, but seeing what's in this screen would help us know where it's coming from. 

     

    Thanks!

Related