C300: New Cinema EOS Firmware is now available

So Who are the official sensors of this board? I just posted something and now its gone, as well as the two posts prior to mine. I mean, really....
 
Well, this is why I am never first to upgrade anything. The C300 firmware upgrade obviously has a problem and now you need to go back to the last firmware according to Canon. I think I will wait upgrading my C100 as well.
 
Something is not right with the C300 firmware. Pulled. Thankfully I didn't do it while I'm in the middle of a production. You know the rule.
 
I mentioned this on another thread, but I did update and then go on a shoot. I had no issues. I am looking at the C300 Clog footage now and all seems fine. Color seems ok, no odd fringing. I didn't shoot in Wide DR so maybe that's what is off? In any case, I don't see any major issues.
 
I'm just a lowly C100 owner, so I don't have firsthand experience with the C300 firmware, but isn't it just a difference in the EF and PL cameras? I guess if they're reporting that it's a slightly different image in the EF than the PL, then one of them is worse? better? I wonder if it's just Canon being perfectionists or if it's a visible difference.
 
I'm not sure that's what they are saying; they are saying both cameras have an issue matching color.... to what I'm not sure. I have read reports of Wide DR being the issue but I don't ever use that so maybe that's why I don't notice an issue. My C100 also seems fine. I shot both for many, many hours and they match up (in C-log) as expected compared to the previous firmware. Unless I am going color blind, I just don't see any issue.
 
When brewing one's own Custom Picture profile on the C300, it seems there was a case of matrix drift - a bit like mismatched power curves between gears on a high performance engine. Going from 2900K to 3200K to 4500K to 5800K, the colour would drift a bit. So, many C300 Custom Picture pilots produced two versions of each profile - one for Tungsten, one for Daylight. Then - IIRC - there was a software update that went a long way to correct this.

However, it seems like the new update has used the older version of the firmware's colour temperature matrix curves rather than the new one.

All just conjecture, speculation, etc - but having been embedded in the software development community for some time, 'it's the kind of thing that happens'.
 
Any first hand experiences with Brian’s profiles before and after the firmware update on the C100? Did the color science change and make the profiles act different?
 
Any first hand experiences with Brian’s profiles before and after the firmware update on the C100? Did the color science change and make the profiles act different?

A little off track, as this is C300:

Checking in from Cadiz, Spain... I downloaded the new C300 firmware last week before leaving for this project. Using Brian's LOG709 with great results - don't have time for my beloved log modes on this one. Heard the raves about his 709 profile and it is new to me as well as the firmware, but so far so good. If there is a classic ****** I'm not seeing it here.

And the upgraded ISOs are making me very happy. Any time one gets beyond a reasonable iso it's just about getting a printable shot, or not at all. This update has saved me in concert with the new Sigma 18-35mm.
 
I use Brian's profiles on my C100 too and after the firmware all was ok, no significant changes I could see. I cut a whole piece with it as B-cam to a C300 with the adjusted FW (and Brian's C-log profile) just fine. Of course I don't have Brian's eye for color, but it looks fine to me.
 
So Who are the official sensors of this board? I just posted something and now its gone, as well as the two posts prior to mine. I mean, really....

You sure that was this thread? Nothing has been removed from this one. A little info for you. We generally don’t remove any posts without discussing it with the poster unless its abusive to another forum member or the like.
 
I'll take you at your word. I had posted a comment that was non offensive and it suddenly disappeared so it seemed like a possible censorship issue.
 
Back
Top