AE CS4 - why such poor RAM preview on my FAST machine?

Hi all, I just installed After Effects CS4 - I have a smokin fast mchine: quadcore Zeon 3.20 GHz, hyperthreading turned on, nvidia quadrofx 3800 with current driver, 12 GB DDR3 RAM, windows 7 64bit ... can you PLEASE help me troubleshoot a problem: even on the simplest compositions, a moving picture or a moving piece of type, the RAM preview stutters along, the current time indicator hops along at a choppy pace, images in the frame dont look like they're moving smoothly, and all i get is about 6 seconds of RAM preview ... seems to me that I used to get better performance on a MUCH MUCH slower machine under windows XP ... i have looked around the forums and seem the advice on multiprocessor options and the like, but nothing I do seems to help ... do any of you have any advice for me to improve my performance??? if you have any questions about my setup or preferences, let me know, I will be on this until I get what I expect out of my (otherwise incredibly fast) machine

Hi Todd, thanks again for your reply ... FYI, I bought the FX3800 for Avid editing, for which it is the qualified video card, and supports distributed processing in the Avid along with my DX HD hardware BOB - I had hoped it would work well with After Effects, too, but I do understand the Adobe is very transparent about the fact that, as long as your card has OpenGL support, probably best to sink your $$$ into more RAM or faster CPU .. but to stay on topic, I am just very stunned that I am not getting better playback with my system ... I have the most recent Nvidia drivers ... I have 2 NEC 2490WUXi2 each connected through DVI-D to my video card, each runnign at its native 1920x1200 res, 59 hertz ... the programs I have installed are Adobe CS4 Production Premium, Win7 64bit, MS Office 2007 Enterprise, latest version of Quick Time, Media Player version 11, and NERO 9 ... you dont think that one of these video player apps (like media player or QT) are messing with my screen performance do you? what about Nero 9, have you heard any compatibility or display problems associated with this app? would unistalling any of these programs be a troubleshooting technique that you'd attempt?
Finally, when you say "an issue with a bottleneck of drawing to the screen" what do you mean exactly? 'cause this kinds sounds like a goood description of what I am seeing ... what might be the cause of such a bottleneck, I am willing to try anything ...
Thanks, sir, for your reply!
Derek Reid
Trader Multimedia Inc.
www.tradermm.com
Date: Tue, 30 Mar 2010 21:46:43 -0600
From: [email protected]
To: [email protected]
Subject: AE CS4 - why such poor RAM preview on my FAST machine?
Just one thing to cut down a frequent misconception:
Your nice graphics card doesn't do much for After Effects performance.In fact, trying to use OpenGL for rendering (including rendering of previews) can cause problems.
I recommend turning OpenGL rendering off for all but interactions. I.e., choose the http://help.adobe.com/en_US/AfterEffects/9.0/WSAF696587-2D81-42e2-B248-4C5C2B7D3614a.html and turn off http://help.adobe.com/en_US/AfterEffects/9.0/WS3878526689cb91655866c1103a4f2dff7-79e8a.htm l. OpenGL is not compatible with Render Multiple Frames Simultaneously multiprocessing.
I'm not saying that OpenGL is your problem. Rather, because you mentioned your nice graphics card, I just had to stress that you need to forget about that with regard to After Effects. It's not really relevant.
It may be that the jerkiness is an issue with a bottleneck of drawing to the screen. (I don't know, but it's possible.)
Your hard disk being too slow wouldn't be an issue with RAM previews, since the frames are all cached in RAM.
>

Similar Messages

Why is my RAM preview only playing the first 7 seconds of my video?

When I try to RAM preview my animation so that I can hear audio it only displays the first 7 seconds and then repeats. The entire clip is 35 seconds long.
Help please!

See this:
http://forums.adobe.com/message/1916125
"FAQ: Why does RAM preview only play part of my composition?"

Why such poor performance?

