Skip to main content
Inspiring
September 27, 2025
Question

Automation Blocks: Toggle nested sequence tracks and export each version

  • September 27, 2025
  • 2 replies
  • 377 views

Hi everyone,

I am currently working with Automation Blocks in Premiere Pro (version 1.1.011) and I’d like to automate the following workflow:

I have a main sequence called “Video”.

Inside this sequence there is a nested sequence called “Headlines”.

This nested sequence contains multiple headline tracks (Track 1 = HL1, Track 2 = HL2, etc.).

What I want Automation Blocks to do:

Open the nested sequence Headlines.

Disable (hide/mute) all tracks except Track 1.

Go back to the main sequence Video and send it to Media Encoder for export. The file name should include the headline, e.g. “Video – HL1”.

Then repeat the process: disable all tracks except Track 2, export again as “Video – HL2”.

Continue until all headline tracks have been exported as separate video versions.

Basically, I want Automation Blocks to cycle through the tracks in the Headlines nest, make only one visible at a time, and export the main Video sequence with that version of the headline.

My question:

Is it possible to control track output (enable/disable video/audio tracks) in a nested sequence directly via Automation Blocks?

Or would this require creating sub-sequences for each headline instead of working with a single nested sequence?

Thanks in advance for any pointers!

2 replies

Mathias Möhl
Inspiring
September 30, 2025

This sounds like it should be doable with Automation Blocks:
You can enable/disable the visibility of a track with the Execute Code block as shown here:
https://docs.mamoworld.com/automation-blocks/block-reference/prOther#track-set-visibility-eyeball

svens82Author
Inspiring
October 3, 2025

Hi Mathias,
first of all, thanks a lot for your tip about using track visibility (eyeball) instead of mute — that really helped me move forward!

However, I’ve run into a problem: when I toggle visibility and then send the sequence to Adobe Media Encoder, the export always comes out without the headline (text) visible. In Premiere itself I can see that the eyeball switching works correctly, but it looks like the job is handed over to AME too quickly, before the change has actually taken effect.

Is there a recommended way to make sure that AME gets the updated state of the sequence? Maybe I need to add a delay or another step to ensure the change is applied before export?

P.S. du bist aus Deutschland oder? Dann hätte ich ja auch gleich deutsch schreiben können 🙂

Mathias Moehl
Community Expert
Community Expert
October 3, 2025

Inside the execute code block you could add a line

$.sleep(1000); 

after the track.setMute command
to wait 1000 milliseconds. This also gives you some more time to see how the eyeballs turn on and off step by step to verify that the logic is correct.
Alternnatively, you can add an alert message before the "add to media encoder" block, to manually confirm that the program should proceed (makes checking if everything looks good in the timeline before queing even easier).

Last but not least you could clone the sequence before sending to AME. If there is really a bug in Pr which fails to update the data before sendinig to AME then it could help to send the clone to AME instead of the original sequence (becauuse the clone had the correct eyeball settings right from the beginning).

Mathias Möhl - Developer of tools like BeatEdit and Automation Blocks for Premiere Pro and After Effects
Richard van den Boogaard
Community Expert
Community Expert
September 29, 2025

I'm afraid we don't provide support on third party extension on this community.

If you're lucky, some other user of Automation Blocks may respond anyway. But your better/best bet would be to contact the maker of this extension directly for (faster) support.

 

Hope this helps.

Stan Jones
Community Expert
Community Expert
September 29, 2025

All true, but @Mathias Moehl is very active here.

 

Stan