topic Re: (In)compatibility of EOS Utility with MacOS Ventura in Camera Software

(In)compatibility of EOS Utility with MacOS Ventura

Stefan1 — Thu, 27 Oct 2022 08:19:43 GMT

I updated last night to MacOS Ventura. Unfortunately, the EOS Utility does not seem to be compatible with the latest version of MacOS. Because of this, I cannot connect with my Canon EOS R6. This is quite disastrous for me, since I use my R6 amongst others as a webcam. Why? In my profession and role, presentation matters a lot.

When will this be resolved? Why is Canon seemingly incapable of keeping their software up-to-date?

De facto, the almost brand-new camera is now not useable anymore.

Re: (In)compatibility of EOS Utility with MacOS Ventura

SteveStone — Thu, 27 Oct 2022 11:01:21 GMT

My issue is with the R7, before the upgrade it would connect to the iMac Monterey via USB cable, as well as wifi. After the upgrade to Ventura the EOS Utility doesn't launch automatically, manual start displays the connect via WiFi, no option to select USB. Speed of Wifi connection is so slow, that makes it practically unusable.

Re: (In)compatibility of EOS Utility with MacOS Ventura

Stefan1 — Thu, 27 Oct 2022 14:51:35 GMT

same here. Without the USB cable connection, it practically does not work. Beyond, the connection is unstable.

Re: (In)compatibility of EOS Utility with MacOS Ventura

shadowsports — Thu, 27 Oct 2022 15:25:25 GMT

Greetings,

There are so many other options for transferring photos from your camera. Ventura has been available for 3 days. Canon is NOT the only vendor who hasn't released updated software for a new OS. I'm sure updated software and applications are coming. Please be patient.

Re: (In)compatibility of EOS Utility with MacOS Ventura

TediM50M2 — Thu, 27 Oct 2022 17:30:07 GMT

Hi,

I've the same issues of EU not connecting my M50 mk2 when I upgraded my Mac mini 2020 to Ventura. Although it does connect using the WiFi method but as others mentioned it is slow. Until Canon updates their software, my current workaround is to use Apple's Mac app: Image Capture. It recognizes my M50 camera when I plug in using USB and I'm able to download (and delete) my files. It also maintains all the Exif meta data so when I open the files with DPP, all the information is there. Hope this helps for now.

Re: (In)compatibility of EOS Utility with MacOS Ventura

tgerz — Thu, 27 Oct 2022 18:09:19 GMT

The OP is referring to the EOS Webcam Utility. While I wish Canon was ready to go for this day one I have a feeling that this free utility is low-ish priority for them. It makes it really nice and easy to setup a professional camera to use with a lot of video services with no extra hardware.

Re: (In)compatibility of EOS Utility with MacOS Ventura

tgerz — Thu, 27 Oct 2022 18:10:22 GMT

This is related to the webcam utility that Canon offers for free. I wish they were ready to go day one for Ventura, but I suspect it is a low priority.

Re: (In)compatibility of EOS Utility with MacOS Ventura

Stefan1 — Fri, 28 Oct 2022 13:47:54 GMT

I am well aware of other methods to transfer photos. But this is NOT my point.

There is - to my knowledge - so single good alternative to use the camera as a video-conferencing camera.

Since this is the tool I rely on in my daily work, the camera is now pretty much useless for this core scenario. We are now working with an iPhone.

Do you know any alternatives for connecting as a webcam that really work (and Wifi does not work properly)

Re: (In)compatibility of EOS Utility with MacOS Ventura

Stefan1 — Fri, 28 Oct 2022 13:49:54 GMT

Image capture does not solve the critical scenario to use the camera for video-conferencing. We are now working with an iPhone: Ventura allows to connect to an iPhone and use it as a webcam. Obviously that is a poor alternative - basically Canon has just killed itself.

Do you know any alternatives for connecting as a webcam that really work (and Wifi does not work properly)

Re: (In)compatibility of EOS Utility with MacOS Ventura

Stefan1 — Fri, 28 Oct 2022 13:51:28 GMT

Indeed Ventura is only there for 3 days. But developers have had access to Ventura for at least 6 months. There is no excuse for that. The hardware is now unusable in a critical scenario that it is advertised for.

Re: (In)compatibility of EOS Utility with MacOS Ventura

shadowsports — Fri, 28 Oct 2022 14:43:53 GMT

Yes. Unfortunately, the threads title didn't say that.

(In)compatibility of EOS Utility with MacOS Ventura

Re: (In)compatibility of EOS Utility with MacOS Ventura

shadowsports — Fri, 28 Oct 2022 15:33:18 GMT

This is nothing new. It happens every time Apple releases a new OS. Camera's stop connecting, printer's stop printing, and webcams stop running. We all know this. It happens over and over. A conservative approach might be to test or wait.

