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
October 29, 2024

Just to be 100% sure I repeated the whole process again making sure that there were no other processes running that could possibly interfere. For example I shut down Synology Drive. Same result: Range not passed to AME and when I buld edited the jobs in AME the Range was not updated on the others selected. 

 

I plan to copy the entire project folder and see if I can replicate the problem on my Mac. 

 

Kind regards

Peter 

Peter_McCAuthor
Inspiring
October 29, 2024

That's exactly what I did. 

 

Have you tried modifying the range when multiple jobs are selected in AME. That also doesn't work? 

EckiAME
Community Manager
Community Manager
October 29, 2024

I retried on Windows 11 using Adobe Premiere Pro 25.0.0.61 and Adobe Media Encoder 25.0.0.54. So I was not able on Mac & Win.

Here is what I did:

  1. Launch Premiere Pro.
  2. Import mp4.
  3. Create sequence out of clip.
  4. Duplicate the sequence four times and rename it to "001", "002", "003" resp. "004".
  5. In each sequence choose a different in and out point using CTI and I and O keys.
  6. Select all four sequences in project pane.
  7. Press Ctrl-M.
  8. Choose Vimeo as target format.
  9. Change source area from "Entire Source" to "Source In/Out".
  10. Send to AME.
  11. Verify the ranges in export settings.
  12. Start the queue.
  13. Verify the clips.

 

Is there anything you did differently?

 

Peter_McCAuthor
Inspiring
October 28, 2024

Laptop is a Dell Alienware M15.

Intel(R) Core(TM) i9-8950HK

32 GB Memory. RTX 2080

Two internal SSD.

Windows 11 Pro. 23H2. 22631.4391

Premiere Pro 25.0 Build 61

Media Encoder 25.0 Build 54.

 

EckiAME
Community Manager
Community Manager
October 28, 2024

Can you share your specs (OS, CPU, GPU, memory)?

Peter_McCAuthor
Inspiring
October 24, 2024

I unchecked it, saved the preferences, exited and restarted AME. I then followed the same Premiere workflow, but no change either to the sending of encoding range to AME or to the fact that AME still doesn't change the range on a bulk edit of 4 render jobs.

EckiAME
Community Manager
Community Manager
October 24, 2024

Can you try unchecking? This is a totally different code path. One is using shared code, the other is communicating with PPro.

Peter_McCAuthor
Inspiring
October 24, 2024

Import sequences natively is checked. I must admit I was never aware of this setting. Do you think it could affect both the link from Premiere and the fact that Range is not changed when editing the preset for multiple AME jobs?

EckiAME
Community Manager
Community Manager
October 24, 2024

Thank you very much for your screen recording!

I did exactly the same like you, except for the Vimeo preset. But also this did not repro for me with a real mp4 video footage that I split up just like you did. What is your "Import sequences natively" setting?

Peter_McCAuthor
Inspiring
October 23, 2024

I have run the test again and it is as I reported. To demonstrate the steps I have recorded my workflow (YouTube video below) including attempting to change the range for four jobs in AME. I have had to blur part of the screen to protect client content but I don't think that is a problem. 

https://youtu.be/Ni495Ll3y-0