Ram Preview won't start when Render multiple frames simultaneously enabled

Hello everyone,
I have an issue with rendering AE CC , with my new PC computer in Windows 8.1 pro 64 bit
As the title says , my issue is Ram Preview won't start when Render multiple frames simultaneously enabled. Actually it starts after 8 -30 seconds depending of project complexity and the rendering is slower and skipping frames !
12 cores with 2 GB ram each.
When I disable the option of multiple frames simultaneously render starts ok.
but it's really very sad that I can't use this beast of CPU in full potential. its an new intel i7 5930K , 32 Ram DDR4 2.4 Ghz
Any advice and options would be much appreciated.
Thanks,
Vonzar.
Setup:
Windows 8.1 Pro 64 bit
CPU : Intel Core i7 5930K 3.5 GHz Six Core Socket 2011-3 140W Box
GPU : nVidia GeForce GTX 970 4GB DDR5 PCI-E
RAM : 32GB DDR4 Non ECC CL16 2400MHz Crucial Ballistix Sport
Mother board : Asrock x99 extreme 6

If you have any render or preview problems just turn off MP because, first, it only works with certain specific effects and codecs, and 2, it causes more problems that it solves most of the time. I only turn on MP rendering when I know for sure that it will speed up my workflow.
You should have a multiple of 4 GB assigned to AE and Other apps and an even number of cores. If you are using MP rendering make sure that the number of actual cores used makes sense and that there are an even number of cores assigned to other applications. Most important of all, don't spend hours trying to tweak MP rendering to save a few seconds in a render. Follow these general guidelines and then run a short test to see if it works. If you project involves any temporal effects at all turn it off.
Here is an example of the MP settings for a 4 year old Mac Mini that actually work for some projects, but most of the time it is turned off.
I should say that I can allocate 3 GB of ram per background CPU and still see 2 as the actual CPU's that will be used but this little Mac Mini works better with 2 selected. Setting the RAM allocation to 4 GB drops Actual CPU's to 0
BTW, I use the mac mini to record most of my tutorials because I figure that if I do a tutorial that will run OK on a Mac Mini, then anyone with an adequate system should be able to follow along without any problems.

