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 16 Codec Error killer...

Jannard

Jannard

Red Leader
Joined
Dec 28, 2006
Messages
8,248
Reaction score
7
Points
0
The newest version of Beta Build 16 is going up on the support page of www.red.com. It kills 99% of the codec errors. We would love to hear your feedback.

Jim
 
We are here to serve... :-)

Jim
 
Thank you Jim and RED Team!

I will install & start testing tonight.
 
Add features, beta release, fix... add features, beta release, fix. :-)

... and, we are very close to a release Build 16.

Jim
 
Wow, has this just been posted ?

Great news, thank you Jim and team.

Just dowloaded it, we'll be testing soon.

Cheers,
Damien

edut : PS I couldn't figure out the time since it's 9pm here, but now I see it was posted 13 minutes ago...
 
Stop! It's worse than 3.1.5!

Stop! It's worse than 3.1.5!

I'm very sorry to report that 3.1.8 not only fails to eliminate the codec errors, it actually is much worse. With 3.1.5, shooting 16x9 we were OK with the 32MM lens, bad with the 16MM.

With 3.1.8 we got immediate codec failure with both 16MM and 32MM lenses, with both RedCode 28 and 36.

Will send whatever files to you that may help.

I fear your development team does not have a suitable test target to eliminate this error. You're more than welcome to fly into sunny Birmingham Alabama with your code writers, right next to my evil, codec breaking tree. I'll give you plenty of our famous BBQ.

I plan to revert to 3.1.5 and wait for further instructions.

Thank you for your efforts on our behalf.

Best regards,

Leo
 
Leo Ticheli said:
I'm very sorry to report that 3.1.8 not only fails to eliminate the codec errors, it actually is much worse. With 3.1.5, shooting 16x9 we were OK with the 32MM lens, bad with the 16MM.

With 3.1.8 we got immediate codec failure with both 16MM and 32MM lenses, with both RedCode 28 and 36.

Will send whatever files to you that may help.

I fear your development team does not have a suitable test target to eliminate this error. You're more than welcome to fly into sunny Birmingham Alabama with your code writers, right next to my evil, codec breaking tree. I'll give you plenty of our famous BBQ.

I plan to revert to 3.1.5 and wait for further instructions.

Thank you for your efforts on our behalf.

Best regards,

Leo
Click to expand...

Can you make direct contact with Jarred?

Jim
 
Leo Ticheli said:
I'm very sorry to report that 3.1.8 not only fails to eliminate the codec errors, it actually is much worse. With 3.1.5, shooting 16x9 we were OK with the 32MM lens, bad with the 16MM.

With 3.1.8 we got immediate codec failure with both 16MM and 32MM lenses, with both RedCode 28 and 36.

Will send whatever files to you that may help.

I fear your development team does not have a suitable test target to eliminate this error. You're more than welcome to fly into sunny Birmingham Alabama with your code writers, right next to my evil, codec breaking tree. I'll give you plenty of our famous BBQ.

I plan to revert to 3.1.5 and wait for further instructions.

Thank you for your efforts on our behalf.

Best regards,

Leo
Click to expand...

Upload your log files and any R3d files that red needs.

I'm personally going to go back through all my RED files and find any LOG files and upload them. If everyone uploaded their LOG files anytime one existed, it would give RED a lot more help in solving problems. It might be a good feature to include in Redcine or RedAlert, an Auto upload LOG file checkbox that the user could set. Then whenever you loaded footage that had a log file with it, it would get uploaded.
 
I don't know what this means, but there is no .log file produced with this build.

Best regards,

Leo
 
Leo Ticheli said:
I don't know what this means, but there is no .log file produced with this build.

Best regards,

Leo
Click to expand...

You have to unmount the media. You can do it via the media menu or I think you can press exit and undo at the same time to unmount the media and write the .log file. It's not automatically written now so I think the firmware should be changed so anytime an error is thrown a .log file should be created/appended with the error.
 
Retrieving the LOG file.

Retrieving the LOG file.

As a general comment, to extract the .LOG file, re-attach either CF media or RED-DRIVE, and wait 1 minute. Then press the UNDO and EXIT keys and wait until the rear status screen says "safe to unmount" and you should find a .LOG file there.

Leo if there is a specific issue with this build, can you drop me a P.M?

The .LOG file is automatically updated, and pressing UNDO + EXIT is also the recommended procedure to use by the way, but if you just remove the card / detach the RED-DRIVE without pressing UNDO + EXIT the .LOG file isn't written out to the media.
 
Leo can you post a picture of your tree and composition for reference?
 
RED TEAM....is it helpful to get all the RED Log data you can good or bad....or just logs if we have a codec fault?
 
I've just spoken with Jarred; the tree I'm testing with is the absolute worst-case scene. Red is working diligently to solve this last bit and I'll be helping test.

This is not a scene that I would ordinarily shoot; I think it's the combination of very bright sky and highly complex tree.

Best regards,

Leo
 
Leo... we really appreciate you setting up a "break the build code error test". I want to make sure that our customers know that your tests IS the last 1%. I am very comfortable that it will be nearly impossible to get a "codec error" under almost any condition (except, obviously) your extreme setup. We will send you our next build to test privately to see if you can break that one. We think it takes care of the last 1%.

Shoot Build 16 with confidence... unless you go to Leo's house of pain. :-)

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