[Arne Münch]

Hi Hector
Thanks a lot for replying.
Sorry for replying so late. I was on a journey for some days.
I actually closed and restarted and tested on another computer.
The script works fine until

var duration = 5344

from

var duration = 5345
or higher, there is this hanging and the bar doesn´t disappear.

Very strange.
Do you know how other people implement progress bars in After Effcect scripts?
Maybe there is a slightly other way which doesn´t cause this trouble?

[Arne Münch]

Hallo Dan

Thanks so much, works perfect again.

Meanwhile I had figured out this far less elegant way;)

I used try{} and ended with the index of the layer.

p = thisProperty;
for (i=0; typeof(layerIndex) != "number"; i++){
    try{layerIndex = p.propertyGroup(i).index;
    }catch(e){};
}

I will change my expression to your way…

[Arne Münch]

Hi Filip
Thanks for the nice approach. Good to know that other people struggle with the same issue:)

For me it really degrades the use of that effect a bit and I will try to use turbulent distort instead when possible.

But when you need to use it a lot in a project here is what you can do:
Create in the “MasterComp” of the project an Null named “Control” withe a slider named “render res”.
Every roughen edges effect becomes the following expression on the scale property of the effect (just copying the whole effect once create to other layers or create a simple preset):

value * (1/(Math.pow(2, comp("MasterComp").layer("Control").effect("render res")(1))))

Then when working and rendering in full, set the full res slider to 0, when working and rendering in half, set it to 1, when working and rendering in quarter set it to 2 and so on.
This way you can easily change all roughen edges effects by a correct multiplier with just one click, to match roughly the desired look.

[Arne Münch]

i think instead of the loop function you need a modulo.

so replace the loopout with something like

s= s%72 – 72

not exacly sure what you really want but this may help

[Arne Münch]

Hi Sandra
This should work:

x = 2; // in Seconds

seedRandom(Math.floor(x*time),true);

[random(1920),random(1080)];

[Arne Münch]

Hi Tomas
Yes indeed. Different render resolutions look different.
I had a 4k project sending HD files to the customer as a preview, they look even different from my half HD preview working space, but the difference was not too much.
For the final render in 4K it really looked bad in my eyes.
Kind of silly. The turbulent distort effect for example does not have that behavior.

[Arne Münch]

thanks, good to know.
Just to make it clear. With your suggestion you mean by hand, dont you?
I guess it is not possible to put the first selected pin via script to the top of the stack, because the script will never know which one is the first selected one?

[Arne Münch]

I hoped I could edit my post, but I can’t
I think I was not clear.
Its just this: When I address selected layers via script, I can simply address for example the layer I selected first by “selectedLayers[0]”

This doesn’t seem to work for properties.
“selectedProperties[0]” doesn’t give me the first selected property, but the first one in the hierarchy.

Is there a way to achieve that?

[Arne Münch]

wow, this compound arithmetic thing i did not know. i will check it out.

precomping will of course also work, but as i am building kind of preset stuff for others to copy comps and change text easily, its not the best option. you would also need to use something like true comp duplicator for not overwriting existing stuff.

[Arne Münch]

yeah, thanks for this, Trent Armstrong, always good to know if something is not possible.
But the solution you suggest means one textanimator for each kerning change you want to apply?
Because I dont see a way to change the kerning of several letters with one textanimator, am I right?