Hi. New Arch Linux user here, but not new to Linux (I'm no expert though, I've merely tinkered with it here and there over the past 7 years or so)
I have this old laptop that I've installed Arch on in order to give it some new life. While it's old, it's not exactly ancient either, and it's a system on which I thought Linux would run well on, at least for modest web surfing/paper writing and the likes.
Dell Inspiron 8200
Pentium 4 1.6ghz
1 GB RAM
Nvidia GeForce4 Go 440 graphics (64MB) -- using Nvidia 96xx driver, because based on what I read it seems open-source 3D drivers aren't usable/stable yet
Using XFCE4 for a desktop environment.
I'm having an issue with performance on the system. I check with top and it shows Xorg using about 20% of the processor idle. That goes up when I'm moving windows or if I make top refresh faster than the default. It seems like pretty much anything having to due with X redrawing hammers the CPU. The biggest offender would be AbiWord. I was working on a document and scrolling takes the CPU usage all the way to 100%. I thought it might be compositing, so I turned it off and performance is even worse. Xorg uses about 30% CPU idle and there is about a 2 second delay when I try to minimize/maximize a window. I have no idea why it would actually run better with the compositing on. Of course, the performance with compositing isn't impressive either.
Also, although this may be expected since general 2D performance seems bad... 3D/OpenGL performance is terrible. I installed a few games and they run like crap. For instance, SuperTux runs at about half speed at best. I am almost certain that it isn't that the computer's too weak for it, because I remember running it a few years ago on my Pentium II/450. I even tried some games in WINE and they lag as well (I know WINE imposes a bit of a performance penalty but these games never really pushed the CPU too badly under Windows XP)
I'm not sure if I misconfigured something or if this laptop just hates me. Any suggestions?
EDIT 4/1/2011 - I'm not bumping this thread because of its age, but if any searchers in the future come across this, I'd like to note that I discovered this issue is not linux-related. My laptop has a faulty heat sensor that is underclocking the processor to about the equivalent of a 233mhz Pentium when the temperature rises just a tiny bit. However when it does this the operating system will still report that it is running at the full 1.6ghz, as it's basically just overheating protection that is kicking in. The system thinks that it is going to catch fire or something and freaks out. It is apparently a common flaw with these machines as they age. I am able to maintain decent performance by keeping the temperature low (of course this means running the fans all the time on low as a minimum, but I'm finally replacing this in a few months so I am not concerned about its well-being) If it does underclock the processor for some reason, pressing Fn+Z will temporarily return it to the original speed and it should stay there providing the temperature doesn't rise again.
Last edited by MrKsoft (2011-04-01 18:00:05)

lagagnon wrote:
MrKsoft wrote:I've run a very usable Ubuntu/GNOME/Compiz based system on my P2/450, 320MB RAM, with a Radeon 7500 before, and that's even older hardware, with bulkier software on top of it.
I'm sorry but I find that very hard to believe. I work with older computers all the time - I volunteer with a charity that gets donated computers and we install either Puppy or Ubuntu on them, depending on vintage. On a P450 with only 320MB almost any machine of that vintage will run like a dog with Ubuntu and Compiz would be a no go. It would be using the swap partition all the time and the graphics will be pretty slow going.
Hey, believe it: http://www.youtube.com/watch?v=vXwGMf141VQ
Of course, this was three years ago. Probably wouldn't go so well now.
To start helping you diagnose your problems please reboot your computer and before you start loading software show us the output to "ps aux", "free", "df -h", "lspci" and "lsmod" so we can check your system basics. You could paste all those over to pastebin.ca if you wish.
Here's everything over at pastebin: http://pastebin.ca/2005110

Why such poor support for iCal?

On the first two pages of this forum, only TWO questions are marked as answered (My own question has been viewed 36 times - no responses at all). Many of the questions refer to fairly serious 'buggy' behaviour by the iCal application. By doing a little Googling, I have found many similar complaints elsewhere, going back several years.
It seems that Apple has a rather unsatisfactory application here. Why is this not being fixed? Does anybody know of any impending major updates that will produce a calendar app without the kind of problems encountered on this forum?

