Canon MXF files being renamed on Import

[dylanp83040924]

Hey everyone, 

When I import native MXF files to Premier CC 2020 it is renaming them to "CLIPS001" and putting them completely out of order. It's doing it in every project I create. I have not had trouble in the past with these files. So not sure whats going on. I have tired importing using Media Browser, Import, and drag and drop. All roads lead to this result. 

[title edited by mod]

[Ann Bens]

Known issue.

Rename CLIPS001 to CLIPS002 and try again.

[dylanp83040924]

ok, but I am not trying to rename them. I have been able to load these types of files in before without them being renamed. 

[Steve Griffiths]

As Ann mentioned it's a known issue (a bug) - so you are stuck with manually renaming your clips until it's fixed. 

Unfortunately it's not on the list of fixes in the just released 14.0.1 Premiere Pro.

[Mizzou95]

You may check to see if they fixed it. Premiere 14.0 had an issue with P2 media no longer being selectable in the import area, wasn't listed as a fix in 14.0.1, but it was (finally) fixed.

[Ann Bens]

Alas bug has not been fixed (btw this is not P2 footage but Canon AVC)

You dont rename the clips just the folder the clips are in.

I am facing the same issue. Bit of a pain.

[dylanp83040924]

Thanks for the help everyone. It seems like my update yesterday fixed this issue. It was super annoying though! 

[Ann Bens]

No it has not been fixed. The issue is random.

[sr833]

As of 3-11-2020 and Pr version 14.0.3 this Clips001 renaming issue still persists. Just watched a Film and TV workflows video from Adobe with Karl Soule where he talked about the importance of keeping metadata true throughout the production workflow. Would be nice if, what appears to be an Adobe 2020 version glitch, this could be resolved on the software end. Wonder if a Jason Levine or afore mentioned Karl Soule could comment on this Clips001 issue. Are we doing something wrong on the ingest end?

[Ann Bens]

Dont see the issue in any more. For me 14.0.3 fixed it.

[sr833]

Thanks. I'll try an uninstall and re-install. 

[sr833]

Fixed. Well fixed for us at least. We found that the "CONTENTS" folder is the issue. Evidently the "S" in CONTENTS ingests all clips as Clips001. On a test we renamed that Contents folder as something arbitrary. The clips ingested as normal with their camera given name. We went back and took the "S" off, renamed the folder "CONTENT" and again, all clips named normally. Something about the "S" in CONTENTS. 

[mayjain · Accepted solution]

Hi All,
Sorry about this issue again. We had fixed it in the past, but it appeared again with different file combinations. We have fixed it in the latest beta 23.1 builds once and for all. It will work even if User-defined field is updated. The fix will also be a part of the next release. 
Please check the latest beta build and let us know how it goes.

Thanks,
Mayjain

[mayjain]

Hi All,

Please check out the latest Premiere Pro version 23.1. This should be fixed. 
Let us know how it goes for you in the latest version.

Thanks,
Mayjain

[Piotr34019420c3ze]

Hello, this bag come back! Please help!

[mayjain]

Hi @Piotr34019420c3ze ,

Sorry for this issue and thanks for highligting it. We haven't seen any such issue in internal testing/verifications. 

Please share your project/media files to help us reproduce this problem at our end https://helpx.adobe.com/creative-cloud/help/share.html . We will investigate and try to understand more on this to take further action if required.

Thanks,

Mayjain