Oh, crazy, that's really a pity that this rounding issue causes so much trouble! You could refine the logic even more using the ternary test:  Maybe you even need to use as test condition "in point replacement" <= 3.9e-10 instead of  "in point replacement" <= 0 although for the very first frame it should be pretty save to assume that the in point is exactly 0 and not just very close to it. ... View more

Have you tried this for the inner "replace in" value? $1 = $2\n$3=$4\n$5=$6\n$7=$8 No plans to improve text formatting at the moment. But you should at least be able to use any new improvements in Adobe's APIs with the execute code block. ... View more

Does it make a difference if you use a bit less tiny number? Like 1e-6 instead of 1e-7? ... View more

To distinguish if the script hangs or is just processing for a long time, best add some write to console blocks which report step by step what the script is doing. Then make sure the console panel is open when you run the script and then you see the progress. Then you can understand better, what the script is doing and if is is just slow, hangs, or maybe runs in some kind of infinite loop. The "Update Texts of Ae Mort with Spreadsheet" already contains such console output, which you can enable with the "detailed console output" checkbox in the input panel. In general, yes, the "Update Texts of Ae Mort with Spreadsheet" needs to look at all clips in the sequence, since it has no idea where the mogrts are, so it needs to look for them. If you have the clips that need to be modified, listed in the spreadsheet, then it will definitely be more effective to just loop over those. This is what the tools in the library at Examples/Templates/Clip Property Spreadsheet are doing. ... View more

In your if condition you can check both the property name and the property value in the same way. The condition of this if block checks if both the property name is "Graphi Parameters\Main" and its value is not "bullet". ... View more

It turned out to be a rounding issue. The problem here is that the time values are saved as floating point numbers in seconds and those have a pretty high, but still limited precision. So when the value "frame number 8" is converted to seconds and then again back to frames, the result could be something like "frame number 8.000001". And then Premiere seems to round that up to "frame 9". The workaround I found is to subtract a tiny number from the in point:     Then the result is something like 7.9999999... which is again rounded to 8 by Premiere.   ... View more

if you want to explore this direction, you could write an ExtendScript panel and execute it from within Automation Blocks using the Execute Code block. ... View more

I didn't have the time to download the project and test it, but is this what you need? ... View more

You could create a webpage which shows the previews of your animations along with their names and then link this webpage in your block scripts using the Open Web Page block . The user can then select one of the block scripts and click the "Help" button of the Automation Blocks library to open that link conveniently.  ... View more

Then you just want a script which moves the selected layer 39 frames to the left and sets the duration of the active comp to the duration of that layer minus 79 frames? (-40 for trimming left handle, -40 for right handle, +1 for slate frame). Script doing that is attached  ... View more

So instead of the block which creates a new comp, you probably want to use a block to duplicate your template comp. Since the block which duplicates the comp keeps its duration unchanged, you need to then set the duration using the Set Attribute of Comp block. After that, inserting the new layer, changing its in point and start time should work exactly as in my example. All you need to do is to duplicate a comp instead of creating a new one and setting the duration after the duplication. ... View more

I just added a new block script to the Community Library for you.  You find it at Comps/Batch Create/For Each Selected Clip Create New Comp And Trim.xml   You can simply select some clips in the project panel and run the tool. It creates for each clip a corresponding comp and puts the clip in that comp. In the inputs panel you can enter a number of frames which should be trimmed from the beginning and the end. If you set these input params to trim 39 frames from the beginning and 40 from the end, I think you get what you want. (39, since you want the extra frame for the slate).   Here is the code of the block script explained: ... View more

If you really want to have the shot numbers (i.e. count the clips) instead of their names, YouTuber "Better Editor" also developed a great solution with my (paid) extension Automation Blocks for Pr: ... View more

