[Mark Von wahlde]

I solved my problem, I think (thanks to posts from this website). The ram preview worked perfectly when I shrank the work area (no more slow audio). I mistakenly assumed that RAM-previewing sound alone would create no memory issues. That assumption caused me to waste a lot of time!

Sound rendering must chew up a lot of memory in ram preview. When I audio previewed only (using the num . key), I could preview the whole layer without any problem.

[Mark Von wahlde]

It previews slow when the only layer in the only composition in the project is audio.

[Mark Von wahlde]

I figured out part of the problem. I rendered the sound after I turned the sound on in the template settings.

So now the problem looks isolated to a preview problem.

How can I speed the sound up to normal speed when I preview?

[Mark Von wahlde]

I figured it out, with your help! Expressions makes the position numbers equivalent and making the arrowhead the child of the parent takes care of the rest.

Thanks again!

[Mark Von wahlde]

Your tip works perfectly if I apply the expression to a paint object that I applied to the same map layer. Thanks very much!

But I want to figure out how to get a shape layer to track the write-on motion path applied to my map layer!

[Mark Von wahlde]

When I use a shape layer, the expressions do an excellent job of making the position numbers match exactly.

Unfortunately, the correct numbers appear to relate to the comp, rather than to the (really big) layer that has the map and the write-on effect on it. The result is that my shape layer’s motion path is WAY off the composition’s display area.

Any ideas?

BTW, this stupid problem has really helped me learn a lot so far!
Thanks