These forums are user-to-user. Apples involvement is limited to providing the platform and monitoring for adherence to terms of use (which your post probably violates!).
Marking of questions as answered is something that has to be done by the question poster. One of the great frustrations of answering questions here is that original posters frequently fail to give any feedback at all on answers, so other visitors don't know if the answer could help them, and the helper doesn't learn how to give better help.
As for unanswered questions, you must remember that the answerers are just ordinary users. If I, for example, had seen your original question, I would probably have decided not to answer it (I have now answered it with a request for further info) as I don't use invitations myself and so have limited knowledge with which to help you. If someone answers a question, and is not able to help, there is a smaller chance that someone who might know the answer will look at the question.
As for bugs, two points. First, there are millions of users for whom iCal performs satisfactorily. Second, this is not a bug reporting site, so if you don't use the OS X Feedback site, or better the developer site, it doesn't register on the developer's radar.
AK
Message was edited by: Austin Kinsella1

Why such poor streaming on ATV3 with Netflix?

I have the latest ATV3 hooked up via ethernet to my airport extreme with 60 Mbs download speeds. There is a lot of banding and compression artifacts streaming 1080p material on Netflix. Itunes HD, Vimeo HD material along with Trailer App HD material look fine with no such problems. When watching the same Netflix HD material on my Boxee Box, I see no such banding or artifacts. Seems to be issues still ongoing streaming Netflix material on the ATV.

Well, I don't know how to explain it any better, I feel I put it pretty straight forward, however here's an example from a small lookbook. The red is not accurate, everything else is.
The only thing I've ever come up with is possibly some 'Out of Gamut Warning' option that I haven't found to disable, twenty_one. However, no, I do know Lightroom VERY well, just not 100%, maybe 95%. When Soft proofing for monitor, all colors in the example are within gamut in sRGB, AdobeRGB, and my calibrated monitor color space.
I've almost exclusively run into this with NEFs, I've used Lightroom with Canon, PhaseOne backs, Leaf backs, Fujis, and more. Oh, and I am a pro, and have worked a wide range of clients from Harper's, Elle, and BEBE, to RED, Playboy and more -not to toot my horn, but to establish I'm not a green.
I'm on Lightroom 5, current build.
Typically I stay with the Adobe Standard Profile or Portrait, but none seem to help this particular issue.
Not sure what sort of NEFs Nikon produced in '76, but I to have been with Adobe since Photoshop 2. I'm viewing on a calibrated monitor in good viewing conditions. I don't print, this is most commonly an issue with lookbooks and catalogs when they need perfect color, the issue remains when viewed on other monitors. I've also tested images on my studio's Eizo CG276 and run into nealry exactly the same results (nearly in that there are pixels of difference, however it's a different size than my normal editing monitor).

Why such poor quality saturation and contrast with NEFs?

Having used Lightroom since the beginning, I'm at my wits end.
Ever since Lightroom 1, I've noticed that ACR does a really -really, bad job handeling NEFs when you push contrast and saturation, especially in regards to certain colors (reds, yellows, and blues).
I thought for a long time it was my side, originally using a consumer DSLR (D50), but it affects every NEF I've ever imported, from any Nikon body up to D4.
The saturation gets chunky with little effort (even after attempting to correct via the Calibration panel), the same when pushing contrast. Not pushing it beyond the files' limits, just a simple s-curve.
When importing other RAW formats, this is less often the case.
It's really frustrating to be able to rely on Lightroom doing and adequate job 75% of the time, and it makes me look bad in front of clients.
Has/ does anyone else run into this? Does anyone have any ideas, or tips as to avoiding this?
I really hate the UI of C1, but since it has started implementing cataloging I am getting more and more enticed to switch over completely, as even when I push things waaay too contrasty or overly saturated the results are still miles better.
I'm an unabashed Adobe fanboy with fond memories of the introduction of Levels (Oooooo) back in the day, but I'm feeling I've been pushed to a point where I have to default to whatever program does a better job handeling RAW info, and ACR is not cutting it at a professional level.

