Build 16 Codec Error killer...

[Jannard]

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

[Cüneyt Kaya]

bug erasing almost realtime...other companys should start to learn

[Jannard]

We are here to serve... :-)

Jim

[Jeff Kilgroe]

Thank you Jim and RED Team!

I will install & start testing tonight.

[Bruce Allen]

Well that's awesome...

Bruce Allen
www.boacinema.com

[A. Bastaki]

Thanks jim... will load my red up with that asap. thanks Team Red for all your effort.

-----------------

bug erasing almost realtime...other companys should start to learn

em.. what other companies?

[Jannard]

Add features, beta release, fix... add features, beta release, fix. :-)

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

Jim

[Damien Molineaux]

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

[Russ Campbell]

Thanks so much. Looking forward to testing this soon.

[Cüneyt Kaya]

Thanks jim... will load my red up with that asap. thanks Team Red for all your effort.

-----------------


em.. what other companies?

COLOR...hehe

[Leo Ticheli]

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

[Jannard]

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

Can you make direct contact with Jarred?

Jim

[Steve Freebairn]

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

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.

[Leo Ticheli]

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

Best regards,

Leo

[Joel Kaye]

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

Best regards,

Leo

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.

[Stuart English]

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.

[cinepost35]

Leo can you post a picture of your tree and composition for reference?

[cinepost35]

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?

[Leo Ticheli]

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

[Jannard]

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

[cinepost35]

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

Was just curious what the tree looks like that's all.

[Cory Schulthies]

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

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?

[Adrian Correia]

I'm glad too see you were making the most of that time away from the boards Jim. May I suggest you budget in some sleep? Thank you so much for the hard work Red Team!

[Greg M]

so far here so good! No codex errors. I'll go try one of our trees and see what happens...we have better looking trees in Louisiana :)

[Emery Wells]

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.

[Dj Joofa]

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.

[George A.]

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

[Greg M]

I was able to get codec errors by filling the frame with trees/shrubs...not somthing I typically shoot, but nonetheless easy to repeat the error.

[Jay A. Kelley]

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

Jim

God... That's funny.

:)

Jay

Way to go Leo, you managed to find the worst possible shot for RED.. This is a good thing as it will insure once that shot is licked. That should do it.

[Jannard]

We are sending Leo a new Build to torture... today. We encourage him to post his results.

Jim

[conrad gaunt]

bug erasing almost realtime...other companys should start to learn

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:

[Laco Zamba]

Patch :-)

IF InFrame (EvilTree) THEN NOT DisplayCodecError ()

[Ruairi Robinson]

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

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

[Dj Joofa]

Hi,

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



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.

[conrad gaunt]

Patch :-)

IF InFrame (EvilTree) THEN NOT DisplayCodecError ()


or

IF InFrame (Tree AND (NOT Made_of_Plastercine)) THEN DisplayCodecError('Codec Warning: Realistic tree detected, increasing data rate..')

[Antoine Baumann]

Does this new build address the "compression bug" (http://www.reduser.net/forum/showthread.php?t=15859) or only the codec errors?

thanks,
antoine.

[Michael "Dorkman" Scott]

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...
Totally what I was thinking. That thing gave me the chills.

[Matthew Bennett]

We are here to serve... :-)

Jim

create like a god,
command like a king,
work like a slave

[conrad gaunt]

Does this new build address the "compression bug" (http://www.reduser.net/forum/showthread.php?t=15859) or only the codec errors?

thanks,
antoine.

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

[Dj Joofa]

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.

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.

[Michael Stanmore]

If you were shooting anything prior to build 13 the tree would have come to life and eaten you...

[Adrian T.]

I'm glad that RED is addressing this CODEC error problem with such high priority and great effort. But being a software engineer myself I must say that I'm highly worried by this try-and-error approach. That's simply NOT the way to write reliable software!

I really hope that this is only an intermediate solution to the problem and that they're going back to the drawing board of scientific software design and theoretical proof of the algorithms in use. Yes, it's always possible to prove scientifically that algorithms work.

Keeping my fingers crossed...

[Paul Hazlett]

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

That tree looks my uncle Murray.

[Jannard]

I'm glad that RED is addressing this CODEC error problem with such high priority and great effort. But being a software engineer myself I must say that I'm highly worried by this try-and-error approach. That's simply NOT the way to write reliable software!

I really hope that this is only an intermediate solution to the problem and that they're going back to the drawing board of scientific software design and theoretical proof of the algorithms in use. Yes, it's always possible to prove scientifically that algorithms work.

Keeping my fingers crossed...

hehe... trial and error. Big L., you are sorta right. If we had done this project the "traditional and correct way", we would have shipped our 1st cameras out Spring 2112... maybe.

Jim

[Ed Blythe]

Can't we just get Leo a new tree? Seems like that would save a lot of trouble...

[Dj Joofa]

If we had done this project the "traditional and correct way", we would have shipped our 1st cameras out Spring 2112... maybe.


No, IMHO, "traditional and correct way" does not always take longer. There is no agreed upon definition of what is "traditional and correct." I don't see any reason that with the specs the camera that Red has developed a more robust camera would have taken about 2112 to come out.

[Jannard]

No, IMHO, "traditional and correct way" does not always take longer. There is no agreed upon definition of what is "traditional and correct." I don't see any reason that with the specs the camera that Red has developed a more robust camera would have taken about 2112 to come out.

Try building one of these yourself in two years from scratch... with all due respect. You assume quite a bit in your statement.

I have a new Canon 1Ds MKIII and 1D MKIII. There have already been several firmware updates to fix major problems for each of them. Canon has an army of engineers.

Jim

[Dj Joofa]

Try building one of these yourself in two years from scratch... with all due respect. You assume quite a bit in your statement.


I'm sorry if my statement has been seen as inflammatory. I respect Red's innovation a lot. It is not just a question of an army of engineers. A small company such as Red can indeed take on a big company with the right focus, and more importantly passion and dedication, which the Red's team appears to have.

On the reality side. We have indeed built a camera and a very powerful system to go with it from scratch in less than 2 years that in overall complexity is no less than Red (if not more).

I am just giving my honest feedback, more so from the experience we gathered in building such systems, and I apologize if it has hurt anybody's feelings.

I want to see Red succeed and that is why I offer my experiences on this forum as I do not want Red to make the same mistakes that we and others before us also made.

A wise person learns from his/her experience, a wiser person learns from others' experiences.

[Jannard]

I'm sorry if my statement has been seen as inflammatory. I respect Red's innovation a lot. It is not just a question of an army of engineers. A small company such as Red can indeed take on a big company with the right focus, and more importantly passion and dedication, which the Red's team appears to have.

On the reality side. We have indeed built a camera and a very powerful system to go with it from scratch in less than 2 years that in overall complexity is no less than Red (if not more).

I am just giving my honest feedback, more so from the experience we gathered in building such systems, and I apologize if it has hurt anybody's feelings.

I want to see Red succeed and that is why I offer my experiences on this forum as I do not want Red to make the same mistakes that we and others before us also made.

A wise person learns from his/her experience, a wiser person learns from others' experiences.

Want to come give us a hand? :-)