Hi Sam, the "for each clip as Bug" does NOT mean "for only the clips which have the project item bug". It just means: When looping over all (yes all) clips, please store each of them in the variable named Bug during the loop. In other words, it just overwrites the content of Bug without looking at it.   What you need to do is to loop over all clips and then for each of the retrieve the corresponding project item and check if it actually is the one store in Bug. Comparing the project items is a little error prone, since project items can be specified in. various ways. Hence, to check if two project items are the same, we best compare their ID:   ... View more

Yes. Did you watch the tutorial? It explains it in full detail. ... View more

You have three different bins (one for start clips, one for middle clips and one for end clips). Then the tool just picks start clips from the bin with the start clips. etc ... View more

If you use the "get prop of clip" block, you retrieve the actual text that the template parameter has. If you use just "prop" itself, you get the graphics parameter column instead of the value column:   The "in text ... find" block returns 0 if no occurrence of the word was found. Hence, we check if it is NOT 0, because then we know that the keyword has been found.  This will return true if the prop is "Graphics Parameters\Darth" but also if the prop is "Graphics Parameters\My Darth V" i.e. it only checks if the word "Darth" occurs anywhere in the name. If you want to be more precise, you can do an equality check with the full parameter name: ... View more

I just created this tutorial, which shows a similar workflow: https://docs.mamoworld.com/automation-blocks/tutorials-pr/batchSequenceCreation ... View more

I recorded a tutorial, since I feel this could be interesting for many users: https://docs.mamoworld.com/automation-blocks/tutorials-pr/batchSequenceCreation   ... View more

This sounds like my (paid) extension Automation Blocks for Premiere Pro would be very helpful for you. See this discussion: https://community.adobe.com/t5/premiere-pro-discussions/using-automation-blocks-to-create-randomized-large-batch-edits-from-csv-spreadsheets/td-p/14816665     ... View more

Unfortunately, time remapping cannot be accessed by Premiere Pro's scripting API and hence also not by Automation Blocks. See https://community.adobe.com/t5/premiere-pro-discussions/extend-script-time-remapping/m-p/11572218   The only workaround that comes to my mind is to use an effect for the ramp instead of the native time remapping controls. You could 1) apply the effect "Posterize Time" to the clip and then 2) add keyframes to the Frame Rate parameter of the effect. For more details about creating the keyframes with Automation Blocks see https://docs.mamoworld.com/automation-blocks/tools-pr/keyframeTools#craft-your-own-keyframing-tools   ... View more

To keep the location and duration of the clip in the main sequence unchanged should be even simpler: Remove the two last blocks, which adjust the start and end time of that clip and instead set the inPoint of that clip to its current inpoint minus the start handle duration. That way make sure that the correct portion of the clip is shown (otherwise it will be offset by the start handle duration). Not sure about the other issues. Can you identify when they are happening? Note that we are inserting the original, unmodified clip in the nested sequence. Hence, if you have any effects, time stretching or other modifications applied, they won't carry over to the clip in the nested sequence. ... View more

I see. No, there is no such feature. hence, you would probably need to loop over all sequences and check where this item has been used. ... View more

Do you want to Set the File of the project item? ... View more

Here is a version which adds handles:     I added it to the Community Library at Clips/Nesting/Precompose With Handles.xml   ... View more

Yes, my name is Möhl, but since ö is causing so much trouble, for user names Moehl is a better choice 🙂 ... View more

Replacing a clip by a new sequence containing the clip can be achieved as follows: 1) creat a new sequence from clip 2) set the attribute project item of the original clip to the new sequence ... View more

The great thing with Automation Blocks is that everything can be customized. In Henrique's code, just find the part which loops over the properties that are exported, then add a condition to only export if it is one of the entries you want to export. What might be confision about TMMW's code at first is that it consists of functions, which are collapsed. So you need to right-click->expand on the "run" block to see the details of the main code. # The only thing that you need to figure out is what exactly distinguishes the values you want to export from the ones you don't. Maybe they have some keyword in their name? Like only export properties whose "prop" value does not contain "color" or "guide"? Really depends on your templates. ... View more