Canon EOS R5 Unite and Discuss!

hrmmm...

Major issue with R5 during shoot.

On Friday I was taking graduation photos. My kit for the last three years has been the same, 5D4, 135mm, and wireless Godox AD200 through a nice softbox.

I do very well with that set up,. but I was very interested in eye focus for this, 100% people/portraits.

Instead of the 135mm, I opted for more flexibility and went with 70-200mm (Tamron G2 f/2.8)
This same lens I used recently for hundreds of photos in a dark theatre. During the theatre shoot, at one point the R5 locked up, AF went wacky, pulsating. I've had this happen once or twice before with other lenses as well, and powering down and back on solved it.

Friday this was happening every few minutes. I'd shoot one senior, fine, then into the next session, it would go nuts. Rebooting worked every time, but this was happening 1 out of 3 sessions. (each session is maybe 5-10 shots)

None of this happened when I tested the exact same rig at home before taking it out in the field for real work.

I'll have to do a lot of experimenting to try and figure out what aspect might have been the combo that induced this issue. I don't believe is is just the lens, as again, thousands of photos for the theater setting with only one hiccup. Maybe it was the Godox?

P.S. in looking at the images, (100% in focus! (Other than when the AF went whacky) This is why I wanted to try R5 vs. 5D4, 5D4 was always good to me, but I still got OOF images when distance changed etc, and AF did not update fast enough)

It appears the issue was in fact AF related. With similar consistency to my 1 out of 3 AF going whacky,. in reviewing the images I will have a series of perfectly focused images, and then suddenly one that is completely a blurry mess. Shutter speed and remains the same, flash fired, but the AF appears to be racked WAAAAAY out. It's doesn't look motion blurry, so I don;t think it's IS/IBIS related,. it looks just completely OOF. I think this is always the last image when the AF went kablooey.

If you ever used a taped T-Con on an old DSLR and gotten the "AF jitters", this is what it was like happening every 3rd student in the session.

I have a wedding photographer friend share the same issue with me. However in his case he was using RF70-200 2.8.

This is bizarre behaviour. I would have assumed that in your case the third party lens would be the culprit but he was using a native lens. It happened to him at two weddings already.

The electronics in modern cameras and lenses are using less and less power compared to systems available ten years ago. Lower voltages and smaller currents means that any external influence like radio frequency interference may influence these electronics more easily.... In studio and event shoots often RF triggers are used which emit radio signals right on top of the camera. I wonder if RFI may be the cause of throwing off focus or exposure. Personally I haven not experienced sudden OOF but at times totally off exposure on TTL flash shooting using a trigger.
RF interference is a growing problem: WiFi points and mobile phone access points everywhere ,,,, solar panels causing strong interference and disabling emergency communications.
We have gone a long way since only the neighbours could hear me (I am a licensed radio amateur) on their stereo system.

ironically, the problem had read about and was concerned about, inconsistent exposures with ETTL and Godox wireless, did not manifest itself at all. Exposure remained spot on throughout.

My friend had R5 since Day 1 and not many issues, but lately she said she had like 6 lockups in 1 day, and had to pull battery every time or something.... I wonder if the latest firmware is breaking things more so than before.

I've had random crashes as well, but I never have to pull the battery. I just re-press the shutter and it resets quick.
But this is very annoying, and I have ZERO idea why it will crash/when it will crash. Seems very random, unless it's related to overheating or something...

I've had it crash:

- Changing FF to Crop Mode in settings (doing nothing else)
- Crash during AI Servo, but not taking photos.
- Crash during AI Servo/Bursting at 20FPS.


So it's not even crashing when focusing/taking photos always, but sometimes just changing a setting??
This is definitely the most unstable camera I've ever used. I can go days/thousands of shots without crashing, but then suddenly get 3-5 in 10 min. or something. Just is so random...


Edit: With that said, I've had the 1DXIII crash as well, in Live View / Bursting at 20FPS as well..

I've had no issues post latest firmware updates. Even shot ~2k images mostly full burst surfer runs without locking up. Also did the same for baptisms, also post updates, no lock up.

I was shooting native EF glass with Canon R adapter, EF 70-200 mk 3, EF 100-400 mk 2 w/ 1.4 TC mk 3

Mainly in Silent 20FPS or Mechanical?

I never shoot mechanical, only silent 20fps.

Kickflipkid687 wrote in post #19247601
...


Edit: With that said, I've had the 1DXIII crash as well, in Live View / Bursting at 20FPS as well..

I had a lockup on 1DX3 here and there as well. But it was always a one off,. not like this last bout with the R5. I have yet to update any firmware, I'm on what came with it, whatever that may be. I guess I should try an update

P.S. this was likely the first time I was in single frame, mech shutter, (because of the strobes, no burst) but I was still in AI Servo.

I've had freezes i think with any firmware update. But more so in the latest one I feel like. Most recent one.

Had my very first temp warning on the 5 this weekend ( all stills, no video) . was hired to shoot a civil war re-enactment Saturday. Temp out side was a hot , humid, 95 degrees.. it was brutal.. everything was fine until I started shooting bursts to catch the canon fire.. then I noticed a thermometer icon in the top right corner… seemed to take longer to write to the cards, and the battery started to drain rapidly.. it never stopped working or shooting though.. I was just about done when all of this started.. so I packed up and left.

Never had this happen before , to be fair.. I’m a landscape guy.. so this is the first I’ve shot like this with this set up..

Here are a some shots from the shoot …

A couple more…..

CyberDyneSystems wrote in post #19247269
hrmmm...

Major issue with R5 during shoot.

I opted for more flexibility and went with 70-200mm (Tamron G2 f/2.8)
This same lens I used recently for hundreds of photos in a dark theatre. During the theatre shoot, at one point the R5 locked up, AF went wacky, pulsating. I've had this happen once or twice before with other lenses as well, and powering down and back on solved it.

I have the same setup including a Godox trigger. I've had the same AF issue at random. Unlocking and re-locking the lens and EF-R adapter was another method I tried. But this does creep up on me from time to time. I've had the same thing happen with a Sigma 150-600mm lens with no flash/trigger. It simply would not focus. Disconnecting and re-connecting the lens solved the issue.

strobe monkey wrote in post #19243587
Do you use "intermediate ISO's" on your R5 ? There was a discussion somewhere a long time ago that it's not good as it introduces more noise... thanks

Such discussion was based on cameras that had lots of noise added by the camera's signal chain after the initial analog gain that varies the ISO setting, combined with analog gains that were only for whole-stops, so the extra 1/3-stop ISOs were pushed or pulled mathematically, or in the case of a few Canons (including the R5), pushes with extra amplifiers just before the ADC. The fact that the R5 has one of the highest base ISO DRs among FF cameras points to the fact that the post-gain read noise is not very strong in the R5, so that it varies little from a consistent trend across the whole range of 1/3-stop ISOs. However, the R5 introduces a new "glitch" because the pre-gain read noise (the noise that occurs reading the actual photosite) drops by over a stop going from ISO 320 to 400, making the deep shadows of ISO 400 a bit better than 320, but that pattern does not repeat anywhere else in the ISO range. 50-320 is like one sensor, almost, and 400 and higher another sensor, because the capacitance of the photosites toggles between those two modes, giving the lower range higher full well capacity, and the higher range, lower read noise. The shadow noise at 320 is better than most older Canons, though, so it is not something that is going to casually give you more visible noise. You'd have to combine things like HTP (where the glitch occurs between 640 and 800), under-exposure, bad light coloration, and low-contrast subject matter to run into a problem, I think.