-
30min video 6 hour rendering time!
Posted by Ace Singh on September 27, 2016 at 12:32 amHi,
So I’m recording some gameplay, I’ve added my webcam footage to it and some audio from my microphone but my rendering time is almost 6 hours! I’m sure that with my PC specs it should be a lot quicker?! I only want to be able to upload the best quality to YouTube so maybe what I’m doing is overkill?
My main gameplay is recorded from Nvidia Shadowplay at the best quality, 60fps and 1920×1080 HD. My Logitech camera is also 1920x1080HD.
Any help is truly appreciated.
My PC Specs –
Windows 10
i7-4790K CPU
GTX 980
16GB RAMVegas Pro 12
My Render Settings –
Wayne Waag replied 9 years, 10 months ago 7 Members · 14 Replies -
14 Replies
-
Steve Rhoden
September 27, 2016 at 3:11 amRendering recorded game play comes with a variety of issues sometimes, so its hard to be specific as to
what is causing your specific issue.
Speaking of specific, what’s your render settings for this?, (which also could be due to your long render time).Steve Rhoden (Cow Leader)
Film Maker & VFX Artist.
Owner of Filmex Creative Media.
Samples of my Work and Company can be seen here:
https://www.facebook.com/FilmexCreativeMedia -
Ace Singh
September 27, 2016 at 9:11 amNot sure why the image isn’t showing up but I’ll write it here just in case
I used the MainConcept template Internet HD 1080P then customized it
Format – Audio: 192 Kbps, 48,000 Hz, 16 Bit, Stereo, AAC
Video: 59.940 fps, 1920×1080 Progressive, YUV, 12 Mbps
Pixel Aspect Ratio: 1.000Frame Size – HD 1080
Profile – High
Frame Rate – 59.94 (Allow Source to adjust frame rate ticked)
Field order – None (progressive scan)
Pixel Aspect Ratio – 1
Number of reference frames – 2
Variable bit rate – two pass – Max 24,000,000 – Avg – 12,000,000
Number of slices – 4
Encode mode – Render using CPU OnlyAudio –
Sample Rate – 48,000
Bit rate – 192,000 -
Peter Holt
September 27, 2016 at 2:48 pmI routinely see 1/10 of real time rendering speeds… The best I ever managed with any version (MSP11, 12, Pro 13) was 1/3 of real time and that was going 1080P to 720P 50FPS and no FX, just a render. That is with no GPU acceleration (never worked in MSP and crashes Pro 13) so just the CPU which is a 3GHz 6-core i7-970 (win7-64, GTX750). Currently I am running an intermediate render of a 7hr job which will run for 80-100hrs. This stuff just is very slow. I know a guy with Final Cut Pro (Mac OS) who says he renders at 1x real time, but then Apple tightly control the video hardware and he has a properly working coprocessor.
-
John Norton
September 27, 2016 at 8:09 pmGoes without saying, I suppose, but removing 2 pass would make it quicker!
-
Ace Singh
September 27, 2016 at 11:02 pmWould that make a huge difference quality wise? Or is this one of those things I’m better of testing…probably the latter lol
-
László Kovács
September 28, 2016 at 5:01 amI always do single pass render with a slightly higher bitrate, but lower framerate (25p)
Never had quality issues.
But, if I would have to change something that may affect quality towards wore, I’d check if the settings still works good.
I mean render 1 or 2 minutes only, and that shows the quality.
That you can do as well, render just 1 minute, see how it looks. And if it’s OK, render the whole thing – overnight maybe.Best regards
László Kovács
-
Peter Holt
September 28, 2016 at 8:07 amI have done both 1-pass and 2-pass on the same material and same render settings, and I recall that the 2-pass generates maybe 10% smaller files, but better quality.
I am not 100% sure if I changed the bitrate also; logically the file size should be purely according to bitrate, and *definitely* the output frame size (e.g. 1920×1080) does not affect the file size for a given bitrate.
Most of the time the difference is not visible but in some videos I could tell the difference in some details e.g. a moving camera shooting a piece of tarmac which has a huge amount of detail and totally maxes out the bitrate even at 100mbits/sec.
I now use 1-pass for intermediate renders and 2-pass for final ones, because anything helps to get inside the 5GB file size limit on Vimeo 😉
-
John Norton
September 28, 2016 at 11:36 am“I always do single pass render with a slightly higher bitrate”
This is what I do also. I know they are not the same, FFMPEG and MC, although you never know whats under the hood completely, with ffmpeg, 2 pass is used more to target a perticular output file size, than quality (CRF).
As mentioned here already, pick a small section of video, ideally a challenging piece in low light, then increase the bitrate until it improves to what is acceptable, and also where it improves no more, all at 1 pass. If output file size is critical then go 2 pass and do the same testing. That way you can settle on a template thats good enough without having to keep changing, especially if you add a bit extra, i.e. if you find that say, 24/18 is just right then set the template to say 24/20 to cover anything. Assuming size is not critical.
-
Angelo Mike
September 28, 2016 at 3:36 pmIn my opinion, your bit rate is definitely overkill for YouTube. YouTube compresses everything to what, 3 mpbs? I usually render video for YouTube from my Canon Powershot G7X (or formerly my Canon Vixia HF S21) at 4 mpbs. I used to do it out of ignorance at 10 mpbs and noticed no difference.
Experiment with bringing your bit rate down in a few second clips to see what’s lower bit rate gives you acceptable quality. The only reason I’m not saying for sure a 4 mpbs bit rate will work for you is because I haven’t personally tested the same kind of video to see the difference, but I’d make a firm bet that the quality difference on YouTube will be negligible.
-
Ace Singh
October 5, 2016 at 2:57 amI tried all of this, I want to use 2-pass because I need a decent file size for uploading….now I have a 10min video that is taking 9 HOURS to upload!
What the hell? Why is the time even longer now?!
Reply to this Discussion! Login or Sign Up
