Welcome to our community

Be a part of something great, join today!

Register 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 :)

Build 16 Codec Error killer...

Had a few codec errors and busted frames last night with 3.1.8. 4k RC28 2:1 3fps CF Sending in log file now.

The busted frames scare me the most of course because you don't know they are happening. The jpeg compression is really bad in these samples but you can see the difference between the two. Imagine the one on the right is the usual pristine RED image.
 
HOLLYWOOD SCHMOLLYWOOD said:
Imagine the one on the right is the usual pristine RED image.
Click to expand...

I tried hard to see the problem but i saw it. However i believe that maybe posting some 1:1 crops instead of oversampled scaled frames would demonstrate the issue more clearly. Thanks for the samples.

Miltos
 
David, that photo is a clean shot of the subject matter that cased the error. Eg high luma detail... I don't think it contains the actual error in that frame.

Actually I think it would be far funnier if you made the codec error so it only happened when certain actors appeared in front of the camera.

Ideally we could upload pictures of people the producers pressure us to cast, but we hate. When they step in front of the camera test the Red would recognize them and bug out, so we can just say "whoops, bud, you cause codec errors. Camera doesn't like you, sorry!"

Bruce Allen
www.boacinema.com
 
I got also a Codec Fault with an evil tree in germany. With 3.1.8.
I went out today to test 3.1.8 on a situation we had many codec errors with build 15. A little sea near the black forrest.
Now with Build 16 no codec fault while shooting the sea. Yeah.
But the I turned the camera to a tree. we have very windy weather here in germany at the moment. so the leaves moved very quickly. and so the Red created again with bild 16 3.1.8 a CODEC FAULT.
The interesting thing in the test was: after codec fault I pushed again record and this time, same situtation, same frame, same t-stop. No Codec-Fault.
In Build 15 if we had one codec fault the hole scene couldnt be recorderd, with build 16 you have another chance the Codec will capture it. Thats my conclusion.
I am unhappy that I am one of these 1% with still Codec Fault but I still love my camera and I know the guys from Red will fix it and I just love to shoot such amazing pictures.

Here the specs of this shoot:
Build 16 3.1.8
4K 16:9
25f
100 ASA
5600Kelvin
1/50 Shutter

I will send jarred the log file now.

Thanks Red-Team for the great work and the great 4K tool you gave us and go on for the Full 100% Stable Solid Rock RED ONE!!!
 
EVIL_TREE_in_germany.jpg
 
Steven,

Which lens was that?

-Thor
 
Hi Thor,
it was the 18-50mm zoom @18mm

The Fault appeared the first time on t-stop 4. The next time it worked. Then I changed to T-stop 8 and it appeared again. after pushing record again it worked.... and so on

And i forgot to tell:
Redcode 36 to Red-Drive

Would love to have here in the community sth. like a manual for codec errors.
In which situations they appeared and how you can avoid them best.
In Build 15 our conclusion was to shoot everything in 4K 2:1 and then no Codec Error appeared. But now in 16 I think its a little more different and you cant give a usable option. (Always shoot 2:1 or sth.)
steven
 
You must log in or register to reply here.
Back
Top