Jump to content

Cliff Totten

Members
  • Content Count

    273
  • Joined

  • Last visited

1 Follower

About Cliff Totten

  • Rank
    Active member

Recent Profile Visitors

4,256 profile views
  1. So....the sensor is not having any thermal problems in 5.9k. Actually, 5.9k is its normal readout mode. It does this all day long in full frame. The only way to stop its 5.9k read window is to switch to APS-C. So....it reads 5.9k with no heat problems or time limits. It image processes that 5.9k with no heat problems and scales it down to 4k for recording with no thermal problems or limits. It sends 5.9k raw to the HDMI unlimited with no heat problems. It continues all its 5.9k sensor readout, 5.9k processing and 5.9k raw output unlimited with no heat problems....even after
  2. No,...I'm saying the S1 does a 5.9k sensor readout, every day, all day long. 5.9k full width read window is it's normal every day scan. So, the "sensor" does 5.9k with no thermal problems. It always has from day one, even when saving 4k files, the sensor reads at 5.9k. The file saved is oversampled 4k from a 5.9k readout. The new firmware takes that same 5.9k sensor readout and instead of saving that file to 4k, it will now saves in to a 5.9k file and places a 15 min cap on it. The 5.9k readout, 5.9k image processing and 5.9k raw out to HDMI continues with no time limit or thermal is
  3. Clipping occurs when sensor photosites are saturated and can't collect any more photons. There is no "raw" on planet Earth that can "recover highlights" from a saturated photosite. The term "highlight recovery" that everybody throws around is not a real thing. You either clipped and saturated photosites on your sensor or you didnt. You either crossed that threshold or didnt. Neither Log video OR raw sensor data can save you from clipped sampling. Pure white....is always pure white. So is pure black. This goes for both log video and raw.
  4. So here's the deal.... The S1 can do: 1.) Unlimited 5.9k sensor readout all day long 24/7 with no thermal issues. 2.) Unlimited 5.9 image processing with no thermal issues 3.) Unlimited 5.9k raw over HDMI with no thermal issues....even continuing after the recorded file write 15min. time limit. 4.) The GH5 with it's same encoder chip can record unlimited open gate 19mp 6k video....with no thermal issues in a much smaller body. Does anybody else believe the S1 was capped at 5.9k internal recording to protect the S1H?
  5. I love the S-III....except for ONE thing. Sony spread the dual stage gain values WAY too far part. In SLog-2/3 have the "low" db set at 640 ISO and the "high" 0db at 12,800 ISO! This is crazy. That second stage preamp needs to be moved down to 4,000 ISO where the S1H and FX9 have it set. The S-III's ISO's on the first stage look TERRIBLE from 3200-12,800 because of this. I know why Sony dud this. The wanted the S-III to be the "low light king" for marketing reasons. So,...they sacrificed the lower gain amounts to collect higher performance on the extreme low light conditions. This was a
  6. Wonderful!...I'm betting Cannot programmers just read this article and went; "Oh shit....we gotta disable this hack on the next firmware" Cannot is not going to just sit by and watch it customers try to circumvent all their hard crippling work. Cannot marketing people want this stuff there for a reason. Enjoy the hacks while they last!
  7. I'm really curious to see what the market tolerance is today for contrast hunting AF. Years ago, Lumix had 10bit recording to high bit rate codecs. This gave them leverage over their competition and compelled buyers to tolerate contrast hunting AF. We never wanted "Depth From Defocus"...but we bought it anyway to get acces to the other features. Today?...that leverage has eroded. 10bit color and high bitrate codecs are now becoming standard issue on all the competition. Lumix's most valuable features are no longer exclusive and we no longer need to just "live with" contrast hunting
  8. Andrew - You know Cannot was hacked by a data ransom organization. If Cannot doesn't pay them...could you imagine these hackers releasing all the internal confidential emails from R5 developers and managers and Cine team and marketing execs? Could we see all the dirty back room plotting and planning on how they were going to sham their customers? Woah...that would be massively embarrassing for Cannot.
  9. At this point, now that we know what Cannot has done with the R5, why "exactly" are we all pissed off? 1.) Are we pissed because Cannot crippled the R5 to such ridiculas levels? Are we pissed because we think that protecting EOS Cine camcorders is a stupid idea? Are we pissed that Cannot just didnt let the R5 do everything it was truly capable of? 2.) Are we pissed that Cannot LIED to its customers by trying to make us believe that the cripples were not avoidable because of heat limitations? In other words....If Cannot just came out and said from day one; "Yes,...we have placed
  10. Look....Cannot has worked hard to cripple the R5 and limit it's ability to be used as a replacement for their Pro Cine models. I'll say it again, Cine EOS managers were in the R5 technical planning and devopment meetings from the beginning. Nobody wants the R5 to take $1 away from the Cine EOS model sales. Cannot is not afraid of bad press on the R5. What DOES terrify them are customers circumventing the R5 marketing control measures and making it go beyond Cannot's intentions. It's vital for the R5 to live in the carefully calculated market "box" that Cannot made it for. We can all
  11. Is modifying a product that belongs to you illeagle? How many things that we buy and then make changes to? People modify computers and electronic equipment every day. Could you imagine if Dell tried to sue you for modifying your laptop hardware? Could you imagine Ford suing you for modifying your engine...etc....etc. If you own it, it no longer belongs to the campany that made it. Its your thing and you can screw it up all you want.
  12. Andrew....do you know the "Magic Lantern" guys? Do you know how to contact or reach out to them? I would literally bet my life that they are very interested in this R5 mess. If you want to upset Cannot and REALLY ring their bell, get some dialog going with ML and REALLY start a fire here.... If Cannot has not yet encrypted their firmware, could you imagine ML reversing all these cripples in firmware? Maybe It could be just as easy as taking timer values in lines of code and replacing them with high values like "99999" or something of that sort. Cannot doesnt fear bad R5 pr
  13. If this R5 firmware is not encrypted carefully and this thing gets "cracked" and becomes virtually limitless? If everything that Cannot has done, every measure they have made to cripple it....is reversed? This will terrify Cannot management more than any negative press that the R5 can ever have. If the cap comes off the bottle and the genie escapes? The R5 will run wild in places that Cannot desperately does NOT want it to ever be used. Cannot has a very "specific" intention for the R5 and they have worked soooo hard to keep it inside that box. It absolutely must stay there. The
  14. Yes,...if the S1H did have phase detect AF, it WOULD be flawless. Too dangerous and that us why it won't ever have PDAF. The camera industry has a "pizza pie" of customers. They work together to divide the customer revenue so that each company has a "group" to live off of. Panasonic has its crowd, Sony has its people, Cannot and Fuji and Oly each have their own customers...for carefully calculated reasons. The Japaneese camera industry is an important one for the country of Japan. Its almost a "national pride" issue. They cherish it and the Japanese companies want each company to suc
  15. If I were Cannot, I'd pray to God that I have security measures in place in the R5 to block it from being firmware hacked by the Magic Lantern guys. If somebody can hack and unlock the R5 software?...customers would be left with one HELL of a nuclear bomb 8k monster beast camera that would TERRIFY Cannot's marketing execs and cine EOS managers. Yeah....you better pray the R5 does not get hacked.
×
×
  • Create New...