[quote="Bob Ennis"]Lou - I trust that when you reset the SS you did it by resetting the FRAME, not just the SS board. While at GV, I had been told by GV engineers that while the hardware to manage the SS is all part of the SS board, it is the FRAME PROC that actually "directs the traffic". Thus I had been told to let everyone know to NOT reset the SS by resetting the SS board. Even more important, (again, paraphrasing the GV software gurus) NEVER EVER use the Unlock All/Unload All command in the Cache sub-menu. Repeated use of this technique to clear the SS memory almost guarantees an eventual lock-up (or other anomalies), as the command addresses the SS board & not the Frame Proc - this causes a disconnect between the Frame & SS board. Thus, the best way to clear out the SS cache is unfortunately to reset the frame. I'm not sure if this is at the root of what you're experiencing - as I said, I was also seeing your issue in v14, even after resetting the Frame. With the proposed revamp of the SS operating system, this disconnect problem (as well as the "BUSY" message) should theoretically go away.[/quote] I'll try a Frame reset, I thought I had, but it's been a while.

Lou - I trust that when you reset the SS you did it by resetting the FRAME, not just the SS board. While at GV, I had been told by GV engineers that while the hardware to manage the SS is all part of the SS board, it is the FRAME PROC that actually "directs the traffic". Thus I had been told to let everyone know to NOT reset the SS by resetting the SS board. Even more important, (again, paraphrasing the GV software gurus) NEVER EVER use the Unlock All/Unload All command in the Cache sub-menu. Repeated use of this technique to clear the SS memory almost guarantees an eventual lock-up (or other anomalies), as the command addresses the SS board & not the Frame Proc - this causes a disconnect between the Frame & SS board. Thus, the best way to clear out the SS cache is unfortunately to reset the frame. I'm not sure if this is at the root of what you're experiencing - as I said, I was also seeing your issue in v14, even after resetting the Frame. With the proposed revamp of the SS operating system, this disconnect problem (as well as the "BUSY" message) should theoretically go away.

[quote="Bob Ennis"]I had this same problem on my last remote using a Kalypso. There was an issue about channel 7 or 8 automatically trying to a still that just wasn't there - and this also happened quite often after doing a save or after caching an animation. I found that I was able to select another output and load a single frame still into that output...this caused the message to go away. I believe that the message was bogus anyway, as it would sometimes pop up after just loading a single still, and like yours, it would stay on indefinately. There are still some wacky still store bugs in the current release software. At NAB GV was touting an upcoming release of a new software version in which the still store ops were revamped. Maybe when that version finally comes out it'll help put an end to the ongoing still store problems.[/quote] Thanks Bob...tried all outputs too. I'm stumped. Unfortunately I can't wait for thier next release. I always appreciate your help, especially with your new affiliation.

I had this same problem on my last remote using a Kalypso. There was an issue about channel 7 or 8 automatically trying to a still that just wasn't there - and this also happened quite often after doing a save or after caching an animation. I found that I was able to select another output and load a single frame still into that output...this caused the message to go away. I believe that the message was bogus anyway, as it would sometimes pop up after just loading a single still, and like yours, it would stay on indefinately. There are still some wacky still store bugs in the current release software. At NAB GV was touting an upcoming release of a new software version in which the still store ops were revamped. Maybe when that version finally comes out it'll help put an end to the ongoing still store problems.