Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Error rendering MP4

  • Error rendering MP4

    Posted by Peter Brown on November 26, 2011 at 10:08 pm

    When I try to render in MP4 (main concept AVC/AAC ) I get an Unknown error
    it say vegas cannot determin the error .
    Does anyone have any idea’s?

    Joe Martinez replied 13 years, 2 months ago 7 Members · 11 Replies
  • 11 Replies
  • Steve Rhoden

    November 26, 2011 at 10:46 pm

    What version of Vegas are you using?
    Ive heard similar complaints with this in Vegas 11.

    Steve Rhoden
    (Cow Leader)
    Film Maker
    Filmex Creative Media.
    1-876-832-4956
    https://filmex-creative-media.blogspot.com/

  • Angelo Mike

    November 26, 2011 at 11:21 pm

    I’ve gotten that a few times as well. No idea what caused it, but it usually went away on its own.

    http://www.scenethroughglass.com

  • John Rofrano

    November 27, 2011 at 1:52 am

    Are you getting this error using one of the build-in templates?

    Usually an unknown error when rendering can be caused by selecting rendering options that are incompatible. Vegas will happily allow you to select options that don’t work together. It’s best to stick with the templates and not change them unless you are certain of what you are changing.

    ~jr

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

  • Peter Brown

    November 27, 2011 at 8:12 am

    Hello Again
    Thanks for all your input
    Yes John I tried other MP4 templates without changing them: (I tries Sony Internet 1080p and 720p) still got the same error?

    And yes I am using Vegas pro 11

  • John Rofrano

    November 27, 2011 at 6:42 pm

    [Peter Brown] “I tried other MP4 templates without changing them: (I tries Sony Internet 1080p and 720p) still got the same error?”

    Does it give you the error right away or does it render for a while and then give the error?

    ~jr

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

  • Peter Brown

    November 27, 2011 at 7:35 pm

    It errors right away..
    As soon as I click on “Render” the render dialog box appears then before the blue line comes it shows the error box

  • John Rofrano

    November 30, 2011 at 2:49 am

    [Peter Brown] “It errors right away..”

    That’s usually a bad template but if all the templates are doing that it could be another problem. Do you have any codec-paks installed like K-Lite? It could be that some other codec has replaced the Vegas AVC codec and is causing problems.

    ~jr

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

  • Malcolm Matusky

    December 1, 2011 at 6:55 pm

    I could not render anything in a new install of VP11, did a reinstall with deleting all the downloaded codecs and now it works fine.

    M

    Malcolm
    http://www.malcolmproductions.com

  • John Rofrano

    December 2, 2011 at 4:50 am

    [Malcolm Matusky] “I could not render anything in a new install of VP11, did a reinstall with deleting all the downloaded codecs and now it works fine.”

    …and I know we sound like a broken record when we keep asking people if they have any codec-paks installed but they really do mess up your editing PC and should be avoided unless you’re building a multi-media PC for playback and not editing (which is what they are intended for).

    Thanks Malcom for reaffirming this. 🙂

    ~jr

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

  • Emilio Le roux

    May 29, 2012 at 1:43 am

    In my case I believe this problem began with I installed a new version of my ATI RADEON HD4500 drivers.

    I found out that there is a SYSTEM tab in the template settings with a single button. ‘CHECK GPU’. The button tells me that ‘OpenCL is available’.

    Thus I concluded that the ATI driver installed the OpenCL thing, and now Vegas was trying to use my GPU to accelerate the conversion resulting in some crash in the renderer.

    Solution: in the ‘video’ tab of the settings, there’s a Encode Mode setting. You can set it to ‘render using CPU only’. It solved the problem in this case.

Page 1 of 2

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