Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

“Send to Adobe Media Encoder” command doesnt respected the In and Out points

New Here ,
Sep 03, 2025 Sep 03, 2025

Description:
In previous versions of Premiere Pro (such as 2024), using a custom shortcut assigned to the “Send to Adobe Media Encoder” command respected the In and Out points set on the timeline. However, in Premiere Pro 2025, this behavior has changed.

Now, when I use that shortcut, Premiere sends the entire work area to Media Encoder — even if the work area is disabled — and completely ignores the In and Out points. This breaks a key part of my workflow, where I quickly mark In/Out and send just that range to export.

Currently, I’m forced to use the manual export dialog (Ctrl+M) to ensure the In/Out range is respected, which adds unnecessary steps.

Steps to reproduce:

  1. Mark In (I) and Out (O) points on a sequence.

  2. Use a custom shortcut assigned to “Send to Adobe Media Encoder.”

  3. Media Encoder opens the task with the "work area range" setting instead of "In/Out source".

Expected behavior:
The export should respect the In/Out points marked in the sequence — as it did in Premiere Pro 2024.

System info:

  • Premiere Pro version: 2025.4

  • Media Encoder version: 2025.4

  • OS: [windows 10]

Bug Needs More Info
TOPICS
Export , Interoperability or 3rd party tools , User experience or interface
41
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Pinned Reply

Adobe Employee , Sep 03, 2025 Sep 03, 2025

Hi @Juan Manuel349609618pas,

Thanks for submitting your bug report.  I tried using my own custom shortcut, but it worked as expected.  Can you tell me what specific keys you have assigned as your custom shortcut so I can try to reproduce the issue? Sorry for the frustration, and thanks for reaching out.

 

Status Needs More Info
Translate
1 Comment
Adobe Employee ,
Sep 03, 2025 Sep 03, 2025
LATEST

Hi @Juan Manuel349609618pas,

Thanks for submitting your bug report.  I tried using my own custom shortcut, but it worked as expected.  Can you tell me what specific keys you have assigned as your custom shortcut so I can try to reproduce the issue? Sorry for the frustration, and thanks for reaching out.

 

Status Needs More Info
Translate
Report