Premiere Pro Appending Filenames With "_1"

[MeKevinB]

Long time listener, first time caller. This is my first post. Please be gentle.

After the most recent update to Premiere Pro - 32.3.1 (Build 61) - I see that Premiere Pro adds "_1" without quotation marks to every filename before export in the Export dialogue.

I understand this is necessary when the filename already exists in the given folder. We've all seen this and it's a good prompt to change the filename or the destination of the export. But PP is doing this by default even if the folder doesn't cirrently have a file with the same name. It does it when the destination folder is empty. I've been seeing this happen for the past week or two so reboots, clearing media cache, all basic troubleshooting I've tried is not fixing this. It's minor but also really annoying. I've been using PP for over two years and it only started doing this the past couple of week. Is anyone else seeing this? Is there a fix?

[Jeremias5E36]

Hi, Kevin!

I'm also experiencing this bug, and hoping that an update can fix this.

[kristian444]

Same thing here, and only after the latest update. Either it's a bug, or the setting for it has a very un-obvious name, as I can't see what's causing it.

[Michael Grenadier]

I see this behavior if I've aborted a previous attempt at exporting a sequence.   

[chris-joyce]

I'm experiencing this too. Very frustrating and I can't figure out how/where to change it. I hope it's a bug that will be remedied soon!

[kristian444]

What I've now noticed, and not sure if this is replicatable, but it seems like this only happens when I'm working on one sequence in a project. If I create a second sequence and work on both of them, then this doesn't happen.

Another minor annoyance I have - of it not remembering what preset was last used - also seems to disappear when there are multiple sequences. Might be a coincidence, but might help..?

[Michael Grenadier]

let's talk workflow...  When I start a new project, the first sequence is named Project_assy1. (assy stands for assembly).  When I start working the next day, I duplicate that sequence in the  project panel, and then rename the original project Porject_assy2, so that the project I want to work on is already in the timeline AND I have a backup so I can go back and review the previous version if necessary.    Some people prefer to add the date rather than version number...  (but if you add the date, do not use "/" in your sequence name as that becomes the default export name and trust me you don't want to go there...  And I only see this behavior as I've said, when I've aborted a previous export (or have already exported that sequence).  

[Fritz6C15]

HELLO ADOBE?!? Is anybody home or are you just taking our money? Address this issue that, just like virtually ever single other interface change, only serves to disrupt workflow. FIX THIS!

[cam matador]

These sorts of problems also exist when using Media Browser to move subclips and other content from one project to another if a drive to drive or directory to directory move is involved. Literally will rename not just custom clip names but also append source media files to avoid duplicates. The software is too stupid to realize duplicates need not be created. Adobe has never fixed the relationship between subclips and master clips. Using Media Encoder as the hack pass through engine to facilitate the move is also where custom clip names get blasted on a bin level. Can also be a problem with proxies occasionally.

Adobe doesn't even comment on this mess. The foundation of their software is a joke and far from professional. All the extended features are nice but without a solid media framework and foundation you have nothing. 

[Michael Grenadier]

The way a program integrates with an operating system is a complicated issue and not always easily addressed when you're designing software for both windows and apple.   Adobe may have chosen the safer workflow to prevent accidental overwrites...  and finding a "cleaner" solution may be difficult if even possible...   And of course, both Apple and Microsoft (but in particular Apple) have a habit of changing basic stuff in their OS that I imagine is not easy for Adobe to keep up with.