Skip to main content
Inspiring
May 2, 2024

Media Encoder inherits the wrong Sequence names for the Output Filename

  • May 2, 2024
  • 30 replies
  • 2165 views

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.

30 replies

Participating Frequently
April 29, 2026
#!/usr/bin/env python3
"""
fix_prproj_outpath.py
Fixes stale OutPath values in a Premiere Pro .prproj file.
Prompts for input at runtime — no hardcoded paths.
Safe: writes a new _FIXED file, never touches the original.

Usage: python3 fix_prproj_outpath.py
"""

import gzip
import re
import sys
from pathlib import Path


def prompt(label, default=None):
if default:
val = input(f"{label} [{default}]: ").strip()
return val if val else default
val = input(f"{label}: ").strip()
if not val:
print("Error: value required.")
sys.exit(1)
return val


def fix_prproj(src_path, old_path, new_path, out_path):
src = Path(src_path)
dst = Path(out_path)

print(f"\nReading: {src}")
with gzip.open(src, 'rb') as f:
data = f.read().decode('utf-8')

old_count = data.count(old_path)
print(f"Found {old_count} occurrence(s) of old path")

if old_count == 0:
print("Nothing to fix — old path not found. Check your paths and try again.")
sys.exit(0)

fixed = data.replace(old_path, new_path)

remaining = fixed.count(old_path)
replaced = old_count - remaining
print(f"Replaced: {replaced}")
print(f"Remaining (should be 0): {remaining}")

print(f"Writing: {dst}")
with gzip.open(dst, 'wb') as f:
f.write(fixed.encode('utf-8'))

# Spot check
outpaths = set(re.findall(r'"OutPath":"([^"]+)"', fixed))
print(f"\nOutPath values in fixed file:")
for p in sorted(outpaths):
print(f" {p}")

print(f"\nDone. Verify in Premiere before using in production.")


def main():
print("=" * 60)
print(" Premiere Pro .prproj OutPath Fixer")
print("=" * 60)

# Source file
src_path = prompt("\nPath to .prproj file")
src_path = src_path.strip("'\"") # handle drag-and-drop quoting
src = Path(src_path)
if not src.exists():
print(f"Error: file not found — {src}")
sys.exit(1)

# Detect old path from file
print("\nScanning for stale OutPath values...")
with gzip.open(src, 'rb') as f:
data = f.read().decode('utf-8')
found_paths = sorted(set(re.findall(r'"OutPath":"([^"]+)"', data)))

if not found_paths:
print("No OutPath values found in this file.")
sys.exit(0)

print("\nOutPath values currently in file:")
for i, p in enumerate(found_paths):
print(f" [{i}] {p}")

# Old path
if len(found_paths) == 1:
detected = str(Path(found_paths[0]).parent)
print(f"\nDetected old folder: {detected}")
old_path = prompt("Old path to replace", default=detected)
else:
old_path = prompt("\nOld path to replace (copy from above, folder or full string)")

# New path
new_path = prompt("New output folder path (no trailing slash)")

# Output file
default_out = str(src.parent / (src.stem + "_FIXED" + src.suffix))
out_path = prompt("Save fixed file as", default=default_out)
out_path = out_path.strip("'\"")

fix_prproj(src_path, old_path, new_path, out_path)


if __name__ == "__main__":
main()

I used this script on a dupe of my pproj file to fix the output path. It should prompt for the correct path.

Participating Frequently
April 29, 2026

This script is only fixing half of the issues, so don’t bother. The issue is somewhere between Premiere and ME. where I don't know

Participating Frequently
April 29, 2026

Posting my findings on this bug because it absolutely maddening when ripping a bucket load of files. 

 

Bug Report: Media Encoder Inherits Stale OutPath Metadata from Original Project

Issue

Media Encoder inherits stale OutPath metadata from the original project file when sequences have been renamed via repeated Save As operations. ME uses the original job folder path and filename for output — not the current sequence name or current project location.

Steps to Reproduce

  1. Create a Premiere Pro project with multiple named sequences; export at least one sequence through ME to establish OutPath metadata
  2. Use File > Save As to duplicate and rename the project
  3. Rename all sequences to reflect the new project
  4. Repeat steps 2–3 four or more times
  5. Select all sequences > File > Export > Media > Send to Media Encoder
  6. Observe output filenames and destination paths in ME queue

Expected Result

ME queue reflects current sequence names and current project folder as the output destination.

Actual Result

ME populates output filenames and destination paths from the original project's ExportSettings metadata — specifically the OutPath values stored in the .prproj XML — pointing to the original job folder and original filename. Affects sequences inconsistently within the same project; some sequences receive correct names while others inherit the stale path.

Confirmed via: Decompressing the .prproj (gzip/XML) revealed all ExportSettings.Info blocks retained the original OutPathvalues despite sequence renaming. Zero instances of the current job path were present.

System

  • Premiere Pro Beta 26.3.0 (build modified Tue Apr 28 2026)
  • Adobe Media Encoder Beta 26.x
  • macOS (Apple Silicon — M3 Max)
  • Project workflow: multi-sequence batch export via File > Export > Media

Workaround

Decompress .prproj, find/replace stale path strings in the XML, recompress before sending to ME.

Submission

Post to: https://community.adobe.com/t5/premiere-pro/ct-p/ct-premiere-pro
Select Bug as the post type.

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?