Welcome to our community

Be a part of something great, join today!

  • 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 errors gone!

Leo Ticheli

Well-known member
Joined
Apr 20, 2007
Messages
818
Reaction score
0
Points
0
I just tested the latest debug build sent to me this morning on my codec error inducing tree and could not break it.

Shot to Red Drive; 16x9, RedCode 28, 23.98 timebase at 24 & 30 fps. Shooting with 16MM prime, deliberately over-exposed.

Could not step through frame by frame to look for compression failures because this debug build won't open in QT, FCS, RedCine, etc., but did not see a problem during playback on the LCD.

As soon as a complete build is in hand I'll complete the tests.

Best regards,

Leo
 
I just tested the latest debug build sent to me this morning on my codec error inducing tree and could not break it.

Shot to Red Drive; 16x9, RedCode 28, 23.98 timebase at 24 & 30 fps. Shooting with 16MM prime, deliberately over-exposed.

Could not step through frame by frame to look for compression failures because this debug build won't open in QT, FCS, RedCine, etc., but did not see a problem during playback on the LCD.

As soon as a complete build is in hand I'll complete the tests.

Best regards,

Leo

Leo - what is the # of the build?
 
This build does not have a number displayed; it's a "debug" build sent to me to test with my codec-breaking tree and sky.

The build cannot be used for production because the files cannot be opened, only played back in camera.

Hopefully, Red will soon release this build so we can all use it.

Until then, I'm sticking with 3.1.5.

Best regards,

Leo
 
Thanks for your help with this Leo! And thanks to your tree.

Graeme
 
We still have a few tricks left in the bag, but it is comforting to all that we are near the end of the dreaded "codec error" syndrome.

The team has worked long hours over this.

Thanks to Leo and the "tree from hell".

Jim
 
Brilliant!

And thanks Leo - you're kinda like that guy in every programming class who's super-useful for debugging because they have a knack of breaking everyone's code...

You might find it wise to decide on an admission price for tree filming - when all the Hollywood blockbusters filming on Red, Epic, etc want to make sure their fresh firmware update is bomb-proof, they will be lining up outside your gates.

SO DON'T BURN THE TREE!

Hopefully you'll remember us and give us an indie rate.

Bruce Allen
www.boacinema.com
 
Leo,

Can you post a still of the tree. I have been shooting foliage for about three months with no incident and I am curious which shot busted the codec.

I am glad to hear it is gone .

Thanks,

David
 
Oh baby, Oh baby!!!

Oh baby, Oh baby!!!

Just loaded up the QT component for the new build.

No sign of a bad frame anywhere!!!

Now we're cooking!

Thank you, Red Team!

Leo
 
A little Alabama summer thundershower just started; I'll send a snap of the tree as soon as I can.

It's really nothing special; my theory is it was the combination of wide angle, 16MM, and 16x9 with high contrast and tons of fine detail that overwhelmed the compression engine.

I think people who escaped the codec errors may have been shooting tighter, thus less detail in the frame.

Best regards,

Leo
 
We're sending a tree removal service to transport the tree to CA so we can
keep testing.
 
Leo AND Red Team,
Thank you. That's the kind of constructive criticism and collaboration that will only make the camera stronger.
Soon even a slow adopter like myself will try out 16...
Cheers,
Harry
 
Deanan,you should install in the Red Labs a camera shooting timelapse from the crew, in the background a watch ! On day this will be an incredible historical document.
Wow!
Marc
 
A Tree.... How cool is that? Not charts - a tree. Can't fool mother nature.

bob
 
Back
Top