[Dan Ebberts]

That’s interesting. It works for me.

[Dan Ebberts]

You could try this for the number of characters, not counting the line breaks:

text.sourceText.value.replace(/\r/g,"").length

[Dan Ebberts]

You have to work it into the expression that links a property in the precomp to the slider in the main comp. If it’s just a simple link, it could look like this:

C = comp("main comp");
ctrl = C.layer("controls").effect("Slider Control")("Slider");
L = C.layer(thisComp.name);
ctrl.valueAtTime(time + L.startTime)

[Dan Ebberts]

I don’t know of a way to retrieve the selectorValue for a previous textIndex (which is what I think you’d need). I think you’d need some kind of selectorValue.valueAtTextIndex() function.

[Dan Ebberts]

What is it exactly that you want to happen? It’s not clear to mean from what you’ve described so far…

[Dan Ebberts]

Your expression needs to calculate how long ago the trigger event happened. Also, you didn’t mention how long the fade in should take, so I just set it to .5 seconds:

L = thisComp.layer("Punkt");
M = thisComp.layer("Punkt_Maske");
fadeDur = .5;
if (M.transform.position[0] >= L.transform.position[0]) {
  t = time - thisComp.frameDuration;
  while (M.transform.position.valueAtTime(t)[0] >= L.transform.position[0]){
    t -= thisComp.frameDuration;
  }
  linear(time-t,0,fadeDur,0,33);
} else {
  0;
}

[Dan Ebberts]

An expression like this for Audio Levels will turn the audio off:

[-192,-192]

Or, apply the Stereo Mixer effect and apply expressions to the Left Level and Right Level to set those values to 0 (or tie them to a slider).

[Dan Ebberts]

It will probably be something like this:

val = 100;
tolerance = .5
key1 = (thisComp.layer("Control").effect("Slider Control")("Slider").numKeys-1);
keyTime = thisComp.layer("Control").effect("Slider Control")("Slider").key(key1).time;
endStroke = thisComp.layer("Rotating Lines").content("Trim Paths 1").end;
if (time >= keyTime){
  t = time;
  while (t >= keyTime){
    if (endStroke.valueAtTime(t) < tolerance){
      val = 0;
      break;
    }
    t -= thisComp.frameDuration;
  }
}
val

I put a tolerance value in there in case it doesn’t quite get to zero exactly on a frame boundary. You might not need it, but it probably doesn’t hurt anything.

[Dan Ebberts]

I cover that here:

http://www.motionscript.com/articles/bounce-and-overshoot.html#calc-overshoot

[Dan Ebberts]

I’m not sure I understand what you mean, but an easeInOut has zero velocity at both ends, so I’m guessing no.