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 on release build 15

G

geoff tompkinson

Well-known member
Joined
Jan 17, 2007
Messages
108
Reaction score
0
Points
0
Website
www.gtimage.com
Is it only me that cannot shoot 4k 16:9 on either the release version or the previous version of build 15 when recording to CF. Always get a codec error after a few frames.

Or is this well known ?

4K 2:1 is fine however.
 
codec error on release build 15

I've had the same error with the CF cards (not tried with red drive). But I've found at redcode 28 4k 16:9 it is happy to record, and also at redcode 36 4k 2:1. I assumed this was to do with it (4k 16:9 Redcode36) being such a huge quantity of data to send to CF card and the limited speed of the cards.

id this a known limitation of build 15? I was hoping it would go away with the release build.
 
4K to CF

4K to CF

turleyt said:
I've had the same error with the CF cards (not tried with red drive). But I've found at redcode 28 4k 16:9 it is happy to record, and also at redcode 36 4k 2:1. I assumed this was to do with it (4k 16:9 Redcode36) being such a huge quantity of data to send to CF card and the limited speed of the cards.

is this a known limitation of build 15? I was hoping it would go away with the release build.
Click to expand...

Recording 4K 16:9 at REDCODE 36 is not permitted to CF - the data rate is too high. So RED-DRIVE only.

The choice on CF cards is 4K 2:1 at REDCODE 36, or 4K 16:9 at REDCODE 28.

Operations Guide Page 39 / 40 has a table...
 
my bad for not getting in with the latest ops manual!
 
So first off I know that Build 15 is now released at v2.2.5 (and we have updated to it) but yesterday we got this error using v2.2.1 when using 4K 16:9 at 23.98 at both RedCode 28 & 36 (recording to RedDrive):

IMG_5493s.jpg


It seemed that when the detail in the shot got too high the camera would freeze the shot and return this CODEC_ERROR statement for several seconds before stopping the recording and returning to normal.

Switching to 4K 2:1 with any other combination of framerate and RedCode quality fully fixed it and we couldn't crash it no matter how high the detail in the scene got.

Also using v2.1.7 we managed to show the split screen bug where the top half had severe image degradation and the bottom half looked fine (click for full 4K TIFF (54MB):



The settings for that shot were 4K 2:1 23.98 RedCode 36, mounted on a tripod and static.

I haven't had a chance to duplicate these conditions with the release build yet but in the mean time if anyone else has experienced similar issues with these builds please chime in here, or if anyone at Red can definitively say the bugs are squashed that would be great too!

With RedCode being rewritten from the ground up in Build 16 I'm hopeful these will soon be non-issues anyway. I can't wait to see how much better the image can be (and if the 85mm Prime chart in another thread is shot on an alpha build 16 it's probably a good indicator of what's to come!).

Cheers!

Paul
 
Release??

Release??

Hi,

We've just installed Build 15, 2.2.5 and we still can't record 4k 16:9 and we still have the flicker issue on the monitor. So for us, there's no difference from the two latest upgrades.
 
Yeah, the LCD flicker stuff remains in the release build. The good news is that it's sporadic and doesn't affect the recorded image... but it's there.
 
mccainds said:
Were you in focus check zoom in mode? I saw that error while trying to record in while in that mode.
Click to expand...
No, this was in normal full view mode. I remember your bug too in an earlier build but Red corrected that by disabling recording whilst in zoom.

HTH

Paul
 
Stuart English said:
Recording 4K 16:9 at REDCODE 36 is not permitted to CF - the data rate is too high. So RED-DRIVE only.

The choice on CF cards is 4K 2:1 at REDCODE 36, or 4K 16:9 at REDCODE 28.

Operations Guide Page 39 / 40 has a table...
Click to expand...

But I can't shoot 4k 16:9 at redcode 28 to CF either - always getting the codec error.

Only really stable with 4k 2:1
 
I just formatted a red cf card to 4k 2:1 25fps project redcode 36 recorded a timelapse at 4k 2:1 1fps for 20 minutes. it seem to record ok, no dropped frames or anything. click the play button above the rear lcd and got a 'Play back error: CLIP FAULT'
 
v2.2.5.

v2.2.5.

We shot with v2.2.5. today and after few shots we also get CODEC ERROR (4K 16:9 redcode26 mode)! What about downgrading to v. 2.2.1?
 
AKABAKA said:
Ooh, Paul, are you shooting at Kinkakuji? Beautiful shot!
Click to expand...
I'm not sure of the name but if it helps it was south of Shinagawa but before Yokohama. It seems you're familiar with the area if you can recognise it anyway!

Hanami was very short this year due to rain shortly after the sakura began blooming, so we really only got a couple of good days of shooting them before they disappeared (and this is from a client's shoot, not our own).

Cheers,

Paul
 
We had a sunny day and I went to old town to shot some sun/shadow tests.
With wider optics pointing to crowd I got Codec Error on every second take.
Redcode 36, 4K, 16:9, fw15 b 2.2.5., Red Drive, 25fps.
Then I did close aperture about two stops and it works flawlessy.
Original shots were safe in terms of aperture as traffic lights weren't on and was checking on 320 ASA.

So closing the aperture 2 stops seems to work arround it.

Priit
 
You must log in or register to reply here.
Back
Top