ION persistant memory catastrophic failure

eugp said:

  We have been saving consistently every few hours with a "save_confirm" macro  that sent to a file in a folder that had been built for this show.

 

I too would be looking at the macro.

FWIW, simultaneously pressing Update and Select saves to the last saved location (or always to HD, can't recall), without having to navigate thru the file menu.

Steve B.

Hi,

I too, will be looking at the macro.  But, this is the same macro I have used for months now and have been able to retrieve the save list from.  I will gather the logs this evening and send them off when I can.

This ION has been set up this way for the last two shows and I start a new show by deleting the cues only.  It has started up fine prior to this event, so it is certainly unusual and not good that it dumped the cues.  Whether or not the loss of the file saves is a connected or separate issue also needs to be determined.  I believe it is connected.  

We are lucky that it happened on a small workshop show relatively early in the tech process and we all have concluded it was an appropriate object lesson for the students.  It shows clearly why you need at least basic cue tracking sheets and patch paperwork.  It also gave the student LD practice at firing off the building of cues for seven pieces in short order.  

For me it is a lesson on basic tech procedure that I will not forget.  Always walk away with the show file in your pocket.  After all, machines are fallible, hard drives fail, power supplies fail, equipment gets stolen, and you can never be too careful.

eugp said:

It shows clearly why you need at least basic cue tracking sheets and patch paperwork.  It also gave the student LD practice at firing off the building of cues for seven pieces in short order.  

For me it is a lesson on basic tech procedure that I will not forget.  Always walk away with the show file in your pocket.  After all, machines are fallible, hard drives fail, power supplies fail, equipment gets stolen, and you can never be too careful.

I always like to take the extra step of opening show files in an OLE to make sure the backup is reading properly.  It's also nice to have an older version of the show readily available in case of a re-record goof.  I know Eos can do a selective merge of an old cue, but sometimes it's just easier to just look at the old data.  I think of it as soft tracking.

-Josh

eugp said:

It shows clearly why you need at least basic cue tracking sheets and patch paperwork.  It also gave the student LD practice at firing off the building of cues for seven pieces in short order.  

For me it is a lesson on basic tech procedure that I will not forget.  Always walk away with the show file in your pocket.  After all, machines are fallible, hard drives fail, power supplies fail, equipment gets stolen, and you can never be too careful.

I always like to take the extra step of opening show files in an OLE to make sure the backup is reading properly.  It's also nice to have an older version of the show readily available in case of a re-record goof.  I know Eos can do a selective merge of an old cue, but sometimes it's just easier to just look at the old data.  I think of it as soft tracking.

-Josh

Yes, I did exactly that before I walked away last night as well.  Also keeps you safe if the little tiny flashy thing gets lost.

For the 15 years I worked on Expression I saved 4 disc's as my back up.

Now on Ion I keep 2 flash drives.

Thanks for the update, I've not been consistently loading them into OLE. 

I'll add it to my daily routine.

Ah, they called second meal. Wow, it's filet mignon. mmmm

Hi,

Well folks, I must apologize for my freak.  I have looked through the log files (a great resource) and then grillled my young student LD on why, when clearly the cues were in the board at 5:20pm 12/7 and being run through, the cues were then somehow missing after a logged show file reload at 5:25pm.  Apparently the LD thought there was "something wrong" with the cues and decided to (while I was at dinner and without consulting me) overwrite the show file with an older file.  She apparently did not notice or appreciate that the file she was using was from the first day just after the patch was almost complete and the cues were not built.

We are still left with the question of why the "save_file confirm" macro is sending the save to never-never land.  But at least I have restored confidence that the ION did not suddenly loose the cues.  This explains why the show file overwrite was empty, when the LD went to overwrite she picked the first file in the list, which would normally be the last known save, but since that list was nearly empty, she got the file that was 3 days old.  I am still lost as to where all the file saves went that we had been so conscientiously running.

A "directed" save with the mouse to the show folder ( and to the flash drive of course) seems to work just fine, but the save_file confirm macro does not cause the show file to be created where one would expect.

Not that I would ever want this to happen to anybody, but the show looks noticeably better after having been rebuilt.  The cues are clearly defined and purposeful due to the intensity and concentration of the quick rebuild.

Again, I apologize for the excessive subject title, this was not a catastrophic failure at all, but a macro problem.