Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Vegas 12 rendering crash

  • Vegas 12 rendering crash

    Posted by Steven J casey on July 10, 2013 at 3:25 pm

    Discouraging to see so many other posts about render crashes, but so far none of the suggestions I’ve found have helped my situation.

    I’ve been asked to edit footage sent in MP4 1080p, 29.97. It was a two camera shoot of a couple presentations, so my only editing is to cut back and forth between tight and wide shots, which I did by using a mute envelope on the top track. Playback is fine, I need to render to DVD for the customer. Renders stop at frame 74 every time, Vegas does the infamous infinite count up of render time but is not actually doing anything.

    So far I tried moving my start point up so that frame 74 was actually removed from the project, but the “new” frame 74 is still the hang point. Turned off GPU, set RAM preview to 0, restarted Vegas, no change. Saved the project under new name, no change. Copied/pasted the files into a new project, no change. Reset Vegas using the ctrl-shift keys on start up, no change.

    I did manage to render an mp4, but this took about 5 hours when typically on my machine would be a few minutes (see specs below, it’s not a lack of horsepower). I don’t know what camera the footage was captured with and not sure the codec is part of the issue, but if it were I would think playback would be affected. Playback is perfect, only rendering is the issue.

    Thanks for your thoughts.

    Dell Precision T7500
    Intel Xeon CPU X5650 @ 2.67GHz 2.66 GHz (2 processors)
    60GB RAM
    Quadro 4000
    Windows 7 Ultimate
    CS6
    M-Audio FW 410
    Vegas Pro 12

    Tyson Onaga replied 12 years, 9 months ago 4 Members · 5 Replies
  • 5 Replies
  • Angelo Mike

    July 10, 2013 at 3:28 pm

    What worked for me was copying and pasting everything into a new project. You’ll have to redo all the track level plugins, but it’s the only thing that works after trying to edit at two changes at a time before my project crashed, and then having it crash on render. I’m rendering to a DVD as well.

    At least, this worked on Vegas 11. Maybe Sony had the foresight to remove this workaround on Vegas 12.

  • Steven J casey

    July 10, 2013 at 3:38 pm

    Hi Angelo, I saw your earlier post as well so I know you feel the same pain. I already tried copying/pasting into a new project and nothing changed. Also, I have absolutely no plugins on the tracks, so this should be minimal impact on processing power.

    I also know the frustration of Sony support. My experience has been to wait 3-4 weeks for them to respond with “try restarting your computer.” Seriously, that was the extent of their advice. Another time they literally never responded.

    Dell Precision T7500
    Intel Xeon CPU X5650 @ 2.67GHz 2.66 GHz (2 processors)
    60GB RAM
    Quadro 4000
    Windows 7 Ultimate
    CS6
    M-Audio FW 410
    Vegas Pro 12

  • Stephen Mann

    July 10, 2013 at 3:49 pm

    ” Playback is perfect, only rendering is the issue.”

    Playback where? Players like VLC use their own codecs optimised for playback. Vegas and other editors rely on codecs, often from third-party sources, for quality encoding.

    “set RAM preview to 0”

    Vegas requires some preview RAM. I suspect that some very early versions used the preview RAM for scratch space and the programmers today have forgotten about it. If you never use Shift-B to preview a selection, then set it to 1024. I don’t recall who did the tests, but a test render took longer with RAM preview set to zero, and in experiments the sweet spot on his installation was around 1024(1Mb).

    “Vegas does the infamous infinite count up of render time but is not actually doing anything.”

    This was a common problem in Version 8 or 9 if you had any unused media in the Project Media list. Try the “lightning bolt” icon to remove unused media. It’s a long shot, though, but can’t hurt anything. Also, do you have any nested projects? If a nested project has a problem, it can cause the parent project to wait forever.

    Use the Resource Monitor (resmon.exe) to see if Vegas knows what it’s waiting on when you get into the infinite wait. In the Overview tab, look for the Vegas process, right click on it and select “Analyze Wait Chain”. Normally that should be blank, but if not, then it may provide a clue.

    Frame 74 is curious. Does it only happen with this media? Can you duplicate it with any other media? Are you doing everything on a single disk drive for the OS, program and project files? When you go into Preferences, hold the Shift key and you will see an “internal tab” on your preferences window. In the Internal Tab where it says “Show only prefs containing:” enter “Path”. DO NOT CHANGE ANYTHING in the internal tab. Make sure that you are not running out of disk space in any of the referenced paths.

    Steve Mann
    MannMade Digital Video
    http://www.mmdv.com

  • Steven J casey

    July 10, 2013 at 4:18 pm

    “Playback where?”
    On the Vegas timeline.

    “If you never use Shift-B to preview a selection, then set it to 1024”
    My initial setting was at 2000 while Vegas tells me I have over 32000 available. I changed it to 0 based on my searches through other posts on these boards, but of course this had no effect.

    Just removed unused media but this had no effect. There are no nested projects and the resource monitor window is empty when this happens. I’m using a separate media drive that contains only the footage for this project and both this drive and my OS drive have over 200GB of free space.

    I’m at a loss.

    Dell Precision T7500
    Intel Xeon CPU X5650 @ 2.67GHz 2.66 GHz (2 processors)
    60GB RAM
    Quadro 4000
    Windows 7 Ultimate
    CS6
    M-Audio FW 410
    Vegas Pro 12

  • Tyson Onaga

    July 10, 2013 at 6:46 pm

    Since moving frame “74” doesn’t change the problem, I would look at: FX, Renderer, HD issues.

    a. Try turning off any FX you’ve added to the given track.
    b. What happens if you try to render the problem region with (eg) QuickTime Photo-JPEG (I assume you’re using MainConcept MPEG-2).
    c. Try copying/renaming the source media to a different location (maybe different HD) and using either Replace or Add As Takes. Additionally, you could use “chkdsk [drive] /f” on your source material HD.

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