Posts by felt_tips

5242 posts
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Helps us moderate the forums
  • Has been part of the Envato Community for over 5 years
+11 more
felt_tips Moderator says


Since CS5.5 Ae has been 64bit and much faster.
I dare to say even faster than CC. I’m working for almost a month on CC now, and it has big advantage with disk cache, but for me CS5.5 still has much better response time. I dunno, maybe it’s just me.

I think there’s some truth in that. CS5.5 often felt snappier. But I think that CC is actually faster to work with. You perhaps don’t notice it so immediately, but the disk cache makes a massive difference (especially if you’re using a dedicated SSD for cache).

5242 posts
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Helps us moderate the forums
  • Has been part of the Envato Community for over 5 years
+11 more
felt_tips Moderator says

CS4 is a 32bit program. Since CS5.5 Ae has been 64bit and much faster.

Looks like your computer’s 32bit too, so maybe time to upgrade.

5242 posts
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Helps us moderate the forums
  • Has been part of the Envato Community for over 5 years
+11 more
felt_tips Moderator says

Yeah had something similar a week ago. It was my own fault, but it’s what motionvids says, universal expressions. When you use sliders always hold alt when parenting it. That way a (1) will appear behind it. Which makes it universal. You can also change things like (“Slider”) in to (1) and it still works. The main reason is that (“Slider”) or any other default name will have a different name in other languages. That’s if you want to do it manual. ;)

And remember to rename all effects that you link with expressions. For instance, change “Tint” to “Tint 1” or “Yellow Tint” or “HelloThere” or anything but the default name, because if you leave it as the default name, when opening into another language version, it will adopt that language’s default name and your expression will fail.

5242 posts
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Helps us moderate the forums
  • Has been part of the Envato Community for over 5 years
+11 more
felt_tips Moderator says

Just a heads-up for those who want to buy SSD: I had serious problem with OCZ ssd-s (SSD OCZ Vector Series), they worked fine for 4-5 months, but then all of a sudden they just broke.

Always go for the pro ones, not the consumer ones. As an After Effects person, you’re loading these things pretty heavily.

I’ve been using an OCZ Vertex 256GB for a couple of years for cache. I’ve heard some people have had problems with OCZ products, but for me – so far so good.

The most recent ones however are the Samsung 840 pro SSDs and I think it’s these I will buy in the future.

5242 posts
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Helps us moderate the forums
  • Has been part of the Envato Community for over 5 years
+11 more
felt_tips Moderator says

The SSD for your system is not only important in terms of loading the OS and reading the programs. The system disk is constantly used by programs for swap space. This is a kind of virtual RAM.

To make your After Effects go faster, still the best thing you can do is install a lot of RAM. Minimum 32GB. More if you can afford it. As much as you can afford in fact.

But beyond RAM, the reason for 3x SSD is as follows. Although SSD is fast, it’s not unlimitedly fast. After Effects will be using disk for three things – reading and writing assets to and from disk, swap space on the system disk (a kind of virtual RAM), and cache – the frames that Ae is constantly caching to disk in the background.

With 3x SSD, it allows you to separate and manage your disks, so you can make sure that your cache is not filling up, eating up your system disk’s swap space and ruining its efficiency, and you can have a whole 512GB SSD dedicated entirely to disk cache – that’s enough to cache an entire project sometimes – the speed difference this makes (along with a lot of RAM) is vast – the time waiting for previews is cut by orders of magnitude.

But also you should avoid bandwidth log jams in reading / writing because by having the IO needs distributed over 3 disks you effectively triple the bandwidth. In reality it’s about diminishing returns – three disks won’t actually give you triple the bandwidth, but computers are multi-threaded these days, so the OS and a program like Ae can be reading/writing to disk simultaneously (I think). If Ae itself is multi-threaded in the future, maybe it will be able to read multiple streams from multiple disks simultaneously too.

When you’re working on jobs where speed and delivery are critical, the $1500 or so that it will cost you to kit yourself out with a similar set-up is peanuts. You may not have noticed if you don’t work under pressure a lot, but it’s those extra few seconds previewing hundreds, if not thousands of times a day that eat up all of your time and break your workflow.

