[Steve Roberts]

Yes.

[Steve Roberts]

PS filters don’t work in AE 6.5, unfortunately.

Steve

[Steve Roberts]

How are you viewing it when you see the pause?

– RAM preview?
– rendered file, if so, which codec was used to render it? It should be one with a low enough data rate to play back smoothly from your HD.

Steve

[Steve Roberts]

Have you tried other filters in AE’s effect>stylize menu?

If they don’t work, you could render an image sequence from AE then do a batch operation on the sequence in PS. Quick ‘n’ easy.

Steve

[Steve Roberts]

Sorry, if you’ve already messed with shutter angle, you’re stuck. The number of subsamples can’t be changed, unlike in a 3D app.

Maybe you can do that with the Reelsmart Motion Blur pluginmwhich can be applied to rendered footage, an adjustment layer at the top of the comp, or to a precomp.

Steve

[Steve Roberts]

Your AE comp should have used the DV 720×480 preset size with non-square pixels.

If it then looks too wide in AE, use pixel aspect ratio correction in the comp window. Switch it off when rendering.

That’s one way to do it, anyway.

Steve

[Steve Roberts]

Use the Render Queue to render to a codec that supports an alpha channel, and render to millions+ colors, RGB+alpha.

We generally recommend Quicktime’s Animation codec at 100% quality.

Steve

[Steve Roberts]

This expression changes nothing:
[scale[0], scale[1]]
… it just says “change nothing: make the scale behave as you’ve manually set it via keyframes”, but if you imagine it as a starting point, you’re on your way.

Here’s the one from my last post:
[scale[0], wiggle(15,50)[1]]

It’s saying “the X scale will behave as you’ve set it (keyframes or whatever) but the Y scale will wiggle over a range of 50% 15 times a second”.

The first variable is frequency (15), the second is amplitude(50).
xScale is scale[0].
yScale is scale[1].
zScale is scale[2].
Don’t forget to enclose the whole thing in brackets.

Therefore, the X wiggle would be:
[wiggle(15,50)[0], scale[1]]

There are other, more elegant ways to write the expression, but this one works for now.
Check out “expressing your wiggle” on the Adobe Studio. It’s not really a tutorial, but examples of wiggle expressions.

HTH
Steve

[Steve Roberts]

This expression changes nothing:
[scale[0], scale[1]]
… it just says “change nothing: make the scale behave as you’ve manually set it via keyframes”, but if you imagine it as a starting point, you’re on your way.

Here’s the one from my last post:
[scale[0], wiggle(15,50)[1]]

It’s saying “the X scale will behave as you’ve set it (keyframes or whatever) but the Y scale will wiggle over a range of 50% 15 times a second”.

The first variable is frequency (15), the second is amplitude(50).
xScale is scale[0].
yScale is scale[1].
zScale is scale[2].
Don’t forget to enclose the whole thing in brackets.

Therefore, the X wiggle would be:
[wiggle(15,50)[0], scale[1]]

There are other, more elegant ways to write the expression, but this one works for now.
Check out “expressing your wiggle” on the Adobe Studio. It’s not really a tutorial, but examples of wiggle expressions.

HTH
Steve

[Steve Roberts]

In your situation, you’re transferring video from one app to another for further rendering. You want an intermediate, low-compression (actually lossless) high-quality codec. Use Quicktime’s Animation codec at 100%.

Remember, this is not a delivery codec, so it will not play back smoothly on your computer because its compression is so low, and as a result, its data rate is so high. At the end of the project, choose a delivery codec so you can play back the file for your chosen final medium. That could be Sorenson or Windows Media 9 for the web, DV for tape, or a broadcast codec that your editor uses for eventual broadcast (Avid, media 100, Blackmagic, etc.).

Hope that helps,
Steve
P.S. No need to double-post. 🙂