Well, I don't know how to explain it any better, I feel I put it pretty straight forward, however here's an example from a small lookbook. The red is not accurate, everything else is.
The only thing I've ever come up with is possibly some 'Out of Gamut Warning' option that I haven't found to disable, twenty_one. However, no, I do know Lightroom VERY well, just not 100%, maybe 95%. When Soft proofing for monitor, all colors in the example are within gamut in sRGB, AdobeRGB, and my calibrated monitor color space.
I've almost exclusively run into this with NEFs, I've used Lightroom with Canon, PhaseOne backs, Leaf backs, Fujis, and more. Oh, and I am a pro, and have worked a wide range of clients from Harper's, Elle, and BEBE, to RED, Playboy and more -not to toot my horn, but to establish I'm not a green.
I'm on Lightroom 5, current build.
Typically I stay with the Adobe Standard Profile or Portrait, but none seem to help this particular issue.
Not sure what sort of NEFs Nikon produced in '76, but I to have been with Adobe since Photoshop 2. I'm viewing on a calibrated monitor in good viewing conditions. I don't print, this is most commonly an issue with lookbooks and catalogs when they need perfect color, the issue remains when viewed on other monitors. I've also tested images on my studio's Eizo CG276 and run into nealry exactly the same results (nearly in that there are pixels of difference, however it's a different size than my normal editing monitor).

Ram preview is short?

Why is Ram preview so short? i get maybe 2 min of preview time at 1/2 res 1092x1080 on a new Mac Pro with 32GB of Ram! It seems if AE is out of RAM it could render to the SSd or any hard drive and playback 30 min of footage but no i only get 2 min, anyone know if this camn be fixed? I have disk Cache enabled and set to 72GB, I thought this was suppose to fix this?
Thanks, Mark

Hi Rick,
This has been an issue since I cam remember, CS4 possibly earlier, i am using the latest CC now and on a new Mac Pro i don't see why this is still a limitation.
Mentioned above I have disk Cache enabled and set to 72GB, Caching on the 1TB internal Mac Pro SSD. If I render out the clip full res it only uses 6GB of space and I have the comp set to 1/2 res. It is a simple panning background made up of about 20 PS layers, very simple, I don't know why that would make a difference, isn't Ram preview just rendering the frames out to ram? If there is movement it renders a new frame right? and there is movement in every frame. CPU is not my issue, it is the length of the timeline Ram preview will render (not how long it takes). Why can it Ram preview 30 min of footage if needed to my SSD and play it back? It seems like it would be simple!
Thanks, Mark

After Effects CS5.5 - Very Serious Performance Issues w/RAM Preview

My system: Windows 7 Professional, two Intel Xeon X5650's, 12GB RAM, and a NVIDIA Quadro FX 4800.
Problem: RAM Preview in CS5.5 gives me less than 2 fps (yes---two frames per second). This is even with the most simple of compositions. I created a 1080p 23.976 project with two simple solid layers and keyframed position and scale values for one of them with no other effects on either solid. RAM Preview gives me 1.8 fps.
I still have AE CS5 installed and it gives me solid, predictable results with RAM Preview. When I create a similar test project inside CS5, it creates the RAM preview almost instantly and displays in proper realtime (23.976 fps).
My settings for both CS5 and CS5.5 are similar (and I have tried many variations in my attempt to fix this problem).
PREVIEWS
Fast Previews: Adaptive Resolution Limit 1/4
Enabled OpenGL and both sub-options for OpenGL enabled.
MEMORY & MULTIPROCESSING
RAM reserved for other apps: 4GB
I have tried various settings for Multiprocessing, all of which results in the same less-than-2 fps RAM Previews. Currently I have MP'ing enabled with 1.5GB allocation per background CPU and the actual CPU's used is 4. Again, no matter what I set it to, I get the same performance issue.
On my screen magnification ratio setting, I am using 25% and my Resolution/Down Sample is set to quarter. On my preview tab, I have tried setting my resolution from the default of "Auto" to "Quarter" with no difference.
In summary: On the same machine, AE CS5.5 RAM Preview offers terrible performance; CS5 RAM Preview offers great performance.

