Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

The bad frames in 16.3.1.6 are in 2:1 as well

Some more details.

1. Was this with camera #655 or another camera?
2. What lens?
3. Filters?
4. Have you had this problem with RC36 as well?
5. Were there any problems with A Camera and how was that setup? Tech specs, type of shots, etc.
 
Did any of the footage from that B camera exhibit this codec error when stationary, i.e. no pans?
 
sorry. more details coming. just starting to look at footage. although B was not 655. 655 was A cam on Optimo 24-290 with 2x extender. C cam was 10mm ultra prime, 14-40mm S4 and it's footage looks fine to CF. we did not shoot any RC 36.
 
No problem Warren. Sorry to throw a bunch of questions at you. Just want to help narrow down the potential causes. Let us know when you have more info.

Thanks!!
 
I would like everyone to know that I'm not complaining. Just letting everyone know what could happen and let RED know what is happening. I had discussed the risks in using 3.1.6 with Stuart and I accepted them. The good news is our crashes in 3k-60fps were resolved.

I am going to send in the LOG file however I have to get the drive back to B camera to extract it. Hopefully later today.

A camera(long lens tight shots) and C camera(very wide shots) did not have any of these errors.
 
Just wondering. Are these things visible on playback or do you have to render the clips before spotting them?
 
LOG file extraction

LOG file extraction

I am going to send in the LOG file however I have to get the drive back to B camera to extract it.
Click to expand...

Just for reference everyone, you don;t need the original media attached to get the camera LOG file. Any media will do - CF or RED-DRIVE, Just install / attach, then press UNDO and EXIT. When the camera says safe to remove" then remote / detach the media and the .LOG file will be present.
 
Stuart English said:
Just for reference everyone, you don;t need the original media attached to get the camera LOG file. Any media will do - CF or RED-DRIVE, Just install / attach, then press UNDO and EXIT. When the camera says safe to remove" then remote / detach the media and the .LOG file will be present.
Click to expand...

how far back does the log file go?
 
HOLLYWOOD SCHMOLLYWOOD said:
We weren't playing back on set but I can tell you that we weren't aware of them while shooting. Not in RED LCD.
Click to expand...

How about in quicktime. Did the wrappers show these bugs. I've had weird things pop up only in RedAlert and Redcine on renders, but nothing on the small offlines. Just want to know if this is a similar thing.
 
Kjetil Haugen said:
How about in quicktime. Did the wrappers show these bugs. I've had weird things pop up only in RedAlert and Redcine on renders, but nothing on the small offlines. Just want to know if this is a similar thing.
Click to expand...

it was visible in the proxies.
 
You must log in or register to reply here.
Back
Top