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

Codec Fault Evolving!!!

Ido Karilla

Ido Karilla

Well-known member
Joined
Oct 7, 2007
Messages
555
Reaction score
1
Points
18
Location
Tel Aviv, Israel
On the first days of shooting we have experienced "codec fault" only while using redcode36 and wide lenses, we are shooting 4k 16 by 9.
We are now on the 6 day of shooting, same camera build 15, and we are experiencing "codec fault" even with redcode 28 and not very wide lenses. It is a very warm Israeli spring day 40 deg Celsius, any possible connection? Other Ideas? Red team we need your attention to that please, this are our working conditions.

Thanks.
Ido.
 
16/9 is really not the way to go at present time.
Are you recording to drives or CF cards?
Are you using RED CF cards?
Switch to 2:1 if you can.
switch to drive it may help.
Cheers
Albert
 
were on day 6 of shooting (!). 4k 24fps 16:9aspect.
still no answer..
 
We shot our feature using REDCODE 36 and recording in 4k 2:1 and we experienced the same Codec Faults.
The only solution is to turn off quick time proxy's in camera and generate them by using RED ALERT or RED CINE.
 
If you're shooting 16:9 then you can turn off quicktime proxies anyway since they aren't supported by anything.
 
roryhinds said:
downgrade to Build 13.

Build 15 is not ready for production.
Click to expand...

Build 15 is considered stable and RED ONE cameras currently ship with this firmware build.

Do not go back. Build 13 is painful to work with.
 
With an ambient temperature of 40 C (104 F) you may be near the edge of where the camera starts to have issues, for what that is worth. I'm sure protecting the camera from direct sun, etc. is always a good idea in any case.

I'm not sure anyone knows exactly what causes the codec fault. I have not heard anyone else report the codec error was affected by high temperatures. That might be an interesting clue, if it is.
 
SF Geek said:
If you're shooting 16:9 then you can turn off quicktime proxies anyway since they aren't supported by anything.
Click to expand...

Camera generated QT Proxies are the only solution on PC to extract audio from Red files.
Unfortunatelly they are MUST.

Priit
 
QT proxies are the only way to get audio on Mac as well. Can you get the audio from non-supported quicktime proxie formats?
 
Our team is experiencing the same codec error, under the same settings.
The codec error appears when shooting 4K 16:9 with QT proxies enabled or not , using the hard drive or the CF card. It appears to have something to do with the particular contrast ratio in the picture. If we completely blow out the picture equally or underexpose it considerably, it will still record without error. But what appears to be correct exposure levels , results in the codec error. This has always been in an outdoor situation where it is very bright and sunny. As advised on this forum, shooting 4K 2:1 does seem to avoid this problem. So what is the word from RED on this?
 
Codec errors in my opinion are cause by errors in the media. When RED RAID are not protected during transport sectors error can occurs.

Make sure there are no bad sectors in the Red Raid.

Do not treat the drive like a brick, it's not a brick.

Reformat your drive on a mac or pc, then format it again in the camera.

Then run all your setup setting, then format your media again in the camera.

That should fix your problems.

15 release is good for productions use now.

Shot in 4k 2/1 28.

Tek

P. S. Hire a real DIT if needed. LOL, Heat will also be a factor with the drives.
 
I've been shooting outdoor for three weeks in Italy and I cannot use 4k 16.9 irrespective of whether its at 36 or 28 or with QT proxies off.

In my experience only 4k 2:1 is currently stable with complex or moving scenes.

geoff
 
Put more sky in the shot?

Put more sky in the shot?

karilla said:
On the first days of shooting we have experienced "codec fault" only while using redcode36 and wide lenses, we are shooting 4k 16 by 9.
We are now on the 6 day of shooting, same camera build 15, and we are experiencing "codec fault" even with redcode 28 and not very wide lenses. It is a very warm Israeli spring day 40 deg Celsius, any possible connection? Other Ideas? Red team we need your attention to that please, this are our working conditions.

Thanks.
Ido.
Click to expand...

If you use a wide angle lens in full sun and stop down you get more depth of field and the edges of the circle of confusion become sharper, this can increase the bandwidth through the compressor and overload the transfer to disk.

Try framing so that there is 50% of the frame with sky in the shot, or 50% of the frame in total black shadow and see if the error goes away after a reboot (a flag bit might get stuck.)

It that helps, use ND filters and shoot wide open, the lower DOF will decrease the bandwith since the soft parts of the frame will block from the compression.

Let the group know if this helps since some others seem to be having it with larger sensor area formats?
 
Wide angle lenses stoped down till super sharp (Ultras used here) and load of detail is not reliable with 4k 16.9 (for us).. Softening the image by shooting wide open (or filtering, or misfocusing) solves it for some lenses..

I would be happy with a 3840 16.9 frame if that brought the data down (as 2:1 seems to) to a managable level..

regards

Michael

PS I reckon red missed the problem cause they tested with those soft s4:shifty:
 
You must log in or register to reply here.
Back
Top