I could but I won’t. H265 and soon to be h266 are part of the heat problem
I use it to compress ripped Blu-Rays.
Upvote
0
I could but I won’t. H265 and soon to be h266 are part of the heat problem
Is there a firmware for R6 as well with similar fixes/addons or only R5? Also, can anyone explain to me what is Cinema RAW light? I am a noob but eager to learn more. Just recently learned bRAW is Black Magic Raw )
Has B&H already shipped all their day one preorders of R5?When the R5 was released it was a “number one” seller on BH websites... after the cripple debacle it’s since been reduced to just “top seller” status.
They likely are based on SW, but I've not seen any statistical analysis on how much / well hardware implementations help...I could but I won’t. H265 and soon to be h266 are part of the heat problem
Yep, I think to offer what they decided to offer required a lot of design / trade-offs / component iterations till they got to where they are with the R5/R6.Hmm, so it appears Canon's internal recording is a bit ahead of the dedicated external recorders, even with its limitations. I imagine the folks building external recorders won't be rolling them out until they solve the overheating issues so you can have unlimited recording. It will be interesting to see how long that takes and what measures they have to take.
I don't expect any firmware update to fix the heat limits on the R5. Everyone is talking about this like it needs a “fix”. I think this stems from some of the theories floating around that the camera is not getting hot. However, reports are that the cards are getting hot.
Has anyone considered that releasing the camera with these limits is not an oversight? There is no way that Canons testing missed the overheat and recovery times. Think about the camera in the lab; they record some video to run a test. Then do a little more. They would have seen the reduced recovery times on day one of testing. This would have been reported up the line and then a management decision made.
I don't buy the argument it is to trick anyone into buying more expensive gear. The full-time full-length production filmmaker is not banking on an 80/20 hybrid camera replacing their cinema cameras.
So my theory is that The limits are there to protect hardware around the cards. Those limits are there intentionally. To me, it seems like they made a trade-off between using high-speed cards to accommodate high frame rate stills, and recording / cool downtimes. As a stills camera that would have been fine.
They reasoned that a wedding pro/documentarian/editorial pro/long-form journo/ hybrid portrait 5-series shooter, who has to turn around a bucket load of editing is not going to want to deal with HOURS of hi-res footage. Not to mention terabytes of video data from shooting 8k or oversampled 4K all damn day. Companies who do that have entire production lines with tons of gear and don't bank on a mirrorless DSLR to be the primary workhorse!
I think the Big C reasoned that the 8k video primarily would be used sparingly to compliment an 80% stills 5-series shooter.
But then, on a different floor, someone in the marketeering team, working to a different beat and living in a social media-driven bubble, or worse still, a state of delusion, decided to go hell for leather on spruiking the 8k video, and the rest is history.
The Engineers ran for cover. And here we are.
I don't expect any firmware update to fix the heat limits on the R5. Everyone is talking about this like it needs a “fix”. I think this stems from some of the theories floating around that the camera is not getting hot. However, reports are that the cards are getting hot.
Has anyone considered that releasing the camera with these limits is not an oversight?
If the CFexpress is the problem, why the CFexpress card does not overheat when shooting in 4K 30p non HQ mode? I shot for hours in this mode to both CF and SD cards without an issue. Both HQ and non HQ modes got the same bit rate as per the manual.
Besides, both the CFexpress and SD cards return to room temperature in a matter of minutes. The camera, however, doesn't seem to be affected; it doesn't care even if I inserted a new, unused card. It won't work.
I believe that this theory is misleading.
"We simply did this by ignoring the laws of physics"..."Fixed a bug where the camera overheated. The camera now records for unlimited time in all video modes. We apologise for the inconvenience this has caused for video creators wanting to utilise the camera to its full potential."
They need to focus on the website... its ridiculous that the website is down for more than a week and they dont care
Never seen a website down for so long on current digital world for even smaller companies... dont know if we can trust them when they cant even take care of their own website
Let's hope this will kill all the talk about overheating once and for all.
What exactly do they need to do to get it back up?
I give up, I tried to upload some images I took today, my 1st attempt at using the R5 & high FPS on our trainee guide dog free running. Apparently the image is too large for the server, it's only about 21mb so not massive. I dont want to reduce the size as it defeats the object. Anyone know how to upload larger files?
Anywhooo, I was pleased with the results, at F2.8, 2000sec, ISO 200 , 70mm using the RF 70-200mm, the eyes were pin sharp and this is a black Labrador with very dark, almost black eyes. I tried this with the R and couldn't get any images in focus. Result!!
They likely are based on SW, but I've not seen any statistical analysis on how much / well hardware implementations help...
Since the R5 supports h264 and h265, then it would be interesting to know why some modes are h264 which is cheaper in effort than h265 (and still supports 10bit and 4:2:2). h265 creates smaller files for the same quality, thus lower i/o and provide improved capacity, but I'd love to know if the higher i/o from h264 is offset by the lower encode effort / cost.