[Filip Vandueren]

Import the audio and “animation > Keyframe Assistant > Convert Audio to Keyframes”.

You get a new layer with sliders that hold values corresponding to the amplitude of the audio.

ou can use a simple pixkwhip expression to use this value in the scale of a layer or a bulge-effect etc.

[Filip Vandueren]

As a work around,

you usually get good results if you do this:

create a 3d null layer, copy the position keyframes of your camera.
Then nudge the null a few frames earlier.
set the camera’s auto-orient to “point of interest”
Pick-whip the point of intrest to the null-layers-position.

or use this expression for point-of intrest:

position.valueAtTime(time+0.2)

try different values for the 0.2

The upside of the non-expression methid is that you can’t subtly alter the keyframes or their timing to get more of a “looking around whilst in the cockpit” effect, instead of the “camera bolted to a helicopter’

😎

[Filip Vandueren]

As a work around,

you usually get good results if you do this:

create a 3d null layer, copy the position keyframes of your camera.
Then nudge the null a few frames earlier.
set the camera’s auto-orient to “point of interest”
Pick-whip the point of intrest to the null-layers-position.

or use this expression for point-of intrest:

position.valueAtTime(time+0.2)

try different values for the 0.2

The upside of the non-expression methid is that you can’t subtly alter the keyframes or their timing to get more of a “looking around whilst in the cockpit” effect, instead of the “camera bolted to a helicopter’

😎

[Filip Vandueren]

If you’re using th Pan-behind tools, there can be changes in:
Position, Anchor-Point and Mask-shape,

so be sure to set keyframes for al of those properties.

[Filip Vandueren]

if all layers are 2d,

you can just pick-whip the start and end-points of the beam effect like in the Tutorial mentioned

if the layers you’re pointing from and to are real 3d layers,
then create a 2d layer with the beam effect and use this expression:

targetLayer=thisComp.layer("3d object 1"); // change this to the correct layername
targetLayer.toComp(targetLayer.anchorPoint);

this converts the positions in 3d-space to 2d points.
use it on both start and endpoint with the right layernames

[Filip Vandueren]

if all layers are 2d,

you can just pick-whip the start and end-points of the beam effect like in the Tutorial mentioned

if the layers you’re pointing from and to are real 3d layers,
then create a 2d layer with the beam effect and use this expression:

targetLayer=thisComp.layer("3d object 1"); // change this to the correct layername
targetLayer.toComp(targetLayer.anchorPoint);

this converts the positions in 3d-space to 2d points.
use it on both start and endpoint with the right layernames

[Filip Vandueren]

OK, you’re blowing up two things,
but you want the illusion that the second one forms itself from the debris of the first one:

make the 2 animations as described.

the 2d one, you precompose (moving all attributes into new comp)
On that precomposed layer, enable time remapping.
Select the two keyframes that automaticlally appear, and do a ‘reverse keyframes’

Move the reversed layer a bit forward in time untill you have a nice overlap of the particles and it appears seamless.

[Filip Vandueren]

Forget about it,
😎
No offence taken, Ron

You guys had information I didn’t know of, I had just seen the Keynote and the press-releases.
I think what Phil Shiller said is a surprise because of the longhorn and windows bashing that’s been going on for the last half year at very public events.
Making the machine boot to windows seemed to me as >:-I “highly illogical, Jim”

[Filip Vandueren]

[Ron Lindeboom] “n one move, Apple has made itself into a company — the only one that I can think of — that will be making machines which can run both the Mac OS and Windows (not to forget even Linux, if you wish) in a single box. Not emulation, full OS system software.”

Hi Ron,

I don’t see this happening.
I don’t think that just because there’s an Intel Chip in the machine, they will make it possible.
Just like you won’t be able to run XBOX 360 games on a Powermac G5 (OK, bad example 😉 )

Apple will want to differentiate their products, perhaps with some kind of motherboard innovation. The hype is: they want to make great products, and they can’t do that with IBM’s processor roadmap.
Noone will see it as progress if they start building the same computer as say, Dell with an apple-logo smacked on it.

So, it’s prob. technically very feasible, but Jobs will ‘forget’ to enable that feature.
He’ll have too much egg on his face if he’s going to say:
“oh BTW, now you can run Longhorn on your mac too, isn’t that a nifty thing ?”
😎

[Filip Vandueren]

Well as far as I can tell,
they’re going to ship computers that have an Intel chip in them,
not a cd you can install on your (w)Intel Box.

I think it’s a clever (maybe even late) move, because Apple was becoming a hostage of the PowerPC chip’s failure to keep up with the roadmap.
Come on: drumroll, drumroll: 2.7Ghz! what a dissapointment that was.

However, where will all this leave the mega-hertz myth ?

And what’s it gonna be called ?
not a powerMac, not a G5 ? Ooh they’re going to have fun coming up with a wow-name for that.

how about the inMac 😉