3 Things Gone or Downgraded on the R5 Mark 2 - EOS R5 Mark 2 Tip 3

New products don't always make everything better, sometimes they remove rarely used features or change things in a way that reduces a features capabilities or use.
While the R5 mark 2 makes a lot of progress in a lot of important areas, I quickly noticed 3 features that I used at least occasionally that had either disappeared or had be rendered less useful or less capable. This video covers those features, how I used them, and how to work around their loss on the new camera.
An honorable mention, that didn't get mentioned in the video goes to being able to shoot Canon Log 3 with Rec.709 color primaries. Though why you might want to do that and why loosing it may or may not matter is really a topic on it's own.
══════════════════════
💵 Support the Channel and Content Like This 💵
══════════════════════
⯈ Click the Thanks Button under the video.
⯈ Use PayPal: paypal.me/poin...
⯈ Buy yourself something from the affiliate links below.
⯈ Amazon.com: amzn.to/4dloDzU
══════════════════════
Gear I Use to Make Videos
══════════════════════
(Affiliate links)
⯈ Canon EOS R5 - amzn.to/3uJNNVI
⯈ Canon EOS R5 Mark II -
⯈ Canon EOS R5C - amzn.to/4goyveX
⯈ SmallRig NP-F Battery Adapter Pro (power for extended shooting time)- amzn.to/3ybCY3h
⯈ Anker Prime 27650 mAh Power Bank - amzn.to/4dsP8o4
⯈ Canon RF 15-35mm f/2.8L IS USM - amzn.to/37SuLDw
⯈ Canon RF 24-70mm f/2.8L IS USM - amzn.to/3M9I0yQ
⯈ Rode NTG2 -
⯈ Rode Wireless Go -
⯈ Zoom F6 - amzn.to/2TWsSvo
══════════════════════
Chapters
══════════════════════

[@TheOriginalGregToo]

Super excited to see your R5II coverage! Your channel is the only channel I have found that does such meticulous deep dives, and I absolutely love it. Thank you!

[@jacy123]

I used the IBIS High resolution 400mp option for shooting paintings that would be printed large. It was awesome. I would take a 400mp jpg and then take a 45mp raw and use the jpg for the line detail and then upscale the 45mp accordingly to match the 400mp and use it for the enhanced color data, then I’d combine them. I got some truly huge and sharp images that looked great. I did not upgrade for the reason that this feature is missing and that the new censor is noisier than the original censor in semi low light situations.

[@brucebrain1595]

That's the feature that came to my mind first when I saw the titel of this video. With regard to the sensor and cpu performance, it should be easy to implement this feature in the R5mII as well and it wouldn't have hurt. The AI upscaling might be an option for moving subjects but sometimes comes with strange artefacts as others have reported.

[@PointsInFocus]

The whole path, both the multi-shot super-res and AI up-scaling just frustrates and confuses me. I was really excited to see multi-shot super res coming to the R5 when it was announced, only to be really frustrated and aggravated by the implementation to the point of flat out dismissing it after testing it. Also, when push comes to shove, If I want to up-scale an image, I rather do it on my desktop/laptop where I have more control, more refined software, multiple models and more compute power to throw at the problem.

[@jacy123]

@@PointsInFocus I also would much rather use my high-powered computer for upscaling and AI implementation. As far as the high resolution shots, I thought a second iteration would have been great if they had given us tiff files which retained the full bit depth, I could see how it might be necessary to do a little bit of raw processing to mitigate some noise before stitching images but when it comes to the color bit death they could’ve easily made that work I think. Again, the high resolution images are so valuable to my work that there’s no way I’m getting rid of my original R5.

[@PointsInFocus]

Personally, I'd just be happy with them giving me a set of raw files to process in post and leaving it at that. What really annoyed me is that also computationally and programiatically the easiest thing to do too. But they apparently couldn't take the lazy route either. As far as I'm concerned, a camera is best when it's designed to be a tool for capturing images, not one for processing them. The time they spend on adding these kinds of post processing things, is just time that's being taken away from adding useful features for capturing images. I like to think that if you can afford a $4000+ camera and the associated lenses, you can probably afford a computer to process the images on, and you probably care enough about the quality of your images that you're going to want that kind of control anyway.

[@jacy123]

@ agreed! If the hi res ibis stitch was possible through DPP as a raw process, I’d be happy with that! I really wanted 14bit 400mp images for my clients.

[@darylhermann3792]

This is a really good video. I love how technical you are. Have you used a Nikon Z9 or Z8 and how do they compare features related to the R5ii. I want one of the two and they each seem to have different pros and cons.

[@PointsInFocus]

I've used a Z9 for all of about 15 or 20 minutes back when it was first released... So, I can't really talk intelligently about it. Even the little I remember as obvious differences with the R5 are things that probably don't apply anymore with the host of firmware updates that it's gotten.

[@darylhermann3792]

Ohh ok thanks for your honest feedback. One think I’ve noticed on the R5ii is they need to allow a user to assign the precapture ability to a custom menu button. Another thing I wish was that they made the R5ii similar to the r3 where the video/photo mode was a selector switch on the back and the left are where the video/photo mode is they should have added customizable buttons. Ohh and the front should have had 2 custom buttons like the R3 and R1 and every recent Nikon camera. I think the R5iv will sort all that out lol

[@PointsInFocus]