5242 posts
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Helps us moderate the forums
  • Has been part of the Envato Community for over 5 years
+11 more
felt_tips Moderator says


http://www.superbiiz.com/detail.php?name=256GMXSSD1&similar=284 This one’s a great deal and super popular for those interested, probably the one I’m going to order.
I would double think about the brand of SSD. As far as I could see, looks like kingston and samsung are best, but not sure though.

So far I’ve used Samsung 840 Pro 512GB x 2. One for system, one for jobs.

and 2x Vertex SSDs (256GB). 1 for cache, 1 for OS backup.

All seem to be holding up well so far.

5242 posts
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Helps us moderate the forums
  • Has been part of the Envato Community for over 5 years
+11 more
felt_tips Moderator says

For full-on speed, have three separate SSDs…. one for the OS and programs, one dedicated solely to Ae disk cache and the third to store the project and all of its assets on.

Expensive, but it’ll pay for itself quickly enough if you’re working on fast turnaround freelance projects.

5242 posts
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Helps us moderate the forums
  • Has been part of the Envato Community for over 5 years
+11 more
felt_tips Moderator says

This is exactly what I need! Everything works perfectly
Felt, you are a true guru of AE!
I am very, very grateful to you for help that you provide!
-Oleg

I’m happy that it worked, Oleg. Glad to be of help! :-)

5242 posts
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Helps us moderate the forums
  • Has been part of the Envato Community for over 5 years
+11 more
felt_tips Moderator says


Hello Felt !
Thank you very much for the work done! But I think there is a small problem. Try to move Camera POI away from the center of composition and then rotate the Precomp.

I think the problem is as follows… when you use the layer space transforms across compositions, it’s not quite clear whose world you’re using… (or indeed whose comp in the case of toComp etc.) Is it the world of the composition that the expression appears in, or is it the world of the comp containing the layer referred to… i.e. LayerinDifferentComp.toWorldVec()... I’m actually not sure, so I did the following.

Make a 3D layer called Solid 1 in a comp called Comp 1. Pre-comp it moving attributes. Make the layer created 3D, collapsed and call it “Pre-comp”. Inside precomp, make a 3D Point Control effect (I think this exists in CS5.5) and call it “world vec”. On this effect use the expression…

thisLayer.toWorldVec([0,0,1]); 

This makes sure that the toWorldVec calculation is taking place with respect to the world space inside that comp. (which of course is the same as the layer space of the layer “Pre-comp”).

Then, make a Tint effect on the layer “Pre-comp”. On the Amount to Tint property do this…

v = thisLayer.source.layer("Solid 1").effect("world vec")(1); //pick up the world coords from the effect
vWrld = thisLayer.toWorldVec(v);
vecCamToLyr = normalize(thisLayer.toWorld(thisLayer.anchorPoint)-thisComp.activeCamera.toWorld([0,0,0]));
dot(vecCamToLyr, vWrld)>0 ? 100 : 0;

I’m using the dot product, because toCompVec seems to be unreliable with any vector other than [0,0,1]. Not quite sure why. I’d need to spend some time testing it. The dot product compares the orientation of the calculated vector in world space and the vector from the camera to the layer.

I’m being a bit rushed with this, ‘cos I’ve got lots to do, but hopefully this will work. It seemed to work when I gave it a quick test.

5242 posts
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Helps us moderate the forums
  • Has been part of the Envato Community for over 5 years
+11 more
felt_tips Moderator says

Hello Felt !
Thank you very much for the work done! But I think there is a small problem. Try to move Camera POI away from the center of composition and then rotate the Precomp.

Oh yeah… well spotted.

Hmm, I’m not sure why that should be. I’ll have a look at a bit of debug when I have a moment.

The curious thing is that the simple (level I) toCompVec() version doesn’t work in this instance either… in fact, it works exactly the same as my method above. I think I perhaps need to convert to layer space somewhere… I’ll get back.

by
by
by
by
by
by