Skip to main content
C
Citizen_Sam
Inspiring
April 9, 2024
Answered

Automation Blocks - Multi-Import and Render: Duplicate Sequences instead of Send to AME

  • April 9, 2024
  • 1 reply
  • 5672 views

Hi There.

 

Loving the possibilities of the Multi-Import and Render Properties of Clips from Spreadsheet script. It can be a real game-changer for our Localization work.

 

Is there any way to modify the script so it makes a new Pr sequence for every language variant, instead of sending it to Media Encoder?

This topic has been closed for replies.
Correct answer Citizen_Sam

Great! Would you mind uploading the final code such that other users who might find this thread in the future can use it?


Sure! Attached is the code that exports project files for localization.

1 reply

Mathias Moehl
Community Expert
Mathias MoehlCommunity Expert
Community Expert
April 9, 2024

Attached you find a script where I removed the block to add to render queue and added a block to duplicate the sequence before creating a new instance.  I didn't test it, yet. Could you let me know if this works for you? As sequence names it uses the colum headers.

I also removed code for the UI to specify the output folder and file naming options.

Mathias Möhl - Developer of tools like BeatEdit and Automation Blocks for Premiere Pro and After Effects
C
Citizen_SamAuthor
Inspiring
April 9, 2024

So, I actually tried nearly the same thing (patting myself on the back).

 

What you end up with are multiple, identical sequences, with the graphics specified by the last column in the spreadsheet.

 

This makes sense, it's 'replacing footage' until it gets to the last column, but it's not duplicating the footage. So all sequences have the same footage in them.

 

I guess it would have to make multiple copies of the footage per-column, and replace them individally per-language.

 

What would be even BETTER for my workflow is if you could make multiple PROJECTS per column.

 

This is basically what the original script does when it sends to media encoder, but they go into a TEMP folder with naming conventions you can't control.

 

It'd be awesome if you could basically do the 'send to ame' thing, which replicates the projects, but gain control over the Premiere project file names and perhaps save location.

Mathias Moehl
Community Expert
Mathias MoehlCommunity Expert
Community Expert
May 4, 2024

Is there a way to expand this script so the created projects get imported into the Production? Potentially in specific folders based on project name?


Automation Blocks has no specific blocks, yet, to deal with productions. But you should be able to call something like

https://ppro-scripting.docsforadobe.dev/general/production.html#production-addproject

with the
Execute Code block

Mathias Möhl - Developer of tools like BeatEdit and Automation Blocks for Premiere Pro and After Effects
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices