Optimize render time... how ?

Hi everybody
The story I'm going to tell you is very dramatic.
I have the following configuration :
Windows 7 64 bits
i7- 3770k
Motherboard : Asus P8Z77-M PRO
GC : Geforce GTX 660 2GO
Ram 16 go
1 SSD 240 go
1 Seagate barracuda 2TB Sata 3.5 IN 7200T/M
I precise I use CUDA.
When I work on a composition a bit complex (for ex : with 1 noise reducer effect), render time are very long. I'd say After Effects take 3 seconds to render 1 frame... It's too long for me. It makes me cry.
I'd like to know if this time depends on my hardware. If it does, what could you advice me to change within my computer ?
I precise that when After Effects renders these videos, I open task Manager and I can see that only 3-4 go de ram is used ; and the UC is increased to 30-40% only...
Can somebody help me ?
Thank you in advance,
Regards
PS : sorry if there are mistakes in my english, I'm french !

Perfectly normal. Effects processing takes time, especially when temporal logic is involved. It requires linear processing in a single thread. Do a search on this forum, we have discussed this in detail a hundred times. And 3 seconds are "too long"? How do you ever hope to do anything in AE? Even 10 minutes per frame can be totalyl normal on complex effects...
Mylenium

Similar Messages

IMovie events and projects on external HD but optimizes every time, how do I stop this?

iMovie 11 v 9.0.9 I have the events and clips on an external HD and every time I start iMovie it "optizimizes" then "processing Events". How do I stop this repetitive and long process?

It might be worth trying a complete uninstall/reinstall of iTunes and related componentry, as per the following troubleshooting document:
Removing and Reinstalling iTunes and other software components for Windows XP

Is 12hrs a normal estimated render time for a 10min video?

I'm trying to make visuals for my music, which consists of 4 pictures, 4 adjustment layers (each with 1 evolution keyframe from start to finish on each), & 2 audio spectrums. Being brand new to AE, iss 12 hrs a normal render time upon exporting?
I'm running on an i7-4820k, Windows 7/64bit, 32GB of RAM, & a Geforce GTX 760.
Any answers/questions for me would be great!!

Ah, your lack of experience won't help, I'm afraid. You cannot intuitively decide how to optimize rendering without lots of experience. AE just doesn't work like Photoshop or FCP or Illustrator. You could, hover, transcode your mp3 to aan uncompressed codec and save some processing. You could copy your Audio and Audio Spectrum layers and put them in their own comp and render that out as prores422. Bring the rendered movie back in and replace all those layers with the movie. Adjustment layers are sexy but misleading. You probably are using them incorrectly, most beginners do. Fractal noise can be a rendering slug. Render that as a movie if you can.
Prerendering is basically just looking at your comp and deciding what effects/layers are not dependent on others. Precomposing is a process of grouping layers together to form a desired output that can be fed back into the main comp for a specific effect or filter. The classic example is drop shadow on a rotating object. If you just apply the drop shadow to the rotation object, the shadow is applied before the object is moved and the shadow moves with the object as it rotates, destroying the illusion. If you precompose the rotating object and apply the shadow to the precomp, the movement is rendered before the shadow is applied. It's complicated but you get the hang of it after a few epic rants.
Try to have fun. AE is unbelievably cool.

Macbook Pro 2012 vs Retina Render time difference

Just purchased the 13-inch: 2.9GHz dual-core Intel Core i7 regular macbook pro.
With my budget of a $1700, should I get the 13-inch: 2.6GHz with Retina display Intel Core i5
instead for render work like After Effects? how big of a difference is render time??

Just purchased the 13-inch: 2.9GHz dual-core Intel Core i7 regular macbook pro.
With my budget of a $1700, should I get the 13-inch: 2.6GHz with Retina display Intel Core i5
instead for render work like After Effects? how big of a difference is render time??

Premiere-After Effects Dynamic Link render times vary wildly after minimal composition changes

