[Kieran Lefort]

I’ve had to make a tiny tweak to startPos to make it fit around my own terrible scripting, but that’s done the trick. Thanks so much!

[Kieran Lefort]

startPos = L.toComp(L.anchorPoint) – [w,0]; is giving me an “Invalid or unexpected token” error.

Currently investigating.

[Kieran Lefort]

Haha! Hi, Trent. I’m glad you like it. Most of the stuff I’ve done in expressions has been for dynamic setups like text that can be of any length etc.
The following on the circle’s position almost works:-

rectLeft = thisComp.layer(“rectangle”).sourceRectAtTime().left;

rectRight = thisComp.layer(“rectangle”).sourceRectAtTime().left + width;

easeOut(time,0,1,[rectLeft],[rectRight])

I’m going to try yours now.

EDIT: Forgot to mention that I’ve already separated the X and Y dimensions. I often find Position easier to work with like that if I only need to affect one dimension.

[Kieran Lefort]

A further question for Filip: your example appears to be for one slider. How do I adapt switch(sl) to account for a second slider?

Thanks.

EDIT: Never mind. I’m redirecting the two sliders to an intermediate third invisible slider that I’ll point switch(sl) at.

[Kieran Lefort]

Oooh, this is exciting. I’ve not come across switch statements before. Thank you. I will adapt this to my comp.

To answer your question: depending on the combination of slider values chosen by the user, there are 68 possible outcomes and I need to cater to all of them. I didn’t ask for this stupid thing, I just have to make it!

[Kieran Lefort]

Apologies. This is my first time in the redesigned forum and couldn’t find it.

[Kieran Lefort]

Hi Andrei,

Thank you for that. I’m a little confused about the first one. I’m still quite new to expressions and haven’t come across “?” before. What does it do?

The second version worked quite well. I’m wondering if there’s a way to incorporate the layer’s scale into it somehow.

This might be hard to explain, but I’m going to try. Unfortunately, I can’t share screenshots or snippets because, y’know, NDAs and all that.

Layer A sits in the top 10% of my comp and Layer B is not allowed to touch it, BUT the upper edge of Layer A is allowed to get as close as possible. I hope this makes sense so far.

Layer B, for other reasons, has to scale from the bottom, so the location of its upper edge changes, but that upper edge still needs to be able to get as close to Layer A as possible without touching it.

Is there a way to essentially say “as the scale decreases, the object is allowed to get closer”?

Another way to explain it might be this…

Lay your hand, palm up, on your desk and touch the bottom edge of your keyboard with your finger tips. Now curl your fingers in and slide your hand up until your knuckles touch the keyboard. This is effectively what Layer B needs to be able to do.

My brain hurts just thinking about this. ????

[Kieran Lefort]

Just to wrap this up and to help for anyone else stuck in the same spot, I’ve solved my original issue.

All you need to do is add a Protected Region to the start and end of the Master comp before exporting as an EG template.

So in this case, I had a 5 sec comp and just used the work area bar and Composition > Responsive Design – Time > Create Protected Region from Work Area to apply a 1 sec Protected Region to the beginning and end of the comp.

In Premiere, the resulting MOGRT doesn’t have the usual start/end of clip triangles (I’m sure they have a proper name) in the corners and can be stretched for as long as I want.

[Kieran Lefort]

I think adding Media Encoder into the mix would only complicate things further.

It’s massively frustrating that these people have figured out how to use MOGRTS, but when I sent them a PNG asked me why it didn’t have all the checkboxes and sliders the other stuff I gave them has.

[Kieran Lefort]

Hahaha! If I could, I would. Unfortunately, this has to conform to a strict design.

I’ve found a different animation for this particular project, but I’m still interested in any solutions to this problem as it’s bound to come up again.