The Set Property of Sequence block of Automation Blocks 1.1.000 now actually supports properties "workarea in", "workarea out" and "workarea enabled". But note that these functions don't work reliably in Pr's scripting API (and I guess that's also the reason why they are not documented). See the API bug infos here: https://docs.mamoworld.com/automation-blocks/block-reference/prSequence#work-area-enabled--in-point--out-point   ... View more

Here is simplified example showing what happens if you nest loops inside each other:   On the right side you can see the console output of the "write to console" blocks. And as you can see, the first "write to console" message is executed 3 times (once for each iteration of the outer loop) and the second "write to console" message is executed 9 times, namely 3 times for each run of the outer loop. ... View more

Hi Sam, there are different flavors of cvs files - some use tabs as as separator symbol between the cells, some use tabs and some use ; In Open Office during import you can choose which separator symbol you want. Make sure to use comma.   This is what the import dialog looks like in my German Open Office: ... View more

I think there is no way to execute a jsx script directly, unless you run it with VS Code and the Debugger: https://extendscript.docsforadobe.dev/vscode-debugger/getting-started-with-vscode-debugger.html   If you happen to use my (paid) extension Automation Blocks for Pr, today we added an update which can execute jsx code, too. See https://docs.mamoworld.com/automation-blocks/block-reference/prOther#executing-jsx-files   ... View more

Update: Today we published Automation Blocks 1.1.000, which has remote execution via http requests built-in. See here for details: https://docs.mamoworld.com/automation-blocks/remoteExecution   ... View more

Today we published an update of Automation Blocks, which includes a block to execute arbitrary jsx code.  You can use this now also to execute the qe dom code you found to apply effects to clips. See here: https://docs.mamoworld.com/automation-blocks/block-reference/prOther#clip-apply-effect   ... View more

Today we published an update of Automation Blocks, which includes a block to execute arbitrary jsx code. With this, you can now also change audio channel mappings. See https://docs.mamoworld.com/automation-blocks/block-reference/prOther#projectitem-audio-channel-mappings   ... View more

Today we published an update of Automation Blocks, which includes a block to execute arbitrary jsx code. With this, you can now also lock tracks with Automation Blocks. See https://docs.mamoworld.com/automation-blocks/block-reference/prOther#track-set-locked ... View more

I just did some more experiments: In this test you can see that when setting the frame rate to 23.976, Premiere displays it as 23.98, but when retrieving the actual value with Automation Blocks again, it is 23.97600000something - i.e. really almost 23.976 except for some tiny rounding issues. I used alert() to show the actual frame rate both before and after changing it. When I run the tool the second time, I see the 23.976000... value also in the first alert message. Hence, I can be sure that this is the value that Pr actually stored and that the 23.98 is just what it displays.   Here is a variant of your tool, which sets the framerate of all selected project items: Instead of your equality check, which sets the framerate only if the item does not have EXACTLY that framerate already, I added a more fuzzy check. Now it only sets the new framerate if the item does not have a very similar framerate already. I also added some output to the console, such that you can see what is going on. Script is attached.     ... View more