Jim

[Martin Preiss]

Want to come give us a hand? :-)

Jim

I do!

[Häakon]

hehe... trial and error. Big L., you are sorta right. If we had done this project the "traditional and correct way", we would have shipped our 1st cameras out Spring 2112... maybe.
There is absolutely no doubt in my mind that this is completely accurate. RED is taking an (extremely) radical path to product development, but you don't have to look hard to see it has been worth it. Sure, their approach has kicked up some dust and ruffled some feathers along the way (RED has had to deal with their share of the frustration just as much as the customers), but look where we are at. Jim has said from day one that you don't have to pick up your cameras until they were "done;" it looks like that took them about 9-10 months to accomplish. Given the size of their team and the age of their company, that's rather remarkable I reckon. And in that time, many of us have still had a camera to play with, rough edges or not. We knew we would have to deal with some problems here and there but the bottom line is we've been making beautiful 4K images from a $20K camera and there just plain isn't any other camera that comes close.

I scrutinize RED a lot because a company of this caliber needs to be held to the highest standards and told straight up what needs to be worked on so that they can make the best camera possible. And maybe I've been a thorn in Jim's side at times, but guess what - all of the feedback on this website has helped them to test, tweak, and fix those problems faster than it could be possible any other way. The reason you won't see a 4K camera from the "other guys" until Spring 2012 is because no one else is willing to have an open product development cycle like RED. And by then, RED will be on their third generation chip which I'm sure will be another industry killer. I read so much flack about fanboy-this and overhype-that on other forums or mailing lists that seem to want to tear RED apart for being different, but however you want to slice it, they're the ones making it happen.

It sounds like the latest build has some nice stability improvements and I'm very much looking forward to the release candidate. Don't slow down this pace, RED... the pieces are coming together and it only gets more exciting to shoot with the camera every day.

[Josué Ignacio Saldaña]

A wise person learns from his/her experience, a wiser person learns from others' experiences.

However, there is a difference between self-gratifying "wisdom" (speaking from life experience and not to you personally) and the type of wisdom that has been in motion from RED in its truly noble cause. Even if "history" ever tries to prove otherwise, it is evident in this day and time that what RED is doing is for those who are alive and able... which is probably the reason why the hopes of many are lifted by RED and not by some probable super-duper camera out there... get the diff'?

[Fredrik Callinggard]

Well I have some good news!!!!

I was able to recreate my green screen shoot today.

Tungsten green screen. 4K, 16:9, 23.976fps, varispeed 30fps. Lights in frame etc.

With the old 16 build I got codec error literally within 2 seconds!

With build 3.1.6 and .8 NOTHING! It was ticking like clockwork no matter how much I tried to abuse it!!!

So that's a few % of the 99. Just wanted to throw that into the mix.

So it's off for a new green screen shoot for me hahahaha.

PS I have e-mailed Stuart the logs.


Fredrik Callinggard

[Jannard]

Well I have some good news!!!!

Fredrik Callinggard

I love good news! And I hope we can deliver a build that puts "codec error" to rest forever... in a few days.

Jim

[Josué Ignacio Saldaña]

but however you want to slice it, they're the ones making it happen.

While everyone else talks about:

"If it were me, I would..."
or
"I am in development of..."
or
"One day I'll show..."

Though it isn't correct to discredit anyone's "wisdom" for we don't know what they are capable of or how they are going to help shape the future... it isn't fair either to discredit a company for taking their own capital and broaden the entire standard to include those not able by the "traditional means." RED isn't just making some type of new "product," they are helping so many of us change the way we believe that things could be done... and that is dangerous in the eyes of some, because now their projected profit margins have been completely changed.

