Kenton VanNatten | Avid Editor (for hire)
"I am not obsessed... I'm detail-oriented"
"There are few technological barriers. You can fix almost anything if you throw enough money at it."*******************************Randall L. Rike, ACI, ACSR Mac*Win*Unity*ISIS*DSSystems Engineer @ BET Networks [a Viacom company](wwld)
http://www.AvidUserGroup.NL fcp2avid "The Technology Is Not Guilty" - Nicolas Philibert quoted in "Documentary in the digital age" by Maxine Baker (2006)
Last ditch efforts:
In the Settings folder, under Avid, trash MC State, Site Settings, and Site Attrributes.In the Project folder, trash the Project Settings file (.avs).Launch Avid and create a new User Profile.Turn off Render-on-the-fly prior to opening the Bin.
Moving forward ... I always have a Bin called Sequence Backups. Periodically, I make interim copies of Sequences, store them there, and keep the Bin closed when not in use. A closed Bin is less likely to get corrupt in the event of a system crash. For a larger project, create multiple Backup Bins. These are in addition to any other copies you make for offsite storage.
It helped me! Thanks guys, you saved me half a days work with this discussion!
Regards
SimRah
avid andy:just to bring this thread to a conclusion - I found the problem:I had installed a trial of a 3rd party plugin. THe plugin had expired while I was cutting with disastrous results. It caused avid to crash and when it came back up the bin was totally inaccessible.When I removed the plugin from the plugin directory. The bin and it's attic cousins became accessible again - so i don't have to recut this sequence again.Hopefully this helps someone someday.
I know this post is ancient but this helped me out today and I just wanted to say thanks.
This solved my problem... in 2024! Thanks Randall!
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller