Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Slow Rendering Time??

  • Slow Rendering Time??

    Posted by Edwardoplunkett on November 30, 2006 at 11:48 am

    Hello Everyone,

    Just started using Vegas 6d to create family dvds. Have about 6 years of dv tape to deal with…A project long overdue.

    Anyway, have tried a sample render of dv video that is 7 minutes long with no special effects, titles, etc. and Vegas is telling me it will take 55 minutes. Output format is DVD NTSC.

    This seems excessivly long. My PC config is noted below. Is this render time appropriate? My rough calcs indicate 6 hrs for every 1 hr of timeline…

    What am I doing wrong??

    Intel P4 2.4 OC to 2.8
    1GB Corsair
    XP Pro
    Nothing special video card

    Regards,

    Ed

    Edwardoplunkett replied 19 years, 8 months ago 3 Members · 5 Replies
  • 5 Replies
  • Edward Troxel

    November 30, 2006 at 7:57 pm

    Something is slowing it down.

    First of all, I’d use one of the DVD Architect presets instead of the DVD NTSC one. Beyond that, make absolutely sure that NOTHING has changed (i.e. track opacity still at 100%, track motion is NOT on 3d, etc…)

    Edward Troxel
    JETDV Scripts

  • Edwardoplunkett

    November 30, 2006 at 9:56 pm

    Thanks for the response.

    After hacking with it all day I have figured it out…
    1. Too many processes running in the background. Killed nearly everything and now I’m getting about 10 minutes of rendered mpeg2 in about a half an hour.

    I’ll try DVD-A next to see if that helps as well in the short term. Long term plans are complete PC upgrade. More on that later…

    2. Had another problem – Vegas would crash after about 5 minutes of rendering. Turns out my chip was getting too hot with 100% cpu hit due to rendering as well as the extra heat from overclocking. I dialed the chip back down to a stock 2.4GHZ, and things are working fine now.

    Now to burn a DVD…

    More questions to come I’m sure. Thanks for your help.

    Regards,

    Ed

  • Edward Troxel

    December 1, 2006 at 2:32 pm

    I was afraid the overclocking would cause problems. Heat is definitely an issue when rendering.

    Edward Troxel
    JETDV Scripts

  • Actxiom101

    December 3, 2006 at 6:46 am

    I am curious how a person checks the heat levels, knows that overclocking is occuring and “dials down to 2.4 ghz”? That sounds like very technical stuff. How do us earthlings make this knowledge work for us. Turning off stuff in the background makes sense. I even have had great success in the last few days uninstalling a bunch of Google bells and whistles. Freeing up all external and internal (40g) hard drives (I have 3, 160g, 160g, and 80g)have about 20% available capacity is another effort.

  • Edwardoplunkett

    December 3, 2006 at 12:56 pm

    One of my more learned colleagues taught me to build PCs a few years ago. The motherboard he reccomended (Asus) came with software that allows you to vary the CPU speed quite easliy by increasing supply voltage or upping the frequency. There are various ways to overclock, and I am by no means an expert, hence my rendering problems – which were due to the extra heat generated during rendering (cpu at 100% for extended periods of time).

    Regarding how hot things are acutally getting – Somehow temps are output of the mobo and CPU, and various apps (Everest for one) can output that data to the user. My Asus OC utility shows CPU speed, temp, cooling fan speed, etc.

    OC in moderation, can give you notably faster performance that stock CPU speeds. OC in excess can fry expensive CPUs or cause your pc or apps to hang/crash. You have to find the right balance of speed vs. problems. I am going to continue to run my machine at 2.8 all the time, except when I need to render, when I’ll drop it back to stock 2.4ghz.

    Google overclocking for all you need to know…

    Regards,

    Ed

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