Codec errors...

[Jannard]

We have found several causes (new ones) of codec errors. There will be a new build shortly that addresses these. While there is no guarantee (yet) that every one will go away... we are comfortable that most will be resolved. The complexity of a new build, multiple frame rates, data rates and new compression scheme make this a difficult task. But we will not stop working until every one is taken care of. Even then, we won't stop working... but we are anxious to fix this and work on something else. We know you are too.

Jim

[gdv]

Jim,
I think the market, producers, DPs and all the rest of decision maker in which camera to use when going for a shoot, will be tolerant for a few more months.
If by about 6 months most of the problematic issues with the Red will not be solved I think the industry will pass and go to another camera/format.
So if Red is a "life wanted", problems needs to be solved.

[Warren Kommers]

Jim,
problems needs to be solved

They will be. Thanks for chiming in on these issues Jim. It's very reassuring.

[Jannard]

Expect the new build in a couple of days...

Jim

[Steve Sherrick]

Jim,

Do you foresee this as a moving target? In other words, is it something that can be completely solved or will there always be the potential for them to strike due to the seemingly endless scenarios that the cameras will be faced with (obviously there's no way to test them all). If each camera is using a variety of lenses, with a wide spectrum of scene detail, and also many different combinations of camera settings, I wonder if this will always be a challenge or if you think you may have found some common causes for them. I have only experienced the codec errors on Build 15 4K 16x9 23.98 with scenes with lots of detail (mostly shots with trees in them). Haven't pushed Build 16 too hard...yet. So i guess I'll find out if it's still an issue or not.

Look forward to hearing more about it, and thank you for the tremendous effort you guys are putting in to perfect this camera.

[Jannard]

I think we have figured out where we are today... but if we were ever to try to squeeze a bit more data rate out of the camera, we would likely have to deal with this again. But if that happens, we have a lot more experience finding the causes... :-)

Jim

[Steve Sherrick]

Not to stray too far off the topic Jim, but is the limitation (especially thinking in terms of getting more data rate out of it) with the recording media or is it a combination of the compression engine and drive speeds that will make it difficult? I'm assuming we are getting close to the leveling off point with the compression engine, but perhaps there is more magic to be found in there. Certainly if anyone can pull it off, Graeme can. But it seems to me that pipe is getting pretty full and we're venturing very close to the bursting point. Am I off base there?

[cinepost35]

I think we have figured out where we are today... but if we were ever to try to squeeze a bit more data rate out of the camera, we would likely have to deal with this again. But if that happens, we have a lot more experience finding the causes... :-)

Jim

But....if the RED team was able to squeeze one more frame out of 3K 16:9 Redcode 36 to get from 47fps to 48fps max that would be like getting a whole new camera again.

[Jannard]

But....if the RED team was able to squeeze one more frame out of 3K 16:9 Redcode 36 to get from 47fps to 48fps max that would be like getting a whole new camera again.

Give us a bit of time... we want this too.

Jim

[cinepost35]

Give us a bit of time... we want this too.

Jim

Thanks.... Have multiple REDS prepping for a big project that is chomping at the bit to possibly use that extra frame if it became available in the next 4-6 weeks.

Off coarse if RED where to have RAW ports we would be interested in those in a heartbeat also.

[Martin Preiss]

Expect the new build in a couple of days...

Jim

Couple is always 2 :-), Thanks Jim for the effort, hope we can update as soon as possible. It's nice to be backed up, and I can say to everyone on set, that our issue is being solved.

Just for my imagination, will be nice to see some photo from ordinary day in RED HQ :-). For memories from pioneer days (As Bros Lumiers has some as well, cos truly, you are truly a great-grandson of them, by what you do). Later when talking to grandkinds: "See this guys here on the photo, he was solving that issue, from that film I was talking about, miiiles away on other side of planet...and he solved it...such a nice folk"
:biggrin:

[Pawel Achtel]

Expect the new build in a couple of days...

Jim

Nice one, Jim. Your responsivness and willingness to listen do not stop to amaze me. This is more valuable than having the best camera on the market. You can offer both! Congratulations.

[Kjetil Haugen]

Very very good news. Thanks for the update and thank you very much for listening.

[Dave Neathery]

Jim,
I have never had the codec errors with either of my Reds, but I have had both of them stop due to what the software called sound errors. (B16 only).
Are these part of the codec errors you have brought up in this thread?

(I had a bunch of students from the local film school help me shoot the premier of that new musical this past weekend. They really loved getting to use the Reds and want another chance to use them. Not that you are hurting for customers, but I'm sure they will new dream of having their own Reds.)

Thanks,

Dave

[Mike Burke]

Expect the new build in a couple of days...

Jim

I have Build 16 v.3.1.2 installed now.
I have in my hand Build 16, v.3.1.5.
Is this the new build you are referring to?
Should we hold off installing 3.1.5? Thanks.

[Dexter Gregoire]

I have Build 16 v.3.1.2 installed now.
I have in my hand Build 16, v.3.1.5.
Is this the new build you are referring to?
Should we hold off installing 3.1.5? Thanks.

Yes, hold off on installing 3.1.5

3.1.2 was a lot cleaner IMO. Shot 5 and 1/2 hours. Only 1 codec error at the end of the day. I thought it was because of heat. We were sweating just standing there.

3.1.5 gave me error reports within 15 min. On playback and recording.

[Stuart English]

V 3.1.5 and v3.1.2 should be indentical in this respect, so a) no 3.1.5 is not the build Jim is referring to. and b) yes you can upgrade. Form 3.1.5 you can go back to 3.1.2 if you wish, so no risk.

[Stuart English]

If anyone is having codec errors or file errors of this sort, send us a P.M - to me or Deanan or Brent - and we'll get you to send us the .LOG file from the camera, that is the most useful diagnostic tool to understand what caused that issue in your system. You don't need the original media, the LOG file is stored in memory in the camera, so as long as the error was relatively recent it will be there.

[laguun]

If anyone is having codec errors or file errors of this sort, send us a P.M - to me or Deanan or Brent - and we'll get you to send us the .LOG file from the camera, that is the most useful diagnostic tool to understand what caused that issue in your system. You don't need the original media, the LOG file is stored in memory in the camera, so as long as the error was relatively recent it will be there.

Stuart, one of our cameras gets stuck in record with 3.1.5. (camera os reloaded, factory defaults) with c/f cards sometimes. ARe you interested in these .LOGs as well?

[Stuart English]

Stuart, one of our cameras gets stuck in record with 3.1.5. (camera os reloaded, factory defaults) with c/f cards sometimes. ARe you interested in these .LOGs as well?

Of course !

[Dexter Gregoire]

If anyone is having codec errors or file errors of this sort, send us a P.M - to me or Deanan or Brent - and we'll get you to send us the .LOG file from the camera, that is the most useful diagnostic tool to understand what caused that issue in your system. You don't need the original media, the LOG file is stored in memory in the camera, so as long as the error was relatively recent it will be there.

I have recently formated the hard drive after transfering the R3D's. Will the LOG file still show info? I'll prepare and email to you. Thanks.

[Steven-Marc C.]

Thank you Jim and Red team for being so reactive on this issue. I will be testing the new build. Once this has been sorted out, build 16 will be fantastic! RedSpace is proving to be really efficient during the shoot and time-saving in post.