ajay

After this firmware update, we've got a good indicator that Canon is not going to open this camera up for any serious video work. It's really meant for casual video work in which a hybrid shooter may want to get a few nice video clips. From a video perspective, there's no way would I use this camera for any serious, professional work. I've 100% made up my mind to stick with Sony for what I do. I thought I might go back to Canon and use the R5 for both my stills and video work but I've seen enough from Canon to know that they have not changed their tune. So...A9 for stills, A7SII

It would appear that way. Who wants to find out?

According to Gordon's communication with Canon, the R5 has three temperature sensors: (2) internal...near sensor/autofocus system? and (1) external ambient temperature. That still doesn't address the timer that's being employed. Doesn't make sense really. Could just be a bunch of BS from Canon.

So based on Gordon's tests, the new firmware takes into account external temperatures and recovers quicker when cooling is applied. I guess we're back on for the Tilta Cooling Kit. The good news is that now the firmware can be downloaded and hopefully Alex and others @ ML can start working on additional firmware to add functions to the crippled R5.

According to TechRadar, the firmware doesn't address the overheating and actually engages it when using an external monitor: "Canon has today released the EOS R5’s first firmware update and it’s available to download from the camera maker’s regional websites around the world. However, if you were expecting the firmware to improve on the current video limitations the R5 suffers from (as previous reports indicated it would), you’re going to be sorely disappointed. The EOS R5 firmware version 1.1.0 only brings a couple of minor upgrades – it improves image stabilization for video record

That would be great if this would work with CFast as well. Still a kludgy work-around for a $4k camera however. Good luck.

Congrats! So...This formatting "It" works meaning FAT32 formatting using Linux? Does this only work on SD chips, not CF Express? That's why no 8k raw nor 4k 120p? Please unconfuse me.

In other news, Canon's entire EOS R engineering staff have committed harakiri. Please see Canon's website for new job postings.

To summarize where things stand at present with trying to "fix" the R5 (correct me if I am wrong): Hardware Fix There really is no way to "fix" the camera from a hardware standpoint other than to power-cycle the internal button battery to reset the NV ram. All camera settings would be lost every time the R5 would be deep power-cycled. Fans/cooling devices wouldn't fix the timer. Firmware (Magic Lantern Style) Fix There's no way to analyze the firmware of the R5 until Canon releases a new version of the firmware as a file that can be downloaded. There might be a potential to add o

The question is will some of the heavy-hitters out on YT and the web sites will call Canon out on this? They should if they're not biased. It's nice to see most who have already started the drum beat are crediting Andrew as well as others. Well deserved.

The Canon rumor sites are buzzing about two new cinema cameras with the R-mount. That's probably why this camera has been crippled. What Canon should have done is marketed the R5 as a high-end stills camera for $3.5k with mediocre 4k modes and for a $500 upgrade that would include high-end video options. I think that would have gone over a lot better than the mess they have made. Lots of ill-will with Canon right now.

That would be great if there could be a work-around from Magic Lantern but the way ML works is by supplementing the existing firmware, not changing the existing firmware. Not that it isn't possible, but ML would have to create their own frame modes, codecs, etc. and it wouldn't be as easy as simply changing a timer option in the original code. Months and months (or more) of work. That said, if they could pull it off it would be an amazing camera.

I don't understand why you would go through all that work to reconstruct the file. Why not record what you want, then record another short, bogus file and kill the battery. Forget about trying to reconstruct the file and just create a dummy file that you don't care about.

Let's say you have 15 min to record. You record for 13 min. Then press record again and pull the battery (battery door sensor disengaged.) The last file is corrupted but that was just a dummy file. After reinserting the battery do you have a fresh 15 min. or does it remember the 13 min recording and you only have 2 min?

Good question. I certainly would never want to pull the battery right in the middle of a recording. That's an easy way to corrupt the memory chip. But that's what Marcus did. Not a good idea under normal circumstances but it does prove the point.

There are two contradictory reports on this. Can we get clarification? Andrew tried this and it didn't work but Marcus's video states it does work. ???????????????????????????????????

Let's say for the fun of it, Canon removes this goofy timer and you can record to the stated limits and not have to wait long to use all video modes if/when it overheats (really overheats). You now have a somewhat usable camera for video work. But wait, there's more... There's the other cripple hammer... Ridiculously hard to edit codecs. I get that 8k produces humongous files, but they certainly could have provided better codecs that are easier at editing for all other 4k modes. Without a doubt, this is a second cripple hammer with this camera. This is all very intentional.

Another way possibly to trick the R5 would be to install a dummy battery and power-cycle the camera using the dummy battery. Might this possibly reset the camera losing it's settings/memory? Something to try.

Possible work-around from removing the button battery? Horshack on the DP thread thinks that you can trick the camera by overriding the battery door switch and pulling out the battery. This prevents the camera from going into a normal shut-down and it loses its settings. Something to try Andrew? https://www.dpreview.com/forums/post/64283375

There once was a camera built on deceit Who's video features were said to be sweet. But amongst all the clamor, Came Canon's Cripple Hammer, And now we know it really doesn't overheat.

Another question, was the camera allowed to reach the ambient temperature of the fridge prior to powering on the camera? It would seem that the camera would need to be chilled for at least 2 hours before conducting the test. (The starting EXIF temperature reading should have been close to the temperature of the refridgerator prior to the start of the test.)

So...let me play the devil's advocate here and make sure nothing is being overlooked with Andrew's latest test: Do we know with absolute certainty that Canon is using the EXIF temperature data to determine when to shut down the camera? For example, what if there is a temperature sensor on the back of the sensor itself? That sensor is floating w/o a heat sink. It very well could overheat while the remainder of the camera stays warm but not hot. It appears wifi was enabled during the test. This typically generates more heat. Why did temperatures remain constant while wifi was opera

I believe it has the same tracking as the A9, A9II, A7RIV and the newer crop-sensor cameras. Touch-to-track a subject. (Using the touch screen.) I wish the end of September would get here.

I get that. But just like other Sony cameras using Clear Image Zoom, I would think (and hope) it will do some form of autofocus but w/o eye AF and no tracking.

Are you sure about this? I had heard that it disables eye and tracking AF, but didn't disable AF completely.