-
Whats reccomended for Optimizing the Ram Preview specifically.
-
Premiere is a realtime application versus AE and AME which are not. If you launch Premiere while rendering via AME, AME will take far longer because Premiere will grab the CPU resources instead of leaving them for AE. AE is also a background render application and not realtime so it will just take far longer to Render out. However Premiere will not have as many resources available including ram and disk access and would be effected since it’s a realtime application due to the realtime playback.
If you want the most performance with ram preview and render queue in AE then set the CPU left for other applications to 0. If you need to use Premiere then while it’s render queuing then that can always be changed if the performance is not enough to playback realtime. However setting CPU’s to sit idle when you only have 4 to 12 threads is not a good idea since AE requires the most processing and ram for it’s work and is the largest time sync.
Eric-ADK
Tech Manager
support@adkvideoediting.com -
Multiprocessing only takes longer when your ram preview is for very short segments and you have allot of CPU threads such as a dual Xeon. If you only have 4 to 12 threads then multiprocessing will definitely speed ram preview up most of the time unless you don’t have enough ram for the system.
Eric-ADK
Tech Manager
support@adkvideoediting.com -
Sorry Eric, my point was that setting the available CPU’s to zero assumes that while After Effects is rendering there are no other processes competing for CPU time.
I frequently start a render then proceed to work on something else.
-
No I listed above as to why you can set it to zero and still continue work. I did not assume that AE is the only application launched and even stated why and how it works. What I said was Premiere will be effected by far more than just the CPU processing and the system has to have all of the resources available for Premiere to function in Realtime. I never set the CPU to anything beyond 0 left and most of my clients work on other projects while AE is rendering. I wasn’t the one assuming here. I have tested this far more than most and am fully aware how it works.
Eric-ADK
Tech Manager
support@adkvideoediting.com -
Interesting, this has not been my experience at all. When I’m rendering a file that After Effects estimates will take a a few hours, I’ve found that when switching to work in Final Cut or similar the performance in the foreground application slows down when there are fewer CPU’s available for other apps.
I’m on a 12 core MacPro with 64GB of RAM, OS 10.8.5 if that’s relevant.
-
The application slowing down will always be the case because the CPU’s are getting interrupted by the higher priority application. Scheduling is then deciding which threads are getting handled by what cores and when. However setting half the CPU’s to left over doesn’t change this that much. That means there are far less CPU threads for Premiere to start with since it’s the higher priority app. However allowing the OS to moderate the threading based on Priority puts cpu processing threads to what is required for the higher priority application. Windows manages this fine. If OSX does not then that is specific to the GCD in OSX.
Eric-ADK
Tech Manager
support@adkvideoediting.com -
Well Getting Back to the Original Problem, I have looked at and tested everything everyone has been saying and their have been multiple opinions.
Keeping in mind my computer specs I mentioned in the original post. I have actualy found that allowing 4GB of ram for other applications and totally turning off multi-frame rendering has been the fastest results for my RAM preview. I don’t really get it but that has made significant improvements on my preview speeds.
What I am doing is just RAM previewing like 15 seconds or so at a time to see if the animations I made are how I want them and then I scrub forward and keep going. turning off the multi-frame rendering has made that happen like 5 times fast.
And since I export via Adobe Media Encoder to H.264, the render Queue speeds are irrelevant to me.
-
In order for Multiframe processing to work ideally you need enough ram per thread to render complete frames per thread so essentially you have 8 frames rendering at 1 time instead of 1 or 2. If you don’t then there is far more CPU moderation involved as data is constantly re-cached to ram so the CPU threads can finish frame data. This add’s significant latency to the process besides not rendering as many frames at 1 time as the system has threads. In this case it’s better to single frame render where you only need enough ram for 1 or 2 frames while the threads split the data processing those few frames at any one time. This uses far less caching which can improve speed with lower amounts of ram. The trade off though is the render queue times are vastly longer. In your case that is not a concern but that is the trade if you don’t have enough ram to support that many threads with multiframe rendering on.
The short segment time has to do with AE launching AE processes for each thread. That takes time for the OS and CPU to provision resources and start the process.
Eric-ADK
Tech Manager
support@adkvideoediting.com -
I realize I’m around a year and a half late to the conversation but I thought you might be interested to know… lately I’ve been having some relentless crashes while rendering. Couldn’t figure it out for the life of me. Checked everything… researched… no dice. I thought it was weird cuz I’ve got a 4GHz i7… a fairly new GTX 770… and 16 gigs of ram.
I also had 0 CPUs reserved for other processes.
I said what the hell… I’ll give the other processes a couple of CPUs and see what happens. Hasn’t crashed since.
Reply to this Discussion! Login or Sign Up