[Dan Ebberts]

I think there’s a text preset named “Word Processor” that already does that.

Dan

[Dan Ebberts]

Interesting problem. The expression in the tutorial was designed with the idea that the “hit” animation runs at normal comp speed, centered around each hit point marker in the audio layer. What you’re talking about here is something different.

You need it to speed up/slow down the hit animation depending on the time between markers in the audio layer. That’s possible to do, but there are some loose ends, like what speed does it run at before the first audio marker or after the last one? How does it know how long the animation is?

It would take a little work, but I think it’s doable.

Dan

[Dan Ebberts]

Interesting problem. The expression in the tutorial was designed with the idea that the “hit” animation runs at normal comp speed, centered around each hit point marker in the audio layer. What you’re talking about here is something different.

You need it to speed up/slow down the hit animation depending on the time between markers in the audio layer. That’s possible to do, but there are some loose ends, like what speed does it run at before the first audio marker or after the last one? How does it know how long the animation is?

It would take a little work, but I think it’s doable.

Dan

[Dan Ebberts]

There aren’t built-in triggers for stuff like that, but you can still do it (but it can get kind of messy). Here’s an example. This expression will scale up a square over three seconds so that it stops at title safe (10/90%).

scaleTime = 3;

if (position[0] > thisComp.width/2){
  xScale = (thisComp.width*.9 - position[0])/(width/2);
}else{
  xScale = (position[0] - thisComp.width*.1)/(width/2);
}
if (position[1] > thisComp.height/2){
  yScale = (thisComp.height*.9 - position[1])/(height/2);
}else{
  yScale = (position[1] - thisComp.height*.1)/(height/2);
}
s = Math.min(xScale,yScale);

linear(time,0,scaleTime,valueAtTime(0),[s,s]*100)

Dan

[Dan Ebberts]

There aren’t built-in triggers for stuff like that, but you can still do it (but it can get kind of messy). Here’s an example. This expression will scale up a square over three seconds so that it stops at title safe (10/90%).

scaleTime = 3;

if (position[0] > thisComp.width/2){
  xScale = (thisComp.width*.9 - position[0])/(width/2);
}else{
  xScale = (position[0] - thisComp.width*.1)/(width/2);
}
if (position[1] > thisComp.height/2){
  yScale = (thisComp.height*.9 - position[1])/(height/2);
}else{
  yScale = (position[1] - thisComp.height*.1)/(height/2);
}
s = Math.min(xScale,yScale);

linear(time,0,scaleTime,valueAtTime(0),[s,s]*100)

Dan

[Dan Ebberts]

Is it possible that you have the name column set to “Source Name” instead of “Layer Name”?

In general, you need to line everything up and create the parent/child relationships before applying the expressions. There are a lot of ways to go astray here. The expressions will only work as-is for arm pieces with the same starting orientation as the example. Working in a non-square pixel comp will also undoubtedly mess things up.

Dan

[Dan Ebberts]

Is it possible that you have the name column set to “Source Name” instead of “Layer Name”?

In general, you need to line everything up and create the parent/child relationships before applying the expressions. There are a lot of ways to go astray here. The expressions will only work as-is for arm pieces with the same starting orientation as the example. Working in a non-square pixel comp will also undoubtedly mess things up.

Dan

[Dan Ebberts]

I think you’d have to convert your database to some kind of text file and the parse it with the script, but it all sounds doable.

Dan

[Dan Ebberts]

The only way I can get that error message is if something in the parental chain of the camera has at least one scale dimension set to 0.

Dan

[Dan Ebberts]

Rectangular pixel issue?

Dan