Went to the Media Browser, clicked the root folder that held the "CONTENTS" folder, and context-menu'd "Import" and every clip is named "CLIPS001". This did not happen with the previous version, just this new Premiere 2020.
Premiere Pro v14.8 on WIndows 10 - Canon XF utility installed on PC
My Canon Camera transfers footage onto my computer. With a specific File Structure. This is the structure for my Camera Canon XA50 ../CONTENTS/CLIPS001/Filename.MXF ../CONTENTS/CLIPS001/Filename.THM ../CONTENTS/CLIPS001/Filename.XML
I believe Other Canon Cameras like the C200 have maybe a couple of other files for each video file. On top of the MXF, THM and XML files.
So, When I use the media browser ti import
Each file comes into Premiere Pro and Gets named CLIPS001 for every single file I import. All called CLIPS001.
Ok now if I rename the FIle structure to read CONTENT rather the CONTENTS so: ../CONTENT/CLIPS001/Filename.MXF ../CONTENT/CLIPS001/Filename.THM ../CONTENT/CLIPS001/Filename.XML
When I do this the files all get imported with the actual Filename as expected
That user reports you can call that folder anything as long as it doesn't have an S in it basically.
Can we have this fixed please? It's super annoying. And if I rename the folder it no longer works with the CANON XF Utility.
Note this happens whether I import from the File-Import menu or through the Media Browser.
I also note that the creation dated for these files do not get imported either. I'm not sure if it's related or whether I should submit a separate bug report for that. But can you look at the filenames issue for this report. And check the creation date.
This is still happening now, November 2020! Is anything being done about it, I have several huge projects happening right now, thousands of clips all named CLIPS001!
FYI - If an AC or DIT programs the camera head to write custom cam file names for C300 it will trigger this issue in September of 2020 so it is almost resolved. Your clips will import all with the same name and will not translate to Resolve XM or EDL. You need to manually change camera file names in source folders to say CANON (all caps) where the custom name exists and Premiere will import with the proper file names intact.
FIX THIS SH**!!! So many buggy things that do not get addressed but we have AI reframing and shot detection. So take your cut to online and weep that all the cam names are incorrect. Just repeat after me: "We pay money to be Adobe Beta Testers!"
This issue is currently resolved unless the "User Defined" field is altered from "CANON" to something else. So a clip with a filename of "A001C059_20012242_CANON.mxf" will import just fine, but a clip named "A001C001_200527XT_AYRO0.mxf" (using the User Defined option in the camera) will import as CLIPS001. Renaming the files to remove the custom field allow them to import with proper file names.
Premiere Pro update released today... Still no fix for this. Plus this new update is even more unstable than the previous version. Shortcuts to expand and minimise the timeline aren't working. The search box in the Project panel is flashing non stop. Playback takes about 10 seconds to start after pressing play... Plus much more. All of which were fine before. Will start a separate thread for some of these later. But blimey. Adobe have lost the plot.
AdChoices