Here is something strange that happens a lot to me.
I'll have a sequence in Premiere Pro CC 2014 that is entirely or largely an AE comp that I have dynamically linked. I'll use a specific case as an example, but it's happened with various projects.
In this most recent one the visual (but not audio) of my Premiere sequence is one AE dynamically linked comp of about 90 seconds. It's more or less a fancy slide show- some photos with moves, some text, motion blur, masking, maybe a few filters. Fairly basic stuff as far as After Effects goes.
Anyhow, I like to render the sequence in Premiere and then watch it down with music to see if the timing works and make adjustments from there. That's my usual workflow. The strange thing is that when I render, the render times can vary tremendously. With this particular project, one time rendered in about 2 minutes in Premiere. I watched it down and I noticed a spelling error, which I fixed. Just changing one word of text in AE. This, of course, causes the entire linked comp to need to be rendered again in Premiere. This time when I go to render, it took about 20 minutes and it only got about 70% of the way through. A huge difference and all I changed was a couple letters, which shouldn't impact how intensive of a render is needed. What I usually do is cancel the render when it takes that long, then quit Premiere, reopen, and render right away after I open. When I do this, after the application restart, the sequence will then render in the faster approximately 2 minute duration. Almost invariably this is true.
So I end up quitting and restarting Premiere a lot to get the faster render times. But of course that's annoying.
What is going on here?
I know that some might have critiques of the workflow and watching in Premiere and the fact that one letter change forces the entire sequence re-render. I know I could break it up and there are ways around that. But I am not interested in such critiques. My work flow actually is quite efficient when the 2 minute render time happens. Just not when it takes 10x more than that for the same thing. Why are there these huge render time swings?
My guess is that some cache gets filled up, so when the application is just started, and the cache is empty, the render works much better. But I really do not know.
Help please.

There is currently a bug that causes Dynamic Link performance to be poor when the main After Effects application is running. (The underlying issue is that the main After Effects application is sending many more messages during Dynamic Link than it needs to.)
The easy workaround is to quit the main After Effects application when using Premiere Pro to process a dynamically linked After Effects composition.
This bug is fixed in an update due to be released in less than two weeks.

Help with configuring Qmaster for optimal render times.

