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

Jannard

Jannard

Red Leader
Joined
Dec 28, 2006
Messages
8,248
Reaction score
7
Points
0
While everything has improved dramatically with Build 16, there are still instances of "codec errors". We don't like them. In fact, they are the single focus of the team right now. We believe we know what is causing them and we have a solution. It will take us though the weekend to squash them. Please be patient... we are on it.

Jim
 
Jim,
I have posted several times, usually kind of humors comments or questions about this or that.

I just wanted to say you have inspired me very much in my work and in your can do, fair, and perceptive outlook. I wanted to buy your camera at the onset of reservation numbers, but was only able to drum up the funds at the time of the second res group offer. I simply based this decision on what I perceived to be the advent of a new camera from someone who's intentions were truly to make the best camera that could be made today.

I figured if you could get Oakley to the Point that you got it to then my money was in good hands. You had me at "Dedicated to purpose beyond reason" the single best product mission statement ever.

I just wanted to thank you for proving me correct and allowing me to make the one of the best investments i have ever made.

But for fuck sake enjoy your Forth of july.
 
Jim is Jim. I am me. As for Jarred, who knows? He's certainly tall enough for two people :-)

Graeme
 
Great. Glad to hear that. Not sure why they weren't the single focus of the team before. The codec errors are definitely the Red's single greatest problem today.

If build 16 becomes stable and a month goes by without anyone having codec errors, I think this would make a HUGE difference to the value of the Red brand.

Codecs simply should not crash and burn. This is a *fundamental* design rule when designing a codec that everyone except for Red seems to have gotten right: If given the choice between losing a little detail and failing to record the image, LOSE THE DETAIL!

No word processor on the market crashes if asked to save a document given a strange sentence. No digital sound recorder crashes if given strange sounds to record. No DSLR crashes if given a weird picture to take. AFAIK no digital video or cinema camera crashes if given a weird image to store. Except for Red's. It's not a small problem, it's very big. I hope you guys do fix it soon. I really don't see any point in announcing new recording modes, products, etc if it is not fixed. This indicates misplaced priorities and is actually very worrying.

So glad to hear you guys are focusing on this.

Bruce Allen
www.boacinema.com
 
I haven't seen a codec error since build 13. Build 16 has been working fine for me. I've been recording 4K 16:9 RC28 and RC36 to the RED Drive and CF cards...not RC36 to the CF cards of course. I'm also recording at 24fps not 23.98fps.
 
Bruce Allen said:
Codecs simply should not crash and burn. This is a *fundamental* design rule when designing a codec that everyone except for Red seems to have gotten right: If given the choice between losing a little detail and failing to record the image, LOSE THE DETAIL!

No word processor on the market crashes if asked to save a document given a strange sentence. No digital sound recorder crashes if given strange sounds to record. No DSLR crashes if given a weird picture to take. AFAIK no digital video or cinema camera crashes if given a weird image to store. [/url]
Click to expand...

Sorry, Bruce, but with all respect: this is completely incorrect.

1. Nobody else but Red could have gotten it right, since this codec IS the core of their concept and it's unique.
2. This is much more complex than just getting detail or crashing.
3. A codec like Red's is a tad more complex than a word processor. And while a word processor is one of the oldest of all computer applications, I can still show you Microsoft Word crashing in a minute…
4. Years ago I found one very popular frame grabber card with a codec as simple as M-JPEG crashing on hand-drawn pictures from my little son when we tried to animate them. I couldn't believe it as well…

Finally, the codec must have been changed a lot to do the magic found in sweet 16. Logically, only after these changes they can iron out the errors.

Regards,

Uli
 
More capability means more things to worry about. Photoshop is my favorite program (right behind RED Alert! and REDCINE, of course) and it crashed twice this week. Apple, Adobe and the other "big" guys work everyday to keep up with the features they have enabled. We work every day and every night.

If there is good news here... Build 16 is very close. It is light years ahead of previous builds and we just have a few things to nail down (as compared to previous builds). To say we have come a long way in a short time seems an understatement.

Jim
 
Thanks for the update and thanks to the RED Team for working non-stop to get it just right.......
 
Jannard said:
More capability means more things to worry about. Photoshop is my favorite program (right behind RED Alert! and REDCINE, of course) and it crashed twice this week. Apple, Adobe and the other "big" guys work everyday to keep up with the features they have enabled. We work every day and every night.

If there is good news here... Build 16 is very close. It is light years ahead of previous builds and we just have a few things to nail down (as compared to previous builds). To say we have come a long way in a short time seems an understatement.

Jim
Click to expand...

Jim,

It's the 4th of July. Go spend some time with your family! :-)

-Thor
 
Jannard said:
More capability means more things to worry about. Photoshop is my favorite program (right behind RED Alert! and REDCINE, of course) and it crashed twice this week. Apple, Adobe and the other "big" guys work everyday to keep up with the features they have enabled. We work every day and every night.
Click to expand...

But you guys are WAY ahead in the feature-per-dollar game already.

We tolerate Apple and Adobe's "features before stability" approach because you we can always do the work again if there's a crash.

If Photoshop crashed *and then deleted your original file* I'm sure it would no longer be your favorite program.

This is not a post production software product. If I am filming something I can only get one take of, I get scared with the Red. Even if I had 10 Reds shooting all at once for safety, the image content could very well cause codec errors on all of them for all I know.

Jannard said:
If there is good news here... Build 16 is very close. It is light years ahead of previous builds and we just have a few things to nail down (as compared to previous builds). To say we have come a long way in a short time seems an understatement.

Jim
Click to expand...

Of course! Not denying all of this. Not asking you to work day and night either.

If you told anyone asking for any more features "hang on, we are focusing totally on making it stable first" then they would be quiet. Even me! I will shut up now.

Bruce Allen
www.boacinema.com
 
Guys...

This thing is coming.
I'm starting a short-shoot in a bit more than a week. That'll be my build 16 Christening... Really look foreward to it by now!

Gunleik
 
Build 16

Build 16

Not adding any additional features, but focussing on debugging those that we have is EXACTLY what is going on here with the Beta Build 16 firmware.

When its debugged it will become a production release.
 
You must log in or register to reply here.
Back
Top