I'm rendering using 720p, with 2000 FPS. After rendering, I'm getting a huge file with 244 frames/second. The source files are only 29.97 frames/second so why is the render going up almost 10 times???
$\begingroup$
$\endgroup$
3
-
2$\begingroup$ What exactly are you rendering? A 3D scene? Compositor? Video Sequence editor? You say your source files have 29.97 frames per second and you are rendering with 2000 (?) frames per second, why such an unusually high value, more than 60 times the original value? What were you expecting would happen to file size with such high frame rate? $\endgroup$– Duarte Farrajota Ramos ♦Mar 15, 2016 at 1:59
-
4$\begingroup$ Do you mean 2000 frames (not frames per second). $\endgroup$– PGmathMar 15, 2016 at 2:26
-
$\begingroup$ Rendering video thru the NLE $\endgroup$– MastertexanMar 18, 2016 at 2:03
Add a comment
|
2 Answers
$\begingroup$
$\endgroup$
7
Check your render settings. To get 29.97 fps you should have a framerate of 30 with a framerate base of 1.001. If you change the base to 0.123 then you will get 243.9 fps
-
-
$\begingroup$ I added a screenshot of my Dimension and Encoding menus $\endgroup$ Mar 17, 2016 at 20:53
-
$\begingroup$ My video length is 2:15:58 but when I render say, 10 mins of video, everything comes out just fine. It's only after I render the full length that I get the huge rates $\endgroup$ Mar 17, 2016 at 21:11
-
$\begingroup$ Interesting, current releases have a max frame count of 300,000 (for 2.77 it has been increased to 500,000), I wonder if exporting large frame counts to video has a bug. Can you find a frame count where this starts happening? If you export using other codecs does the same thing happen? I would report this as a bug and see if the developers can find a cause for bad frame rates with longer videos. $\endgroup$– samblerMar 18, 2016 at 6:02
-
$\begingroup$ How can I look for that? Render it out 10 mins at a time? $\endgroup$ Mar 18, 2016 at 18:33
$\begingroup$
$\endgroup$
https://developer.blender.org/T47844
After more than a week talking to some guys, it appears the problem is not the actual video itself, rather the way Windows is reporting the status.