I have a 6 machine Qmaster cluster. All machines in the cluster are PowerPC based and I have set up the cluster manually through Qadministrator. I personally like to have everything set up manually so no changes can be made for any reason to this cluster. I have processed a 2.5GB video in the cluster and in an Intel based Mac Pro.
Using Compressor, my output for the file is H.264 for iPod video and iPhone 640x480. The source was placed on an external Firewire 800 drive and destination is to the local disk on the Intel machine.
For the cluster, the source, also from the external Firewire 800 drive, is connected to the cluster controller, which has full read write access to all nodes in the cluster and is not a node in the cluster itself, just set to be the cluster controller. ( I saw this setup on a Qmaster setup page here, http://www.eventdv.net/Articles/News/Feature/Distributed-Network-Encoding-with-A pple-Compressor-37923.htm ) Also, I am using the same output settings, H.264 for iPod video and iPhone 640x480, and output is being written to the cluster controller local disk.
Once the batch is completed, it takes 23 minutes to render the video in the cluster as opposed to 25 minutes on the Intel machine. Not the difference in render time that I hoped for.
Here are the specs for the machines,
Cluster nodes:
1.6 Ghz Powerpc g5 1.25 GB
1.8 Ghz PowerPC G5 4GB
Quad 2.5 Ghz PowerPC G5 2.5 GB RAM
Dual 2.0 Ghz PowerPC G5 2.5 GB RAM
Dual 2.0 Ghz PowerPC G5 6 GB RAM
Dual 2.7 Ghz PowerPC G5 2.5 GB RAM
Cluster Controller:
Dual 2.0 Ghz PowerPC G5 2.5 GB RAM
Intel Machine:
2 x 2.26 quad core Intel Xeon 6GB RAM
Now I know these machines in the cluster are old but all machines, except for the cluster controller, have gotten fresh installs of Leopard 10.5.8, all relevant updates applied and fresh installs of FCP6, Qmaster and Compressor. I still cannot figure out how to speed up rendering. Is there something in this setup that I am doing wrong or is it the limitations of the old hardware. In theory, it should break up this video into segments across all machines in the cluster but it doesn't. The chunk of segments are sent to the Quad G5 and yes I have enabled multiple cores in the Qmaster prefs pane. So I figured i'd only enable 2 instances on the quad core machine and then it started to send segments to other machines but render time is still slow.
Also, even though all machines had read/write access to each other, I would scroll through the log files and see that it could not read the segment from the source media, but I could clearly see the activity light flickering.
After all of this trial and error, I still cant get the render time under 23 mins for this video.
If there's anyone out there with some advice, it would be much appreciated. Also, I forgot to save a copy of the log file, so my fault on that one but I will post once I get a chance to get back to working on that cluster.
Thanks.

Update:
So I have been able to get the cluster working. I've used Compressor and have the source media located in the shared folder that the controller mounts as cluster storage on all of the machines. The problem that I can't figure out now is why the cluster won't read the source media from any other location. I've read through Qmaster documentation and the permissions are supposed to be bypassed when you are using Qmaster.
I have both the mac HD and clusterstorage drives mounted for each machine, on each machine. Still, the cluster won't transcode the file unless I drop the media into the shared folder first. Every sharing option I could think of has been enabled. I have enabled file sharing, appletalk, set read & write permissions for each drive in each machine for all users and It still won't work any other way.
It just seems impractical to have to first copy the source media to the shared folder mounted by the controller since all locations on each machine have been totally opened up.
If anyone has some advice about this issue, it would be greatly appreciated.

Help - Getting slower render times with AE CS6

Hi everyone
Wonder if anyone else is getting as described?
I have a 3m37s project which is predomnantly motion graphics using live shot footage (.MXF files), Illustrator and a few JPGs.
In CS5 AE I get render times which average around 45mins, so I thought I'd see how quickly CS6 could crank it out by - as you can see I'm getting times which are in excess of 2 almost 3hours!
The project contains a few 2.5D moves as well as tiny bit of Trapcode 3D Stroke
I have mentioned on this forum that I'm having the Error 5070 problems with start up and Ray Trace is unavailable but these times seem seriously wrong to me.
Mac Pro 3,1 (2x 2.8GHZ)
20GB RAM
OS 10.7.4
NVIDIA GeForce GT8800
NVIDIA Quadro 4000 both on GPU Driver 207.00.00.f06
CUDA Driver 4.2.10
All files are on a 2TB drive (7200rpm)
Rendering to a 1TB drive (7200rpm)
Corsair SSD 60gb Cache drive
As an observation when I watch the frames counter ticking over, CS5 seems to steadily work it's way through the render at around less than a frame a second, CS6 seems to crank out 2-6 frames then hold for 30secs before working on another batch. It crawls to a halt near the end.
Can anyone offer any help or advice?
So far I'm not having a great time with my CS6 transition
Thanks
Rob
Message was edited by: Bokeh Creative Ltd
because of a Typo

Thanks Rick - Yes what confused me was that it only took 45mins in CS5 even with MP 'on'
Still having no joy with Ray Tracing though, even though I have a Quadro 4000 card, I get the 5070 error on start up. Any ideas?

Xtremely long render times

I am doing a very simple project that seems to be taking longer than it should. I'm taking Sony HDV 1080i clips, about 10-15 minutes long, and adding an elapsed time window, and a time code reader window to them for a research client. 3 layers, no editing, no sound. I have place the HVD file in it's native sequence, so there's no rendering until I add the filters from FCP. Then, it takes from 11-15 hours to render these sequences, then another 2 or so to export the files as h.264 for the client's use. That seems really long to me. I made a compressor setting, h.264 1920x1080, 25000kb, so I might avoid the long render time, but that took about 9 hours. Am I missing something? I usualy work with DVCPro HD, and notjhing I do, with lots of laysers take that long.

Not looking over your shoulder, I'm making a few possibly invalid assumptions.
The HDV is your first major problem. You should transcode that to ProRes422LT on ingestion and build your sequence in that format. The files are much larger but they're uncompressed. Well, they're compressed but they don't require decompression before they can be rendered.
Exporting to H.264 from PRLT in 1080 is four to six times realtime depending on your system's specs. I't seight times on mine.
Placing your HDV sequence into a native sequence only means the base layer doesn't need to be rendered to be played. But the HDV must be unpacked, frame at a time, to be rendered with effects and that takes two to six times realtime. You say the clips are 15 minutes but you don't say how long the sequence that takes 15 hours to process is.
bogiesan

I get 120 hours render time on quicktime h.264 usualy setting

My Computer :
Processor : Radeon HD graphics APU A10-5745M 2.10GHz
Ram installed : 16 Go ( 15.52 usable , 12go on AAE CC )
Graphic cards : R7 m260 and HD 8610G
My project : 10 min long , 3 audio spectrum with glow and a '' bass shake fx on all of them ''
Usual render time for 1 audio spectrum 5 min long song and bass shake FX = 30 min , Same setting
My setting Quicktime H.264 , Lossless sound , Best quality .
I try to render and i alway get between 80 and 120 hours ... make no sense , it should be max an hour . theres 20k frames to be rendered .
Now when i installed media encoder it does not help it and still is Sooooooo long to render .... im not sure how to fix this without losing quality

It seems to be helping quite a bit , but the render is still up at like 41 hours so .... i don't understand ? does having multiple audio spectrum and a bass shake effect on all of them for 11 minute increase the render time by so much ? my first video was quite fast even on h.264 ? it doesnt look that fancy to me lol

AME render time 2x SLOWER in CS6 than CS4

I just upgrade to CS6. A good portion of my projects are very long continuing professional education videos for streaming on the web. AME4 could render an 8-hour video into baseline, H264 700x290 in about 12 hours. (I know, strange, custom frame size. It's for side-by-side speaker and overhead presentation.) I opened the same CS4 project in CS6. It was resaved for the new version. I also created a new sequence and copied the files over, just to be sure. With EXACTLY the same export settings, render time is about 27 hours!
AME4 was not a 64 bit app, whereas AME6 is. So, my 16 GB of ram should be put to better use, I would think. According to Premiere, ram available for other apps is around 13GB. In task manager performace, processor is at the ceiling but memory use is only 6GB:
System specs are:
Media drive is Western Digital Caviar Black 2 TB SATA III 7200 RPM 64 MB Cache
GPU= AMD RADEON HD 6570 DP 1GB PCI EXPRESS 2.0 X16
How can I get AME6 to access more memory? Why in the world would the render speed more than DOUBLE with a newer version?!? Any suggestions would be greatly appreciated!

Yes. A CUDA card is on my wishlist, but my company may be tapped out for a while after new ram and an upgrade to CS6.
I did queue this one. I wasn't aware that this would make a difference. I'll try the direct export method next time.
RE: "encoding times have increased with the newer more feature rich versions" Really? So was I just mislead/misinformed that a 64 bit version of this encoder would be faster? Wow, that sucks. But is there no way for AME to access more than 6GB of my ram? I guess the slowness may be the price you pay for stability. My 8-hr project failed two times in AME4. I have 5 hours left of encoding on AME6. It's my last, best hope for being able to deliver this project on time.

Adding Masks Slows down render times massively

Adding any sort of vignettes/mask when using DL in Premiere CC creates massive render times in premiere. On a two minute promo it takes 15 minues to render what took 4 minutes without Masks.
Anyone know how to improve this? In the middle of a production, and this alone makes me want to use Resolve.

I should add that I'm Exporting to Media Encoder.
Leaving Renderer to CUDA or CL seems to be the culprit.
Setting ME to 'Software only' seems to improve render times.

CS5 on mac 10.6.4 slows system to a crawl, render times really long

We recently upgraded our towers to 10.6.4 and all productivity has slowed to a snails pace using After Effects. On 10.5 the speed was almost TOO fast on our renders...it was awesome. Now I'm looking to get that speed back.
I have a few very simple comps. 1920 x 1080, 23.98fps, 5 layers (4 QT renders from final cut XDCAM and Animation codec, 1 adjustment layer with levels and hue/saturation for color correction). Approx 40 seconds long each.
I've followed the Adobe advice of turning the multiprocessing on and using the following settings from here http://forums.adobe.com/thread/543440
leave 4gb for other apps, set minimum 3gb per processor = 33min render
setting it back to what WAS screaming fast on 10.5:
leave 3gb for other apps, set minimum 0.75gb per processor = 19min render
turning multiprocessing off = 5min render
same project on 10.5 system with multiprocessing turned ON with the above mentioned settings = 2min render
what is going on here? is there a compatibility problem with CS5/10.6 and Animation codec files? that seems to be the bulk of the slowdown, but still over twice as slow?
additionally, when AE is rendering the rest of the system becomes unusable...every action, even dragging a finder window around, results in beachballs and a 30 - 40 second lag in response. this happens with or without multiprocessing.
I just want to get back to work...any ideas on how i can configure this beast to get back to my former speeds?
8 core mac Pro
OS 10.6.4
12gb RAM
many thanks in advance. i'm willing to send beer for a winning fix.

Good to know, thanks for the update. 10.6.x does manage memory differently, but our testing for performance has shown a slight improvement in the newer OS. So I am guessing that the OS update is not the issue. I just ran another test on a Mac with your configuration and saw a 4% improvement on 10.6.4 over 10.5.8.
It's uncertain what state the system memory was in when you started your tests. That's why I asked for a restart of the computer. The times reported seemed like there was a possibility that the OS was swapping. XDCAM footage places a high demand on system resources. But it's hard to say without being there.
What I was seeing with the initial post was that the two extremes of allocation per background cpu were tried, but not the middle ground. To better see this, launch the Activity Monitor utility or look at the last line of the MP preference. With the 4GB reserved and the 3GB/ bkgnd cpu setting you weren't getting any extra processes spawned for multiprocessing. You can see this in the preferences multiprocessing section as "Actual CPUs that will be used = 0". Then, by setting the pref to .75GB/bkgnd the app launched 8 bkgnd processes, but for the task at hand, I am guessing that they were starved for memory and sometimes failed to render. This was faster than the first test, but still slow. By setting the pref to 1.5GB/bkgnd cpu you were now getting 4 new processes spawned for multiprocessing. The background processes had enough memory to succeed so that made it render faster still.
Now, try setting it to 1GB/bkgnd cpu. That will launch 6 processes which should render faster as long as that is enough memory for the task. If the Memory pref for Reserve RAM for other apps is set back to 3GB, it will allow the spawning of 7 bkgnd processes. If that is a successful balance for this project then it will be the fastest render time. But, our testing shows it will be at the risk of starving the OS for memory, thus the more conservative 4GB recommendation for a 12GB system.
It's a fine line and why we are recommending that one give up a little speed by reserving more memory for other apps. True, there will be less processes spawned for multiprocessing, but there will also be less chance for the OS to start swapping to disk which greatly slows down performance for all tasks. If that compromise is not acceptible, then the alternative is to buy more ram so that all 8 processes can adequately receive enough memory for the job, and yet still maintain adequate reserves for the OS and other apps.

Render Times on FCP Not Accurate?

Hi, <- My casual Greeting
Hopefully there are a few video editors out there on the forum... cause this one is program specific....
So I have been an avid Final Cut Pro guy for the last 4 years. I love the program.... I can work very easily in it but recently I got a new job in which I have been using both FCP and Adobe Premier.
Here is my issue... I have been using files that come in as MPEG 2 and have been using MPEG Streamclip to convert them over to a ProRes file for FCP. From FCP I have had to export them into 3 formats
1. Mpeg 4 (the file format our website takes)
2. FLV (Format for online video sites)
3. QuickTime (XDCAM) for our tricaster
The last week I have been using FCP and my render times have been (for a 5 min clip)
1. Mpeg 1 hour+
2. FLV 20 min+
3. QuickTime (XDCAM) 1 hour +
Yesterday I was told to use Premier as my boss uses Premier on a regualr basis and I assured him that the times would be the same as FCP is a Mac native program and that Premier was made to work on a mac but is essentially a PC program (I am eating my words now)...
I redid the renders on the same file...
On premier the render times were
1. Mpeg 30+ min
2. FLV 12 min
3. QuickTime (XDCAM) 40 min
Why is this? Do I just have something really messed up in my settings that FCP is not rendering quickly and Premier is? I would hate to have to hop over to Premier... I enjoy using FCP way to much.
The other question I have is why are FCP render times not accurate...
The renders will start saying 5 min then 10 then an hour etc.... and the time will not be accurate. If it says 5 min it may go for an hour... or if it says an hour it may just complete while still telling me I have an hour to wait.
Adobe Premier, right off the bat, will tell me the frame it is on and the percent and time left... almost to the T.
If possible... please help me get my fcp back on the right track.
Tim

Rendering can be much faster if you have a multi core intel Mac and you use Qmaster with Quick Clusters.
Here's how.
Set up Quick Clusters in Qmaster. (A description of how to do this is in the manual and also can be found in the Qmaster forum here in the Apple discussions as well as out on the web.)
Export your sequence from FCP using "current settings". (Do NOT use Quicktime Conversion!)
Open up Compressor and submit your file. Add the three output elements.
Submit the file and click "use unmanaged services"
Go have a cup of coffee while all the cores chug away at things. I guarantee it will be faster than the way you are currently exporting (if you aren't using clusters)
x

Optimising render time: Which timeline elements/clip effects increase render time?

Hi,
I was just wondering if anybody had further information about Premiere's output render process, specifically the effect clip effects, tracks/layer and clip formats have on render time.
The reason I ask is I seem to be getting inconsistent file export/render times, some projects of similar length and on the same hardware seem to take significantly longer than others.
Essentially I am looking for timeline connfigurations/properties which adversely effect the final output render time. Any further information/documentation regarding this would be gratefully recieved.
Regards,

I am essentially just trying to optimize workflow, as we are having quite high project throughput. So yes I would not use an effect, or think of a more efficient method to achieve said effect, if it was going to significantly bottleneck the workflow by several orders of magnitude, and yet only added negligible subjective aesthetic improvement.
It comes down to classic "Cost Benefit Analysis", thats why I was asking for technical documentation, to see if there is anything we are doing which is having a big hit on performance, which may have a more efficient alternative or may not improve the quality to a level which warrants to slowdown.

Render time has INCREASED!

I'm running FCP 6.0.4 on a Quad 3GHZ Mac Pro with 8GB of RAM. I am working with Sony XDCAM HD 1080i (35MBS, VBR) footage.
I edit a 28:30 local TV program and have produced over 20 episodes so far. Its a fairly simple format and most of the shows are relatively the same, so I had grown accustomed to consistent render times. The main element that needs rendering on every show is a small animated logo in the lower right frame. It is on-screen for 95% of the program. For the first 20 episodes, even with some select clips having multiple layers of graphics and color effects, to render the entire show, it would take 2-4 hours at the most. Again, these render times were consistent for the first 20 shows or so.
However, for the last few shows, I am experiencing extremely long render times for the same format I've been working with for over a year. It now takes 8-12 hours to render the entire show. I have four internal 750GB hard drives. I do not store any footage on the OS drive and I always make sure I have more than 30% free space on my source disk.
Would anyone have any idea why render times would have drastically increased?? Was there a recent
software update or something that may have caused this, either with Leopard or FCS?
Any suggestions would be appreciated.

Run, don't walk, to the Aja site and download a copy of their Kona System Test utility. It's PowerPC, which is a little annoying because it takes a long time to launch. But it's a great tool to test disk I/O performance. (Also, despite the name it is not in any way related to the various Kona I/O boards. I haven't received by LHe yet, and I've been using the System Test tool for ages to keep an eye on my framestore bandwidth.)
For comparison's sake, I get on the order of 160 MB/s reads and writes on my framestore. It's a very humble configuration, just two internal 750 GB SATA drives striped using Disk Utility. If you're getting less than that, something ain't right.
How exactly are you setting up your projects? Are your timelines using the XDCAM compressor, or are you using ProRes? If you're using an XDCAM timeline, do you have ProRes rendering turned on? Do you send your finished shows back out to XDCAM, or do you go out in some other format? I ask this part because it's possible — though since you've been doing these shows for a while you almost certainly already know this — that you don't actually need to stay in the XDCAM format at all, unless you're going back out to XDCAM media. If you're laying off to some other mastering format, or going out with a Quicktime master, you can skip rendering back to XDCAM entirely, which may save you hours and hours.

Optimize render time... how ?

Similar Messages

Maybe you are looking for