Premiere Pro Appending Filenames With "_1"

September 2024 and this is still happening and very annoying. I just exported 30 lectures as videos, then resaved the project as a new one so I could edit them down a little to create audio files of the same lectures. Closed and reopened Premiere to try and avoid this issue and it does it on every single export. What's worse is it keeps trying to export as video; I distinctly remember being able to change the export settings for the first timeline and then it would keep those settings for the subsequent exports avoiding this issue; now for each of the 30 exports I have to choose the different directory, change the file type, AND then remove the _1. 

I was very disheartened to hear this was reported last year with no resolution or even comment from Adobe. Each issue makes Resolve look better and better.

Hi,
when I'm exporting video, Premiere automaticly adds suffix "_1" to the existing sequence name.
We have an archive system in our company (news webpages) which requires to have same name of  XML file of exported sequence and of exported video.
We are exporting approx. 20 videos per day per videoeditor. So Its very ennoying to rename each export.

Hope this will be fixed soon.

Thank you
Michal

i cant recall how long ago it started, but ive been seeing this for a while too. the file name is fine if i hit escape, and click export again.

i did a full uninstall of all the adobe programs along with clearing all my adobe preferences/settings. not sure what's triggering this...

Michael Grenadier

You're really not seeing it any other time? What version and build are you on?

This is so frustrating. Every single decision they've made with the new export window is awful. Absolutely pants-on-head stupid. Just add this one to the list, because they're probably never going to fix it and give us some empty platitude about "taking our feedback seriously." But to confirm, yes, i also have this issue and it's only recent. 

Also, I don't want to hear that it's complicated to make programs for two different OS's. No kidding! But it's their job to do that. Cars are also complicated, but I don't give my mechanic slack if they screw up a repair. I don't give Adobe any slack either, it's literally their job to create these programs. 

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.

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. 

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!

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).  

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..?