Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro The Lengthy Vegas Process

  • The Lengthy Vegas Process

    Posted by Tyler Wentzel on February 6, 2009 at 8:06 pm

    Hey everyone,

    I am discovering as I am working with longer and longer video projects on Vegas, that the average time it takes to get a 1 hour video onto DVD, is about 5 hours. Rendering to MPEG-2 for Architect takes around two to two-and-a-half hours, and burning takes close to two hours as well. Is this normal, or is my computer just really slow?

    I have a 1.68GHz processor and 2GB of RAM. The processor is definitely VERY minimal for video editing, but it’s what I’m working with for the time being. Until I upgrade PCs, I’m wondering if it’s my processor that’s hindering the rendering speed…With a faster processor, can a video be rendered to the various file formats in real time? Is real time as fast as it gets? This is all very confusing to me.

    And I brought this up in an earlier post, but just to clarify…for NO compression to DVD, the only option is that one renders the video to MPEG-2, and the audio to a separate Architect-compatible format, such as AC-3; then the two separate formats, audio and video, are brought into Architect separately on the timeline, then burning can commence? Is that right?

    Thanks for your time and patience.

    Tyler

    John Rofrano replied 17 years, 3 months ago 6 Members · 13 Replies
  • 13 Replies
  • Douglas Spotted eagle

    February 6, 2009 at 8:12 pm

    A-your computer is really slow.
    B-why are you rendering twice? You’re losing quality as a result.
    C-even on a slow computer, unless you’re color correcting everything, using lots of composites, or heavy layering, rendertimes seem high based on your basic description.

    Are you running antivirus by any chance? That’ll bring a render to its knees in most instances.

    Douglas Spotted Eagle
    VASST

    Certified Sony Vegas Trainer
    Aerial Camera/Instructor

  • Brett Underberg-davis

    February 6, 2009 at 8:15 pm

    It will speed up considerably the more memory and cores you can bring to the process. I’ve burned fully prepped single-layer DVDs with 90 mins or so of video out of Architect in as little as 6-10 mins on my Quad Core 2.6GHz, 4GB RAM system.

    But rendering time is also highly variable. It just took me 1.5 hours to render a 2.5 min credit sequence, mostly because I was using a pretty stupid approach to do it.

    But to keep it simple, more cores, more RAM or the ability to put together a render farm (I wish I had the chops to do that myself, and the hardware available to grow such a farm) all will do wonders for your rendering time when everything else is an apples to apples comparison.

  • Mike Kujbida

    February 6, 2009 at 8:17 pm

    [Tyler Wentzel] “Is this normal, or is my computer just really slow?”

    In today’s market, it’s painfully slow 🙁
    [Tyler Wentzel] “With a faster processor, can a video be rendered to the various file formats in real time?
    Is real time as fast as it gets?”

    With a quad core, my renders can, depending on how many FX are on the project, be real time or faster.
    For example, a 10 min. video I did a few years ago on a P4 3.4 GHz machine took 3 hr. to render to MPEG-2 (LOTS of FX and chroma key).
    My quad core did it in 30 min.
    Upgrade to a machine with the new Intel I7 chip and your render times will drop dramatically.

    [Tyler Wentzel] “…for NO compression to DVD… Is that right? “

    That’s correct. If you set the bitrate properly according to the lenght of your program, DVDA will not recompress anything.

  • Tyler Wentzel

    February 6, 2009 at 8:42 pm

    My reasoning for rendering twice, was because when I would go to burn the project, the warning message that came up even after I rendered the video to MPEG-2 format, stated that the audio track would need compression.

  • Tyler Wentzel

    February 6, 2009 at 8:45 pm

    Thanks for your advice.

  • Mike Kujbida

    February 6, 2009 at 8:46 pm

    Tyler, as long as you give both files the same name (mymovie.mpg and mymovie.ac3) and render them to the same folder, DVDA shouldn’t compress again.
    If it does, then it’s operator error and you need to review what you did and where you might have gone wrong.

  • Tyler Wentzel

    February 6, 2009 at 8:52 pm

    Thanks Brett. So what’s the difference between Core 2 Duo and Dual Core, if I was to buy a laptop with such a processor? Additionally, obviously a PC is going to have many more options for a solid HD editing system, but for a potentially mobile individual, what laptop would come close for a reasonable price as far as a speedy editing machine is concerned?

  • Tyler Wentzel

    February 6, 2009 at 8:54 pm

    Yes, I most likely did something wrong there. I believe that when I rendered the video, then rendered the audio, I renamed the file for the audio without thinking. That must have been the problem.

  • Allen Zagel

    February 7, 2009 at 1:11 pm

    Hi Tyler

    Just to clear my thinking, exactly which MPEG-2 template are you rendering to in Vegas? Are you using the DVD Architect Stream (PAL or NTSC) or a default stream?

    If you’re not rendering to the DVD Architect NPEG-2 then it is possible DVDA will re-render.
    Allen

    ASX Media Group, Inc.
    http://www.asxvideo.com
    NEW DVD – Europe, Trains-n-Trams

  • John Rofrano

    February 8, 2009 at 6:42 pm

    > So what’s the difference between Core 2 Duo and Dual Core

    Core 2 is the second generation dual core by Intel. “Dual Core” was an abomination and should be avoided like the plague. They were slower than single core machines! I’m surprised they are still around. I guess they are fine for web surfing and word processing but you don’t want Dual Core for video editing, you want Core 2 Duo.

    ~jr

    http://www.johnrofrano.com
    http://www.vasst.com

Page 1 of 2

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