Problem with Adobe After Effects CS5.5

[pranjev]

Hi, as import no matter what video into the program, and as I start to apply effects on it, Video is blurry, pixelated run and play very blurry, the picture pixelated is seen in the squares and degraded, as put on pause or stop for a while, then fix and release-same again.

Can anyone help to deal with this problem?

Thank You!

[poisondeathray]

You might have the composition viewer not set to 100% size, or 1/2 or quarter pixel . Or perhaps you might have 1 or more layers set on "draft" mode.

You need to ram preview in order to "see" in playback in realtime with all effects appiled

[pranjev]

The review is nothing setting set to 100% and 1/2 or quarter pixel. I did a review in RAM mode, but then the video begins to play from the Middle, and don't play all, play only part of it?

[poisondeathray]

Hi, as import no matter what video into the program, and as I start to apply effects on it, Video is blurry, pixelated run and play very blurry, the picture pixelated is seen in the squares and degraded, as put on pause or stop for a while, then fix and release-same again.

You say "as I start to apply effects on it" ; but what happens if you do not apply anything? Is the video blurry when you do NOT apply effects to it ? ie. if you just import into the composition, but do nothing

What about exporting a still image or video, uncompressed - is quality still poor ?

Did you check the layer switch for draft mode ?

The ram preview might be limited by your hardware (e.g. not enough memory). Set the in/out points for the preview if you only want to see a section

[pranjev]

If you do not apply effects, and do nothing-then everything is normal, problem is gone. The problem occurs when you apply a filter auto color and began to change the parameters of the "Temporal Smoothing". The rest of the time i don't have a problem. The video is not blurry when effects have not been applied on it.

I don't know how to check the key layer for draft mode. I tried the same with uncompressed video - I don't have a problem.

I have 64 bit Windows 7 Ultimate SP 1. Do you think I can have a limit of a RAM Preview, since I have 4 GB RAM memory? How can I check if I have a limit on the RAM Preview?

[poisondeathray]

So is the problem ONLY with auto color with high temporal smoothing ? If you lower the temporal smoothing value, problem goes away ? What about other effects ?

Yes your RAM is very low for AE, so you can only preview short sections before you run out of memory.

[pranjev]

I wanted to say that the problem appears after the filter is applied Auto color, while changing the values of temporal smoothing. the rest of the time the problem not appears.

Please check out the video I did, and you'll understand what I mean:

[poisondeathray]

That's normal - the longer the period of time for the smoothing, the more calculations it has to make. Look at the orange bar beneath the preview in the composition window - it's in the process of calculating when you see the pixellation. Leave it for a few seconds until it's done, and it will become full resolution (the orange bar will complete and disappear). A faster computer will make the delay shorter (things will be calculated faster).

The green bar in the timeline means the calculation is done for that state and cached in ram. The more ram you have, the longer the ram preview you can have

[pranjev]

This means that if you have more RAM memory, this problem will be solved?

If I have 8GB RAM memory will be solved this problem?

This is the maximum RAM for my motherboard supports.

[poisondeathray]

This means that if you have more RAM memory, this problem will be solved?

If I have 8GB RAM memory will be solved this problem?

This is the maximum RAM for my motherboard supports.

No, it's a CPU problem. It just takes time to calculate all those frames. When you average 10 seconds, for a 30FPS video that's 300 frames it has to calculate through - that can be very slow. More RAM just means longer RAM preview - you still need to calculate before it's cached into RAM. If you don't have enough RAM, the old calculated sections need to be re-calculated each time you go back. Newer AE versions have better caching and can cache on HDD as well as a secondary cache level, and cache each state

[pranjev]

Which of the newer versions of After Effects would you advise me to try? I want to see if there might be some significant change, even a little is it.

[poisondeathray]

Which of the newer versions of After Effects would you advise me to try? I want to see if there might be some significant change, even a little is it.

It won't change very much for this, because the problem is CPU for that filter. It's not GPU accelerated either, not even in the newest version

Newer AE versions have better caching of various states and filter settings if you have enough storage space. So they use a secondary cache in addition to the RAM. It "recalls" various states. e.g. if you set the filter setting to 5, then change it to 6, each time, each frame it has to recalculate = very slow , right ? If you go back to 5, it has to re-calculate everything in the old AE versions everytime you make a change. If you change your mind and turn the filter setting back to "6", it has to recalculate everything yet again. If you add a second or third filter, or disable them, each time , each change it re-calculates everything from scratch. But in the newest CC 2015 versions, it caches the calculations when set to "5", so the swap back is almost instantaneous, it doesn't have to re-calculate everything again or each time. Once the "6" is finished calculating, that is stored too. Every old calculation state is cached. It doesn't have to re-calculate old calculations, even in a multi stack filter chain - it draws the old calculations from the cache and starts to work only on the changed or added filters. You can imagine this makes it many times faster when tweaking various filters, but it also takes up lots of storage. Most people put the AE cache on a SSD, so it's closer to "instantaneous" when recalling from the cache, but even a HDD makes a big difference. But this caching doesn't help the initial slowdown (the 1st instance calculation), that is still the bottleneck and is CPU limited on that filter