Welcome to our community

Be a part of something great, join today!

Register 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...

Leo Ticheli said:
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
Click to expand...

Was just curious what the tree looks like that's all.
 
Leo Ticheli said:
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
Click to expand...

so we shouldn't have any codec errors unless its a worst case scenario situation like that. Sounds like its almost there. Anyone else had any issues with this build?
 
Im as thrilled as everyone else to hear this but lets be fair... we've heard this a few times before. :) Let the testing begin.
 
Leo,

Kindly post a picture of the tree. I think it should be a good test case.

On a related note, a codec error because of some difficult scene should not even happen on the 1% -- it is not just good programming.
 
Hi,

Leo was kind enough to send me a couple of pics of the evil tree that keeps causing all the B16 trouble.

As you can see, the bastard was quite worried when he heard earlier today that the Build 16 Codec Error killer update was released.

Unfortunately, he managed to defeat the killer update yet again.

Let's show this bastard! Bring the new update that takes care of this last 1%.
 
We are sending Leo a new Build to torture... today. We encourage him to post his results.

Jim
 
K.Berlin said:
bug erasing almost realtime...other companys should start to learn
Click to expand...

Established companies, with existing product lines, already know how to fix bugs, and its about quality, not speed. Only making incremental changes to existing products also helps keep problems/bugs to a minimum straight away, but results in less interesting/delayed products also, so different philosophy.

When Red steps up to the mass market with Scarlet, daily bug fixes aren`t going to equate to greater sales, out-the-box `readiness` is, which is one reason I`m going to become a beta-tester for Red tomorrow (for no fee!), as well as the fact that nearly everything I want to film is `complex` in nature (well thats the nature of, er, nature), so I`m going to be as cruel to Redcode as I can be. That said, I`ve had no problems with build 15 so far, but then again I haven`t pushed it yet (waiting for that Red Raid before I treck into the `heart of darkness`).. but keep up the good work..and sleep regular for build17, I know it isn`t intuitive, but discipline yourself , it makes problem solving easier long-term, its a brain thing! :matrix:
 
eastco said:
Hi,

Leo was kind enough to send me a couple of pics of the evil tree that keeps causing all the B16 trouble.

As you can see, the bastard was quite worried when he heard earlier today that the Build 16 Codec Error killer update was released.

Unfortunately, he managed to defeat the killer update yet again.

Let's show this bastard! Bring the new update that takes care of this last 1%.
Click to expand...

You know in the movie The Ring everything that's cursed gets all messed up when you try to shoot it?

I'm not sure this is a codec error, so much as... that tree looks evil.

Just saying...
 
eastco said:
Hi,

Leo was kind enough to send me a couple of pics of the evil tree that keeps causing all the B16 trouble.
Click to expand...

Thanks EastCo for posting the pictures. They are difficult scenes, but from my experience I don't think they should break the codec solely because of compression.

I seriously think that Red needs to do more on quality control on its software / firmware / systems integration.
 
laboprod said:
Does this new build address the "compression bug" (http://www.reduser.net/forum/showthread.php?t=15859) or only the codec errors?

thanks,
antoine.
Click to expand...

Same thing. Codec stands for COmpressor/DECompressor, because it does both. Picture quality suffers when too much signal is thrown away during compression, either because i) the compression algorithm needs improving/tweaking, or ii) the data rate is too low, or iii) bugs, or all three. I believe i) and iii) are being worked on, RC36 was the answer to ii), although as faster recording media become available, maybe that will be increased slightly again..
 
ronx said:
Same thing. Codec stands for Picture quality suffers when too much signal is thrown away during compression, either because i) the compression algorithm needs improving/tweaking, or ii) the data rate is too low, or iii) bugs, or all three.
Click to expand...

Ronx, you forgot a very important #4:

(iv) Implementation.

For e.g., the take the freely available JM reference codec H.264 from JVT and compare it only in speed (not accuracy, etc.) to FFMPEG. The way code is written for FFMPEG (though I personally am not a big fan of how they have written it), it really beats JM code, at least several years ago when H.264 was young and I was experimenting with it. (BTW, FFMPEG also has hiccups sometimes.)

Unfortunately, software quality via its implementation is not something a lot of companies try to focus on. Too many times the focus is just on a functional implementation that works in a controlled setting just to get it out of the door. Parochial vision impedes seeing the benefits of investing slightly more time in the start in a good framework and structure of code, which saves tremendous time, effort, resources, money, (and not to mention reputation) later.
 
You must log in or register to reply here.
Back
Top