[Pawel Achtel]

hehe... trial and error. Big L., you are sorta right. If we had done this project the "traditional and correct way", we would have shipped our 1st cameras out Spring 2112... maybe.

Jim

Not necessarily, Jim. There are ways where producing reliable software is actually cheaper and faster, but this does not work for most software companies out there because it does not give them repeat revenue stream.

Here, it is different. The approach needed would be "bug prevention" instead of "bug detection" (a.k.a. testing). It may sound strange, but the most reliable software is actually not tested, it is only verified. The development process is focused on preventing bugs to start with and it is substantially different than what is commonly adapted in software industry.

Anyway, with 20+ years of experience, I'd be happy to assist as much as I can. PM me.

[Fredrik Callinggard]

I love good news! And I hope we can deliver a build that puts "codec error" to rest forever... in a few days.

Jim

Well the real good news is this build. Codec errors aside, the images are amazing. I can't be more happy about the noise. I've never been so happy about noise before hahahahaha. It's sooooo beautiful.

I'm not saying that the camera has a high noise level, I'm saying that the noise level it has now is so film like that it doesn't matter. Now we can work with the noise, the very very little of it that the cam produces.

So thanx :gun:


Fredrik

[Eirik Tyrihjel]

I am so happy this camera actually reports "Codec error" at all, what if it just pretended everything was fine and you wind up finding out when it´s too late...

With this new bugfix I will upgrade my camera to build 16 at the next opportunity.

[KETCH ROSSi]

Try building one of these yourself in two years from scratch... with all due respect. You assume quite a bit in your statement.

I have a new Canon 1Ds MKIII and 1D MKIII. There have already been several firmware updates to fix major problems for each of them. Canon has an army of engineers.

Jim

It is great news on the Build 16 as I'm very near a shoot!


And Jim, please don't remind me of what I had to go true with my 1D III and the time (MONTHS) that tucked the Engineers at Canon to even admit of the Codec error which was causing AL SERVO Focus problems, which I sold out of desperation, but at list now my new 1Ds III is finally working well.


And yes any one that complains about the matter in which RED handles this codec errors, they must know nothing about how other BIGGER companies deal with this issues on Release builds.


Thanks again to the RED Team for the outstanding job that they continue to do!


ciao

[Pawel Achtel]

It is great news on the Build 16 as I'm very near a shoot!


And Jim, please don't remind me of what I had to go true with my 1D III and the time (MONTHS) that tucked the Engineers at Canon to even admit of the Codec error which was causing AL SERVO Focus problems, which I sold out of desperation, but at list now my new 1Ds III is finally working well.

And yes any one that complains about the matter in which RED handles this codec errors, they must know nothing about how other BIGGER companies deal with this issues on Release builds.

Thanks again to the RED Team for the outstanding job that they continue to do!

ciao

Yes, I fully agree. Red is much more pro-active and opened than any relevant company I know of.

[amrrahmy]

if i'm allowed to help, and reconstructed the codec to a much better error free one.
would i get a cookie, or a new epic for free?

[Pawel Achtel]

if i'm allowed to help, and reconstructed the codec to a much better error free one.
would i get a cookie, or a new epic for free?

You will get a cookie.

[Jonas Nyström]

Is it possible to go directly from 3.1.5 to 3.1.8?

[amrrahmy]

You will get a cookie.
:greedy:

[Radoslav Karapetkov]

You will get a cookie...


...of EPIC proportions. :tongue:

[Leo Ticheli]

I just tried the build Jarred sent and it is much more resistant to codec errors; only received one in a series of shots which would have immediately knocked 3.1.8 over.

Unfortunately, I can't check them frame by frame because the test build cannot open in post.

That's it for today; back at it in the morning.

Best regards,

Leo

[Erik Bien]

if i'm allowed to help, and reconstructed the codec to a much better error free one.
would i get a cookie, or a new epic for free?

Wow, that sounds really time consuming. You should definitely do it.

[Daniel Reichenbach]

Will shoot a LOT of detailed fields, flowers in the millions and so in a few hours: will see, if the new codec will be happy with it, thanks RED team for your great work.

[amrrahmy]

Wow, that sounds really time consuming. You should definitely do it.

r u putting ur red on the line, or smoking...

[Jeff Coatney]

I don't think its a software problem. Its very clear that Leo's tree is possessed and I think he should call an exorcist. At the very least a voodoo spell of protection written in chicken blood, for heaven's sake. ;)

[Mike Prevette]

On a slightly on topic note. Can I PLEASE have the ability of turning the "CODEC ERROR" warning off on the HDSDI and HDMI outputs? I'd much rather keep any issues in the camera DEPT until I see fit to provide a solution and till the client/producers. My client should never have to see something so ominous.

[Jannard]

I just tried the build Jarred sent and it is much more resistant to codec errors; only received one in a series of shots which would have immediately knocked 3.1.8 over.

Unfortunately, I can't check them frame by frame because the test build cannot open in post.

That's it for today; back at it in the morning.

Best regards,

Leo

Leo... thanks for the testing. What we sent you is better than we have posted, and what we send next will be better still. This situation has the full attention of our team.

Jim

[Jannard]

On a slightly on topic note. Can I PLEASE have the ability of turning the "CODEC ERROR" warning off on the HDSDI and HDMI outputs? I'd much rather keep any issues in the camera DEPT until I see fit to provide a solution and till the client/producers. My client should never have to see something so ominous.

