Export Slowwwwwww
Moderators: Víctor Paredes, Belgarath, slowtiger
Export Slowwwwwww
When i export my project to Movie, it export very very very slow!!!
Help me!!!
Help me!!!
-
- Posts: 34
- Joined: Fri Mar 18, 2005 4:32 am
- Location: Australia
- Contact:
I agree, 4 minutes is long for animation.
Of course, a faster computer would help. Where is that 1 THz CPU we all are waiting for, plus that 400 GB flash memory drive instead of a harddrive? According to Moore's Law and the fact current CPUs run at roughly 4 GHz, we will have to wait another 12 years for that.
In the mean time we just have to be patient and drink a lot of coffee when waiting for our animation shorts to be rendered, or let the computer chrunching at it during the night
Of course, a faster computer would help. Where is that 1 THz CPU we all are waiting for, plus that 400 GB flash memory drive instead of a harddrive? According to Moore's Law and the fact current CPUs run at roughly 4 GHz, we will have to wait another 12 years for that.
In the mean time we just have to be patient and drink a lot of coffee when waiting for our animation shorts to be rendered, or let the computer chrunching at it during the night

Make sure you have the latest version of Moho - there were rendering speed-ups in some of the updates (for example, 5.2.1, 5.3).
Particle layers: see Hiddicop's tip for speeding up rendering containing particles - particularly for re-rendering as you make changes.
Likewise, you can create static backgrounds separately and compose them together with your animation in your video editor, rather than re-rendering a detailed background over and over again.
Speaking of which, it can help if you break your animation into multiple scenes and render them separately - you can use the batch renderer to render them all at once.
Cribble noted that resizing the preview render window to show only the title and part of the progress bar, not the preview images, speeds rendering up.
Discussed again by Hiddicop and Stephen, in a thread which also brought up the point that batch or command-line rendering, which don't show a preview, might also improve render times.
WillBellJr noted that bitmap files (textures, image layers) should not be hugely larger than the final resolution they will be shown at.
Some codecs may possibly take longer to render than others, but you don't always get a choice about this. Likewise for format and resolution.
Rasheed's hardware dreams aside (by the way, welcome back Rasheed!), Stephen noted that of course faster currently available hardware can make a significant difference.
Regards, Myles.
Particle layers: see Hiddicop's tip for speeding up rendering containing particles - particularly for re-rendering as you make changes.
Likewise, you can create static backgrounds separately and compose them together with your animation in your video editor, rather than re-rendering a detailed background over and over again.
Speaking of which, it can help if you break your animation into multiple scenes and render them separately - you can use the batch renderer to render them all at once.
Cribble noted that resizing the preview render window to show only the title and part of the progress bar, not the preview images, speeds rendering up.
Discussed again by Hiddicop and Stephen, in a thread which also brought up the point that batch or command-line rendering, which don't show a preview, might also improve render times.
WillBellJr noted that bitmap files (textures, image layers) should not be hugely larger than the final resolution they will be shown at.
Some codecs may possibly take longer to render than others, but you don't always get a choice about this. Likewise for format and resolution.
Rasheed's hardware dreams aside (by the way, welcome back Rasheed!), Stephen noted that of course faster currently available hardware can make a significant difference.
Regards, Myles.
"Quote me as saying I was mis-quoted."
-- Groucho Marx
-- Groucho Marx
Oh, my golly gosh goodness. Myles, Cribble, I cannot thank you guys enough for this light you have shined in my life. I couldn't believe just how much of a difference this actually made. I feel like quite a doosh for not even trying it. Thankyou thankyou thankyou.myles wrote:Cribble noted that resizing the preview render window to show only the title and part of the progress bar, not the preview images, speeds rendering up.
This is a block of text that can be added to posts you make.
There is a 255 character limit
There is a 255 character limit
-
- Posts: 1
- Joined: Thu Feb 16, 2006 10:53 pm
- Location: Wisconsin
Is there any support for dual-core or hyperthreading processors? Or is the best way to simply run two instances and have each render half of the animation?
I have dual 2.8 Ghz processors, and being able to take advantage of this would be great (Taskmon shows one processor being used very much).
I have dual 2.8 Ghz processors, and being able to take advantage of this would be great (Taskmon shows one processor being used very much).
L|i|f|e my anti drug
Thanksgavi dvan wrote: Oh, my golly gosh goodness. Myles, Cribble, I cannot thank you guys enough for this light you have shined in my life. I couldn't believe just how much of a difference this actually made. I feel like quite a doosh for not even trying it. Thankyou thankyou thankyou.

From what i've heard, not yet. Kind of like the dual processors on PC's aswell, i don't think thats supported either. Definitly a huge feature for the future (aswell as 64bit support).Adamsmasher23 wrote: is there any support for dual-core or hyperthreading processors? Or is the best way to simply run two instances and have each render half of the animation?
I have dual 2.8 Ghz processors, and being able to take advantage of this would be great (Taskmon shows one processor being used very much)..
--Scott
cribble.net
cribble.net