Under AJA Preview there are check boxes, one for "Video" and the other for "Preview." I've checked and unchecked them both and I'm still getting poor RAM previews. No matter what I have toggled, I seem to get between 1 and 2 fps for my RAM Previews.
I am not currently using the AJA card for anything. I will consider uninstalling it if this might possibly solve my problem. It's just a hassle to install and uninstall cards on a per need basis.
If there are any other thoughts, I'd love to hear them. At this point, I'd do just about anything to have realtime previews back.
The machine I'm using, by the way, is an HP z800 with Windows 7 Professional, two Intel Xeon X5650's, 12GB RAM, and a NVIDIA Quadro FX 4800. It has the following installed: CS5.5 Production Premium, AVID Media Composer 5.5.2, and AVID DS 10.5.1 (among other programs).

Unable to RAM Preview in CS6?

Why I cannot RAM preview in CS6 with the same settings I've used in 5.5? In fact I can only RAM preview when I disable After Effects Multiprocessing.
Am I missing something here?

I'm having the same problem. It just stopped working mid-session. It was just after I'd been playing around with seeing how the image quality changed between Ray Traced and Classic, so I'm thinking maybe there is a bug there. If I start a new project, render a few frames of a test comp without MP, then switch MP back on, it works. However, if I load up the project where it originally stopped working, that doesn't work at all, no matter what I try. Might there be some sort of flag/setting in the project file that is to do with Ray Traced/Classic options that has become corrupted? I'm probably clutching at straws, but if there is a way to fix it, whether an official bug fix or tinkering around I'll give it a try to avoid re-building my project (or having to wait for long RAM previews...).
Mac OS X 10.7.4
3.39 GHz Intel Core i7
16 GB 1333 MHz DDR3 RAM
GeForce GTX 550 Ti 1536 MB

Eventual audio RAM preview problem...

AE CS3 (with Production Premium): When I include audio in my RAM previews, at first, the previews are instantaneous (as they are supposed to be), but after 15 minutes or so, AE starts to take a long time to RAM preview any comp that has audio in it. When I disable audio for RAM preview, everything goes fast again. If I shut down AE, and start again, everything is good again - but the same problem starts all over again and eventually, I have the same problem with audio. This problem happens even if I occasionally purge the memory cache. Any ideas?
I have 4 GB of RAM.
I have enabled the 3GB switch.
Win XP Pro.
Dell Precision T7400 - Dual Quad core.
Lots of HD space.
Nvidia Quadro FX 570.
Sound Card: Creative Soundblaster X-Fi

See "FAQ: Why does RAM preview only play part of my composition?".

Random Flashing Color Bars within Quicktime Files during RAM Preview Only

I have been getting random color bar flashes within quicktime files in AE CC during RAM previews using Multi Processor rendering. Files other than .mov seem to not have this issue (although I have seen it twice...though it may be due to quicktimes in the comp). The rendered output using MP rendering is completely fine. If I turn off MP rendering the ram preview is fine. The source material is coming off a RAID 5 at 600-800MBs, I have moved the footage to a local SSD and a standard spindle drive with the same results. I have tried everything.....disabling GPUS in preview, disabling Fast Adaptive Preview, Disabling Disk Cache, Adjusting MP settings and RAM usage per core, disabling hardware accelleration of interface, adjusting gpu memory useage, every codec under the quicktime wrapper including uncompressed codecs, updating Blackmagic drivers, updating quicktime, limiting how many processors Windows 7 64bit can see, resetting AE preferences. I even installed After Effects clean on my second boot drive for gaming with no plugins or other apps, same issues. Have discussed this heavily with tech support at Adobe and they are working on it for a few days before getting back to me. When I got off the phone the tech was of the mind that I have too many cores for the Quicktime codec to handle.
My system :
Windows 7 64bit
Dual Xeon E5-2687W: 16 Physical cores and 32 cores with Hyperthreading
32GB 1866 DDR3
3xNvidia GTX 680 4GB cards
SSD boot and seperate SSD media cache drives
8TB internal SAS RAID 5 using a ATTO card
Blackmagic Deckline Extreme 3D+ card
Any help or thoughts would be greatly appreciated as this is a huge boon to my workflow. Having purchased a $12K system for grading and rendering....not being able to use the ram preview in AE with multiple cores is a huge inconvenience.