We prefer to fix the problem instead of hide it... both will take the same amount of time. :-) We are almost there.

Jim

[Mike Prevette]

I'm not speaking philosophically I think you guys are doing an incredible thing and welcome any and all improvements. I just want to keep it "in the family" so to speak with the camera dept. It's my responsibility as the DP and before I announce any issues to a producer I need a solution. The only way I can get that is if I have the information first. So My request still stands but I'll re word it.

May I please have the option to keep all mission critical warnings [battery, codec, self destruct] to selected outputs?

p.s. I'm getting ready to head out the door with a 16mm lens and some bright t11 light to see If I can break this darn 3.1.8.

[Eirik Tyrihjel]

Am I missing something or is build 15 v2.2.8 (required to get to build 16 - and afaik not included with the latest build 16 package) at this time abscent from the support page? (if I am right, anoyne who didn´t download the first beta 16 isn+t going to be able to get to the second one... or anyone thereafter)

Luckily I had it on file, since I downloaded it a few days ago, but had to get it from my other mac, since I couldn´t find it at REDs website.

(upgrading to beta 16 as we speak...)

[Paul Moss]

just looked into upgrading now and can't find Build 15 2.2.8 were is it how do i proceed without it......??
Paul

[Eryc Tramonn]

Try building one of these yourself in two years from scratch... with all due respect. You assume quite a bit in your statement.

I have a new Canon 1Ds MKIII and 1D MKIII. There have already been several firmware updates to fix major problems for each of them. Canon has an army of engineers.

Jim

You guys are killin' me. Stop already. How about this...can someone tell me when a reliable, affordable and compact moco unit will be available for the RED/Scarlet. Something that directly interfaces with all existing OSX 3D capable apps too. :)

That's something to argue about.

[cinepost35]

RED TEAM have a log file to send where would you like it sent or what thread?

[Eryc Tramonn]

Want to come give us a hand? :-)

Jim

If he's worth his salt...take him up on it Jim. Hell, I'll come sweep up if it means Scarlet's production schedule can happen sooner.

[number6]

Add features, beta release, fix... add features, beta release, fix. :-)

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

Jim

Check's in the mail.

[Thom Steinhoff]

...Canon has an army of engineers.

Maybe they could dedicate a small platoon to give us a hand with a Canon EF mount? ;)

[Mike Prevette]

edit: nevermind

[Jannard]

Maybe they could dedicate a small platoon to give us a hand with a Canon EF mount? ;)

We were contacted by another accessory company that has had one in development for awhile... looks like there may be options coming.

Jim

[KETCH ROSSi]

We were contacted by another accessory company that has had one in development for awhile... looks like there may be options coming.

Jim

I see my EF 200mm f/2L IS on a RED with a working IS system working sooner then later. looks like, and there is nothing better then good competition to make a good product even better.


BTW. if any one needs this lens to try it on RED, SHOUT, offer off course includes the RED team. Not that Jim is unlikely to already have his own in is 500 lens arsenal.:)


ciao

[Joel Kaye]

We were contacted by another accessory company that has had one in development for awhile... looks like there may be options coming.

Full electronic control? Any time frame available?

[REDFEAT]

RED TEAM have a log file to send where would you like it sent or what thread?

Same question, where do we send/upload log files associated with codec errors in this most recent build?

[Jannard]

Same question, where do we send/upload log files associated with codec errors in this most recent build?

deanan@red.com

... although I would wait until we post the next build that has further improvements. Leo has given us a lot of feedback. :-)

Jim

[Brent J. Craig]

On a slightly on topic note. Can I PLEASE have the ability of turning the "CODEC ERROR" warning off on the HDSDI and HDMI outputs? I'd much rather keep any issues in the camera DEPT until I see fit to provide a solution and till the client/producers. My client should never have to see something so ominous.

I completely agree and second this request.

It does nothing but hurt the reputation of the Red camera to have non-technical clients spread the word that they "Used that new Red camera and we kept getting huge errors all day!" They may simply be 'card full' errors, but to the non-technical money people they are big red X's surrounded by dollar signs!

There is no need for anything so scary looking to flash on the client's monitors!

[Brent@RED]

just looked into upgrading now and can't find Build 15 2.2.8 were is it how do i proceed without it......??
Paul

Build 15 v2.2.8 has been added to the Build 16 v3.1.8 download as a separate folder within the download. My apologies for that oversight....

BC

[Steven Caesare]

I'm glad that RED is addressing this CODEC error problem with such high priority and great effort. But being a software engineer myself I must say that I'm highly worried by this try-and-error approach. That's simply NOT the way to write reliable software!

I really hope that this is only an intermediate solution to the problem and that they're going back to the drawing board of scientific software design and theoretical proof of the algorithms in use. Yes, it's always possible to prove scientifically that algorithms work.

Keeping my fingers crossed...

Indeed.

However, where the rubber meets the road is that there often must be compromises within the constraints within the rest of the system. Consider that the RED One:

- Must process even the most pathological of complex test frames in 1/30th of a second or faster in order to be ready for the next frame
-Has a limited power budget
-Has a finite gate/MIPS budget
-Has a thermal envelope target
-etc..

So while it may be possible to mathematically verify that a test frame of entirely random noise in each channel will successfully compress without error, it may require 1/10th of a second to do so. Or it may need 3X the CPU. Or significantly more power.

