[Tomas Bumbulevičius]

Hey Kina, yes.

You need to cycle through all markers, read the value of “comment” in the marker and if its empty – delete them.

The way how to access composition markers or layer markers is a bit different – thus let us know where the markers are (whether its at the top of composition or on a specific layer).

[Tomas Bumbulevičius]

Hey Jeremy, splitting the text by return carriage and picking the line from array.

var myString = “This is \n some example \n text”;
var splitArray = myString.split(“\n”);

splitArray makes your string as [“This is”, “some example”, “text”]

If you know exactly which line is required, then accessing it by splitArray[X] will do it.

Where X – index of line in an array (keep in mind arrays starts from 0, not 1)

So in your given example line2 would be splitArray[1]

[Tomas Bumbulevičius]

Philip, I would suggest to explore this toolkit for rigging – it feels like it could be helpful for your purpose: https://aescripts.com/joysticks-n-sliders/

[Tomas Bumbulevičius]

Hey Clement, why does a keyframe is required? The part you mention “I could create or edit” is not crystal clear on what you are trying to achieve. If you describe a general idea what you want to accomplish, that could help.

There is expression which can generate a random number, but you need to specify where you want to use that information and why keyframes are needed in your plan.

[Tomas Bumbulevičius]

I found out the best workaround for this is as follows:

1. Adding lower and higher ascenders to the text source at the end.
2. Applying text animator which subtracts those characters by setting a range to be text.source.length – X

This automatically creates all lines equal size and tricks sourcerect, AS LONG as you have one text / line. If its more – you have guessed it – its a pain to do 🙂

[Tomas Bumbulevičius]

Hey Tomer, its indeed a bit of dark-side and most often than not we just use them without much thinking about the reasoning. But in general – its micro to macro transformations, affecting different “level” of things. Anchor point basically is a position on a layer thats used as a base for all transform props.

3. Layer transform properties and values are based on the layers placement within the composition. You change the comp size and they both updates.

2. Shape transform properties works in the same way as layer transformations, JUST within layer space. Meaning, its a “deeper” level, where it affects only that object in a layer, and not whole layer itself.

1. For path transform properties, I might be wrong here, but it just another depth of fine-tuning, which does not affect none of the above.

To wrap it up – create a layer, try changing values and you will see how this exactly works.

[Tomas Bumbulevičius]

Hey Philip, the main concern here is this: you mentioned 20 or so time remapped frames.

How different position/scale values will become on each of these frames? Because one way or another I assume you will have to pre-define them somewhere? If thats the case, it sounds like you need a different type of workaround to make this work, otherwise its too much manual labour even for a rig to be used later.

[Tomas Bumbulevičius]

Hey Andrei, any chance you could share a visual reference of what you are trying to achieve? That could help to eliminate the guesswork!

[Tomas Bumbulevičius]

Alternatively, have a .json settings file – not sure whether toSource is formattable option Andrei, is it? Like adding “tidy” tabulators and at least a bit of visual sense.

[Tomas Bumbulevičius]

Once you find this, you won’t be able to unseen it 🙂 Just make sure to set expressions language to Javascript (not a legacy one)

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormat/DateTimeFormat