Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Slow Rendering in Vegas Pro

  • Slow Rendering in Vegas Pro

    Posted by Hasan Khurshid on August 3, 2015 at 8:46 pm

    If someone know about the computer relationship with rendering, please give some advice. I usually shoot with 3 camcorders @1080p 30fps 24mbps. Then I have to do a multicam of these shoots and they are usually around 1 hour. Then I also have to color correct and add brightness and contrast effect also on all these shoots. Then I want a final output @720p 6Mbps for internet uploading. The rendering usually takes for 1 hour video it takes 3-4 hours. How can improve it?

    Specification
    Cpu 2nd Gen Core i7 2600
    12Gb Ram
    Nvidia Qudaro K4000

    Bob Peterson replied 10 years, 9 months ago 4 Members · 6 Replies
  • 6 Replies
  • Norman Black

    August 3, 2015 at 9:14 pm

    A faster computer will speed things up.

    You did not mention what encoder (render as) you were using. If you are encoding to AVC in Vegas then there are two AVC encoder options. Sony AVC is faster than Mainconcept unless MC AVC supports your GPU and then it will likely be faster.

    Most times, the speed is what it is, since the Vegas encoders are what they are.

  • Hasan Khurshid

    August 3, 2015 at 9:18 pm

    Yes I use avc but what will be faster than this computer.

  • Aaron Star

    August 3, 2015 at 10:35 pm

    If your final output is 720-30p. Use the scripting feature in Vegas to batch convert all your master footage to XDCAM-EX-720-29.97p. This will reduce the amount of information for multicam editing, as well as smart render, and render much faster to MP4 with either Sony AVC CBR or MainConcept VBR.

    You can use the batch render stage to perform CC and other adjustments, so that editing is not bogged down with effect filters. Smart renders are almost instantaneous, if you can keep yourself from applying that one minor additional effect that defeats it.

    Farm out your batch renders to another computer, or multiple PCs and write the results to a network drive.

    Handbrake will also read the XDCAM final render output file for conversion to .mp4

    Dump the k4000 for an AMD XT class chip like an R7-270x,7970/R9-280x, R9-290x/390x. Firepro w9000 or w9100 if you need the pro color monitoring equipment. X class cards have the most compute units and generally the best compute performance. MainConcept .mp4 encode is supposedly not supported on the newer R9 cards, however timeline effects like blurs and XDCAM encoding are accelerated. So you are looking for your GPU to speed up the computational speed of the PC, during effects where the CPU is slower at those functions. If you work in 32-bit modes, the GPU comes much more into play, as the GPU is faster at floating point math.

  • Bob Peterson

    August 4, 2015 at 3:49 am

    Have you tried turning on the GPU? With a Quadro 4000, that may help a lot.

  • Aaron Star

    August 4, 2015 at 8:50 am

    Bob has a point if your GPU has not already not been tried. The k4000 has 10 compute units, the same as the older 5770, 6770. The 5770 was the minimum configuration for GPU under Vegas 11.
    Compare that to:
    20 compute units on the r9-270
    32 on the 7970
    44 on the 290x & W9100
    64 on the 390 Fury X

    k4000 = about 1240 Gflops Single Precision
    hd5770= about 1340 Gflops Single Precision
    Fury x= about 8600 Gflops Single Precision

    HD5770 in Luxmark “Room” OpenCL Benchmark = GPU-202
    K4000 in Luxmark “Room” – from cgchannel.com test = GPU-137
    Fury X = GPU-3565

    Not everything the GPU does is floating point math, but vegas does utilize both the CPU+GPU OpenCL virtual compute units.

  • Bob Peterson

    August 5, 2015 at 4:09 am

    Thanks for your amplification of my point.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy