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 faults still there with build 16

I had several Codec errors shooting today. I was shooting 16:9 in 25 fps. But after shooting a bunch of takes in a row i got the error everytime I hit the REC button. I rebooted the camera but it didn´t work so I turned it off for a couple of minutes. Started to think if it had anything to do with the temperature so i changed the fan setting to hot. Then it worked better and after a while I didn´t have the problem anymore. I did change to 4k 2:1 for a while and that worked. But later turned back to 16:9, no more problems after that. The disk was formatted in b16 before shooting. Just a tip, don´t know if the temperature has anything to do with it but it worked for me...

Stuart, I will send the log file to your Tech Support tomorrow. Need to sleep first, 19 hour day...
 
codec error also here

codec error also here

same situation here,

shooting yesterday,
16:9 4K, 25 fps. with SOUND, on red drive, RC 36. camera build B16.

interior (studio) enviroment, relativelly hot - about 30/32 C max, but did not check that with thermometer :(
camera fan was set to high temerature enviroment.

after shooting for approx 6 hours camera started to pop up the error info.
(120 clips, 75 Gb approx was used on red drive when first error occurs)

these errors where shown:

1) Camera Error x Codec_Fault

or

2)Camera Error x Internal Fault.
=====
errata: not sure was it "CAMERA ERROR" or "RECORDING ERROR" - i am not with the camera right now.

=====

not at the same time of course, first one more often. after shooting of approx. TWO SECONDS - error was on the screen. the clip is usable anyhow, but just two seconds long.
we did try obvious things like powering the camera off/on, re-attaching red drive, swithcing from recording mode to playing back etc. nothig helped :(
unfortunatelly we were not in the position to check with another red drive - the other drives were far away that moment; same with CF cards. we will check that today.

i have log file for sending it. but cannot find where to upload/send it when on support site...

anyone know how to do this?

thank you,

filip kovcin
 
could people also report what glass they are using when getting the codec error. I had a thought today that if you are using glass that resolves better/sharper/clearer than Red or nikon glass then maybe that extra sharpness is something the codec can not handle.

Its a pure hunch but I am curious if it has something to do with glass.
David
 
We had one record error the other day at 4k 2:1, 23.98, 24fps. About a quarter of the frame was overexposed. The next take with the exact same framing it worked fine. Sorry I don't have the log file.
 
codec errors and high contrast

codec errors and high contrast

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
 
I have not been able to replicate this.
 
I had so many codec errors that it was embarrassing. I can't even begin to try to explain. It's been with every configuration imaginable and on every take after 15 sec of shooting. I will explain, but have to sleep now - have another horrible day tomorrow where I need to try to pull it through. I know - shouldn't have taken the chance on a beta build, but thought studio with green screen shouldn't be so bad. HAHAHAHAHAA haven't had one take without codec error HAHAHAHA.

Will come back about it though

Fredrik Callinggard
 
weirdcrew said:
haven't had one take without codec error
Click to expand...

That's certainly frustrating. But looking on the bright side: if it is that repeatable, it shouldn't take the red team too long to fix it! Hopefully you can get them all the specifics of your shoot so they can replicate it and squash this bug.
 
well well well, codec error again...
with the new build 3.1.5. Shooting on red drive, 4K 16/9, REDCODE 36, 25fps, T1.4 (with an old zeiss high speed 35mm prime) at an old "not so white" bright wall. I was able to shoot it without codec error, once or twice out of a dozens of time. I did try to cool down the camera with a frozen gel pack on it, but it didn't help (and anyway the camera internal temperature gauge was not showing any problem). The fan was first set to "auto" and I did change it to "variable" and then to "hot" and back to "variable", but it did not seems to make any difference concerning the codec error.
Exact same scene with one stop down (T2) had codec error as well, but at T2.8 it didn't...
I did try 4K 16/9 redcode 28, but it had the codec error.
I did try 4K 2:1 redcode 36 (at T1.4), and it did work...
I then try again 4K 16/9 but the codec error came again, then I try to shoot a street view with houses, cars parked and a bit of sky still @ 4K 16/9 25fps, redcode 36, and it recorded without codec error...

All the clips that I say didn't have a codec error, were shot for at least two minutes. All recording on same red drive formated for build 3.1.5

hope it can be fixed soon.

thanks,
antoine.
 
I haven't loaded the new 3.1.5 firmware... But I'm not experiencing codec errors with 3.1.2 or whatever the first B16 beta revision is.

Have you guys tried rolling back your firmware? Still getting codec errors after doing so?
 
laboprod said:
have heard of codec error with build 3.1.2 as well. Was not on set but camera crew reported to me.

Have not try to roll back to 3.1.2

antoine.
Click to expand...

I had all day yesterday - when I had lights in my green screen shoot, to be garbage matte'd afterwards - so my guess is that this is the problem. I was shooting on both builds any configuration imaginable.

Will come back to post but are shooting today again and are avoiding the lights in the frame, if it's succesful we'll know.


Fredrik Callinggard
 
I discovered a codec error on the first frame of a clip, shooting a test shot, very high contrast; bright sky, dark trees, and a horribly front lit subject.

Recording to Red Drive; 23.98, 16x9, Red Code 28.

When I return to the facility tomorrow I'm going to step through all the footage to look for more problems.

I'm on 3.1.6 and I don't know whether to drop back to 3.1.5. I did not extensively test that build and not under the conditions that many have reported to cause the error.

Here's the BIG problem; there was no indication while shooting that a failure had occurred! The ramifications of this should be obvious.

Now a bit of philosophy. It's interesting that films were made with very early examples of the Red camera, but this does not mitigate the danger of this codec error for us now.

To those who seem to be suggesting that we just chill out and wait for Red to fix this; I have a serious disagreement with you. Many of us are trying to make a living with our cameras, we can't leave them on the shelf or waste the time reviewing every take in the field. We surely can't waste time trying to make the camera shoot a proper take.

Lastly, I seem to remember that Build 16 was said to have more testing and more stability than the release builds. Were we not told that after going to Build 16 we would never want to go back?

I know there is the boiler-plate disclaimer with Build 16, but I believe we were encouraged to make the jump.

Now, perhaps the error is not exclusive to Build 16, and I've never shot a scene that produces it before. Perhaps I've simply been lucky.

I have every confidence that the Red team is working diligently to fix the problem; I also feel our reporting it is vital.

What we need now is advice from Red on how to proceed.

Good shooting and best regards,

Leo
 
Leo,
I believe you are perfectly correct in saying that we should all be diligent about reporting this problem here, as well as sending the boys at Red your files to analyze. I hope that no one on the Red Team takes it personally when someone posts a bit of a rant here. It's very upsetting to be on a paying job with your own camera that you pitched as the best image-making tool at your disposal and have the sort of trouble being reported. That said, the more people post, test, and send the results to Red, the faster it will be resolved.
Cheers,
Harry
 
Well, in all cases, it is not nice to rent your Red knowing that this happens and WITHOUT WARNING the guys who pay you a lot that to avoid this, we have to shoot in 2:1 and not 16:9, where codec error can happen, as everybody knows apparently. we didn't at that point. we were just looking for you where you were to fix this after you got us charged for your personal presence on set.

thanks again, but never again. sorry.
 
You must log in or register to reply here.
Back
Top