Thankfully I'm still at work, so I'll see if the internet explodes with any unwanted glitches from this in the next seven hours before I get home and download it.
ronno wrote:
Installed ok on mine - and it hasn't been pulled yet
Still up on the site, I'll take that as a win. And no searing threads in some other camera forums I occasionally peruse.
What's a little concerning is that I don't see anything in the patch notes about improved AF based on some of the reports people had in 1.0.3. I couldn't reliably tell if I was affected, my keeper rates between two R5ii (one at 1.0.2 and the other at 1.0.3) weren't substantially different to where I'd think 1.0.3 was less reliable (this was while shooting wildlife and BIF at long focal lengths).
I may just upgrade the one on 1.0.3 to 1.1.1 and see how it gets along for a little.bit before updating the second body.
Got the email from Canon today about the new 1.1.1 firmware so now it's global. I've used it with no issues. Another friend who's an avid birder and sports shooter confirmed it's just fine no issues at any time as well. No complaints on the focus system that's for sure. Perhaps they finally got it well worked out. I see no reason NOT to upgrade at this point.
Ok, we can set the number of frames in Pre-capture, but are we still locked to 30fps?
So, 15 pre-capture shots gives you a half-second of pre-capture. Five pre-capture shots only gives you 1/6th second of pre-capture. Ten pre-capture shots is good for 1/3 of a second.
Guess you have to be pretty fast on the button.
Alan Kefauver wrote:
Ok, we can set the number of frames in Pre-capture, but are we still locked to 30fps?
So, 15 pre-capture shots gives you a half-second of pre-capture. Five pre-capture shots only gives you 1/6th second of pre-capture. Ten pre-capture shots is good for 1/3 of a second.
Guess you have to be pretty fast on the button.
I don't think we were ever locked to 30 fps.
dj63401 wrote:
I don't think we were ever locked to 30 fps.
Manual says the camera can store up to 15 frames before the shutter is fully pressed, so if I set it to 5fps, it will capture 3 seconds worth?
I thought it was limited to capturing i/2 second, which means at 5fps it only captures 2.5 frames?
I use Procap on my OM-1 and it works quite differently, so trying to wrap my head around the Canon version.
Prior to this FW update the camera always shot up to 15 frames in precapture. If set to lower than 30 fps, it would stretch out precapture for up to 15 frames at that frame rate. But you could moderate this by how long the shutter release was half-pressed before fully pressing it to begin image capture. For example, if shooting at 5 fps and you only had the shutter release half-pressed for one second, you'd get about 5 precapture frames. But it was an imprecise method because you had to consciously control how long the shutter release was half-pressed.
I haven't installed this FW yet, but it appears you can now select a lower number of precapture frames than 15. My assumption is you will still only get that number of frames if the shutter release is half-pressed long enough to do so. Again using 5 fps as the example, if you set 10 frames as the cutoff, the shutter release would have to be half-pressed at least two seconds prior to fully pressing.
I wish Canon would update the interval timer someday to allow for up to 15fps or so, instead of the ancient 1fps maximum that it currently allows. This should not be hard to program into the software. This feature can make more profit for a single photographer with multiple cameras.
EBH
Thanks. Makes sense now. With the OM-1 you set the total frame count for Pre-cap and the apportion how many frames before and after. i.e. set frame count to 20 and assign 15 to pre-cap (half press) and 5 to after shutter full press.
A surprising summer sale and a fast kick of GAS got me now sitting here with a R52. Ooops!
As I have followed this thread I had decided to upgrade to 1.1.1 if my R52 had some older firmware installed. It had 1.0.3 and as it was rather late, I snapped a few flowers and bugs with the RF100 Makro. The AF was, as I think Jan Wegener described it, jumpy. But he also found that 1.1.1 took care of that problem. Now I have snapped a few flowers and bugs and a Sparrow hawk (Accipiter nisus) and I find the AF fast, accurate and jumpless. Compared to the R5 that I have used for the same flowers and bugs during the last few weeks, the R52 feels very responsive over all.
I also upgraded DPP and now EOS Utility on my Mac Mini M4 Pro. The responsiveness is the main observation with these too. And now the blocking high with its dreadful heat has gone east. So with fresh air in my lungs, I feel pretty, oh so pretty confident that the R52 is yet an other winner!
Customized menu options were expanded from what I recall in previous firmware. I probably missed some.
[Direct AF area selection] toggle between AF areas
[Drive mode] toggle between drive modes, eg. single, HS+, HS-, HS. Probably my favorite for movie button in stills mode.
[Direct select of sub to detect] click between people, animals, vehicles. Very nice.
[Spot detection]
[Register people priority]
[Action priority] on/off with people subject tracking
[Zoom tele]
[Zoom wide]
[One-touch image quality]
DOF button & back buttons - [Switch (ES) cont. shooting modes] Switches between low speed or high speed modes to high speed continuous when held down, this is going to save some time culling images. I wished a reverse of this feature were also available.
So far no real issues that I experienced in v1.03 with AF being inconsistent without using the power saving hack. Spot and single AF points seem better at holding AF instead of the random drifting at times.