The end result is that if you design the system, for the worst possible case, you may end up with a camera that's twice as large, runs 3 times as hot, has 1/2 the battery life, and uses only 30% of the CPU capacity 99% of the time, but when maxed out 1% of the time is deterministic in every conceivable worst-case scenario.

Or... you can attempt to tune and make some compromises (perhaps being willing to slide image Q in pathological cases), but those are often "soft" decisions that require some estimation and iteration to get just right.

[Dj Joofa]

Want to come give us a hand? :-)


I fear that Graeme Nattress will fail me in the interview with his trick deBayering questions. :)

[Paul Leeming]

So I'm reporting from set today that build 3.1.5 gave me a codec error on a high contrast white backdrop in a studio setting. Having downloaded build 3.1.8 this morning before the job I told the client we had a new version that should fix the problem. Lo and behold, after the upgrade, no more codec error! Client was VERY impressed and the footage being shot is great.

I hope Leo can get the team over the last hump, but for me 3.1.8 in the studio is 100% as of right now. Awesome work Red Team!

Cheers from the front line!

Paul :)

[Thor Wixom]

I tried and tried to kick 3.1.8's arse!

I could not break the codec.

I aimed it at trees, shrubs, flowers... I found the highest contrast and most detailed scenes that I could! I even did whip pans until the drive dropped frames because of g-force... but no codec errors!

I shot everything at 23.98, 2k 120 to the drive, 2k 100 to the CF cards, 4k 16:9 and 4k 2:1, 3k overcranked... all the while going back and forth between RedCode 28 and 36. If it was a "legal" setting with 23.98 frame rate, I shot it! (Except anamorphic.)

So, I am happy to report that for me 3.1.8 was rock solid!

-Thor

[Jarred Land]

Glad to hear Thor...

I must say it is nice to have an army of you guys out there helping us test this stuff... with your help and the fearless pack of RED engineers, we have improved things even further since this mornings build... stay tuned :)

[Bruce Allen]

Scaesare, personally I think Joofa, Big L, Pawel, etc are all right - you can build an efficient bug-free codec. I think Red will prove it beautifully when they do their firmware 16 release build.



So while it may be possible to mathematically verify that a test frame of entirely random noise in each channel will successfully compress without error, it may require 1/10th of a second to do so. Or it may need 3X the CPU. Or significantly more power.

I disagree that an algorithm that successfully compresses in all cases would put onerous burdens on the CPU. I am defining success as "compresses any image without crashing" not "compresses any image without losing image quality".

I think the reverse is true - it is *substantially* easier to optimize a crash-proof algorithm for speed than optimize a buggy algorithm - eg you never know if it's your new optimization that's screwing things up, or if it's the old crash rearing its head again. That slows you down a lot.

Also, if you have a function that crashes - and don't know why - then it means you don't understand precisely what is going on. It's difficult to optimize something if you don't know what it's doing exactly.



Or... you can attempt to tune and make some compromises (perhaps being willing to slide image Q in pathological cases), but those are often "soft" decisions that require some estimation and iteration to get just right.

That's what 99% of lossy compression algorithms do. They slide image quality in all cases. Pathological can look badly-compressed, but never crash out.

Anyway, no need to argue, I guess. I'm confident Red will prove that it is do-able by squashing the codec bugs.

They have made it very clear that they're prioritizing it, so I say thank you again to Red for communicating this and wish them lots of sleep.

Bruce Allen
www.boacinema.com

[Thor Wixom]

Glad to hear Thor...

I must say it is nice to have an army of you guys out there helping us test this stuff... with your help and the fearless pack of RED engineers, we have improved things even further since this mornings build... stay tuned :)

I've got a few more challenges to throw at 3.1.8 tomorrow. I'll check for a new build before I shoot, in case one gets released.

Seems like we're close to a clean bill of health! I'm really excited, Jarred. Thanks for the reply.

-Thor

[Mike Prevette]

WOW that was hard. I just tortured the crap out of 3.1.8, I finally won and it cracked. But one burp out of 80 torture shots aint so bad.

I shot 4k 2:1, 4k 16x9, 3k 16x9, 2k 16x9, Redcode28, Redcode36, Varispeed, etc All on cards.

16mm standard speed at t11. Sun, trees, sand, grass.

It finally cracked on me after pointing it at some sand and beach grass. BUT (very big but) after the camera cut, I hit record again and everything was fine. I'll email logs when I get a sec.

[Jannard]

