Skip to main content
Inspiring
October 18, 2024

Render Range not sent to Media Encoder for multiple outputs

  • October 18, 2024
  • 23 replies
  • 1141 views

If I select multiple sequences to export and specify the range to be Source In to Out this is not communicated to Media Encoder. It works OK on individual files.

Additionally if I select all the outputs in the Media Encoder Queue and edit the settings to specify Source In to Out. I get the warning that I am affecting multiple entries, however in fact only one is changed. It works correctly for other settings but not for output range. 

Windows 11.

Adobe Premiere Pro 25.0.0 (Build 61)

Adobe Media Encoder 25.0 (Build 54)

 

Peter

23 replies

Peter_McCAuthor
Inspiring
November 18, 2025

Have you tried it when the Work Area Bar is not showing on the timeline? 

Participating Frequently
November 18, 2025

Unsure, since I am not on Beta.

Participating Frequently
November 18, 2025

OK, so this problem goes deeper than I expected. Even if I select a single cut sequence and try to export it straight out of the Premiere bin the entire 18 minutes will be rendered even if I choose only to render in to out. The in and out will just be marked at the beginning and end of the entire timeline. However, if I drop this same sequence into the source window the in and out are in the correct place. Likewise, if I drop this sequence (with the in and out marked) from the bin onto the "new sequence" icon the new timeline contains a sequence clip that is only the length of the in and out I've marked.

This is definitely a bug and non-sensical behavior... unless some Adobe Engineer can jump in explain the reasons why it is this way. It's aggravating because something that should have been a simple one-step operation now requires a bunch of gymnastics.

 

EckiAME
Community Manager
Community Manager
November 18, 2025

Does this also happen in Beta? I vaguely remember some fixes.

Participating Frequently
November 17, 2025

I am experiencing this same behavior. Windows 11, Premiere 25.3.0. I can a master sequence into smaller sequence clips. When I select all those sequence and export them to Media Encoder it ignores the fact that I have "Source In/Out" set under "Range." Each clips is the full 18 minutes of the master sequence. When I check it's setting in Media Encoder, "Source Range" shows "Sequence In/Out" but has the entire sequence selected. Aggravating. I will have to render all 17 one at a time.

 

Premiere:

 

Media Encoder:

 

EckiAME
Community Manager
Community Manager
November 5, 2024

You are awesome. Thank you so much. I was able to repro this as well, and just created a follow-up ticket for this issue.

Peter_McCAuthor
Inspiring
October 31, 2024

OK. I think I have narrowed this down.

 

If you have the Work Area bar showing on your timelines then the default export seems to be Work Area rather than Entire Source. When this is the case, even though you change it in the export dialogue to Source In/Out it does not pass through to AME. 

 

I can replicate this behaviour by switching the Work Area bar on and off. 

Peter_McCAuthor
Inspiring
October 30, 2024

Thanks.

I guess the Premiere (on Windows) to AME range anomoly is hard to track down. If the AME multiple range update is working properly then this won't be such a problem. 

EckiAME
Community Manager
Community Manager
October 30, 2024

The setting of source area in multiple queue items in AME is a bug. I just filed a ticket for this. Thanks again for your feedback!

Peter_McCAuthor
Inspiring
October 29, 2024

I copied the folder onto an SSD and opened the project on my Mac. One difference I noted was that when I typed Cmd-M to export the sequences the range was initially set to Entire Sequence rather than Work Area as had been the case on Windows. I changed the source to In to Out and sent to AME. The range was sent correctly to all the jobs in AME so, in other words the problem didn't replicate on Mac. However, when I selected all the jobs in AME and changed the range, in this case to Work Area it did not change in the other jobs selected, so that problem seems to exist on Mac as well.