Howdy,
In two of our spaces, we have Eos consoles running backup to RPU's. Two weeks ago, I installed 1.4 on these and all our other devices. At that point, I was working in space A. On at least one occasion I specifically recall the Eos and RPU booting up to different shows (one, the current correct show, the other, "untitled") I was able to easily resolve this by reopening my show, so I let it go and moved on. Also, throughout the run of that show (a show with 400 channels set in setup), The RPU displayed the correct number of channels while the Eos Displayed 10,000 channels both in Live and Patch. These channels were inaccessible to modify or delete because they were beyond the range dictated in setup. I tried changing the channel count to 10,000, delete the extra channels, then returning the setup to 400 chs, but the issue reappeared. While I found it interesting that the Master and Backup were showing different info while synced, it didn't seem to have any adverse effects. On thursday, I talked to Heather with Tech Services and promised to send a file. I Saved As "Too Many Channels.esf" on a USB stick. Unfortunately, I got distracted and blew it off.
This weekend, I am in space B while one of my colleagues is working is in space A. Yesterday morning, he said the boards booted up to Too Many Channels on one and Untitled on the other. This surprised me in that I didn't expect saving to a USB would change the current show. Then, while trying to save his show the Eos crashed, and that then he was unable to reboot it. When I got in, the board was on the floor replaced by an Ion, and by lunch, he had already sent it to the retailer so I was unable investigate at all.
Meanwhile, I was loading in a new show in Space B. Before I fully booted the boards there, I installed 1.4.1. Upon booting, I opened my show successfully but the show name stayed Untitled until I saved again. Also, I couldn't help but notice that the Eos was showing 10,000 chs while the RPU was showing the correct 500 chs. Again, no big deal as I programmed and ran the show with no real problems.
Today, I came in, pressed the power on the RPU, waited a couple seconds, the did the same on the Eos like always. Unlike always though, the EOS froze before booting. On the second attempt it seems to be working fine, but I certainly think this collection of events is noteworthy.
I'll be sending files from both consoles shortly.
[edited by: BSmith at 3:15 PM (GMT -6) on Sat, Jun 21 2008]
