Failed Standalone Transfer

[Ian Levin]

I am a DIT on a Indy feature film set. I was notified about camera issues with a RED 16 gigabit card after I already transferred the card to the hard drive and the card was reformatted and sent back to the camera department. When I opened the log and transfer protocol to create stand alone files in Final Cut Pro 7.0.2, the files transferred in, yet when playing back, the media went completely green and I am no longer able to see the footage. When I restart final cut pro, the media comes back in the log and transfer window, yet when reverting back to the see the footage, I get the same error of the footage going completely green. :emote_22_yikes:

When I look back at the quicktime proxies, the footage seems fine. :confused5:

A friend of mine brought in RD3 data manager, we tried to export the clip into a stand alone file, yet the same green screen error occurred. :angry:
I have tried to do the same using the back-up drive, still I get the same results. The media from the back-up drive was downloaded directly from the flash card media. :frown2:

Any Suggestions?

 

[Uli Plank]

Can you open the R3D in RA or RCX?

 

[Sid Idris]

sounds like your proxy files may need to be recreated. open the R3D files directly in RA or RCX or Clipfinder. If they work there you can use them to create new proxies.

 

[Nir Shelter]

This is not a proxi files matter you must preference the integrity of the R3D files.

As previously suggested open the R3D files in Redcine or Redalert or RedcineX. If you get the same "green frame" error throughout all clips I'd say that card is a goner.
If only some of the files have the green frame error and there are others that don't you have a few files out of the card.

I have seen the same error in the past on some clips and was able to export the portion of the clip that was fine before the error.

Guess you cant underestimate data checks on set...

 

[Ian Levin]

I am able to open the proxy files in RedcineX. All the R3D files open without the screen going green. I am still uncertain why creating standalone files does not fully work. It seems like the footage is on a timer. When making another attempt to create a stand alone file, I can see the footage for a limited amount of time, then when trying go through the footage, it will suddenly go green.
What more can I do?

 

[Vico Martin]

recreate the proxys with RA, if do not work use RR to generate prores.

 

[jimhare]

Probably the Quicktime component or something else falling over. Your best bet is to use RedCineX to create your QuickTime files for editing. I believe this is a much better approach anyway.

Also, spend some time getting used to the protocol. For example, you don't open Proxies in RCX, you open R3Ds. Proxies only refer to the QuickTime component referencing the original R3Ds at multiple resolutions, and without a proper debayer.

Understanding exactly what you are looking at during each stage is so so so important.

Getting a green screen from a proxy shouldn't even raise your heart rate. Only when you have evidence that your R3D is in danger should you be slightly worried.

Even then the wizards at Red can often pull something out of thin air. Once I had a line through my footage and sent them the R3D. They built a custom version of Red Rocket X that actually fixed it!

 

[Jay Gannon]

Yep stop trying to work with the proxies and try to generate the quicktimes out of redcineX, hopefully that should sove it.

 

[Tim Sutherland]

Is the first frame of the quicktime proxy green? If so, it means there is a corrupt first frame in your R3D. Try exporting starting at frame 2 in redline to Pro Res or something like that to see what happens.

This is why you should visually verify the footage before sending cards back to the camera department, so that you could see if it was a recording error or a transfer error.

Tim

 

[Joe Shemesh]

Probably the Quicktime component or something else falling over. Your best bet is to use RedCineX to create your QuickTime files for editing. I believe this is a much better approach anyway.

Also, spend some time getting used to the protocol. For example, you don't open Proxies in RCX, you open R3Ds. Proxies only refer to the QuickTime component referencing the original R3Ds at multiple resolutions, and without a proper debayer.

Understanding exactly what you are looking at during each stage is so so so important.

Getting a green screen from a proxy shouldn't even raise your heart rate. Only when you have evidence that your R3D is in danger should you be slightly worried.

Even then the wizards at Red can often pull something out of thin air. Once I had a line through my footage and sent them the R3D. They built a custom version of Red Rocket X that actually fixed it!

Hi Jim,
Just sent you a PM

best
joe

 

[Snow R. Shai]

...and?

...and?

Ian,
Any follow up info on those green screens?
Was your problems solved?

 

[Snow R. Shai]

Greens screens of death

Greens screens of death

Hello there,

I believe I narrowed down the reason for this.
It is probably a problem with the RED QT component [v3.8], that is triggered by incomplete or corrupted copies of R3Ds.
These corrupted files can be created during a failed copy and not in the camera.
Once R3D Manager copies the files correctly, and the system is restarted, the green screens of death disappear.
If R3D Manager is failing, let the mac, CF reader and CF to cool off.
We had a few failed copies that that turned out good after cooling...
So the files on the CF might be OK.
Other REDUsers reported the same solution, so this really might be it.
Would be happy to hear if this worked for ya...
BTW, did you try to playback the shots in the camera? If you get playback in the camera, you are all good...

We are using a Red One MX build 30, MacOS 10.6.3, FCS3 Installer and QT component 3.8