As we said... we are 99% there (or in Mike P's case 98.75%)... and we have a better build coming. Thanks to all for torture testing this build. I hope everyone is getting more comfortable that codec errors are soon to be a thing of the past. They have bugged all of us long enough.

Jim

[Miltos Pilalitos]

Thanks Jim,

Good to know codec errors will be a thing of the past. Does the fix cover the compression bugs as well?

[Jannard]

Thanks Jim,

Good to know codec errors will be a thing of the past. Does the fix cover the compression bugs as well?

I haven't heard of any compression bugs left in Build 16... did I miss something?

Jim

[Fredrik Callinggard]

I haven't heard of any compression bugs left in Build 16... did I miss something?

Jim

Unfortunately yes. Some people have been experiencing odd frames that's been blurred out. At least I think that's what he's referring to.


Fredrik

[Miltos Pilalitos]

At least I think that's what he's referring to.

Yes, that's correct...

[Mike Prevette]

The frame that busted it (the JPG makes it look blurrier than it is):
4k 16x9, R28, CF, 23.98

http://www.freedomfromgravity.com/red/A004_C006_0707CC_0388.jpg

[Jarred Land]

The odd frame issue we has been almost completely resolved as well.. the codec errors just took front seat the last couple days.

[Casey Green]

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%.
Jim

Jim,

Just wanted to add that I've seen codec errors on other capture devices before and one of the things that notoriously sets them off quite a bit are action sequences with quick, bright explosions. Add some steadicam movement and its a good test subject.

When we were on G.I. Joe, this happened on a few takes where the Video Assist operator was trying to troubleshoot it - I forget the capture system, but I strongly recommend trying at least a couple of these types of shots during your tests.

Hope this helps,

[Thor Wixom]

Any blurred frame compression errors, though?

markp,

I haven't loaded the shots into Redcine yet.

I'll have one of my guys look for anomolies tomorrow.

It's a little more difficult for me in B16 since I'm one of those PC guys. :whistling:

I'll see if there's anything that pops out in Redcine playback, but from the sound of it Red is aware of the problem and fixing it.

-Thor

[Jarred Land]

one of the things that notoriously sets them off quite a bit are action sequences with quick, bright explosions.


Casey, Did you just give me an excuse to start blowing things up at work?

Woohoo!!! thanks man...

[Christian Edwards]

Casey, Did you just give me an excuse to start blowing things up at work?

Woohoo!!! thanks man...

i know of some Sony products that would make the perfect candidate

[Thor Wixom]

Jarred,

I did a shoot recently where my client mixed two chemicals with gasoline, then shot the mixture with a gun. (teehee)

Maybe I could find out what they did and PM you the formula?

-Thor

[Casey Green]

Casey, Did you just give me an excuse to start blowing things up at work?

Woohoo!!! thanks man...

You know it!

4K Pyro! Make us all proud!!!

http://www.reduser.net/forum/uploaded/971_1215585575.jpg

[Jannard]

You know it!

4K Pyro! Make us all proud!!!

Don't encourage him... we have spent shells laying all over the place.

Jim

[Casey Green]

Heheheh.

I wouldn't do that... plus, it's not like anyone might have any left over 4th of July fireworks stashed anywhere, right? ;)

[Mike Prevette]

www.tannerite.com

[Corrado Silveri]

Great reading guys... But it's time to go and try the new build.
I've experienced some codec error with sea and waves, yesterday.
I'm going to check with the same scenario.

[Jarred Land]

Jarred,

I did a shoot recently where my client mixed two chemicals with gasoline, then shot the mixture with a gun. (teehee)

Maybe I could find out what they did and PM you the formula?

-Thor

yes please :)

[Martijn Lembeck]

Just installed 3.1.8. and am happy to see no more codec errors up til now.
But.... Trying to adjust the date has resulted in crashing the camera everytime it reboots itself. It just hangs forever at initialising.....

Idea's anyone?

[Gunleik Groven]

I'm so close to jumping the gun, now.

Next week I'll be shooting a lot in the woods, though. Would love to use the new build...

RC/RL/RA working estimate?

Crimson (have to work in two weeks, if I am to jump ship)

Any ideas?

Gunleik

[Axel Mertes]

Casey, Did you just give me an excuse to start blowing things up at work?

Woohoo!!! thanks man...

Jarred,

don't care about Jim's words, you are big enough, aren't you :)

We did some pyro stuff with build 13 in the past, it was a lot of fun (mostly for that Berlin Bunker project Cold Storage). Explosions come along way better in tunnels, long small rooms etc.

That being said, have fun! :innocent:

I'd love to see new pictures from inside RED office, especially when you do THIS experiments.

For the sake of making build 16 rock solid you have to take some hurdles :weight_lift: ...

Axel

PS: Wo gehobelt wird, da fallen Späne...

[Stuart English]

Just installed 3.1.8. and am happy to see no more codec errors up til now. But.... Trying to adjust the date has resulted in crashing the camera everytime it reboots itself. It just hangs forever at initialising....
Idea's anyone?


First I would disconnect the power source, i.e remove the LEMO connector, wait 10 seconds, re-connect and try again.

If no joy, I'd then disconnect the RED-EVF, RED-LCD or any other items conneted to the camera.

If neither of those work, contact RED technical support.

[Martijn Lembeck]

Thanx for your quick reply Stuart. After having the RED powered down for a while it repaired itself and a the first try it accepted time&date again.

[Bing Bailey]

sounds like the nanoredbots did their healing work

[Jay A. Kelley]

Sounds like the RED army has been hard at work stepping on these bugs.

Congradulations to all.

Jay

[Thor Wixom]

www.tannerite.com


yes please :)

Yep, Mike Prevette nailed it.

Tannerite.

Good times.

-Thor

[Greg M]

On location shooting a national spot and having codec errors with 3.1.8
shooting mural on brick wall

Will post log and image at lunch

[Warren Kommers]

Had a few codec errors and busted frames last night with 3.1.8. 4k RC28 2:1 3fps CF Sending in log file now.

The busted frames scare me the most of course because you don't know they are happening. The jpeg compression is really bad in these samples but you can see the difference between the two. Imagine the one on the right is the usual pristine RED image.

[Miltos Pilalitos]

Imagine the one on the right is the usual pristine RED image.

