[Mylenium]

[Muhneer] “Thanks for the fast reply,

But isnt there something i am missing, i mean there must be some
kind of stop(); for an expression. What if i rotate something with steps
of 10 each time. And i want to let it wiggle its position at frame 40. Then it will never stop rotating and it will rotate and wiggle instead of only wiggling and not rotating.

Am i thinking in the wrong way ? do such things have to been done with sliders ?

Thanks!”

Your logic isn’t quite correct. All expressions will respect animation values if you tell them to. Unlike julian06 suggested you don’t even need to fiddle with conditional statements. All you need to do is add your wiggle to your existing rotation and then keyframe the slider value.

Ex:

wig_amp=effect(“Wiggler”)(“Slider”);
wig_freq=effect(“Wiggly”)(“Slider”);

[rotation+ wiggle(wig_freq,wig_amp)]

There can be no stop() procedure in an expression because it kinda defeats the purpose – the expression would stop to evaluate as a whole and ultimately be do nothing. Think of it like a car – you can’t move it if the motor is out, but you can put it on idle if you wan’t it to function but not actually move.

Mylenium

[Pour Myl

[Mylenium]

Maybe you used an clip rendered from AE and containing a project link. This sometimes happens and is usually nothing to worry about (it happens if one itme in your current project has the same name as an itme stored in the project link). Other than that I can’t think of a reason that would cause this unwantedly.

Mylenium

[Pour Myl

[Mylenium]

You need to apply an expression that triggers opacity or whatever effect you wana use. Dan Ebberts provided some code for this. Try to find it in one of last year’s posts. You could also try Buena Software’s Depth Cue. It contains a plugin for this type of stuff.

Mylenium

[Pour Myl

[Mylenium]

You need to apply an expression that triggers opacity or whatever effect you wana use. Dan Ebberts provided some code for this. Try to find it in one of last year’s posts. You could also try Buena Software’s Depth Cue. It contains a plugin for this type of stuff.

Mylenium

[Pour Myl

[Mylenium]

You should try TMPEG (free, but difficult to tame) or the standalone version of the MainConcept Encoder (which is basically what Encore and After Effects use). It will run as a 14 day trial. I’m sure you could find other options if you do a little searching.

Mylenium

[Pour Myl

[Mylenium]

Are you sure you have chosen them on the install? They will be in the “functional content” and “library” folders respectively.

Mylenium

[Pour Myl

[Mylenium]

Use the masked layer as a matte on top of the actual layer. Mask points themselves cannot be natively tracked in AE. you need scripts or other workarounds for that. One can be found here:

https://www.crgreen.com/aescripts/

Mylenium

[Pour Myl

[Mylenium]

[Jeff Bellune] First of all, Memorex and Fuji are crap.

I wouldn’t agree on that entirely. Memorex DVD+R are actually quite acceptable, but their -R isn’t that great. With Fuji it’s just the other way around. That aside, I completely agree on the burning speed being way to high. We never exceed 4x and apart from 1 raw medium out of 100 that has a manufacturing flaw we never have problems.

Mylenium

[Pour Myl

[Mylenium]

Like I said, use square pixels. If you convert them to anamorphic in Photoshop, you “freeze the squeeze” (wow, it rhymes!). You see, working with video ratios is an illusion more or less. Whenever you have a circular shape, you have effectively less pixels covering the same area along the X axis as you have in the Y axis. Only the playback/ display device will “unsqueeze” them, but based on the “baked” pixels (it won’t animate the tyre as you do in AE, it just happens that at different times the pixels are in such a position that when stretching them out they look round again). This is not entirely technically correct, but I think you get the point. In your case the problem is that due to the fewer pixels in the X axis AE will try to stretch your wheel and make it look round, but since it needs to “invent” pixels by scaling up, it’s always slightly off.

Mylenium

[Pour Myl

[Mylenium]

Ooops, you won’t have much luck. Error 2 means there is something completely screwed, but it’s not specifyable… (yeah, it’s a damn generic one right after error 1 [Could not start AE] ;o) ) A good point to start – again – is your graphics card and its drivers (OpenGL problems?). Does AE crash on startup or only after you try to do something? If it’s on startup, try to watch the launch process and remember until which point it loads. This might give some clue.

Mylenium

[Pour Myl