Problem tethering from my Canon R5 to Macbook Pro

I have the same problem. The Canon EOS R5 only connects sporadically to the MacBook Pro, whether M1 or M2. At most 10% of the time a connection is established at all. Overall, it is very difficult to connect either the ProGrade card reader or the camera to the computer. It doesn't matter which cables you use, whether it's the cables supplied by the respective manufacturer or the sinfully expensive Thunderbolt or USB 4.0 certified cables or Apple cables, you simply no longer have the feeling of being in control of your own system.

In the past with the Canon EOS 5D MK II this was no problem at all, it worked wonderfully whether with PC or MacBook and the cheapest USB-A cable worked. You had a display of the connected devices and the card was immediately visible in the Finder or Explorer, regardless of whether you used a card reader (which cost barely 15 dollars for a CF card at the time).

Just today, after the extremely expensive TeatherTool cables, I tested a fresh USB 4.0 cable from Anker (where at least the price is still right) my NVME hard disk is supported with full write speed, even if the login in the Finder is stubborn to say the least, a 100% stoic same reliable function is not that either.

In short it is frustrating 6.5 K$ MacBook + 5.5 K$ camera and it is simply dependent on chance whether something works or not one feels quite strange as a loyal customer.

An industry in markets at the limit of its native growth options simply seems no longer able or willing, or no longer tolerated by its shareholders, to offer functioning, reliable products. Or you have to be on some list of selected VIP customers in order to access functions that were previously taken for granted and without particularly in-depth know-how or hours of Google research through mountains of useless information that was only used to place new useless products.

It is no longer a problem that products turn into waste as they age. This path has been shortened and you now only get partially functional products for the money. My two MacBooks, despite having the best equipment, are as practical as a typewriter. They are great for consuming all kinds of media as a work tool - they are a great way to spend time in trouble. Appliance goes other!

But maybe I'm just too stupid and everything actually works wonderfully and without any problems.

I'll now send my camera to support to find out if there's something wrong with the camera USB port, but I'm sure everything is fine there. Why else would other USB devices also show unstable behavior and I have this phenomenon on several MacBooks of the latest generation. There were no such problems with my i7 2015!

I also got the WFT battery grip and although it is a little better than the camera's on-board WiFi for live view teathering, there is still a latency compared to a cable connection, especially at 15x magnification and manual When you focus, you simply no longer have a fluid working feeling.

As a next step, I'll try to simply use an external display that I connect directly to the camera via HDMI, but it's just not the same as using a workflow with teather shots.

And I will still test the Fuji GFX 100 II and if it works, Canon will be out.

But as I said, I find the USB-C behavior to be unstable and opaque for the user, and not just in connection with the Canon.

Poorly thought out operating system UX meets dysfunctional aspects of the hardware and crashing programs.

--> PC register does not match crashing frame (0x0 vs 0x10BBC4565)

Crashed Thread:        11  Dispatch queue: NSOperationQueue 0x7fd657941060 (QOS: UNSPECIFIED)

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)

Exception Codes:       KERN_INVALID_ADDRESS at 0xe000000000000120 -> 0x0000000000000120 (possible pointer authentication failure)

Exception Codes:       0x0000000000000001, 0xe000000000000120

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11

Terminating Process:   exc handler [51931]

VM Region Info: 0x120 is not in any region.  Bytes before following region: 140723034734304

REGION TYPE                   

START - END        

[ VSIZE] PRT/MAX SHRMOD  REGION DETAIL

UNUSED SPACE AT START

...

This isn't the kind of user experience I'm used to spending my money on and I don't know what it's like in Cupertino, but I'm still one of those miserable old-schoolers who have to work for their money and to cover their investments.

Experiencing the same. Canon R5 with most recent firmware. Macbook air M2 with updated drivers and software and OS. Can't connect via wifi after HOURS AND HOURS of searching for a solution. Tethering is impossible too!

My Nikon does the same thing. SD cards for cameras often have proprietary formatting or partitioning, unlike computer storage that have some cross-platform formats. Cards from some camera make don't mount like drives, and you need a "translator" function.

The image management software that came with your camera should translate but, if like Nikon's, may have a steep learning curve.

Thus I second VikingOSX's excellent suggestion to use Image Capture, already on your Mac. I do not have to remove the card from my Nikon to use Image Capture. I connect the camera to the computer with the cable Nikon furnished and launch Image Capture. The camera shows up in the IC sidebar.

Transfer images in Image Capture on Mac - Apple Support

Do you have a SD Card reader available for your Macbook Pro, as you may be able to access images via Apple's Image Capture. Using Canon's USB-C cables may be an issue. You should not install any Canon drivers into your Mac.

Canon indicates that if the camera is connected via WiFi, that it cannot communicate with the computer even if connected by a USB-C cable. p864 of the EOS R5 PDF manual.