Skip to main content
Inspiring
May 2, 2024

Media Encoder inherits the wrong Sequence names for the Output Filename

Hi, I'm running Premiere and Media Encoder Version 24.3.0 on Windows 11.

 

I'm having a strange issue where if a Sequence in Premiere has been renamed at any point (for example 'Amazing_Edit_V001' to 'Amazing_Edit_V002', whenever I go to export that sequence using Media Encoder, it sets the default Output Filename to the previous sequence name,  'Amazing_Edit_V001'. Regardless of whether or not I shut down all the programs or even restart my computer after renaming the sequence. It was always inherit the original sequence name. This will also happen if then rename the sequence again to 'Amazing_Edit_V003', it will still maintain the original 'V001' filename when sent to Media Encoder.

 

I should specify that this only applies to the 'Output File' filename. It correctly recognises the the sequence name as the source name on the left.

28 답변

Inspiring
February 16, 2026

This is still an issue in 26.0.1. 
While still also experiencing this issue in 25.5.0 I replaced both my CPU and GPU, as well as doing a complete removal of all Adobe software, using the Adobe Cleaner Tool, and then deleting every leftover folder I could think of, before re-installing everything again. I found no difference at all in regards to this bug. 
I did notice, however, when ‘upgrading’ (and I use that word in the loosest possible sense) to 26.0.1 that Adobe have removed the ‘Pro’ from the name of the software. I’m guessing because they no longer view the humans that pay for their software to be professionals. 

 

Participant
November 14, 2025

why is this closed if the issue is still ongoing?

Inspiring
February 16, 2026

Because if it has nothing to do with the AI tools they’re desperately trying to ram down peoples throats in order to devalue the work of real people, they literally could not care less. 

Participant
November 14, 2025

still experiencing this on 25.5.0

Inspiring
October 30, 2025

Update for anyone in the year 2035 still experiencing this issue who has found there way here in search of a solution. This is the point where Adobe abandoned trying to resolve this issue. Currently, the 'known bugs' section of their website is about 80% to do with the Generative AI features they keep trying to push down our throats. Meanwhile bugs like this that affect their core user-base continue to be ignored. No doubt in few months from now, this thread will be quietly marked as 'resolved' with no meaningful solution ever provided. 

I hope to be proven wrong. 

Participating Frequently
October 6, 2025

This is an issue for me now as well. Build 25.5.0 working on Macbook Pro Nov 2024, OS 15.6.1 (24G90)

jamieclarke
Community Manager
Community Manager
September 11, 2025

Update: we appreciate everyone who shared feedback on this. The issue is being closed for now, though it stays logged for future review.

Known Participant
September 11, 2025

Issue
When sending a sequence directly to Media Encoder, sometimes the sequence name will not be transferred correctly. Instead the name of another sequence is inserted.

 

Steps to reproduce
Unfortunately I didn't have found a way to reproduce the issue.

It seemingly happens randomly. One sequence is named right, the next is wrong.

The sequences were send directly from the timeline panels using the shortcut.

The bug seemingly does not occur when (batch) sending sequences through the project panel (right click -> Export Media...)

 

Expected result
When sending a sequence directly to Media Encoder, it should take the sequence name as file name.

 

Actual result
The name of another sequence is inserted, althought the name of the sequence is visible at the header line in Media Encoder.

 

Sequence name

 

File name 

 

Adobe Premiere Pro/Media Encoder version
25.5

 

Operating system

Win 10

 

Possible fix

This problem wouldn't be as bad if we finally had wildcarts for filenames. This way, I wouldn't have to change every other name manually (special characters in the sequence name could be replaced by a custom legal character - sometimes Premiere just discards all characters behind a point, although it's a legal character, being another problem when trying to export certain sequences).

Placeholders that would be great are: 

  • Sequence name
  • Resolution
  • Aspect Ratio
  • Frame rate
  • Frame count/Duration
  • any (custom) Metadata field

Especially batch exports would benefit from this.

Participating Frequently
September 2, 2025

Why hasn't this been updated with the lastest update?

Inspiring
August 22, 2025

This is still an issue in the most recent update - V25.4.0 Build 99

flystatic
Participant
August 3, 2025

Any update on this Adobe? It's an annoying bug that's been allowed to continue far too long.