Imported Clips from a C300 Mark II and C200 and they are all named "CLIPS001"

Renaming the folder from CLIPS001 to CLIPS002 before importing works to get the correct clip names... but then the problem is that if you use the Canon XF Utility app (to quickly view clips and see all of their info) the Canon app looks for a folder named CLIPS001... so it does not load the clips. Ughhhh!
This is soooo **** frustrating, because it all worked fine 4-5 years ago, and then it was F'd up with a Premiere update at that time.
WHY????
And... why can't this be fixed (ADOBE)??
Come Onnnnn!

This bug is still ongoing in 22.3.0 involving the use of XF-AVC clips that have custom filenames. Clips ending in _CANON.MXF are fine, but anything else causes them to be imported as CLIPS001.

It's a bug that's been happening for almost 10 years. Still Adobe has not fixed it! Why not?????

Heather Brown, this worked, thanks so much!!! How bizah! What a silly problem, Adobe should certainly be able to fix this...

April 1, 2022 12:07 PM ·
change the original folder name from CLIPS001 to CLIPS002 and re-import. Its an adobe problem.

change the original folder name from CLIPS001 to CLIPS002 and re-import. Its an adobe problem.

This it happened a while ago for me and then somehow it was fixed and clip numbering was working fine though March 22, 2022. Then I had shoots on March 25 and 30, and suddenly all the clips are named Clip0001 in Premiere. Adobe, please fix!

Still a problem MAR 11, 2022! Adobe Suck. I want a percentage of every monthly license fee back for wasted time, ****** programming and a complete inattention to users feedback.

WHY still this problem?!??!?!?! This makes absolutely no sense! Monthly Adobe rates for all users should have paid for this fix ages ago. I'm starting two new film projects and all files from the Canon c300mkIII are coming in as "CLIPS001".

Still happening. September 2021. It is a HUGE pain in the butt to change every content folder to Clips002... but here we are suffering this same issue after a couple years.

Is there a fix for this yet?

I'm oddly getting this issue with just one camera from a multi camera shoot.

2 x C300mk2 and 1 x C70

The footage from one of the C300mk2s has this issues but the other does not have this issue and neither does the C70.

Very strange.