Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Problem with rendering to MainConcept in Sony Vegas Pro 11

  • Problem with rendering to MainConcept in Sony Vegas Pro 11

    Posted by Michal Bronec on October 27, 2011 at 6:38 pm

    When using Sony Vegas Pro it wasnt problem, but in Sony Vegas Pro 11 I’m getting this error message: “An error occured while the media file. The reason for that error couldnt be determined”. What should I do?

    I used this format for rendering videos for Vimeo/Youtube etc. If this wont work in Sony Vegas Pro 11, what format do you recommend me for this?

    Michael Morlan replied 13 years, 3 months ago 11 Members · 12 Replies
  • 12 Replies
  • Doug Davis

    October 27, 2011 at 7:10 pm

    I have the same issue.. When rendering to an mp4 it doesn’t even start I get an error stating I don’t have enough memory. It works fine in 10.0 and I’ve got 6gb.. *Sigh*

    definition of upgrade = take out old bugs and put in new ones..

  • Dave Haynie

    October 27, 2011 at 7:30 pm

    I’ve seen similar bugs with Main Concept MPEG-2. For one, it seems bitrate related… I get the “reason can’t be determined” error instantly if I render to a 50Mb/s CBR preset I used extensively in Vegas 10. If I got a 35Mb/s variable bitrate preset, it renders awhile before failing. I may have seen something similar on Main Concept AVC as well… templates that worked fine in 10 but fail in 11.

    The current problem is that the nVidia GTX570 graphics card, the very latest nVidia drivers, and a render to either Main Concept CODEC with GPU enabled results in a GPU-related crash.. not even the mysterious “just stopped” error. This doesn’t happen with any other CODEC.

    I realize that Main Concept sells Sony these CODECs, and I don’t know the level of information available. But for a professional product, “it failed and I just don’t know why” is a totally unacceptable answer.

    -Dave

  • Michal Bronec

    October 27, 2011 at 7:42 pm

    Ok, it doesnt work. So whats the best way for exporting videos (in my case Canon HDSLR mov files) for the internet (Vimeo/Youtube/flash conversion)?

  • John Gordon

    October 27, 2011 at 9:21 pm

    It seems the workaround for this is to not use the GPU for rendering AVC codec. If your GPU is not on the suppported list, you should be using the CPU for rendering.

    https://www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=783051&Replies=9

    John Gordon

  • Elvis Deane

    October 27, 2011 at 9:49 pm

    I don’t have GPU rendering available because of an old video card, and I still get that “undetermined error”. I’ve just started rendering to Sony AVC codec instead.

    Going to pick up a new video card tonight hopefully, and will try it again after.


    Elvis Deane!

    Impossibilia

  • Henk V.d. munnik

    October 28, 2011 at 1:20 pm

    I have the same problem with the Mainconcept. It is a real faillure. I only use the Pro 11 Trial. (registered user of Pro 10)
    If you use the new menu-item Upload to YouTube, you can use the standard quality. But if you want to use the higher quality the problem also occurs. So i assume tha Vegas use the Mainconcept for uploading to YouTube. There is work te be done for Sony. At this time i don’t upgrade to a program that give trouble while it is working fine in Pro 10.

  • Dave Haynie

    October 28, 2011 at 6:25 pm

    The “undetermined error” has always been there, as far back as I can recall. I used to think it was due to a mis-match between the GUI settings and the actual rendering engine. So I’d set a value outside the range of the rendering engine, Vegas let me, but the engine itself kicked it out.

    Just a guess. But they’re just being lazy here, not returning any sort of useful error code. Something, somewhere in the system knows there’s an error, or it wouldn’t have stopped rendering. We’re just not given that information. And if it does relate to settings, that needs to be fixed in the Vegas UI.

    Thing thing about Vegas 11… this has gotten worse, and it’s not GPU related. Could be the same problem I guessed at — we’re clearly running new version of the MainConcept CODECs, since these support GPU acceleration, the old ones don’t.

    -Dave

  • Ted Snow

    October 28, 2011 at 7:21 pm

    This also is from Sony’s website…

    GPU-accelerated rendering with the MainConcept AVC format

    GPU-accelerated rendering with the MainConcept AVC format can fail if your system has an NVIDIA CUDA driver but no NVIDIA CUDA-capable GPU is installed. This will result in an error dialog when as soon as you try to render with the MainConcept AVC format. To fix this, uninstall the NVIDIA CUDA driver, or Render using CPU Only in the Customize Render Dialogue.

    this is the address

    https://www.custcenter.com/app/answers/detail/a_id/5068/kw/5068

    ————————————————
    ASUS P8P67 Deluxe MB
    EVGA GeForce GTX 560 Ti 1 GB DDR 5
    Intel i7 2600k 3.4 Ghz
    Corsair HX750 power supply
    Two Seagate Barracuda 500g SATA III drives
    16 Gig G.Skill Ripjaws DDR3 1600
    Canopus ACEDVio card
    Thermaltake V9 BlacX Edition case
    Xigmatek Dark Knight CPU Cooler
    Win 7 Pro
    VEGAS 8.0
    VEGAS 11.0 32 & 64 bit
    Sony VX2100
    Sony HVR-Z7U hi def
    Alesis HD24

  • William Childress

    November 18, 2011 at 1:33 pm

    I was getting the exact same error with an ATI Radeon 5770 video card. I noticed that the 11.2 drivers were mentioned on the Sony website. They said anything above a certain driver, but I had a hunch and decided to try it. I had loaded the latest driver version 11.11 and GPU accelleration for the MainConcept encoder was a no go. I downloaded the 11.2 drivers and did a custom uninstall related to the OpenCL SDK. I then I did a custom install for the same SDK from 11.2 instead of 11.11. It worked and started encoding immediately without the error. There are issues with the current drivers that still need to be resolved.

  • Jonathan Sperling

    January 18, 2012 at 2:54 am

    Wait I’m confused… Do you mean you did a custom install for the sdk from 11.11 not 11.2?

Page 1 of 2

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