Software development. "Canon should have had this working on day 1". Maybe they did, maybe Apple added a feature or changed something that broke the WebCam Utility? We don't know, so its unfair to blame a vendor who doesn't control what Apple releases.

It's ok to be an early adopter, but you need to accept that some stuff may not work or that some software and/or devices might have issues. No vendor can test every software and hardware scenario prior to a operating system's release. With this in mind, I do not recommend upgrading a software environment on a mission critical or production system (one you depend on for income or work) until you've had a chance to test or ensure all of the hardware and software applications you depend on function properly. You can take steps to avoid these situations. A great way to mitigate this risk is by making a time machine back up of your working environment so you can revert back (just in case) things don't go as planned.

Re: (In)compatibility of EOS Utility with MacOS Ventura

Waddizzle — Fri, 28 Oct 2022 19:09:13 GMT

“Software development. "Canon should have had this working on day 1". Maybe they did, maybe Apple added a feature or changed something that broke the WebCam Utility? We don't know, so its unfair to blame a vendor who doesn't control what Apple releases.”

I agree. Every camera vendor is probably riding the same merry-go-round. A new OS more than likely means negotiating a new licensing agreement for the new OS. That is the Apple business model.

Furthermore, it should be obvious that it is NOT in Apple’s best interests for third party camera software to work properly. Apple would prefer that you purchased your next camera from Apple, not Canon, Sony, or Nikon. Apple would prefer that you kick third party gear to the curb entirely.

For the record, this is at least the 4th time that Apple has broken their own codebase in the past 12 months or so alone. Any software developer would tell you that breaking your existing codebase is a major no-no, a cardinal sin. Apple does it all the time to manufacturer’s of third party cameras. All the time.

[EDIT]. What good is a software development package release 6-12 months ago when there have 3-4 major updates since the release of that version of the development package?

Every time Apple releases an OS upgrade, third party manufacturers have BUY the upgraded software development package from Apple. I have no idea how much an Enterprise level license from Apple would cost, but I am sure that it would be on the order of tens of thousands of dollars per seat/developer.

Re: (In)compatibility of EOS Utility with MacOS Ventura

johnrmoyer — Sat, 29 Oct 2022 01:49:47 GMT

EOS Utility 3 no longer works with EOS R5 camera after upgrade to macOS Ventura. The USB C cable is configured to charge only and not data.

The Android file transfer app also cannot access the USB C port.

Re: (In)compatibility of EOS Utility with MacOS Ventura

johnrmoyer — Sat, 29 Oct 2022 01:23:02 GMT

The EOS 3 utility does more than transfer photos. It can also set the date/time on the camera from the computer date time and change various camera settings. It is a pain for it not to be working. It appears to me to be a permission problem with the USB port. Plugging the USB cable into the camera disables all of the menus on the camera and does charge only.

Re: (In)compatibility of EOS Utility with MacOS Ventura

johnrmoyer — Sat, 29 Oct 2022 15:22:43 GMT

NVRAM reset fixed Android File Transfer but not EOS Utility 3. Image Capture app does see the camera when the USB cable is connected.

Missing functionality for me is ability to use EOS Utility 3 to change Date/time in camera and update IPTC info in camera.

Re: (In)compatibility of EOS Utility with MacOS Ventura

johnrmoyer — Sat, 29 Oct 2022 15:26:45 GMT

Both Android File Transfer and Canon EOS Utility 3 were broken by the update to Ventura. Resetting NVRAM fixed Android File Transfer, but not EOS Utility 3.

I have the free Apple Developer login and development tools, but do not pay to have any software on the App Store.

Apple needs to work on their software testing and release. This is just poor software engineering.

Re: (In)compatibility of EOS Utility with MacOS Ventura

rs-eos — Sat, 29 Oct 2022 17:40:15 GMT

How is it Apple's problem? Apple provides ample developer previews along with public betas of the OS each year. It's up to Canon and actual software vendors to test ahead of time.

And to file bugs with Apple for those cases where bugs were introduced by Apple.

There are basically two types of companies out there regarding software: proactive and reactive. Hopefully Canon will become proactive in the future.

Re: (In)compatibility of EOS Utility with MacOS Ventura

johnrmoyer — Sat, 29 Oct 2022 22:17:28 GMT

It is an Apple problem because when I contacted Apple support I was told to reset NVRAM. Resetting NVRAM fixed Android File transfer and enabled the image capture app to talk to my camera. That should have been done during the upgrade if necessary. The last time I produced such a bug in released software was 1985.

Apple broke applications with their update.

Re: (In)compatibility of EOS Utility with MacOS Ventura

johnrmoyer — Sun, 30 Oct 2022 15:28:51 GMT

After resetting NVRAM on my iMac, deleting EOS Utility3, downloading and installing EOS Utility 3 for macOS 11, now it works again. I hope this might be helpful for someone else.