Similar Messages

  • AE CC=Erratic when "Render Multiple Frame Simultaneously" is Enabled - Preventing OS X Reboot

    AS the header suggests...
    This feature has been experiemental at best since CS4 and it would be awesome if adobe could get it to work properly.
    I have been experiementing with this option since its incarnation and thought that perhaps CC would deal with this but the fact remains that no matter WHAT option I choose,
    and I have tried, timed, testes beyond 30 scenarios with different settings etc etc etc...
    1) In NONE of the scenarios the result is faster than when disbling the option... If for instance enabling for processors AE will render 4 frames REALLY fast... Then take about as long as it takes for singe-frame-render to catch up to commence rendering 4 new frames really fast... And so forth...
    2) In most scenarios AE will end up NOT rendering at all.
    So I can understand that the "feature" is defaulted to NOT Active when installing AE first time
    3) After Multi Rendering i.e. 30 Comps - the Mac needs a reboot, even after purging all memory. As the Mac will act erratically until this has happened.
    The problem is that the Mac wont reboot normally. One has to hold the power button and thus crash reboot.
    The Login window disappears and the a black screen appears with some cryptic messages about "Killing Process" which could not be killed...
    After reboot the Log is gushed full with AE Log Messages stating: 8/23/13 8:30:17.538 PM After Effects[23114]: -[NSMenu menuID]: unrecognized selector sent to instance 0x114d96e10
    It would be really nice if someone would take charge of this app and kill all the erraticness surrounding it.
    New features are grand and all but all the bugs just keep accumulating and that since CS4 !

    1) I tried getting adobe support...
    They set me up with a fony chat... Deceiving to belive I was chatting with a real person... After two lines of chat I knew it was a Machine..
    2) This is a highly known issue and a "bug" which has been reported by 100s of users and that since years
    3) I love AE and the rest of adobe products... Hence me taking the time to publicly report this.
    4) Adobe knows of LOTs of persisting problems but dont BOTHER to fix them...
    If the AE and of TwoLetterApp-Product engineers would take the time the Splash-Screen designer takes to design new App-Launch-Screens with each CS Version, all the apps would be 95% bug free...
    1.1 = Bugs HAVE been reported by so many people
    1.2 = Adobe are aware of their Existence
    1.3 = New Versions Contain Old BUGs (And new Ones)
    If (1.1 == True && 1.2 == True && 1.3 == True)
               adobeFixesBugs.true = False;
    Correct me if my syntax is wrong !

  • A frame failed to render while using Render Multiple Frames Simultaneously

    Hello fellow AE users:
    I've read other threads which deal with this issue, however they don't seem to be exactly what I'm experiencing so I'm starting a new thread. I did do several hours of due diligence by research others' handling of this issue, so I'm not just blindly reposting this question without having done some legwork.
    I'm getting this message when rendering one of my compositions:
    "After Effects warning: A frame failed to render while using Render Multiple Frames Simultaneously. Allocating more memory to the background processes in Memory & Multiprocessing Preferences may fix this problem. (26  ::  142)"
    First, some background on what led up to this. I've built an entirely new system from scratch based on the new Intel 5960X 8-Core processor, with 64GB of RAM on an Asus X99-Deluxe Mobo.Brand new install of Windows 8.1, and brand new install of After Effects CC (latest versions as of this posting) and all of my plug-ins (mostly Red Giant, also all updated to current versions.) I have a new video card in this system (Gigabyte GTX 980 G1 Gaming) however this issue also happened with my old 4GB GTX 680 as well, which was in the original i7-950 system (see below.)
    I've set up Multiprocessing preferences for 6GB reserved for system, 8 CPUs reserved for other applications which leaves "Actual CPUs that will be used: 8", with each CPU having a 6GB RAM allocation. That's 8x6=46G, leaving 18GB free for the operating system, which should be more than enough.
    One could speculate that there is some plug-in that is using too much memory, or something weird with QuickTime or H.264 decoding (the source is one Canon 5D mk II H.264 .mov and one jpeg file). However, this issue did *NOT* happen on my old system, which was 4-core Intel i7-950, 24GB RAM, running the same version of After Effects CC and my plug-ins, and with only 3GB/Thread of ram allocated instead of the 6GB/Thread i'm using here.
    I've simply loaded the old project on the new install and attempted to render. I have not changed any settings. I DID do the thing where you hold CTRL-SHIFT-ALT (or something like that) to reset all of the preferences when loading AE just in case that was the issue.
    So, why would this be able to render using multiple processes on my old box with only 3GB/thread, while it will NOT render on this new system with double that, 6GB/thread allocated?
    Please let me know if there is any other information I can provide that would be helpful to debug this.
    Many thanks in advance for your help!

    Thank you very much for the quick reply, Todd. I'll give that a shot. There also seems to be a problem with the Red Giant Cosmo plug-in. I get Cosmo engine initialization failures, but it's intermittent.

  • AE 2014 Render Multiple Frames Simultaneously issues

    This problem is two fold and I've experienced it for years.  Now I'm using a much faster system that is handicapped by not being able to use multiple cores.  I had hoped that by now this would just work.
    First, when using multiframe rendering AE often hangs attempting to initialize background processes.  As often as one RAM previews this can be quite a problem since it grinds all progress to a halt.  The solution is often restarting AE.  Checking Activity Monitor during this time shows that Adobe QT32 server is non-responsive and a whole line of the AE background rendering processes doing nothing.  I have not found a common element in projects that experience this issue, it can happen just with text on a solid. 
    Secondly, when using multiframe rendering an entire sequence can ram preview, but then disappear as soon as it finishes.  Often after this issue the first issue will pop-up. 
    A little about my setup:
    Late 2013 Mac Pro 8-Core
    64 GB Ram
    2x AMD FirePro D700
    OS X 10.9.4
    AE CC 2014 Updated to the latest patch
    Settings:
    52 GB RAM available for AE
    Render Multiple Frames Simultaneously - ON
    Only for Render Que - OFF
    RAM per CPU - 4 GB (problem persists when set to 6 GB)
    Until this feature actually works reliably I'll have to go back single frame rendering, which is a bit like owning a Ferrari and having a transmission stuck in first gear. 

    warning “RAM Preview needs 2 or more frames” after scrubbing audio in After Effects CC 2014 (13.0)

  • OpenGL vs "Render Multiple Frames Simultaneously"

    My first post on these forums (Like to learn on my own ).  This question(s) accually has to do more with RAM and rendering in general.
    1.) Is OpenGL rendering faster (With a GTX 460) or is Render Multiple Frames Simultaneously faster (Athlon II x3 445)?  I read on one of the FAQ that you can only use one or the other.
    2.) After Effects will stop rendering with at least 10-20% RAM still left over and even call it complete.  Why is this?  I have tried every setting in the book and I can't get it to use any more RAM.  Also in the Render Multiple Frames Simultaneously section I can't get the RAM avalaible for AE over 2.5GB.
    3.) What is the difference between the space bar and the 0 key?  As they both seem to do the same thing, and niether get very far into the movie before stopping.
    My System:
    Windows 7 Home Premium 64 Bit
    AMD Athlon II x3 445 3.1Ghz
    GTX 460 OC'ed
    4GB 1600 RAM
    Small Boot Drive SSD
    This movie is really large (3000x2200ish), but should be able to render further along than it is (Less than 4 sec and 25% left over RAM)...
    Thanks Ahead

    > 1.) Is OpenGL rendering faster (With a GTX 460) or is Render Multiple
    Frames Simultaneously faster (Athlon II x3 445)?  I read on one of the
    FAQ that you can only use one or the other.
    They accelerate entirely different things. Don't use OpenGL for rendering for final export. I leave my preview mode set to OpenGL - Interactive, and that's it.
    > 2.) After Effects will stop rendering with at least 10-20% RAM still
    left over and even call it complete.  Why is this?  I have tried every
    setting in the book and I can't get it to use any more RAM.  Also in the
    Render Multiple Frames Simultaneously section I can't get the RAM
    avalaible for AE over 2.5GB.
    You have 4GB of RAM? Your OS and other software need RAM, too. After Effects using 2.5GB out of 4GB is about right.
    > 3.) What is the difference between the space bar and the 0 key?  As they
    both seem to do the same thing, and niether get very far into the movie
    before stopping.
    Read the documentation:
    "Preview video and audio"
    The 0 key on the numeric keypad starts a RAM preview.

  • Render Multiple Frames Simultaneously

    I'm realy problem with Render Multiple Frames Simultaneously in AE.
    my system :RAM:18Gb - Cpu: Core i7 920 - Gpu:quadro 4000;
    when active  Render Multiple Frames Simultaneously in AE ,system hang .
    what best setting for this option ??

    Like Dave said, there's no perfect setting. It depends on the plug-ins in your normal workflow, the other apps you have open in your normal workflow, the codecs used for your normal footage. Adobe has no control over how 3rd party plug-ins, codecs, and other apps suck up memory so it takes a bit of experimentation. The guidelines are a good place to start. I didn't catch your OS. Anti virus software on Windows Boxes has been notorious for fouling up rendering. I haven't heard much lately, but if you're using MS I'd start there first.

  • Can't Choose Render Multiple Frames Simultaneously

    i'm not even given the option to click the "render multiple frames simultaneously" button. here are my details. any help would be much appreciated.
    Installed RAM: 4.00 GB
    Current RAM Usage: 0.16 GB
    Allowed RAM Usage: 2.50 GB
    Process ID
    Application Name
    Min Needed Memory
    Max Usable Memory
    Max Allowed Memory
    Current Memory
    Current Priority
    2834
    After Effects
    0.40
    4.00
    2.50
    0.16
    1 - High

    That's because you don't have enough RAM to use that feature. You barely have enough RAM to run After Effects at all. I'd suggest at least 16 GB for After Effects work.

  • Why is "Render Multiple Frames Simultaneously" greyed out?

    In Preferences -> Memory & Multiprocessing, the "Render Multiple Frames Simultaneously" option is greyed out.  Any idea why?
    System:
    Win 7 64bit
    AE CC Trial version
    4Gb RAM
    2.5Gb available for AE
    6 core CPU
    Just say if you need more info.

    It might be because you don't have enough RAM for that. You want 2-4 GB of RAM per core of your processor for using multiple cores. And you need to leave 2 GB or so free for the operating system and other computer tasks.

  • What options i should choose for Render Multiple frames Simultaneously?

    Installed RAM: 7,98 GB
    Current RAM Usage: 1,19 GB
    Allowed RAM Usage: 5,98 GB
    Process ID
    Application Name
    Min Needed Memory
    Max Usable Memory
    Max Allowed Memory
    Current Memory
    Current Priority
    6696
    After Effects
    0,40
    7,98
    5,98
    1,19
    2 - Normal
    Program:
    After Effects cs6
    Pc:
    Intel core i3
    RAM: 8GB
    Graphic card: GT440

    AE5+ likes cores & RAM.
    use 6GB as min reserved for OS.
    If footage is greater than 480p (SD television) use 1.5-3GB/thread.
    Not sure which processor you have, if you have a clarkdale processor i3-5xx you are kind of hosed about your only option is to update to 16gb is about the best you can do, if you have sandy/ivy-bridge i3-2xxx/3xxxx update it to i5-i7 and 16+GB of RAM, you'll have a lot more fun with it

  • Error with Render Multiple Frames

    I have this problem before and the only solution I had was to reinstall the WHOLE system and it was fixed that way (but manually install Adobe CC).
    The problem is the next:
    After Effects doesn't render anything if I have "Render Multiple Frames Simultaneously" enabled. If click "Render" and it keep there forever and it never render, sometimes it automatically stop with an error:
    "After Effects Error: Rendering error while writing to file. An output module failed. The file may be damaged or corrupted (-1610153464)"
    This error shows up if I manually stop the rendering process.
    If I disable "Render Multiple Frames Simultaneously" it render without any trouble, but that is not the point, I was able to render using that feature without any trouble before and I doubt I should have any trouble with my current specs.
    When I close AE, multiple "aeselflink" keep running about 15% each one.
    What I'm aware off:
    - I have the latest After Effects version from the Creative Cloud.
    - I have quicktime installed, since It comes in the core of OSX.
    - I have fixed my permissions.
    - I have deleted ALL the Adobe folders from "Preferences" Library folder.
    - I have reinstalled After Effects 2 times.
    - Adobe Media Encoder renders without any trouble
    - I have tried to render .mov, tiff sequences, mpeg, flv, all with the same results.
    Using OSX 10.8.3 with 32GB RAM and i7 processor (4 cores with 8 cores running with hyper threading).
    Thanks in adnvace.
    Here is a video:

    Stock answer no. 1: You have installed a CoDec (or Quicktime Component) that is not safe for MP rendering and messing up things. Could be an audio device driver, something liek a screen recording software or speech-to-text tool, could be Skype or similar even. check that and remove the relevant QT extensions/ diable them.
    Mylenium

  • Render Multiple Frames Headache

    I hope I could get some guidance on optimum usage of Render Mutiple Frames as I have been hitting a wall with little-to-no success so far. I have read all the Adobe suggestions (thanks Todd Kopriva) and I still get failed renders when trying to render multiple frames. I am the guinea pig for the hardware setup for the department. Currently, the hardware is a Lenovo ThinkStation C20X, dual Xeon 6-core 2.4 GHz processors (24 available to AE with hyper-threading), 96 Gb RAM (yes, ninety-six gigs), Win 7 Pro 64-bit, nVidia QUADRO 2000D, AE CS5.5. Our department currently works in an unusual AE project file that is used for display advertising on an unusually-shaped gigantic digital screen in Times Square. Currently, the working comp is 2517 x 4478 which is then nested into two comps for output of TGA sequences that are: TOP = 440 x 3694 and, BOTTOM = 2517 x 554. Most of the working comp space is deadspace as the layout of the signs is comparable to a large upside-down capital letter 'T'. We are currently in transition as the signs are hitting their life cycle and we are refreshing them with a finer pitch-count - in essence, we are doubling the resolution. The new working comp is 5034 x 8956 that is nested into our output comps which are: TOP = 852 x 7386 and BOTTOM = 5034 x 1098. For the most part we do not use "crazy" effects, etc. I have tried rendering multiple frames and have yet to get TOP & BOTTOM to both render without either one or both of them failing using various trial-and-error settings in the preferences; I have limited the # of cores (have yet to try to exceed 8 simultaneous CPUs). I edited the preferences file to allow me to select more RAM per CPU (currently, my pull-down has 4, 5, 6 & 8 Gb RAM per CPU available for me to choose from). Maybe I am going under the false assumption that filling the machine with 96 RAM would allow me to effectively use more CPUs in rendering TGA sequences. I thought that was the whole point. I usually get errors like the following:
    Output To: C:\Sonic RenderTest\Top\TOP_[####].tga
       There is an error in background rendering so switching to foreground rendering after 41 frames completed out of total 900 frames. (26  ::  142)
    After Effects warning: A frame failed to render while using Render Multiple Frames Simultaneously. Allocating more memory to the background processes in Memory & Multiprocessing Preferences may fix this problem. (26  ::  142)
    Didn't think this was possible with 96Gb RAM and 8GB RAM per CPU allocated. Any guidance here is greatly appreciated as I am on the hook with the rest of the department and with my boss as I convinced him that 96 GB RAM would make our lives easier.

    Thanks for the reply Dave. From the projects cited above, one had a QuickTime with Animation codec and the other had H.264. I think we are getting close to honing-in on the issues we are having as it seems that anything with a .MOV as a source file seems to throw AE MP rending for a loop. Currently using AE 5.5. Conversely, MP plays very nicely with projects that do not include a QuickTime file as a source; I have been doing extensive testing using the following settings; 16GB/CPU - 4 CPUs used, 12GB/CPU - 6 CPUs used, 10GB/CPU - 8 CPUs used, 8GB/CPU - 10 CPUs used and 6GB/CPU - 12 CPUs used.
    I guess I still have a few questions remaining in trying to troubleshoot the issue at hand:
    - By any chance are there any MP improvements in CS 6 that may alleviate the issue we are experiencing?
    - I am wondering if I am hitting a bottleneck getting the info (.MOVs) into RAM - to be more specific regarding my setup, in addition to my previous post - My machine currently has two 250GB SAS drives @ 10K RPM that are RAID 0. Disk cache is set to the default settings. We are considering additional drives - thinking one for OS & Applications, 1 for source files and one for output of the image sequences. Any insight to drives, where to set the cache, types of drives (SSD drives fall out of budget for the machine I have - already priced and axed. I think we are considering two more 10K SAS drives as an option)?
    - This one is a longshot, but I thought I saw a crazy post somewhere in my research of this issue saying to get rid of QuickTime. I was always under the assumption that QuickTime was a vital prerequisite for AE. Any truth/validity in getting rid of QuickTIme?

  • More Accurate antialiasing preventing rendering of multiple frames simultaneously after a while

    Hi all.
    I am experiencing inconsistent memory management behavior when rendering my project in AE that prevents me from rendering multiple frames at the same time when some footage items use Accurate antialiasing.
    I have an 8-core i7 MacBook Pro with 8GB of RAM and I'm using AE CS5.5. I am rendering a project with many imported Illustrator layers to keep things nice and crisp. These are in a 3D composition with a camera, DOF, and they are being continuously rasterized. On some of the vector assets I have to set the antialiasing setting to "More Accurate" in the Interpret Footage dialog to remedy some image quality issues. Here is what I noticed when rendering:
    1. When the antialiasing setting on all Illustrator assets is set to "Faster" the composition renders without issues.
    2. I change the antialiasing setting on some Illustrator assets to "More Accurate" to improve image quality. Render Multiple Frames Simultaneously is off. Composition renders for a while, but eventually I get an error: "after effects error : cannot allocate enough memory to antialias file (50:5)”.
    3. To get around the error I instruct AE to empty the cache every 5 frames or less via the Secret menu in the Prefs. This prevents the error from occuring and I can see the RAM being deallocated every once in a while as expected. This lets me render with the quality I need, but is slower.
    4. To speed things up I turn on Render Multiple Frames Simultaneously. I use conservative settings: AE is to use only two cores with 3GB of RAM per core (max allowed). The rendering is sped up. However, I can see that the system's "in use" RAM is steadily increasing with each rendered frame until the computer runs out, at which point AE automatically turns off Render Multiple Frames Simultaneously and starts to render one frame at a time. This doesn't happen whe all vector assets are set to use Faster antialiasing an I can render indefinitely with Render Multiple Frames Simultaneously, but this way I don't get the desired quality. Please note that there is enough RAM for the cores to render several frames, but it seems as if having rendered a frame the system doesn't release or reuse the memory when assets use Accurate antialiasing and goes to use another chunk until there is no more.
    Also, I am outputing to an image sequence.
    Please help me find a workaround for this issue. Thanks!

    Thanks Mylenium. It looks like the underlying problem (cannot allocate enough memory to antialias file (50:5)) has been around for quite some time. I've tried all manner of different combinations of settings and in the end settled on having it render one frame at a time with dumping cache every 2 frames (hey, at least it renders without running out of ram and erroring out). It's just disheartening to know that due to this issue (bug or architecture) AE is only using a bit more than 1/8 of my machine's CPU power. Perhaps AE should have a feature that has it dump all the memory and attempt multi-frame output again every once in a while during make movie.

  • Preview won't start after upgrade to mavericks

    After Upgrading to Mavericks this afternoon (30th Oct 2013, 1420hrs)
    - i face the following problems. (there could be more problems that i may not have found out yet)
    1.
    The Preview application cant start.
    when i double click the prview applicaiton icn, the screen flashes momentarily, but nothing happens. the preview does not start.
    however, when i press the space bar, i can quick look at all the various file type such as *.pdf or *.jpg etc. but i can open it on preview.
    2.
    The same goes to the textEdit application - it does'nt start. the screen just flashes and nothing happens.
    3.
    When i click "Software Update.." from the Apple menu, nothing happens
    Up till now, I have a perfect smooth OS until i migrated to Mavericks.
    Please, can some one show me how can i solve these ?
    I cant open any of my pdfs and any of my txt files since i upgraded to mavericks...
    For you information :
    My current Mac Nook Air is:
    Software  OS X 10.9 (13A603)
    Any assistance from you all will be great.
    Thank you all...

    Back up all data. Quit Preview if it's running.
    Hold down the option key and select Go ▹ Library from the Finder menu bar. From the Library folder, delete the following items, if they exist:
              Containers/com.apple.Preview
              Preferences/com.apple.Preview.LSSharedFileList.plist
              Preferences/com.apple.Preview.SandboxedPersistentURLs.LSSharedFileList.plist
              Saved Application State/com.apple.Preview.savedState
    Log out and log back in. Launch the application and test.

  • Itunes won't start when i plug in my ipod

    itunes won't start when i plug in my ipod touch

    Good catch! Glad you got things working again.

  • RAM preview doesn't save when using multiprocessing

    I'm running After Effects CC on a MacPro 2013. When I normally render a RAM preview, and I finish playing it, the green bar stays.
    When I switch to the multiprocessing feature for RAM previews, after I finish playing it, the green bar disappears.
    I have a large SSD global cache drive being used, so storage of the preview isn't the problem. There's plenty of RAM in the system (64GB). I've tried a number of different multiprocessing settings, and even if I only use 2 processors for RAM previews, they won't save after I play them.
    Is this just the way RAM previews work with multiprocessing, or can I change some settings to fix it.
    Thanks!
    Jerry MacKay
    Littleflick Pictures

    Here's a shot of my current settings. I tried a number of other settings, with different numbers of processors and allocated RAM. But every time I enable multiprocessors for RAM previews, I get the same result (the RAM preview works, until I stop playing it...then the rendered frames are deleted).

Maybe you are looking for