My first piece of advice would be if you've never used either the Z9 or R5/R5-2, rent them for a week (or weekend) and try them out extensively. There's a lot of nuance in the UIs that isn't obvious if you're handling the cameras. For example, you interact with the buttons differently on Canon and Nikon. On Canon, you generally push and release the button and then change the settings with the dials. On Nikon, you generally have to hold the button while turning the dials to change the setting. That impacts how buttons can be laid out. Canon tends to put more things around the grip side, since you don't have to contort your hand to hold a button and turn a dial. The exception being the R1/R3, where the buttons are spaced out more to make it easier to use the camera with heavy gloves (this is a design element that goes back to the EOS 1 film cameras FWIW). This also means that for most things you don't have to take your hand off the lens to change settings. On the other hand, since you have to hold the button while turning the dial, Nikon tends to put more buttons on the left side. But at the same time, that means you have to take your hand off the lens to change settings. This isn't to say that one appraoch is right or wrong. My experience is that some people map well to Nikon's UI and others don't. I don't. While i don't have any shutter time with the Z9, I played around a lot with Nikon gear in the D700 era when I was thinking about going that way, and I always felt like I was fighting with the camera. Sure I could probably get over that after enough time, but I'm not sure I want to put the time into re-wiring my brain to work that way either. I also have a personal problem with Nikon's grip. The low front dial position causes me to have to bend my wrist more when using a Nikon body. Due to childhood broken wrist, this eventually leads to irritation and pain in my right wrist. Canon's vertical dials lets me keep my wrist straight while still being able to access everything and without any long term problems. Point being, you don't really get a feel for that kind of stuff without spending some real time with the cameras. That said, my little time with the Z9 was generally favorable (except for the movie resolution/frame rate menu), and I'd love to have the budget to have one and a Sony A-something to on the shelf, but I don't have the budget for that.

[@darylhermann3792]

@@PointsInFocusthx that is great feedback!!! I too had a broken wrist. It’s interesting what you said about trying one out. I spoke to my camera store and they are actually going to let me test drive them.

[@MtnBikerNZ]

A drawback with the new remote is that you lose the ability to have images geotagged because the camera only seems to be capable of maintaining a single BT connection. Not a showstopper but an interruption to my workflow since I geotag everything. 😢 Now I have to capture a shot with the phone paired before using the remote then copy the location in post.

[@PointsInFocus]

Sadly, I gave up on geotagging when Canon decided to drop the GNSS chip from the R5 series. Not having tags at all is better than having tags that are off by often 10s of mils or more. Every time I've used it in the field, I've gotten stale locations unless I remember to open the app on my phone every time I go to use the camera. I don't think you're supposed to have to do that, but I've never had it work reliably otherwise.

[@JaredRibic]

I was really bummed when I couldn't do multiple exposure in raw on the R3.

[@MartinMonkDotCom]

Great video, thanks - as always. Is there any way to recover the Highlight stop in Dual Pixel RAW on the OG R5 within Canon's DPP software, or even within Lightroom?

[@PointsInFocus]

To the best of my knowledge, no. You need to use the DPRSplit from fastrawviewer.com. Lightroom ignores the second sub image completely, and as far as I know DPP only will do the official Canon DPRaw manipulations.

[@MartinMonkDotCom]

Anyone?

[@sebastianreiprich3747]

On my R5 II I noticed that the rear screen (not the EVF) stutters when I engage the AF and blackoutfree shooting is disabled. Not a major issue, but I hope they fix it in a firmware update. Most of the time I don‘t need blackoutfree shooting because when it is enabled it takes away the option to switch to EFCS or mechanical and to turn off exposure simulation which can sometimes be useful for me.

[@PointsInFocus]

I think that's actually due to the exposure & DoF simulation (which is forced on when you enable blackout free mode), and the resulting dimming that comes from being stopped down. I don't know if there's really a workaround that could be applied to fix that either. The camera needs a certain amount of signal to be able to do the AF work, and when the lens is stopped down that takes a dim environment and makes it considerably dimmer. Ultimatley, the camera needs a brighter image to focus on something dark and with limited contrast than you do to see that something is dark. The R5 would do the same thing, but since it always focused with the lens wide open, it had to be in a much dimmer before the LV shutter times had to be adjusted to maintain the brightness for the exposure sim. This is something I want to look into at some point. There's a clear threshold where the camera drops the frame rate even if it's not focusing, when Exp sim is enabled. Running one shot AF will drop it further at that point (or open the aperture while focusing), Servo AF doesn't seem to have quite the same problem or at least as much of one.

[@sebastianreiprich3747]

@ I have set up my Mark II in a way that it does not simulate the depth of field. So the lens only stops down when I actually take the image. The AF is set to servo mode and every time I half press the shutter button or press the AF-ON button the display skips a few frames. At the same time in the view finder everything is perfectly fine.

[@PointsInFocus]

That's.... Odd... You might want to also contact Canon support (CPS if you have it) about that. That it's doing it on the LCD but not the EVF sounds more like a bug than a feature to me.

[@sebastianreiprich3747]

@ I already did and they want to further evaluate the problem. I have a very short video on my channel that shows what I mean. One day after I made it I figured out that the blackoutfree shooting setting fixes the issue as long as it is turned on. I shared this information with the support as well and now I wait until I hear from them again.

[@CZOV]

I found a better solution for this, not buying R5M2.