Hi,
We have been having nuisance problems with both our Eos & Ion consoles ever since the update to 2.0.1 in September. The Snapshot issue (which others have posted about); boot-up goes to Blind Preset (if Presets are recorded) or Blind Color Palette (if Color Palettes are recorded but not Presets); and booting up into a saved, unedited, showfile will cause the "you've made changes but haven't saved yet" asterisk to appear next to the show name at the top of the screen. These are annoying, frustrating problems, but not anything that has affected a show.
However, last night I had a show affected by a problem with our Ion I had not encountered before, nor since.
Generally we do one show at a time for a few weeks. At the moment we are doing 3 shows in rep (2 shows plus readings) so we are bouncing between files each day.
Quick version: Ion incorrectly saved one showfile (for the readings) under a different, existing showfile's name (Show Two), when using the quick-save "Shift+Update" function Saturday morning during the readings. While noticed later Saturday during the readings, it was forgotten about Sunday evening when pulling up the Show Two file for that performance. Pulling up the most recent save of Show Two resulted in getting the incorrectly saved Readings show file (which used Show Two as its base), which was not discovered until multiple cues were discovered missing from the show in the middle of Act 1.
To correct for the performance, during intermission I loaded the last save of Show Two from Friday night , which had the correct cue list. Show continued without further problems.
Long version:
Background: I have 3 filenames for the rep productions. Essentially: Show One, Show Two, and one for the readings which uses Show Two as its base patch, groups, etc... called Show Two Readings. We've been alternating between Show One and Show Two each night of the week, and did the readings during the day Friday, Saturday, and Sunday.
Friday we came in to do the first rehearsal for the readings, and I created the readings showfile: "Show Two Readings." I used the Show Two save from Wednesday night as its base, and I simply added submasters for the readings. I then saved as the Show Two Readings name. I then reloaded the full Show Two showfile for its tech later that day, and operated under it and saved under it without issues for the rest of the day. Once the performance of Show Two was finished, I did normal end-of show procedures (turned off everything from the console), and then loaded the full Show Two Readings file so it would be ready for me the next morning. I then shut down the console.
Saturday I came in at 9:00am, and booted up the console. It came up in the Show Two Readings file, but with the "you've made changes but haven't saved" asterisk next to the showfile name at the top of the screen. This did not worry me, as this has been a typical, though annoying, behavior since the update to the current software a few months ago. I made changes as needed, and then used "Shift+Update" to save as we rehearsed and performed. It was not until 10:00am in the readings that I noticed that the console had saved as the Show Two showfile name, and not the Show Two Readings name. I resaved it as the Show Two Readings name using the Save As option, and did not appear to have further issues.
Once the readings were done for Saturday, I again saved the Show Two Readings file, and then opened the most recent Show One file for the evening performance. The show ran without issue, and following it I loaded in the Show Two Readings file so it would be ready for me Sunday morning when I came in. I then shut down the console.
Sunday I came in again at 9:00am, turned on the console, and the Show Two Readings file (again with the asterisk, as usual) was loaded and waiting. I again made minor changes, and saved using the "Shift+Update" function without problem.
Once the reading was complete, I loaded the most recent Show Two showfile (which ended up being the incorrect readings save from Saturday). I did not notice that the loaded submasters had not changed from the readings. We then ran the show, and about 3/4 of the way through Act 1, we began noticing that a few called cues were missing from the cue list. It was then I noticed the submasters, and began double-checking the file. None of the missing cues were critical (added minor shifts, tweaks) so I waited until we were safe in intermission to load the most recent Friday save of Show Two, which was the correct one. The rest of the show went off without any console issues.
Following the show, I resaved this version of Show Two so the correct version would be the most recent version in the file stack.
The irony of all this is that 2.0.1 was the first time we ever updated our consoles soon after an update had been released. Normally we wait to see if it is necessary, but as we never had problems in the past, we updated as soon as we heard about the update.
Patrick Hudson
[edited by: Patrick Hudson at 2:55 PM (GMT -6) on Mon, Dec 16 2013]
