[Kari Pieskä]

Aha, ok, seems familiar. Two element array and a comma dividing the elements. In your version you just gathered the two dimensions into “value” and + (x,y) with the multiplys are the two elements.

I know I got it, just have to digest it a bit.
Thank you Dan, you’re very helpful.

[Kari Pieskä]

Great, it works!

Just one basic question: why didn’t my version work? It seems to be trying to do the same thing.
Is it because I have to wrap, or calculate the code in one “sentence” or line?

so when I have my version:
transform.position[0]+x*1.5
transform.position[1]+y*1.8

It doesn’t work, because they are not calculated at the same time? Does everything have to be inside one equation?
Like in your version?

[Kari Pieskä]

I think I’m getting the hang of this business. Thanks a lot for the confirmation!

[Kari Pieskä]

Ok, thanks for making that clearer.
You said that use media encoder to make a 23.98 ntsc. Is there a reason i should first import it to apple pro rez, instead of using media encoder via premiere?

Also you adviced to use 23.98 setting on encoder, but then said that when encoding, it will make a 29.98 ntsc version. Was that a typo? Or is it just that ntsc dvd can not be anything else than 29.98 And encoder is doing the work for me?

Thanks for your time, you’ve been very helpful!

[Kari Pieskä]

Thats a good, clean and simple solution. I see now that my idea was changing the scale value to -100. But it was supposed to come down from 100 while the other goes up.
To the 0 problem I’ll just limit the slider between 80 and 150. That’ll work for now.

Thank you, that was a good forward nudge!

[Kari Pieskä]

I also think this could be a nice little thing. Thank you for your responses, I’ll post adobe and also check if Ridleys solution might work for me.

[Kari Pieskä]

This made things a lot clearer for me, thank you.

Now I know I haven’t overlooked anything, it just doesn’t work that way.

Thanks for this clever naming idea. If I understood correctly, I’d still have to copy more comps than just the main comp. So, I can’t use it.

I’m just going to do it the way I’m sure it works. I’ll put everything to the same level and keep on working untill I can do it some other way.

Thank you!

[Kari Pieskä]

Dans expression seems to work. Though it seems simple, I’m having hard time to understand it throughly. But, it works and for now it’s enough.

Thank you both!

[Kari Pieskä]

Thanks Dave for your input, but it wasn’t that.

I noticed that when controlling with the slider, it controls seconds, and I wanted it to control frames. So when I input 1, it gives frame 24. Where is nothing. And now I understand, if I divide the time remap expression with /24, I can start controlling the frames instead.

The time remap function starts giving out frames instead of seconds, because… It divides 1 second into 24 segments and then.. it .. just works?

Good enough for now. Thank you.

[Kari Pieskä]

Thank you for making that clearer.

I did some more searching, trying and erroring and found out this solution for my actual problem:

If I use time remap on the “head” comp, it cracks this case. Then the time remap function is not inside the “head” comp and the comp stays as a base, intact. Then I can control the mouth shapes with the time remap and can copy this comp to as many scenes I want.

After this comes another question. I added a slider effect to the time-remap. It gave out this code effect(“mouthshapes”)(“Slider”)
It didn’t make the slider work. Then I remembered I saw somebody had added /25 in the end of the code, and that suddenly worked. Why is this?
I work with 24 fps, has it something to do with the framerate? I divides the slider effect, but don’t understand how.