![]() : New firmware version 1.0.4.1 is available for EOS-R5 C We sincerely apologise for the inconvenience and appreciate your patience on this matter. We are currently preparing to release versions of these applications that incorporate a fix for this issue.įor EOS cameras with Wi-Fi functionality, the camera can be remotely operated from EOS Utility via a Wi-Fi connection with the Mac computer.įor more details, please refer to the respective camera's user manual. This issue does not occur on macOS 10.15.0/10.15.1. Following operation checks performed with this version at Canon, we have confirmed a USB connection issue with “EOS Utility 3.11.1 for Mac OS X” and "Picture Style File Registration Tool 1.0.0 for Mac OS X" whereby the functions enabled by connecting a camera and a Mac device via USB cannot be used. MacOS 10.15.2 was released by Apple on December 11, 2019. To Users of EOS Utility 3.11.1 for Mac OS X and Picture Style File Registration Tool 1.0.0 for Mac OS X OK - I hope anyway that EOS Utility will be updated soon. ![]() So Canon has to fix it this time, just like they had to fix it with the MXF parser issue. So how ANY of that is Apple's fault escapes me. But launching DPP4 reveals the presence of NO compatible current EOS Utility - and there simply isn't one available yet on Canon's web page. The ONLY software update that shows up when you select an older model like my trusty ad well-loved 5dMkii is Digital Photo Professional 4. This is clearly the same issue today, when we try to use the offical Canon software update web portal to update the EOS utility. Clearly, Canon had to prioritize that and fix the issue. Then suddenly things changed and it worked just fine. ![]() It's the same as how Canon MXF coming to the C-300/500 series wouldn't work natively with Apples FCP X for months and months. The only party that can address this is Canon. Using a camera gave me a reason to get up and walk around.Īpple dropped 32-bit software to allow that faster and more efficient software could be developed going forward.Ĭanon OWNS the IP inside EOS software, and as such, it's not Apples place to tell Canon what to do with it. I had to do several months of rehab and disability and got hooked. I am just a camera geek like you, but with far too many posts in this forum. ![]() Everyone is in the same boat with Apple, Some of Apple's own applications, like Safari for example, are not fully working properly on all Apple platforms.īTW, I do not work for Canon. Read the announcement at the link just above.Īpple dropped the ball. Yes, Apple announced a long time ago that support for 32 bit apps was ending, and it stopped there. Apple did not begin working with developer until AFTER the product was released. This problem is Apple's fault, through and through. All the users want is to get the software they paid for working. It is not my obligation as a customer to see a VIP contributor ranting on users. Stop pushing your responsibility to others. IfĬanon did not do their homework to get ready for the platform evolution, just assume it and say you cannot support it. Apple is a platform where each software company can opt-in or opt-out to run there. Have the same problem! Is there a solution? I see lots of messages trying to blame Apple, but zero messages about the solution.
0 Comments
Leave a Reply. |