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

Vers. 16.3.15 - Codec error !

Deanan said:
Does the error message say codec error specifically or is it some other error?
Can you please email me the logfile? (d e a n a n at r e d)
Click to expand...

Hi Deanan,

Thanks for your response. Yes it's Codec Error faulty and it happens all the time. I'll try to send you log files but it's missing on some of the shots (seems to not be created when it's codec error?). I will check with the DIT, Kenneth.

And yes Anders it's flat on green screen :pinch:
regards,


Fredrik
 
Hi Fredrik,

Whatever the last log file is should be fine. You can record a clip, then unmount the drive and the log should be there. Please zip it before emailing.

Thanks,

Deanan
 
I got a "Codec-Fault" error today when shooting running water ECU's with 3.1.5 with RC36 on both 2K and 4K. The 2k message was on a B4 lens and the 4k was the Red zoom. When I pulled back, the error did not appear again. The error message seems to appear when there is a lot of fast movement in the shot. I had a CF card in for the 2k shot and went to a RedDrive for the
4k shot. The error appeared on both storage devices. I hope Red can fix this nasty bug!
 
FYI - here is my trouble-shooting exchange with Sean Ruggeri (Red bomb squad) regarding the codec errors I have experienced:

We had many codec errors today with extreme high contrast (blown out
backgrounds and silhouettes, +3 stops background over 100 IRE). We
ran a couple of takes without the actors, just the background
flooding the sensor with light, and it recorded just fine. Bring in
the actors (contrast) and bang! we got the codec errors. AC had a
good workaround suggestion, expose properly and later blow out the
background with a good curve in RedAlert. We did this and it worked
just fine. Seems slamming the histogram to far to the right and
left at once while shooting is problematic.
RC28, 4k, 16:9, 23.98fps, CF, b16 3.1.2, properly formatted media,
no overheating, cool studio environment.

Karl
------------

It sounds like the compression process was working pretty hard
in that situation which will in turn send a really high data rate to
the media which in this case was cf. Possibility those errors may
have been overcome by switcing your media to the Red Drive or if you
had to shoot on cf you could switch the aspect ratio to 2:1 for that
shot which will reduce the data rate and deal with that in post.
However if the post solution you guys came up with works for your
situation brilliant. Let me know if I can help.

Sean Ruggeri
Red Bomb Squad

------------

Seems to me the current camera media is perhaps at it's limit in 4k 16:9 in tough situations, or perhaps at speeds greater than 23.98. I have read many comments regarding codec errors with running water, waves, fast moving objects and overexposed or supersaturated areas. I inquired if the 16GB CF cards (supposedly faster) would help the write speeds for these enormous amount of data, and Sean responded that the 16GB cards are currently being tested and "...you will be very happy with them. They are very fast."

Karl
 
framework said:
Seems to me the current camera media is perhaps at it's limit in 4k 16:9 in tough situations, or perhaps at speeds greater than 23.98. I have read many comments regarding codec errors with running water, waves, fast moving objects and overexposed or supersaturated areas. I inquired if the 16GB CF cards (supposedly faster) would help the write speeds for these enormous amount of data, and Sean responded that the 16GB cards are currently being tested and "...you will be very happy with them. They are very fast."

Karl
Click to expand...

Hmmm only problem was that we tested with every single config imaginable except 2K, which was unacceptable for our shoot (but we did 3K) and we got codec error on all?

We didn't have that much movement (people floating in wires in green screen)

So I don't know.

Fredrik Callinggard
 
weirdcrew said:
Hmmm only problem was that we tested with every single config imaginable except 2K, which was unacceptable for our shoot (but we did 3K) and we got codec error on all?

We didn't have that much movement (people floating in wires in green screen)

So I don't know.

Fredrik Callinggard
Click to expand...

Fredrik,

Have you tried the Red Drive or just CF cards?

Would be really interesting to see if these persistent codec errors occurred on two camera shoots (both cameras with near-identical frames and settings). If the errors were only on one camera, that would be weird and would seem to back-up apocryphal stories of codec errors varying from camera batch to camera batch.
 
codec error

codec error

Same problem here!

Today after two hours of shooting in CF: 2K 2:1 '28' mode 100 FPS (build 16.515) we got codec error which has been appearing occasionally and at random ever since in all shooting modes (in RED DRIVE too).
We restarted the camera but the problem persisted and an internal error started to appear even in the playback.

I hope the new build will arrive soon or at least before we start some new big time job.
 
Update please !!!!!!
HELP!!!!!!!!!!!!!!!!
Now RED camera is useless.
 
any news here?
I'm having redcode errors two, 4K 16:9, 24fps, CF, build 15...., high contrast background scene, not more than 1 stop overexposed though.
It keeps crashing, just creating small clips.
Now that I've read this post I'll try to see if that's coming from that high contrast scenes.
But a buggy "feature" that needs correcty fast!
Carlos Filipe
Portuguese DS Operator
RED Warrior
 
You must log in or register to reply here.
Back
Top