[Michael Slowe] “Clip Browser should be used.”
Absolutely! It may have bailed me out in this case. But I think your practice of transferring everything to ProRes may be even more important.
The “lesson” here is: Use Clip Browser every time you copy a BPAV folder. My question is whether there is an additional lesson: don’t edit natively.
So, to summarize:
July, 2011:
SxS Card->ClipBrowser->RAID->FCP Log & Transfer->ProRes 422. All files transferred into FCP.
BPAV on RAID->ClipBrowser->Backup Drive 1.
BPAV on RAID->drag-and-drop->Backup Drive 2.
August-November, 2011: editing proceeds, all clips are good.
late November, 2011:
Clip 43 suddenly becomes unplayable inside FCP.
FCP refuses to open anything on BPAV from either RAID or Backup Drive 2.
Clip Browser sees every file on RAID and Backup Drive 2, except Clip 43.
FCP successfully imports BPAV, including Clip 43, from Backup Drive 1.
December, 2011: FCP imports BPAV, including Clip 43, from Backup 1 and Backup 2, and all except Clip 43 from the RAID.
I suspect that this whole situation could be due to problems I’m having with my RAID. But the question remains: does the complexity of the BPAV folder make native file editing less reliable than transferring to ProRes 422? If success in native-land relies on several different files for each clip ALL being good, doesn’t it stand to reason that a single ProRes file has a better chance of not becoming corrupted?
Thanks for any insights!
Bob C
{Interesting additional info: This morning, FCP opened the BPAV folders from Backup 1 and Backup 2, seeing every clip (INCLUDING Clip 43), and also opened the BPAV folder (EXCEPT Clip 43) from the RAID. The day before, FCP had refused to open the BPAV folders from RAID and Backup 1 at all.}