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

Build 15 Problem

B

Bill Paris

New member
Joined
Dec 15, 2007
Messages
2
Reaction score
0
Points
0
Wanted to share this and couldn't find the thread that focused on build 15 problems...... I had a shoot today with a client in tow. Shooting 4k 16X9, Redcode 28, 23.98, build 15. The first couple of hours the camera worked fine, but when I tried to shoot a waterfall the camera would stop recording and give me a "Codec Error" warning after about 2 seconds. After trying different things (including re-booting back to factory specs) we found that when we shot areas with little movement/detail the camera would record fine, but when the camera was recording palm trees moving in the wind or the waterfall it would jam up. When we switched to 3K it seemed to work fine as well. In the end we took the camera back to the office and loaded Buld 13 at the suggestion of tech support at Red. The up shot is.... beware of using build 15 on jobs with clients in tow!
 
This was a problem on the earlier builds. Looks like it's reared its ugly head again.

We did some tests to find out exact record times in various modes, comparing two cameras and we found that the record times differed, based upon what the camera was pointing at. Eventually we just covered the lens giving us the longest record time. But some tests had a difference of 5 minutes or more. I guess it's a variable bit rate issue.

Thanks for the heads up.

-CJ
 
Evin Grant said:
Hence the "Beta" status. This was a pretty common problem on build 8 or 9 I think too.
Click to expand...

not being able to shoot 16:9 in 4k should be "charlie" status in my opinion.

i thought i may have missed this limitation or mistook it for continued lack of support of QT 16:9. however, i don't even see it on the download page. am i missing where this was published? besides having to stumble upon it in a forum. or the really hard way....on set. i know.....don't depend on beta. luckily it was just a test shoot. still embarrassing.

see my post on the other thread that is about this dependence on 2:1. just getting frustrating.

still love you red team
 
Yes indeed, we heard a few instances of this, Sean is trying to recreate it right now.
 
This is interesting. We were hanging out of a helicopter yesterday and got the Codec Error several times using build 15. The camera operator noticed it seemed to happen every time he reversed directions and flipped the camera to shoot behind him. We thought maybe it was the roughness of the ride causing a disconnect with the hard drive. (He was handholding afterall at 55 mph) So maybe the 180 degree reversal flip motion was too much motion. Does this require a reboot? We did but I don't know if it was necessary.

This was a test run to see how the camera would do so we were looking for problems like this. The finished footage would give us a blue screen and "failure to write frame" message in Redcine.
 
stimulating codec error

stimulating codec error

You can see flipping cam front to back would create some jarring motion. I had accidently configured for 16:9 instead of 2:1 I intended. We didn't notice until we tried using the Flash card. No more errors after that.
 
That's a Red-Drive dropping frames. It should have popped up on the LCD, indicating how many it dropped. It doesn't take much to induce, and it makes sense on a Tyler mount with combination of high frequency vibration and rotating on 2 of its axis'.

Redcine will not render through the drop frames, it just stops and gives an error. In the QT proxies they'll show up as green frames and when you render out through RedAlert, it'll show as a stutter.

Our first time using the Spacecam AND the Red-Drive had a lot of these problems, as long as we were rotating, doing fast pans, or if there was turbulence. We've since solved that problem and can shoot in any vehicle, drop frame free.

EDIT: I didn't read the post thoroughly enough, the drop frames shouldn't cause the codec error message. Not sure what the hell that is.
 
Can someone at RED let us all know if this is a codec issue and the workaround would be not shooting so much motion in a shot till it's fixed?

give me workarounds and your word your working on it and I am A ok :)

a "real" shoot in the AM so I would like to know what this is :) :)
 
Build 15 is beta so please don't use it for for production. Problems like these pop up because the beta stage is where we need to have them show up if they don't show up before beta.
 
Can RED please repost 14 as it is a decent build that seems less buggy and gives us an option for higher speeds AND AUDIO.

Build 13 has no audio.

Is/has there been a release build with AUDIO enabled?

David
 
Deanan said:
Build 15 is beta so please don't use it for for production. Problems like these pop up because the beta stage is where we need to have them show up if they don't show up before beta.
Click to expand...

I found noisy pcitures as well in ASA 320 / Fan runs automatically / Air-Condition Studio.
BWB
 
Ours was a test just to see if these things would pop up in beta 15. So now I'm curious. Were we seeing dropped frames on the HD or were we seeing codec motion errors? I hope we weren't so unlucky as to get both.

Would codec errors also cause the blue frames same as HD dropped frames?
 
I would recommend never using a spinning hard drive on heli rig. However, the codec error is another problem we're looking into.
 
Build 14 and 15

Build 14 and 15

battistella said:
Can RED please repost 14 as it is a decent build that seems less buggy and gives us an option for higher speeds AND AUDIO.

Build 13 has no audio.

Is/has there been a release build with AUDIO enabled?

David
Click to expand...

Build 13 has audio, it just does not have audio playback on-camera.

As for stability 14 and 15 are from the same code base, so 15 is no less stable than 14. i.e. if there IS an issue on 15 its probably on 14 as well.
 
Deanan said:
Build 15 is beta so please don't use it for for production. Problems like these pop up because the beta stage is where we need to have them show up if they don't show up before beta.
Click to expand...

Ill all fairness Deanan, I've gotten the codec error in every single build (including all production builds). I do seem to get it less than I did in previous builds so it looks like things are improving but this has also been a known problem since the cameras shipped.

Generally you can just hit record again and everything will be fine. Sometimes the problem seems to persist and formatting the drive and/or card and rebooting is necessary.
 
We could be talking about different errors. There was a specific problem fixed around build 8 and we haven't seen it since then. If you are seeing a codec error, please file a ticket with tech support otherwise we have no way of knowing it's still happening or with what frequency. If you can provide a way of reprducing it, that would be extremely valuable.
 
Deanan said:
We could be talking about different errors. There was a specific problem fixed around build 8 and we haven't seen it since then. If you are seeing a codec error, please file a ticket with tech support otherwise we have no way of knowing it's still happening or with what frequency. If you can provide a way of reprducing it, that would be extremely valuable.
Click to expand...

Fair enough. Unfortunately, I don't have a way of repeating it. On my last shoot (production build 13) we only got it once. After getting the error we simply hit record again and it went away. In earlier builds we would get it several times/day so it seems the problem you fixed in build 8 reduced their frequency but we definitely still get them from time to time.
 
You must log in or register to reply here.
Back
Top