Skip to main content
New Participant
April 20, 2025
Answered

Possible to send multiple items to the encoder with shared assets?

  • April 20, 2025
  • 1 reply
  • 367 views

Hi all -

 

Hoping to find a solution to save me time. I have two videos built in Premiere that share assets, one built in 1x1 and one in 9x16. Both of these videos have a .psd file in them that contains a date. I need to create this same video in both aspect ratios for roughly ~30 dates.

 

The issue I run into is if I send to media encoder, I need to wait until all files begin encoding before editing the .psd file or the asset gets updated across all the files previously sent (I learned this the hard way.) Ideally, I would like this to be my workflow:

 

(Update .psd file with date > send to media encoder > update .psd file with new date > send to media encoder) times x, and then > encode. 

 

Currently, I have to update .psd > send to media encoder > wait to encode > and repeat. As you can see, this takes significantly longer.

 

Any ideas? Is there any way for the .psd file to be saved to its last state before sending to the encoder, and then it can be edited without affecting the files already sent to the encoder?

Correct answer EckiAME

macOS 15.4.1 on a 2021 M1 Pro w/ 32GB Memory.

Adobe Premiere Pro 25.2.1, Adobe Media Encoder 25.2. "Import Sequences Natively" is on. PSD is in a nested sequence as an overlay on the video, with a handful of other assets. 

I believe you stated this in your response, but just clarifying - I want to do all the rendering on the backend. Therefore, I will be sending multiple files to the encoder before they are exported. The solution i am looking for is to have the PSD file reference its state from when it was sent to the encoder, not its current state. 



Modifying assets in-place and queuing items won’t work, because at queue time only references to the files are transferred. At render time those files are read, so if you batch multiple items the last version will always be used.

 

You can create a Photoshop file with separate layers for each version and toggle the layers on and off in the Source Settings. Another option is to rename the PSD for each version and create individual sequences. If the structure is always the same, you could build a project template and then just relink the PSDs. Or you can use a very simple .mogrt in Premiere Pro.

1 reply

EckiAME
Community Manager
Community Manager
April 22, 2025

It looks like the project is referencing the last cached version of the PSD instead of the updated one. I’ll verify this behavior and file a bug report if needed.

 

In the meantime, if you rename the PSD file for each export and reimport/relink it in the project, this issue should be avoided.

EckiAME
Community Manager
Community Manager
April 22, 2025

I created a PSD, placed it into a PPro project, craeted a sequence out of it, exported via AME, then chganged the text layer  in the PSD (which showd as updated in PPro), and exported again via AME. Both worked like expected.

This is on macOS 15.4.1 using Adobe Premiere Pro (Beta) 25.3.0.57 and Adobe Media Encoder (Beta) 25.3.0.52.

What are your exact specs (OS, CPU, GPU, memory)? Which versions of AME and PPro do you use? Is your "Import sequences natively" setting in AME on or off? Did you do a regular import of the PSD, selected the layers, and put it into a sequence? Am I missing anything here?

New Participant
April 22, 2025

macOS 15.4.1 on a 2021 M1 Pro w/ 32GB Memory.

Adobe Premiere Pro 25.2.1, Adobe Media Encoder 25.2. "Import Sequences Natively" is on. PSD is in a nested sequence as an overlay on the video, with a handful of other assets. 

I believe you stated this in your response, but just clarifying - I want to do all the rendering on the backend. Therefore, I will be sending multiple files to the encoder before they are exported. The solution i am looking for is to have the PSD file reference its state from when it was sent to the encoder, not its current state.