Background values . . . what/why/and how to remove?

Anne -

How long are the logs kept?  The problem was last Wed, but there hasn't been too much programming going on since then, and we know that the issue was at about 6:30 or so Wed PM. . . . .

Considering that this is  a school, and not much else is happening this year, not sure how much luck we will have reproducing.  If the logs show keystrokes, then maybe we have the chance to see what we did, which may help to reproduce the problem . . .

Any suggestions?

- Tim

Hi Tim,

I can help answer that --

We keep logs for a long time on the desk -- way past a week ago.  We'd definitely be seeing things logged back then.   We can look in the logs and find keystrokes as well, which definitely helps us find out what's going on.

So, please feel free to pull logs and send them in.  We can look back then and see if there are any "smoking guns," as it were, and try to reproduce.  

Hans

Could it be that you have this after loading a new showfile? If a previous showfile has a channel at a level, and you load a new showfile, these levels remain. Using [Go To Cue][Out] should get rid of them.

Nope, started with a clean show, and nothing was loaded at any time prior or after to this occurring.

- Tim

Logs and final showfile sent, as requested.

Today was very odd as well . . . the same show was on the console from last Saturday (same one we had the issues with) and I went to bring up some of the movers, and three out of four of my X-Spots had color values of 100%/100%/100% and shutters closed, also suck much like chan 29, although nothing should have been done to the console.  I was starting a small new item, and reloaded my template over everything, and still had the persistent values.  Only selecting "New show" and *then* loading the template got things back to normal.  Logs were pulled seconds prior to seeing this, so that may be revealing as well, although as stated above, I don't know what transpired between Sat. and today on the console . . . But same thing - shown as background values, source blank . . .

- Tim

Once again, the odd behaviour continues.  Since I programmed the mover look onto a sub described in the post above, another op (not the guy who seems to cause problems . . . ) went to record some basic look subs.  He keyed 1 through 56 @ full enter, record sub 3 enter, and only got about 10 of the channels into the sub, and somehow, a number of other channels ended up flagged "C" for captured.  No chance he hit the capture key - nowhere near where he was working.  He went to write another sub, once again got a subset of what was desired, and even more stuff was captured (flagged "C").

Once again, exit Ion and restart, and all was back to normal.

As an additional point, this is a console that decided to keep coming up unusable as an Eos about a month and a half ago.  We reseated everything as per ETC, but that problem kept coming back.  We sent it in, and they returned it NTF . . . apparently UPS smashes things around enough to cause whatever did that to restore itself. 

Considering that all this stuff is connected via USB (even the dongle is on the main face PCB) and that we are having no issues related to the wing, I really have to wonder if the main face PCB or USB is intermittedly blasting in errant data . . . this is far too basic and far too often to be an inherent bug, or I would think that a majority of the user base would be having the same problem . . . . and it really is making it hard for me to recommend this console to anyone . . . ETC has been great so far, but the inclination is to blame us, and at this point, it's just too many things far too often for this to be purely user error . . . . Several of us have years in the industry, and know our way around a console, and it is still happening . . .

We still have the spare that ETC shipped for the EOS "identity crisis" since we had some critical shows, and confidence is/was very very low that it was truly corrected.  I am tempted to put both side to side, and do the same things on both.  If one goes wonky and the other does not, then we have pretty much nailed this as a hardware problem . . . we just need to find the time and motivation to do so!

- Tim

Hi Tim,

I just sent you an email with some more information in our investigation of what you are seeing. 

Thanks!

Hans