Here is the requested taskmanager screenshot. As my test comp only has a single duplicated quicktime in it, it renders too fast to really catch the AE instances doing anything. So this is from a heavier comp. Settings are as pictured above with 3GB per core using 8 total cores of the 32. It did flash the bars.
Here is what I tried tonight:
- Followed the link on Quicktime having trouble with too many processors. Using MSCONFIG I dropped the recognized Processors to 21, 16, and 8 and tested all three settings. Each had the flashing bars issue. Again as usual, at random, sometimes 3 previews before showing up, sometimes the first preview run. I have noticed that the ram previews that take a little longer seem to be clean. Then sometimes it seems to fly through the preview, grabbing large chunks on the green progres bar above the timeline, or many little chunks very quickly....these are usually the preview runs that will show the flashing bars. I make a point of purging the cach between each one so it doesn't remember, plus I have disk media cache off, but sometimes I get the feeling it's remembering bits.
- I removed all the Quicktime Components from the QTComponents folder and tested it. Flashed the very first run without any quicktime components.
- Followed the Firewall or TCP instructions and made sure everything was allowed through ZoneAlarm. However I could not find the QT32 Server listed anywhere or figure out how to add it. No matter because I closed and force quit all of the firewall processes as well to make sure. Still flashed.
- I followed all the advice on the landing page for Quicktime-related problems
- I also tested out ram previews again thourougly with the same clip but converted to a Tiff sequence. No matter what I tried there was never any flashing in the ram preview with tiffs.
- I also re-tested the clean render output. Made a ram preview with the flashing bars, then without purging rendered it out to a quicktime file and there were no bars at all in the rendered output. I even tried duplicating this render output 6 times in the render queue and rendered them all at once. Not a single one had a flashing bar frame. I even played all 6 1080P uncompressed 4.2.2 YUV 10bit pieces off the RAID with no dropped frames or hichups.
- Killed every process in the taskmanager but for essential windows processes and the flashing bars were still present
- Set the priority to Real-time for every AE process including Adobe QT32 Server, Dynamiclinkmanager, and all the AE processes. Still flashed.
I am now considering disabling two of my GPUs in the device manager. However I'm a bit worried about disabling the wrong one and being locked out. Any thoughts? Is the computer to powerful for some process somewhere? Why only in RAM preview? Thanks again.

Poor RAM management in Photoshop CS4 - need help!

I have done numerous hours of research over the years only to give up and come back to this subject later on. I will try again!
I must ask: is there ANY way to get Photoshop CS4 to automatically flush used RAM after closing image files? I'm tired and annoyed of CS4 eating more and more RAM without freeing anything after an image has been closed. An image shouldn't still eat up memory when it isn't even open anymore. It seems to be terrible RAM management of the program itself and how Adobe has forgotten to write that little snippit of code to clear the RAM after an image has been closed.
I know this is not because of:
Cache levels
Setting too large of a saved history state; purging history cache or any kind of cache still never frees RAM
A lack of updates; I have been up to date with CS4 very punctually as they were released
The computer I am on; this poor RAM management has been around since CS2 and it's the same on the last 4 computers I have used
Does CS5 still do this too?

