EOS VR Utility bug after updating to macOS 15.2

[EscapeVR]

After updating my Mac Studio to OS 15.2, the VR Utility Application is no longer working correctly. 

When I go to export footage from RAW to ProRes, it stalls out at the 5-min left mark, and never finishes.

Can’t process my VR footage now. Can someone from Canon take a look & release an update?

[John_Q]

Hello EscapeVR,

Have you updated the VR Utility software? There was an update released on 12/10/2024 that may resolve the issue. I have also reached out to our engineering team to see if the issue has been/can be resolved with an update as well.

[EscapeVR]

I've updated to 1.5.11, and I'm still having this issue. It freezes at the end of the conversion with like 3-5 minutes left -- and I have to force quit the application.

[John_Q]

Hello EscapeVR,

I'm sorry to hear that the issue remains. I would agree with Waddizzle in deleting the previous software install completely and reinstalling the VR Utility software since the operating system has been updated. My team did inquire on whether you had used the v1.5.11 install. I have passed this additional information along as well.

[sturmen]

I am not EscapeVR, but I did delete and reinstall v1.5.11 and the issue remains.

[EscapeVR]

I deleted/trashed all versions, re-downloaded the newest, and still have the same problem.

[John_Q]

Hello EscapeVR,

Thank you for the follow up. I have escalated this issue/post to our engineers for further review. We will follow back up with a post with more information once we get a reply. I do apologize if this causes you any inconvenience.

[sl0throp]

Any word on this? We are having this issue as well.

[RacerX135]

No, You pretty much have to roll back to Sonoma for it to work correctly. I can not believe they make us pay for this app and then do not support it properly. Mac OS 15.2 has been out for months now.

I rolled back and works fine now but that is not an ideal solution.

[dd_chroma]

I did a fresh install on a Sequoia Mac that didn't have EOS VR Utility installed. The problem definitely appeared on Sequoia. Back on a Sonoma Mac it was working fine.

One guess is that it could be a file access issue which requires specific access settings when writing to the file system - I've had to fix this on some of my own developed apps.