I tried hard to see the problem but i saw it. However i believe that maybe posting some 1:1 crops instead of oversampled scaled frames would demonstrate the issue more clearly. Thanks for the samples.

Miltos

[Greg M]

problem shot

[David Mullen ASC]

What am I looking for in this photo?

[Miltos Pilalitos]

I am with David on this. What seems to be the problem Digital FX?

[jbeale]

problem shot

I gather that particular frame is ok, just an example of the scene which triggered a codec error with Red.

[Bruce Allen]

David, that photo is a clean shot of the subject matter that cased the error. Eg high luma detail... I don't think it contains the actual error in that frame.

Actually I think it would be far funnier if you made the codec error so it only happened when certain actors appeared in front of the camera.

Ideally we could upload pictures of people the producers pressure us to cast, but we hate. When they step in front of the camera test the Red would recognize them and bug out, so we can just say "whoops, bud, you cause codec errors. Camera doesn't like you, sorry!"

Bruce Allen
www.boacinema.com

[Miltos Pilalitos]

haha that was funny!

[Steffen Kienzle]

I got also a Codec Fault with an evil tree in germany. With 3.1.8.
I went out today to test 3.1.8 on a situation we had many codec errors with build 15. A little sea near the black forrest.
Now with Build 16 no codec fault while shooting the sea. Yeah.
But the I turned the camera to a tree. we have very windy weather here in germany at the moment. so the leaves moved very quickly. and so the Red created again with bild 16 3.1.8 a CODEC FAULT.
The interesting thing in the test was: after codec fault I pushed again record and this time, same situtation, same frame, same t-stop. No Codec-Fault.
In Build 15 if we had one codec fault the hole scene couldnt be recorderd, with build 16 you have another chance the Codec will capture it. Thats my conclusion.
I am unhappy that I am one of these 1% with still Codec Fault but I still love my camera and I know the guys from Red will fix it and I just love to shoot such amazing pictures.

Here the specs of this shoot:
Build 16 3.1.8
4K 16:9
25f
100 ASA
5600Kelvin
1/50 Shutter

I will send jarred the log file now.

Thanks Red-Team for the great work and the great 4K tool you gave us and go on for the Full 100% Stable Solid Rock RED ONE!!!

[Steffen Kienzle]

http://www.moviemovement.de/EVIL_TREE_in_germany.jpg

[Thor Wixom]

Steven,

Which lens was that?

-Thor

[Greg M]

What am I looking for in this photo?
'sorry, on location...this scene produced a dozen codec errors, see previous post
4k
16:9
RC36
23.98
B16 3.1.8

log file sent

[David Mullen ASC]

Would you guys have gotten the same errors if you had used 2:1 instead of 16:9?

Truth is that I just shot a feature on Build 15 in 4K 2:1 and never got a codec error.

[Steffen Kienzle]

Hi Thor,
it was the 18-50mm zoom @18mm

The Fault appeared the first time on t-stop 4. The next time it worked. Then I changed to T-stop 8 and it appeared again. after pushing record again it worked.... and so on

And i forgot to tell:
Redcode 36 to Red-Drive

Would love to have here in the community sth. like a manual for codec errors.
In which situations they appeared and how you can avoid them best.
In Build 15 our conclusion was to shoot everything in 4K 2:1 and then no Codec Error appeared. But now in 16 I think its a little more different and you cant give a usable option. (Always shoot 2:1 or sth.)
steven

[Thor Wixom]

yes please :)

Jarred,

I just PMed you a link to tannerite in action. :gun:

-Thor

[C.H.Haskell]

Beating up on the new build in real time with no errors. Nothing bad to report here. :)

[Greg M]

Would you guys have gotten the same errors if you had used 2:1 instead of 16:9?

Truth is that I just shot a feature on Build 15 in 4K 2:1 and never got a codec error.

not sure, but for commercials 16:9 is preferred. Its an option in camera so it should work regardless.

btw- so far this is the only trouble scene today.

[Steffen Kienzle]

Hi David,
to be honest I havent got the time today to test the same situation with the tree with 4K 2:1. I will try it tomorrow.
As I told in Build 15 we had like you the experience that with 4K 2:1 no codec error appeared. I hope it´s in Build 16 the same but I will try the tree tomorrow with 4K 2:1.
steven

[roryhinds]

16:9 has been problematic from the start.
I think RED is a 2:1 camera.

[Stuart English]

16:9 has been problematic from the start.
I think RED is a 2:1 camera.

There is no doubt that 4K 16:9 has been and remains the greatest challenge, but one we are getting closer to resolving with each Beta version of Build 16.

[Jens Jakob Thorsen]

Are all these reports of errors really just reports about this last 1%?
Just kidding, I know you people at RED are all working to get rid of this ASAP.
I am(was?) a 35mm guy, but I abosultely love my RED @ build16 and hope to see a rock solid build soon. Counting on shooting my next feature on RED.
Keep on trucking.

Best
JJ

[I Bloom]

Admittedly I haven't read this entire thread.

For the sake of feedback, I had the older version of 16 yesterday shooting a scene with shining seawater and I could barely get through the scene because of faults. We installed the update (3.1.8) this morning and to my surprise I got a codec error immediately, and had about three more over the course of the day. I have trouble putting my finger on what was in the image to cause this, the shots seemed more or less normal to me with proper exposure.

Loving build 16. Keep up the good work. But I'm more or less desperate for a fix.

Warmth and respect,
IBloom

