Imported Clips from a C300 Mark II and C200 and they are all named "CLIPS001"
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.
Gary Huff commented
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.
This issue appears to be resolved with the latest update.
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.
Andy Seaver commented
This really messes up my workflow. How can 2020 be released this way?
Sam Gordon commented
Astonishing that this hasn't been fixed yet.
Update from Adobe on Twitter:
"Hey there! Our developers said they have a fix in the works! So sorry you got caught in this issue. I can't share a specific date but I promise it will be available as soon as we can make it so – literally being worked on as we speak. Caroline"
I've just tried moving things out of the CONTENTS folder and no luck. Thanks for the suggestion though.
If I relabel the CLIPS001 folder to CLIPS002, then it works.
I've also noticed a significant speed decrease with Premiere reading the files from Canon Cinema camera's. It takes a good ten seconds per click through the folder structure before it's able to read any video files on the card (this is when importing the media via Media Browser).
This isn't an awful speed decrease, but certainly further shows an that something significant has changed within Premiere to affect its ability to read the files from these camera's.
Gordon Sandvoss commented
Have you tried moving the files out of the "CONTENTS" folder? I did this and everything worked.
chris fine thompson commented
Just installed Premiere v 14 and to my horror cannot import MXF files at all! I get an importer error or unsupported format error. Trying to import MXF files from Sony XDCAM.
Is there a a fix for this yet?
S KANAKRIYEH commented
YES, this is an issue. A workaround is to right click on your top row, the one with column labels (name, description, frame rate, etc) and go to METADATA SETTINGS, drop down PREMIERE PRO PROJECT METADATA, the check off FILE NAME to get the original file name to display.
Also if you want them to be in order of shooting, you can sort by timecode (MEDIA START)
Also have the same issue.
Have found a temporary workaround by renaming the C300mkii source clips folder to CLIPS002.
But this is a terrible issue to have on a doc with a lot of memory cards to work through.
Premiere Pro Version - 14.0.1 (build 71)
Mac Pro (Late 2013)
2.7GHz 12 Core Intel Xeon E5
64GB DDR3 Ram
AMD FirePro D700 6GB
Camera Footage with issue - Canon C300 Mkii
Chad Haberstroh commented
Yes this is still an issue in 14.0.1. Come on, Adobe.
Gary Huff commented
Just tested it with 14.0.1 and XF-AVC clips imported through Media Browser or drag-and-dropped right into the project bin are named "CLIPS001", every one of them. This is on macOS Mojave 2017 iMac.
Zach Rutledge commented
Even after the newest update, this is still an issue.
Tim Lee commented
Same issue here. How is this still unresolved?
Cole Norum commented
Checking in here. Also getting issue and have been since beginning to use 2020. Unfathomable to me how this is an issue. Unacceptable, Adobe.
Kevin Monahan commented
Upvoted. It's a known issue.
Nels McLaughlin commented
This is about as infuriating as it gets.
Matt Cori commented
Peter Hatch commented
Same thing here. Annoying. Please fix Adobe. The bugs in your updates are getting to be a real nuisance.