Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Lets do some math a 10 second video of 60FPS means ur rendering 600 pictures.
Now lets say it takes a hour to render a really nice scene, with many objects and nice lights with reflections and everything it might even take longer.
Thats is roughly 600hours worth of rendering.
So no this is NO BUG!
You can use this to lower your render time in cycles: http://www.blenderguru.com/articles/4-easy-ways-to-speed-up-cycles/
I just rendered a 58 minute video from 84725 Image sequenced frames on a standard 1TB HardDrive with the settings of 1080P, 100%, H.264 - MP4 (lossless not selected) , no audio included, in 3-4 hours at 24 frames per second back to the standard drive.
Video was being reproduced at a FPS of @ 6 frames per Second.
Doing the math - 84725/6fps = 14,045.83 Seconds /60 to minutes @ 234.1 minutes /60 to hours = 3.9 hrs
Let's say your video was 10 seconds at 24FPS that's only 10*24 = 240 frames and you say it took 9 hours to render?
Then again, I only rendered image sequences, if you are rending a Blender Animated Scene where you have models in Blender doing animations and cameras flying all over the place, then yeah, I can see that being 9 hours for a 10 second shoot. SFM can take just as long or longer to do the same.
did you make sure cycles is using your graphics card ?
do you have a nvidia card ?
my math is good 60 frames a second if u render 1 hour a frame its 600 hours
so if your frame only takes 1/2 min its about 600/1200 mins wich is 10-20 hours
Pentiums don't render so well for the final product, too slow.
As KingSlayer said, if you're running a system with an nVidia card, then you should use those CUDAs to speed shiz up. You can do that by going to 'File > User Prefrences > System > Compute Device' and setting it from CPU to what ever option that isn't just soely only CPU.
Now, only if I could not be using the two cores of this CPU and instead be using those 1664 CUDA cores of that 970! ... oh this would be easier then. 2 hours a frame is killer slow X_X
How many cycles are you per frame block and what is your frame block size?
Optimizing these could possibly decrease rendering time.
Its getting better, but Cycles needs a lot of work on the noise front...
Also, never ever render direct to video format unless doing a fast preview. Always render to an image sequence and add the sound afterwards in the sequencer. That way you can sync the sound and do other fixes without rerendering the whole thing.
Otherwise, Cycles rendering is going to be slow because it is tuned for photorealism. You can remove some features to make it faster but it's still going to be slower than blender internal.
For comparison, take Toy Story :
"Finished animation emerged in a steady drip of around three minutes a week. Each frame took from 45 minutes up to 30 hours to render, depending on its complexity. In total, the film required 800,000 machine hours and 114,240 frames of animation." (from wikipedia).