[Cassius Marques]

You can use soundkeys to generate values according to the waveform (let’s say beat).

and use these values to drive the opacity of a number of layers. For example, generate values between 1 and 100. And through expressions tell one layer to be 100% visible when the value is between 1-25. The other layer to be visible as the value is 25-50 and so on(taking 4 layers as example).

As the number os layers go up, it can get tedious, since it’s one “if-else” expression to each layer, so i’m gessing it can compensate (opposing normal editting) if the audio is long and there aren’t many layers.

[Cassius Marques]

4: is the pixel polly effect.

The rest, Ted precisely summed up.

[Cassius Marques]

What just disappears?

as far as I remember, just go into your text composition, double it’s resolution, and at your main comp, scale the text comp to 50%. DON’T collapse it’s transformations.

Apply the corner pin data first, then adjust the resolution, so things get updated.

[Cassius Marques]

And you judge that by the fact that everything “stops” moving?… I mean, if everything is parented to the same null, including the camera, the null at least will seem to be static, since you are looking at it through the camera. Other layers may vary depending on their position.

Could be this happening?

Have you tried creating a new project with just a null and a camera?

[Cassius Marques]

Are you sure you parented the camera to the null? you said one thing in the thread title and another in your post discription.

or maybe another thing, what kind of wiggling transformation are you making? if it’s rotation, and you null isn’t centered on your camera pov, you’ll have some odd or close to none transformation (null too far away?).

[Cassius Marques]

make sure, in your timeline panel, that there is no 2d layer between any of your six (one for each side of the cube) 3d layers, don’t use photoshop styles too.

[Cassius Marques]

Well, things can get tricky with precomps…

Make sure:
*Your precomp has no effects applied, turning them off wont help…you have to delete them.
*each layer inside the precomp is set to cast/receive lights/shadows
*Photoshop layer styles are not used (right click all layers in the precomp go to layer styles -> remove all) I’ve seen this messing things up.
*In the main comp, watch for 2d layers between your precomp and other layers (e.g. your background) 2D layers, will break the 3D “stack”.

If you had all that done before, then all I can think of is to duplicate every camera and lights into the precomp (and don’t collapse it)…it sucks but on some occasions I can’t seem to avoid it.

hope this helps, good luck.

[Cassius Marques]

thanks for the reply…

anyway, for start, pixel polly has no built in camera at all…it will only work if the camera is perpendicular to the layer. I’m aware of that example in VCP’s site, yet it’s very limited.

And what I mean by forces, is some kind of turbulence field that I can tweak. Like those in Trapcode Particular.