My smartphone auto restarts when it freezes. I'm not sure why Canon can't do a auto restart, then use the last settings, until they figure out what the real reason for the frezzing issues on the R6/R5/R3, it would save time and frustration not having to do a battery pull and missing shots. But I know nothing about software/firmware development so I'm not sure if that can be done.they probably just need better programmers. Canon is a camera company i cant see the software being that complicated compared to cellphone tech. the issue seems like a simple fix.
Canon recommends resetting the camera to default settings (via the menu) *before* performing firmware updates. Existing settings can be saved to a memory card and then re-applied after the updates. They also recommend that the lens is removed prior to updates. I suspect that many people don't do either.I guess it's the reset to factory settings ?
Yes indeed. It would be a very good idea if all manufacturers incorporated a menu option to return the camera to the original v1 firmware. Then user could simply download whichever update they preferred (assuming all versions were continually available on the manufacturer websites).My smartphone auto restarts when it freezes. I'm not sure why Canon can't do a auto restart, then use the last settings, until they figure out what the real reason for the frezzing issues on the R6/R5/R3, it would save time and frustration not having to do a battery pull and missing shots. But I know nothing about software/firmware development so I'm not sure if that can be done.
Back in 2012 Canon sent out a product advisory for the EF200mm f/2L IS USM and EF800mm f/5.6L IS USM Lenses when used with the 5D3.I take a wait and see approach when updating a camera that hasn’t been giving me any issues.
Interestingly I can’t seem to be able to activate the 240 fps FHD. The high frame rate option is still 119.9 for me?Canon USA has the new firmware version 1.2.1 up on their site.
Everything is the same, except for adding the fix to 1.2.0 for the camera reset bug.
Canon Support for EOS R3 | Canon U.S.A., Inc.
Find support for your Canon EOS R3. Browse the recommended drivers, downloads, and manuals to make sure your product contains the most up-to-date software.www.usa.canon.com
Edit: found it, not the greatest implementation. You can only select the 240 once 120 is selected and you navigate the Q button in shooting mode to select a sub menu to access the 240.Interestingly I can’t seem to be able to activate the 240 fps FHD. The high frame rate option is still 119.9 for me?
And this folks is what happens when cameras become heavily dependent on computing, the increase in functionality comes at the cost of an increase in complexity....
As I always keep reminding people, there is always a cost for everything. The personal choice is if you're happy with the tradeoffs.
In every industry. Automotive, transportation, Air Traffic, Defense, aerospace. Firmware and software updates and revisions are common place. Errors in these updates are also common place. Rollbacks and recovery modes pretty common. Often many vital systems are redundant, thus updates and revisions are most often completed on an offline or secondary system first. The customer or end user most often never see these common occurances.And this folks is what happens when cameras become heavily dependent on computing, the increase in functionality comes at the cost of an increase in complexity. Along with this comes an increasing number of variables that are difficult to account for whenever changes and updates are made. Without a proper testing environment and time to carry out exhaustive tests, the consumers/end-users become the beta testers.
Now just like your personal computer, cameras can have software (firmware) bugs, and they also freeze up and require power disconnection (battery removal) to get them running again. As more computing functionality gets added, expect much more of this. Anyone who has ever worked in the IT industry will tell you this is a immutable aspect of computing technology.
As I always keep reminding people, there is always a cost for everything. The personal choice is if you're happy with the tradeoffs.
Excellent points.In every industry. Automotive, transportation, Air Traffic, Defense, aerospace. Firmware and software updates and revisions are common place. Errors in these updates are also common place. Rollbacks and recovery modes pretty common. Often many vital systems are redundant, thus updates and revisions are most often completed on an offline or secondary system first. The customer or end user most often never see these common occurances.
Photographers who use a pro camera like the R3 are not beta testers. They can't put an event, like a wedding, on hold saying "I've got a problem with the camera, wait while I reset it, oh damn I've got a bigger problem, please wait while I get an older firmware version and downgrade".And this folks is what happens when cameras become heavily dependent on computing, the increase in functionality comes at the cost of an increase in complexity. Along with this comes an increasing number of variables that are difficult to account for whenever changes and updates are made. Without a proper testing environment and time to carry out exhaustive tests, the consumers/end-users become the beta testers.
Now just like your personal computer, cameras can have software (firmware) bugs, and they also freeze up and require power disconnection (battery removal) to get them running again. As more computing functionality gets added, expect much more of this. Anyone who has ever worked in the IT industry will tell you this is a immutable aspect of computing technology.
As I always keep reminding people, there is always a cost for everything. The personal choice is if you're happy with the tradeoffs.
Yes I am still seeing ads and it is very annoying.Sporadically yes - but see the comments on the Pro Board thread about the latest ...
They're busy making great new lenses for all the other companies who aren't intentionally cutting them out of their market.WHERE IS SIGMA?????????
.....After they remove the function to shoot 50 frames at a195 fps in the update, maybe I can sell bootlegged copies of the firmware since to those who do not mind a few bugs in trade for insane fps.
Do you actually own a R3....or just an R7 owner trolling?After they remove the function to shoot 50 frames at a195 fps in the update, maybe I can sell bootlegged copies of the firmware since to those who do not mind a few bugs in trade for insane fps.
I actually own one. Why are you trolling?.....
Do you actually own a R3....or just an R7 owner trolling?
That's precisely how its done in my experience. Computer system changes are strictly controlled, they're tested on an offline or secondary test-bed platform, often using human testing as well as automated software packages to check all the standard operations and functions that can be performed. There are thorough check lists of things that need to be covered, verified and approved before system changes go live, and there's always a rollback plan in case anything goes wrong. As you said, most of it is never seen by the end users because systems engineer, system testers and change management people make it all seamless, so as not to disrupt critical operations.In every industry. Automotive, transportation, Air Traffic, Defense, aerospace. Firmware and software updates and revisions are common place. Errors in these updates are also common place. Rollbacks and recovery modes pretty common. Often many vital systems are redundant, thus updates and revisions are most often completed on an offline or secondary system first. The customer or end user most often never see these common occurrences.