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 Error 16.3.15 in full Production

I,

I have noticed this slight desaturation between LCD and red alert too. Make sure you are monitoring redspace as this makes it closer than it has ever been. From cc standpoint it is easy to get the saturation levels you need with very little effort. I think if red pushed the chroma any more then things would get a bit cartoon like on the qt proxies and then that would be a drag.

I loaded 16 about ten minutes after it came out. Thank you for having the confidence to go with it a reporting back to this community. It helps.

I think going to redcode 36 might solve your problems short term.

If you know that the LCD is slightly oversaturated you can easily match it to the MacBook rather than trying to match the MacBook to it.

Have a great shoot!

David
 
Is just fair to say that there was no codec error or no errors of all and the camera performed smoothly TODAY, more smoothly then our production logistic :-)

Will see what the days ahead will bring.

And if I could I will change the big red "OUT_OF_SPACE Error" to simply "ROLL OUT". Much be more calming then this warning :-)

And i was inspired by David Mullen, ASC with his blog about shooting, so you can read about day by day shooting and with some photos at my webpages. Hope will write something useful sometimes.
 
Oh yeah I forgot this strange thing!
All costumes or just black fabrics (even from crew, so it's not fault of costumes) I seen thru the camera @ Panavision HD monitor appears there as PURPLE! No black just darkpurple. As you can see it sometimes with IR or UV lights. It's strange, hope it's not in RAW it's just the preview! And 1080p don't work with Panavision HD monitors it's all green as hell.

But the black going to purple...(I switched signals from cameras to two panasonic HD monitors (one smaller one bigger) and vice versa and it's everywhere. On RED LCD it's not so obvious, but still there I think...
 
issic said:
Oh yeah I forgot this strange thing!
All costumes or just black fabrics (even from crew, so it's not fault of costumes) I seen thru the camera @ Panavision HD monitor appears there as PURPLE! No black just darkpurple. As you can see it sometimes with IR or UV lights. It's strange, hope it's not in RAW it's just the preview! And 1080p don't work with Panavision HD monitors it's all green as hell.

But the black going to purple...(I switched signals from cameras to two panasonic HD monitors (one smaller one bigger) and vice versa and it's everywhere. On RED LCD it's not so obvious, but still there I think...
Click to expand...

what is your filtration?

there are several threads here on IR pollution caused by stackin' NDs -
 
Offhollywood said:
what is your filtration?

there are several threads here on IR pollution caused by stackin' NDs -
Click to expand...

Interesting. Thanks Offhollywood. Using Tiffens. Will try tmrw with and without NDs but as we catches the last glimpse of sunset tonight, there was no NDs there and I think I saw it as well. Will check it tmrw in practical test.

On other hand...if the camera is sensitive to IR pollution and can't use standard rental ND filters...I will see that as big concern and problem...
 
issic said:
Interesting. Thanks Offhollywood. Using Tiffens. Will try tmrw with and without NDs but as we catches the last glimpse of sunset tonight, there was no NDs there and I think I saw it as well. Will check it tmrw in practical test.

On other hand...if the camera is sensitive to IR pollution and can't use standard rental ND filters...I will see that as big concern and problem...
Click to expand...

Evin has a huge thread on this -

http://www.reduser.net/forum/showthread.php?t=13765
 
issic said:
But the black going to purple...(I switched signals from cameras to two panasonic HD monitors (one smaller one bigger) and vice versa and it's everywhere. On RED LCD it's not so obvious, but still there I think...
Click to expand...

I think this is a RED 709 color space conversion thing. If you have ever used a panasonic camera they typically use a gamma curve that will tend to render blacks in the purple zone.

I was not sure if you were seeing this on the LCD or in REDSPACE or RAW.

As far as the IR problem it tends to show up more with the heaviest ND's and I just noticed that FILMTOOLS website is now offering several levels of ND with IR filtration build in.

www.filmtools.com


David
 
Maybe you should try the Rosco IR cut filters. They are doing a great job for me, even with a ND20 Tiffen. And you don't have any reflections in your shot, because the surface is not mirrored. I don't had any problems with the IR pollution unless heavy NDs are used.

Sebastian
 
ready2roll said:
Maybe you should try the Rosco IR cut filters. They are doing a great job for me, even with a ND20 Tiffen. And you don't have any reflections in your shot, because the surface is not mirrored. I don't had any problems with the IR pollution unless heavy NDs are used.

Sebastian
Click to expand...

Yeah getting them monday, pitty they are not hardened. Little worried about tough condition on set.
 
Hey Issic, have you tried 4K 2:1 RC28 24fps to CF card?

Do a 4% slowdown in post of video and sound to get PAL (we do it all the time), and crop to get 16:9...

If I were shooting something production-critical it's the only setting I'd use.

I've been going through issues in Reduser and haven't found any bad reports for that combo for b16.

Also, since that is the first combo ever introduced, the computer programmer in me says that's the combo most likely to have been tested.

It looks like everything else (including 4K 2:1 RC28 to Red Drive) has some kind of issue.

Here's a quick summary from Reduser reports (names removed and sorted by resolution) of settings with reported codec errors. I wasn't very thorough so probably missed some...

4K 2:1, RC28, 24fps, Red Drive, 16.3.1.6
4K 16:9, RC28, 25fps, CF card. 16.3.1.5 & 16.3.1.6 (several people)
4K 16:9, RC28, 30fps, Red Drive 16.3.1.5
4K, 16:9, RC28, 23.98fps, CF, 16.3.1.2
4K, 16:9 & 2:1, RC28, unknown fps, 16.3.15
4K, 2:1, RC36, 23.98fps, unknown recording media and b16 ver

3K, 2:1, RC28, 60fps, Red Drive, 16.3.1.6
3K, 2:1, RC28, unknown fps, unknown storage, 16.3.1.5
3K, 2:1, RC28, 50fps, CF, unknown b16 ver
3K, 16:9, RC28, unknown fps, unknown storage, 16.3.1.5
3K, 16:9, RC36, 25fps to Red Drive? (he just says "disk"), unknown b16 ver

2K, 2:1, RC28, 100fps, CF, 16.3.1.5
2K, 2:1, RC28, 100fps, Red Drive, 16.3.1.5

Bruce Allen
www.boacinema.com
 
I just wrapped a job where we ran into some dreaded codec errors. The majority were got with this setup:

BUILD: B16 3.1.5
PROJECT FPS: 23.98
SHOOTING FPS: 23.98
ASPECT: 2:1
REDCODE: both 28 and 36
MEDIA: RedRAID

I also did tome 3k stuff that was full of errors, and some 2k 120fps stuff that had NO errors.

One repeatable error was a with a specific shot. I was zoomed in on 2 cars at a starting line I was at approx 180mm T11, then as the car zoomed twards me I pulled out to 25mm and panned with them. Everything was fine until I stopped my pan and the cars exited the frame. The camera would crash every time.

My thought is that the motion blur of the pan allowed the data rate to stay safely low, as soon as I came to a stop the data rate spiked and it would be overloaded.

Who do I send this info to at RED? Do I use the support ticket system?
 
Errors and LOG files

Errors and LOG files

Mike Prevette said:
I just wrapped a job where we ran into some dreaded codec errors. The majority were got with this setup:

BUILD: B16 3.1.5
PROJECT FPS: 23.98
SHOOTING FPS: 23.98
ASPECT: 2:1
REDCODE: both 28 and 36
MEDIA: RedRAID

I also did tome 3k stuff that was full of errors, and some 2k 120fps stuff that had NO errors.

One repeatable error was a with a specific shot. I was zoomed in on 2 cars at a starting line I was at approx 180mm T11, then as the car zoomed twards me I pulled out to 25mm and panned with them. Everything was fine until I stopped my pan and the cars exited the frame. The camera would crash every time.

My thought is that the motion blur of the pan allowed the data rate to stay safely low, as soon as I came to a stop the data rate spiked and it would be overloaded.

Who do I send this info to at RED? Do I use the support ticket system?
Click to expand...


Yes, use the support ticket and ask to whom you can e-mail the camera LOG file. ...
 
Bruce Allen said:
Hey Issic, have you tried 4K 2:1 RC28 24fps to CF card?

Do a 4% slowdown in post of video and sound to get PAL (we do it all the time), and crop to get 16:9...

If I were shooting something production-critical it's the only setting I'd use.

I've been going through issues in Reduser and haven't found any bad reports for that combo for b16.

Also, since that is the first combo ever introduced, the computer programmer in me says that's the combo most likely to have been tested.

It looks like everything else (including 4K 2:1 RC28 to Red Drive) has some kind of issue.

Here's a quick summary from Reduser reports (names removed and sorted by resolution) of settings with reported codec errors. I wasn't very thorough so probably missed some...

4K 2:1, RC28, 24fps, Red Drive, 16.3.1.6
4K 16:9, RC28, 25fps, CF card. 16.3.1.5 & 16.3.1.6 (several people)
4K 16:9, RC28, 30fps, Red Drive 16.3.1.5
4K, 16:9, RC28, 23.98fps, CF, 16.3.1.2
4K, 16:9 & 2:1, RC28, unknown fps, 16.3.15
4K, 2:1, RC36, 23.98fps, unknown recording media and b16 ver

3K, 2:1, RC28, 60fps, Red Drive, 16.3.1.6
3K, 2:1, RC28, unknown fps, unknown storage, 16.3.1.5
3K, 2:1, RC28, 50fps, CF, unknown b16 ver
3K, 16:9, RC28, unknown fps, unknown storage, 16.3.1.5
3K, 16:9, RC36, 25fps to Red Drive? (he just says "disk"), unknown b16 ver

2K, 2:1, RC28, 100fps, CF, 16.3.1.5
2K, 2:1, RC28, 100fps, Red Drive, 16.3.1.5

Bruce Allen
www.boacinema.com
Click to expand...

this is a cool list for now bruce...should help...
i have also the feeling 4k 2:1 rc 28 24fps to CF is the safest way.
 
Hey Bruce, thanks for info, but we can't go off path of 16:9 25fps 4K RC28 for several overlapping reasons.And I don't really have time to test camera in different conditions. If I will be forced I will go for 4K 2:1 25fps RC28 for just that shot.

We had pair of codec errors todat as well.But the setup looks very similar to one I described. But now there was no smoke but unfocused background on 300mm lens. Again vertical and horizontal lines and background lighter then foreground with lots of vertical or horizontal lines and with leaves details...so for computer identical.
 
First Code error with this build

First Code error with this build

I was on set today shooting a Nascar spot. Anyhow, never had a codec error every, period in shooting this and that, although mostly to the Red Drive.

Here was the setup. We were shooting this build, near the rear of the back tires of the Nascar car(can't remember the driver name, sorry not that much into Nascar) for a peel out, smoke shot etc., running two channels of line level audio to a red drive, shooting 3K 16:9 at 29.97. (28) As the car peeled out, we got a codec error, three or four times. All eyes fell to me in a very uncomfortable way.

I switched to compact flash, same res and frame rate, killed the audio, slightly shifted the focus, and it Bingo....no codec error. My theory is that the extremely loud audio, and or vibration caused by it car caused it....but to be frank...I have no idea. BUT I did get the shot.

Other than that, the camera performed flawlessly, and the clients soon forgot about codec error. (although it looks like a bit of ADR is in my future)

I know there are a lot of theories floating about as to what causes the codec errors, is it possible that sound or vibration could be one of them???!!

Just sharing my experience. I never erased my media, so does that mean I can still get my Log files and send it to you??? Or since I switched media is it gone?

Today, codec errors aside, I was really proud of this camera. This was a high end shoot and it performed like a champ. I think I won a few converts.

That being said, I will download the latest build and see if I can break it.
 
You must log in or register to reply here.
Back
Top