[Tomas Bumbulevičius]

Hey, there are many ways of achieving this, through expressions and through scripting.

Considering you might not be familiar with scripting – it would be good to know how your control layer affects the selection of data.

For example, if its some “slider” which increases index of array item in JSON, you could set expression to pick index from comp name – which, after duplicating it, would automatically update.

Not fully automatic process, but considering how much info you did provided, its a pure guess. If you share more details, chances are high that we could help you further.

[Tomas Bumbulevičius]

Hey Arne – unlikely to be possible. As Preview Resolution is project panel item, it can be access from scripting only.

Do you render different resolution outputs? Does it mean that half/quarter of best quality would look completely different?

[Tomas Bumbulevičius]

Hey Rifton, what specifically doesn’t work in your execution?

How do you want to repeat this animation? Meaning, should it move down the website, pause and then move down again incrementally? Expression you have seems fine, but I would suggest using 2 values:

easeOut (time, 2, 5, 220, endPosition)

That way, your position would be interpolated based on time, from 2seconds to 5 seconds (you can change these, up to you, its just an example)

[Tomas Bumbulevičius]

While I haven’t tried this specific approach Filip, I do recall in the past that posterizeTime (as well as making comp 1frame long for calculation purposes only) doesn’t reliably work in all cases.

I have faced situations where it seems that no further calculations might be needed, but everything hanged on to a close-to-freeze situations, due to calculations heaviness on every frame. Thus, I think Benjamin is experiencing exactly the same scenario.

[Tomas Bumbulevičius]

Hey Daniel, most likely solely through graph editor and keyframes editing you won’t be able to slow down things.

For this reason, add additional keyframes with smaller incremental values in between, set them to be linear-type (no easing that counter won’t slow down when keyframe is reached), and it should be good to go.

[Tomas Bumbulevičius]

Indeed, I can accompany Filip – it will be a slow approach.

To add even further, if you are using shapes, they became slower since CC 2020. Haven’t compared with CC 2021 yet, but on 2019 version shapes were SIGNIFICANTLY faster. Even if you don’t use new shapes transformation functionality – they became really slow. Keep that in mind in case if you link data with shapes in some way – it will slow things down.

On a different note – Filip, did you happened to see improvements on expressions, which had to be faster if not required to be re-calculated? I believe it was introduced in 2020 as well – but definitely not a vastly noticeable thing.

The reason why I mention this – maybe, it would be possible to benefit from this with data files.

[Tomas Bumbulevičius]

Just an idea – see if inPoint of a layer you are timing to, matches the start time of composition. If not – try to take that difference into account .

[Tomas Bumbulevičius]

POTENTIAL SOLUTION:
In case if someone runs into the same issue, try to include files from this (or similar) location on your machine:
C:\Program Files\Common Files\Adobe\CEP\extensions\CC_LIBRARIES_PANEL_EXTENSION_3_12_165-1\jsx

[Tomas Bumbulevičius]

Will, coming from a data-driven automation I would say that setting auto-scale would be easier than figuring out a font size. UNLESS you have restrictions on font-size due to branding requirements.

1. You need a function to define, which, after certain amount of characters would add a line break.
2. Second thing to take into account – whenever a word is longer and assuming its non-breakable into next line, you must downscale the layer when width X is reached.

Last but not least, when doing such calculations, always pre-compose the text phrase before using it. Will save you A LOT of headaches in the process.

[Tomas Bumbulevičius]

In addition to what Robert wrote – if the layer in your comp is “Comp layer”, when you need to update that comp’s duration AND layers lengths as well. Otherwise – you won’t be able to set outPoint of it. Unless, timeremapping is applied to comp-type layer.