My PC sees my EOS-R7 but the EOS-VR Utility doesn't

[TomPetroff]

Hi, this is my first post. 

I connected my new R7 to my PC and it easily recognized it. I was able to access all the folders and files. My device manager sees it easily as well. Updated the camera to the latest firmware and purchased the RF-S dual lens and recorded a short video and took a few pictures. My computer showed the content in the folders. However, when I open the VR utility app, I can see everything but the camera connection. So I figured why not just create a folder on my desktop and put the content there. The app sees the folder, but I get an error message that says: "one or more clips that the application cannot handle." I chatted with canon support and all they could say is reinstall the software and try a different port. But the computer sees the camera????  Anyone else have this issue?

[John_Q]

Hello TomPetroff, 

A paid subscription is required to make all application features available. How long are the clips where you're getting the error message? I have included a link to the user's guide for the software HERE which may help you.

[shadowsports]

Greetings,

This should be helpful:

VR Utility Manual

https://app.ssw.imaging-saas.canon/app/en/vru.html

Available Subscriptions:

https://sas.image.canon/store/plan?serviceId=01FM15Y3BNRXETWZ58AQ54VJXK

[TomPetroff · Accepted solution]

Just a few seconds long. So i called Canon and spoke with a specialist and apparently you cannot connect the camera directly to the app, or at least not with the latest release. We  found that you had to drag the folder itself from the camera (or copy it) since it contains the Metadata for the software to read.

[shadowsports]

Tom,

Great work on your part!  This is partly my fault then because I actually knew that.  After rereading your post, I see now that what you were trying to do is access the folder on the camera from the VR utility which you cannot do.  My apologies.  I don't believe this is bug, but instead a limitation of the software.  At this point I'd say it's as designed because the operating system on the camera is locked down.  I believe this is done for safety and to protect Canon's intellectual property.  I published a KB article a while back and I don't think I've ever made it public.  It's written specifically for the R5 C, but definitely applies to other cameras I'm sure. I should probably revisit it.  Either way, your follow-up post is extremely helpful to myself and for others.  🙂