Hi all,
I am on a film that is shot on RED anamorphic. We are converting the footage from our R3D files to 1920x1080 ProRes422 HQ QuickTimes using RedRushes. We then import the QTs and merge them with our mixer's WAV files, using either the matching timecode between audio and camera or occasionally by slate when there is a tech problem on set.
We have 3 systems attached to a new XSan2, all running 10.5.7, FCP 6.05. The slowest system is a 2x dualcore 2.66 mhz w. 4 gigs RAM, the fastest a 2 x quadcore 2.94 mhz w/ 8 gigs RAM.
When we got attached to the San, we started having a troublesome problem with trimming edits using the Trim window and any of the bracket, carel (>
, arrow, or +/-1 keys.
What happens is that while trimming an edit, one side will update correctly and the other side will either show a freeze frame, a black frame, or occasionally pull up frames from an entirely different clip!
This is happening across all our systems. And not with the same clip every time. Not with the same sequence every time. Not even with the incoming and outgoing sides every time. No consistency we can pinpoint yet!
We also notice that at the bottom of the trim window, the counters which show how many frames you've trimmed back and forth will read, for example, 00:00 on outgoing, 00:00 on incoming. When the problem occurs, you could trim backwards one frame for example, and you will see, for example, -14:21 on outgoing, -00:01 on incoming!!!
We tried pulling material onto a local drive to see if it was something about the San. It was better, but the problem still occurred.
We started the project without a San and had to juggle material onto different drives, so there has been a lot of media copying, folder renaming, and reconnecting media going on.
We are finding few clips are also losing their connection to the QT's on the San. Instead we get a message saying: " is missing. Then FCP cannot reconnect to the picture at all, even though the picture is available on the drives. Not sure how to handle this except to re-merge the clips and cut them back in.
Any suggestions would be most helpful. We are sending files to Apple Pro Support because they were stumped without seeing the material. I just am concerned that our cut eventually links back to our R3D files in the end because this is a bit scary!!! Arrgh!
Thanks
Ann Husaini
afhusaini@gmail.com