Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Sony Vegas Pro 12 Rendering Problems Galore

  • Sony Vegas Pro 12 Rendering Problems Galore

    Posted by Nicholas Mauer on January 29, 2013 at 1:07 am

    Long story short: All my render jobs look like crap. Basically, any project that has the slightest effects applied, mainly pan/crop effects, the rendered output has a bunch of glitchy footage and tearing. I’m at my wits end and I’m about one messed up rendering job away from putting my fist through the monitor. Here’s the setup:

    Import clips:
    1920×1080, 59.940p

    Export to:
    Youtube (preferably in 720p)

    Computer Specs:
    Core i7 930 OC’ed to 3GHz
    24gb RAM
    Radeon HD 7850
    Rendering to a 60gb SSD

    I’ve tried every kind of rendering setup (1080p, 720p, 60p, 60i, 30p, 30i, with GPU, without, etc) and container (.mp4, .mts, .m2ts, .avi, .wmv) and so long as the project settings are set to “Best”, the rendered output is a garbled mess. And that’s the best part, while editing, so long as I have the preview set to “Best->Half”, it works like a charm. I can scrub through the project, preview the project, no problem. The second I switch to “Best->Full” in the preview, things go haywire. I’ll scrub though and things start bouncing around all over the place, but it’s never consistent. Even if I manually bounce between two frames, it’s never the same glitch. Sometimes the clip will have multiple instances of itself spread across the screen, sometimes it’ll have clips from completely different clips within the project, and sometimes, just to blow my mind even further, it’ll work fine.

    It’s frustrating to an absurd degree. Building a complete project, then watching the final render crumble before your eyes. It’s like watching your house burn down. I post an example if anybody response. Until then, you can find me in the corner, crying.

    Bill Campbell replied 13 years ago 9 Members · 17 Replies
  • 17 Replies
  • Steve Rhoden

    January 29, 2013 at 2:14 am

    You are having some system conflict and corruption going on
    with your system and Vegas. Have you already tried uninstalling
    and then reinstalling Vegas 12 (Build 394)?

    Steve Rhoden
    (Cow Leader)
    Film Editor & Compositor.
    Filmex Creative Media.
    https://www.facebook.com/FilmexCreativeMedia
    1-876-832-4956

  • Nicholas Mauer

    January 29, 2013 at 2:43 am

    No reinstall yet. I was trying to avoid that. I’ll attempt a reinstall and respond with a follow-up later.

  • Steve Rhoden

    January 29, 2013 at 4:04 am

    Its never a need to fear a reinstall, it doesn’t disrupts your
    presets, setups or plugins… But at times its necessary to
    correct a corrupt installation or conflicts.
    Have you recently installed any other video based software
    on your system by the way?

    Steve Rhoden
    (Cow Leader)
    Film Editor & Compositor.
    Filmex Creative Media.
    https://www.facebook.com/FilmexCreativeMedia
    1-876-832-4956

  • Phil Seymour

    January 29, 2013 at 7:13 am

    As Steve asks, have you installed any other video software or one or more of the dreaded third-party codecs?

    Windows 7 Pro64, i7 CPU, 16GB RAM, SSD boot drive, GTX 570 Graphics, Vegas Pro 12

  • Nicholas Mauer

    January 30, 2013 at 1:59 am

    Codecs? Blah, I never touch the stuff.

    No other NLE have been installed on this system. However, when going through the reinstall process I realized I made a bonehead mistake: I never uninstalled Vegas 11! D’oh! Sadly though, after uninstalling Vegas 11 and reinstalling Vegas 12, the problem still persists. The only work around I found is to render the project piecemeal in 1080p/60fps, then re-render the clip in whatever format I want it (like .mp4). Nothing else works without it going ballistic.

    I’d be much happier if it through out an error and didn’t render at all, at least I would have something to work with. Instead, I receive a finished painting of a portrait where somebody has smeared red paint with their fingers all over it. It’s depressing.

  • Phil Seymour

    January 30, 2013 at 5:15 am

    Well, maybe the latest build might help. Strange how something works on one machine and not another… provided they are not loaded with tons of crap as our machines aren’t. Oh for Vegas porting to a Mac.

    Windows 7 Pro64, i7 CPU, 16GB RAM, SSD boot drive, GTX 570 Graphics, Vegas Pro 12

  • Dave Osbun

    January 30, 2013 at 2:17 pm

    I wonder if your video card drivers might be the cause of this issue. Do you have the latest Radeon drivers (ver. 13.1)? If you do, maybe you’ll want to try the latest beta drivers, which were released yesterday (13.2). Here’s the link, if you’re running Windows 7:
    https://support.amd.com/us/gpudownload/windows/Pages/radeonaiw_vista64.aspx

    Intel i5 3570K Ivy Bridge 3.40GHz quad core
    Asus P8Z77V-LK
    16gb RAM
    ATI Radeon HD7850 2gb
    Crucial M4 SSD + Seagate Barricuda 7200rpm
    Windows 7 Pro 64

  • Jay Allen

    January 30, 2013 at 3:54 pm

    I have all the same problems you are having. I loaded the new build yesterday and just to confuse me more I tried rendering to main concept and still crashed, but when I turned on Cuba it rendered – just the opposite of what you would think.

  • Mark Barton

    January 30, 2013 at 6:29 pm

    Well if I had this problem, I would not be overclocking my CPU, while I was trying to find the problem. You don’t have ECC RAM, so just because it runs is no guarantee the data is not getting corrupted in the process. This might be why it works when you break it down into smaller batches.

  • Nicholas Mauer

    January 31, 2013 at 12:43 am

    [Jay Allen] “when I turned on Cuba it rendered”
    What does that mean?

Page 1 of 2

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