Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Vegas 13 Render Engine Still Not Usable for Production Work

  • Vegas 13 Render Engine Still Not Usable for Production Work

    Posted by Ken Bennett on July 11, 2015 at 8:23 pm

    That’s right. When V13 came out it caused so many problems I had to go back to V12 to do production work. The problem back then was V13 was so unstable it would crash 5 to 10 time a session. And as I remember, it couldn’t render anything cleanly longer that a few minutes.

    With the latest updates I thought I’d try V13 again. More stable with only about 2 crashes per session,but the render engine… still the worst ever. On any program longer than a few minutes, it with start to insert white flashes (full single frames of white) that get more frequent as the program plays. First it’s a flash every few minutes. By 2/3s of the way into the program it is flashing about every 1 or 2 seconds. Total insane.

    And the other major issues with V13’s render engine is the render time. My 90 minute show is taking 5 hrs and 20 mins to render. Whereas in V12 this would take about 2 hrs.

    Is anybody really using V13 with any success? And is there anything we can do? Sony seems to not care any more. Does Sony want me to move to Adobe Premiere Pro or Apple FCP X?

    Help? Maybe!

    Ken Bennett
    Video Adventures
    Capturing Your Life’s Adventures!

    Aaron Star replied 11 years, 1 month ago 5 Members · 17 Replies
  • 17 Replies
  • Steve Rhoden

    July 11, 2015 at 8:51 pm

    Is anybody really using V13 with any success?
    Yes, I am… For extensive Production Work and Broadcast content
    24/7 right around the clock, fast with not a single issue or rendering anomalies!

    Steve Rhoden (Cow Leader)
    Film Maker & VFX Artist.
    Owner of Filmex Creative Media.
    Samples of my Work and Company can be seen here:
    https://www.facebook.com/FilmexCreativeMedia

  • Ken Bennett

    July 11, 2015 at 10:08 pm

    Maybe you can tell me what your system has and what settings you have in V13. Because nobody has been able to provide such info to me. I don’t have any of these issues in V12.

    THX

    Ken Bennett
    Video Adventures
    Capturing Your Life’s Adventures!

  • Steve Rhoden

    July 11, 2015 at 11:23 pm

    Well, i use basic powerfully built off the shelf systems, simple, that’s it.
    I do not use any specialized GPU card any at all, that’s the key of my
    peace of mind with Vegas…(I’ve made long and detailed posts here
    in the past about why i choose this root and dont use specialized GPU cards
    ),
    but that’s too long for me to get back into right now.
    so that’s it in a nutshell!

    Steve Rhoden (Cow Leader)
    Film Maker & VFX Artist.
    Owner of Filmex Creative Media.
    Samples of my Work and Company can be seen here:
    https://www.facebook.com/FilmexCreativeMedia

  • Wayne Waag

    July 12, 2015 at 12:10 am

    Like Steve, I’ve never had a problem like you describe with V13 or V12 or any other version. I don’t do production work, but I do a lot of rendering and I’m sure the machine doesn’t know whether I’m a hobbyist or professional. For me, the opposite has been true–V13 has been so much more stable than V12. The conventional wisdom is to disable your GPU in Video Preferences (although I’ve never had a problem) and to render using CPU only. If you are still having problems, then you’ve got some other system problem and/or problems with your source material/project/render settings although that seems a bit unlikely.

    wwaag

  • Stephen Mann

    July 12, 2015 at 2:55 am

    I buy the upgrades as they come out, even mid project. Never a problem. (Well there was that text problem in 10, but Sony fixed it pretty quickly).
    Of course, I don’t try using GPU. I firmly believe that GPU support should default off. Turn it on when you are satisfied that everything else is working.

    Another tip I have – never overclock your editing PC.

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

  • Steve Rhoden

    July 12, 2015 at 3:26 am

    Not to mention Vegas Pro 13 is a major improvement over Vegas Pro 12
    in every way including stability, SO, im very much unsure where your
    issues are stemming from Ken.

    Steve Rhoden (Cow Leader)
    Film Maker & VFX Artist.
    Owner of Filmex Creative Media.
    Samples of my Work and Company can be seen here:
    https://www.facebook.com/FilmexCreativeMedia

  • Ken Bennett

    July 12, 2015 at 3:49 am

    I guess the only answer for me to keep Vegas is to find a PC/Vegas guru who can remotely logon and check my system and settings. Because so far, all I’ve gotten from my sources are “maybe this” or “maybe that”. So if V13 really is more stable and works great with others, there has to be a gremlin in my setup.

    Ken Bennett
    Video Adventures
    Capturing Your Life’s Adventures!

  • Steve Rhoden

    July 12, 2015 at 6:36 pm

    Trust me, something is lingering there on your system that’s conflicting
    with the performance of Vegas 13, the thing that baffles me is why its not
    affecting Vegas 12.

    Steve Rhoden (Cow Leader)
    Film Maker & VFX Artist.
    Owner of Filmex Creative Media.
    Samples of my Work and Company can be seen here:
    https://www.facebook.com/FilmexCreativeMedia

  • Wayne Waag

    July 12, 2015 at 7:34 pm

    I presume that you’ve already tried turning off your GPU and performed a clean re-install of V13. As I recall, when I went from V12 to V13, I had problems at the outset, finding certain plug-ins like Mercalli and Vegasaur did not work properly. In V13, I believe there was a complete rewrite of Vegas making use of a later version of Microsoft’s DotNet framework, that was included in the Vegas installation file. The solution for me was to remove the older versions and install the newest version which at the time was 4.5.1. There is a diagnostic tool available from MS that will tell you exactly what versions are installed on your system. Supposedly, multiple versions should not be a problem, but in my case it was, although I had to reinstall a very old version 1.1 to support Procoder. If you try this, make sure that you back up your system completely and also create a restore point. As a last resort, you could always do a clean install of the OS and “start from scratch”, although I’d be loathe to do this.

    wwaag

  • Steve Rhoden

    July 12, 2015 at 7:59 pm

    From what im seeing, it may be a little deeper than that Wayne!

    Steve Rhoden (Cow Leader)
    Film Maker & VFX Artist.
    Owner of Filmex Creative Media.
    Samples of my Work and Company can be seen here:
    https://www.facebook.com/FilmexCreativeMedia

Page 1 of 2

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