[Steve Sherrick]

Shot lots of trees and such with build 3.1.2 and didn't have the errors. Tried to bust it. Here are some examples. Maybe not exactly the kind of shots that are busting it.

http://www.reduser.net/forum/uploaded/161_1215661257.jpg
http://www.reduser.net/forum/uploaded/161_1215661281.jpg
http://www.reduser.net/forum/uploaded/161_1215661308.jpg
http://www.reduser.net/forum/uploaded/161_1215661535.jpg

[Tai Wah Lim]

Admittedly I haven't read this entire thread.

For the sake of feedback, I had the older version of 16 yesterday shooting a scene with shining seawater and I could barely get through the scene because of faults. We installed the update (3.1.8) this morning and to my surprise I got a codec error immediately, and had about three more over the course of the day. I have trouble putting my finger on what was in the image to cause this, the shots seemed more or less normal to me with proper exposure.

Loving build 16. Keep up the good work. But I'm more or less desperate for a fix.

Warmth and respect,
IBloom

Ibloom, what aspect ratio did you shoot at - 4K 16:9? Lim

[Jannard]

It is difficult to break, but you can do it... which is why no one is sleeping around here.

Jim

[Thor Wixom]

It is difficult to break, but you can do it... which is why no one is sleeping around here.

Jim

I went out to break it today, and I broke it.

Put the camera at 100 ASA. Not the best setting for outdoor / high contrast scenes, but this is what Steve did:

Look at this page: http://www.reduser.net/forum/showthread.php?t=16054&page=14

Go to post 133 and 134.

So, I did the same thing. Broke it first try.

Then I went to ASA 320 and severly over exposed it, which is exactly what shooting outdoors at ASA 100 effectively is.

Broke it again.

I was also shooting trees, leaves, bright sky, etc.

I'm trying to upload my log files, but I'm having trouble with my internet. I'll get them over to Stuart as quicly as I can.

-Thor

[Thor Wixom]

Update,

I got the log file to Stuart.

-Thor

[Gunleik Groven]

So... the moral is still: Green with lots of details and some over/underexposure still add mud or codec error?
If I'm going out to shoot in the woods I should do what?

[Jason Sinclair]

test .

[Gunleik Groven]

http://www.reduser.net/forum/search.php?searchid=1392082

LOL

Just as an offtopic sidecomment: Put my HVX up for sale exactly one hour after touching the RED for the first time. I knew I'd never open it again.

It's a nice cam and made me a good living, but to compare the two in any image-qualitydiscussion is quite... amusing.

[Jay A. Kelley]

For those that do not know.. Leo just posted in another thread that RED has defeated his evil tree. No more Codec errors.

Jay

[Warren Kommers]

For those that do not know.. Leo just posted in another thread that RED has defeated his evil tree. No more Codec errors.

Jay

What about those badly compressed frames that you don't know about until later? Any news there?

[Pawel Achtel]

For those that do not know.. Leo just posted in another thread that RED has defeated his evil tree. No more Codec errors.

Jay

He didn't chop the tree down, did he?

[Jarred Land]

new build coming in a matter of minutes... With new REDCINE, RED Alert!, Quicktime Component and something else special ( REDrushes )

Codec Errors should be a thing of the past now... we will let you guys confirm that.

[Shawn Bannon]

Very Exciting. Thank You

[Zach Hilton]

REDrushes...oooo....you've peaked my interest!

[Jeff Kilgroe]

REDrushes... :matrix: New build... I'll try to break it. Hope I can't.

Thank you RED Team for all the bug killing efforts!

[Jannard]

REDrushes... :matrix: New build... I'll try to break it. Hope I can't.

Thank you RED Team for all the bug killing efforts!

If you can break it... we'll fix it. We still have some more room to improve the code. :-)

Jim

[Emmanuel Cambier]

RedRushes, I can't select the "scale" option.

It seems nice though.

Emmanuel

[Steve Sherrick]

Two words - Thank You!

Look forward to trying it out. Great work guys.

Steve

[Deanan]

RedRushes, I can't select the "scale" option.

Are you on Tiger?

[Thom Steinhoff]

RedRushes, I can't select the "scale" option.

It seems nice though.

Emmanuel

That seemed a little bit of a problem. Couldn't select it right away, either. But clicked around a few times, then clicked back and then it worked. Maybe a timing thing, or an order of operation thing. Didn't spend a lot of time figuring out the pattern--I was too anxious to see all of the processors spinning!

I'm on Leopard.

Very cool app, though!

[Deanan]

I see the problem now. Try clicking towards the upper part of the check box. I'll be able to fix it easily.

[I Bloom]

I've been shooting 4K 16:9.

IBloom

[Jochen Schmidt-Hambrock]

Are you on Tiger?



I'm on Leopard.


Mind your grammar. It´s "Are you on a tiger?" and "No, I am on a leopard."

Tss..

;-)

[Joe Vinson]

Mind your grammar. It´s "Are you on a tiger?" and "No, I am on a leopard."

Tss..

;-)

Exactly. Kinda like "ich bin ein Berliner," right? :)

[Tai Wah Lim]

I've been shooting 4K 16:9.

IBloom

Thanks Ibloom. Have you tried on the new B16 3.2.1? Lim

[dominik(hamburg)]

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
hello,

when the release build is expected?
best- dominik

[dominik(hamburg)]

When the release 16 is expected?

best dominik