Touko Maksimainen
Forum Replies Created
-
app.project.item(1).layer(“”).property(“Position”).getSeparationFollower(0).setValue=value;
0 for x, 1 for y, etc.
-
Actually, that is indeed viable, thanks!
-
That is indeed how it works. However, I have here a master comp where user inputs data. The data is then distributed over a series of other comps via expressions. So by design the sourceText parameters of the slave comps are never used. The only way I can see getting around this is to rewrite the whole thing using not expressions, but scripting instead.
-
That only works if you have a known default value to test against, which is unfortunately not the case here.
-
Another issue I find is that if you have text in a template comp that is brought in from another comp via expression, you can’t override that text with this system, which is a big letdown. We have a complex set of comps that use text and parameters from other comps, and I thought this new feature could be used to implement instancing within the system, but it seems it can’t be done.
-
Todd, what are your thoughts on just turning Hyperthreading off? It seems a bit questionable to reserve 3 gigs of RAM for virtual processors? (ie. allocating actual resource to imaginary instance). I read it somewhere that 20% is the maximum performance gain from using Hyperthreading in the first place, it doesn’t seem reasonable to buy twice as much RAM just for that?
Thanks to Hyperthreading, the number of cores After Effect sees can be so high that if you want to make sure all processes get the recommended 3gb you’ll have to spend an insane amount of money for RAM. Some of the latest hardware can field up to 32 logical cores so you’d have to get 96gb of RAM for that. (Instead of 48 with HT off)
For many of us that is not affordable, so wouldn’t it make sense to switch off Hyperthreading completely so that you are able to allocate your limited RAM to where it matters (the physical cores.)?
-
There are two solutions I’ve found for this problem. One is to increase the keyframe distance which at least makes the problem less common. The second is to use Apple H.264 codec which produces error-free video but is generally not as good and versatile a codec as MainConcept is.
I think the problem is with MainConcept codec but it’s only readily visible on still footage.
I use TMPGENC to encode my videos, which uses MainConcept like After Effects does. Sorenson Squeeze supports Apple H.264.
-
Well, I’ve run into this often, and it took me a long time to figure out.
AE doesn’t allow bezier handles for linked multi-spatial properties (Anchor Point, Position, Orientation, Scale). Your options are to either try to make do with the speed graph or separate the property dimensions.
Right click on the property and click Separate Dimensions. Now if you for example applied this to Position property you would get position x, position y (and position z if 3d) which you can then animate separately using the bezier handles.
It actually isn’t AE’s fault, it’s just many other programs separate the dimensions by default. If you were allowed beziers with multi-spatial properties you would run into problems like the gimbal lock.
-
I’ve found that After Effects standard issue tracker does a horrible job at small motion. You can have footage with the best contrast, zero noise and motion blur and your track will still produce jitter with small (sub-pixel) motion. Andrew’s method will probably help but if you are using CS4, it’s a much better idea to use the bundled Mocha tracker instead.
-
Sorry, but it seems like the only easy way is to get the Middle Eastern edition. Otherwise your only options are limited to various tedious work-around such as the one you just described.
I’ve also tried exporting as vector pdf from Word but it didn’t work out. Don’t remember why anymore though.