Your historically conditioned to believe software apps should swap data a standard way. The way your using the system is probably not the most effective processing for your workflow.
- I have hundreds of TIFFS that take 60-120MB each in processing, and 8gb of RAM. The more total RAM actually usable that I can use the better. How the heck can using less of what is actually available RAM enhance my workflow? Standard are standards for a reason. The ink industry for printing is non-standardized and people waste $3-5 billion+ a year only increasing on unused ink that is still remaining in their cartridges, because there is no standard way of manufacturing ink, filling cartridges, or monitoring how much ink is actually left in a cartridge. I'd love for more standards in more markets. Unless natively stable, all other programs on my computer work flawlessly with said demonized traditional methods and standards, even in high bandwidth applications a hell of a lot more intensive than Photoshop CS4 will EVER be. Currently people keep disregarding the fact that in my situation CS DOESNT FREE THE RAM. CS4 is balloon. Balloon inflate. Never deflate even when emptied. Overflow into other rooms of critical OS space where balloon shouldn't be when it fill the room full. How many analogies must I give? Must I use sign language? Binary?
You don’t have enough experience with these topics. This is actually a
true statement. Most companies with systems large and small have to
think about what it costs to process specific jobs. If one in a thousand
jobs swap, a decision must be made to know how much it would cost to
retrofit a very expensive environment to keep that one job swap from
occurring. Most times it is better to let the swap happen for this
non-mission critical item than pay $50,000 to upgrade all systems.
I said NON EMERGENCY SITUATIONS. Emergencies are once in a while. You're repeating what I said like a parrot, but in different longer sentences with more words telling me I don't get what I'm talkinga bout. You're missing the full picture of what I am actually saying. That 1 in 1000 overflow would be exactly true in my situation with 7GB used, but it's not. Why not? Because the CS4 balloon will not deflate itself or reuse the empty space inside the balloon when it's needed, and the OS isn't given back any of the empty space to work with to know it doesn't need to page anything. In turn CS4 is going to try and scratch too when the OS is telling it that is has no more RAM left when indeed it does, but its hiding it in its own reserve balloon from itself. If a company needed just 700MB more room and either they spend $50k to upgrade to that, or get CS4 to release some space once in awhile, they'd sure as hell bother Adobe or write their own mod to force CS4 to release unused allocated RAM to get it.
Self inflicted only because I want to push the limit of what is actually usable on my machine, not some 'safe zone' with high tolerance. My system is tuned for a fine line of performance and I know what it can hande. I know what it uses and it does not spike usage for random OS operations. It can handle 7GB to 7.2GB of RAM of freely used RAM to one active program if it needs that big of a workspace to work. If CS4 isn't going to reuse the hollow areas in that balloon, then that's not my fault. My OS can handle the fine tuning, and CS4 is what cannot, obviously, since it can see that much RAM but not use the last %10 correctly.

Why is it when I use light leaks in after effects why does it stop When I'm in the middle of a ram preview?

Why is it when I use light leaks in after effects why does it stop when I'm in the middle of a ram preview? also any idea on how render as well and and how to increase ram?
Please answer me back when you can
tthanks

FAQ: Why does RAM preview only play part of my composition?
Getting started with After Effects (CS4, CS5, CS5.5, CS6, & CC) | After Effects region of interest
Mylenium

Why do RAM previews get slower towards end of comp?

I was just wondering, why do RAM previews and even updates in the comp. monitor when playing with effects get slower as you get deeper into the comp.? When i first begin a comp everything is extremely fast but when 2 to 3 minutes of the comp is completed everything slows down and each frame takes like 4 or 5 seconds to load. Do you think it's a matter of RAM?

No. Whatever issues you have are specific to your setup like calculations on effects accumulating or multiplying. This can easily happen with particle effects or temporal effects like Timewarp - the later the time in the comp, the more particles or frames have to be processed. You have not provided any relevant info, anyway, so there is not much point to making generic claims based on such vague and incomplete info. We know nothing about your system or even what version of AE you use, so aprdon me, this is pointless.
Mylenium

After Effects CS4 freezing with RAM preview audio?

Firstly, I'm on a mac. This problem just started a few hours ago after I made some system updates. When I hit preview in a comp with audio it runs through the frames, then locks up when it would normally start playing. I just get that dang spinning beach ball of doom. If I turn off the audio on the layer, it previews fine. I believe the only think I had updated when this problem began was upgrading to quicktime 7.6.2. Would this effect the RAM preview? Since the problem, I've updated AE to 9.0.2 and OS 10.5.7 with no change.
Anyone come across something similar?
Thanks

Mmh, well, seems ominous, but quite obviously QT is somehow involved. do you use any dedicated video hardware such as AJA or BMD cards? If so, the QT update may have introduced an incompatibilty with their drivers... Even if not using any such equipemnt, definitely check your QT system control panel. Also use OnyX to flush your QT components cache. They may just need to re-initilaized to function properly. Short of that I'm not aware of such issues, but anything is possible. If the issue persists, using Pacifist and downgrading your QT may be the only option. What Mac are you on exactly?
Mylenium

AE CS4 - why such poor RAM preview on my FAST machine?

Similar Messages

Maybe you are looking for