Update so it reads Canon EOS R5C files correctly. Right now AME renames all Canon EOS R5C files to C

Forum|Forum|3 years ago
August 1, 2022
7 replies
385 views

AME can't seem to read Canon's new Cinema EOS R5C files correctly. AME renames all files to Clips0001 regardless of what the original file name is. The correct file name shows in the AME browser, though. But it doesn't carry through to the compression like other camera files do. All file name burn in when trying to render proxies show Clips0001. Sorry for no examples, my footage so far is not shareable, not even screengrabs.

Formats

Fergus H

Community Manager

Hello,

My apologies for the late reply to this. Can you please tell me what format you’re using on the R5C?

Thanks,

Fergus

Fergus H

Community Manager

Aasulv,

I got the chance to test this today and I was unable to duplicate the problem you're seeing. I'm using Media Encoder v22.5; what version are you using? Enclosed is a screen capture of what I see after dragging files from a folder of clips from the R5c into Media Encoder.

Regards,

Fergus

Fergus H

Community Manager

Hi Aasulv,

Thanks for the additional information. By changing the default from CANON to something else, I was able to duplicate the problem you're seeing.

I have submitted this as a bug. When I have an estimate for a fix, I will update this post.

Thanks again!

Fergus

P

Pacific PeaceAuthor

Participating Frequently

Thank you Fergus. If somebody else reads this I should probably clarify that this is NOT about changing any file name after they are recorded. This is about utilizing a camera menu under Recording/Media Setup>Metadata called 'User Defined', a small area of the file name that is designed to be defined by the user. So this is all done in camera. This part of the file name defaults to CANON when the camera comes from the Canon factory.

P

Pacific PeaceAuthor

Participating Frequently

Hi Fergus. Just noticed that this might be due to AME reading the files wrong when you customize the file name. I just tried to customize the file names for my C300MK2 to 300M2 instead of the default CANON, and now AME requires workarounds from that camera too to read the files correctly. Canon has had the ability to customize this part of the file name for a very long time, since 2015 if I remember correctly. So lots of time for Adobe to figure out how to read those files. Many users of Canon cameras leave it at the default CANON, but others, like me, need to customize it to separate the models. See screen grab of my prior post. Any plans to fix this?

P

Pacific PeaceAuthor

Participating Frequently

Thanks. I'm on AME 22.5 (Build 57) MacBook Pro M1 Max 64GB RAM. Here's what I get.

P

Pacific PeaceAuthor

Participating Frequently

XF-AVC which comes in .MXF format. Doesn't seem to matter which resolution or frame rate. I typically create a folder named 'WORKAROUND' and move all the files there before dragging into AME, then AME will read the file names correctly, but it's tedious. Would be better if I could just go straight from the file structure as it is. Premiere Pro also has issues reading the Canon EOS R5C XF-AVC file names correctly. Comes up as CLIPS001 if imported from original file structure. This happened before with another Canon camera, and I had to move the files or temporarily rename the CLIPS001 folder, and Adobe eventually figured it out so I didn't have to. I'm on Mac with M1 Max.Cinema RAW Light files from the EOS R5C have so far shown correct file names.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded