Well tonight we were running a dance show. The board randomly crashes. Hadn't been doing anything strange. Just running the show and when I was put on
Standby I noticed an error message. It read something to the
effect of "Something bad has happened. Do you wish to save an error file?" Said yes and restored the board off of a checkpoint file. The checkpoint file had been written 2 minutes before
hand and acted like we had recored it a day before.
Whenever it writes a checkpoint file it will delete everything in the syntax
line. So say I was about to record a
cue "
cue 165 time..." writes checkpoint file and it just lets you keep typing so strange things happen.
Fades are jerky. They aren't very smooth and there doesn't seem to be any set thing that will make them jerky. We've tried and tried to replicate them, but can't on a consistent bases.
When a laptop is connected with a Cat 5 cable there seems to be a
lag in how the board responds to cues. You hit go and it takes a second or two to read that you hit go.
One of my favorites is the fact that it won't give you a correct read time of cues. So when you hit go on a 15 count
cue it will give you the remaining time in a box. However the time remaining is usually incorrect. You hit go on that 15 count
cue and it will start with 3 seconds remaining and show that the
cue has completed in the
cue list. However the levels are still running in that window and it will complete in the correct time. Sometimes it won't even show that it's running the
cue until after it's complete. You hit go and nothing on the board will change, but the lights on
stage change and then it shows that it's complete.
I'm sure that I'll remember something else later but he's a starter list.