vegas pro 15 an error occurred while creating the media file...

iggy097 wrote on 8/30/2017, 3:09 PM

Kept getting this error, everytime I clicked render ( never even got to the option to choose what type of render ) "vegas pro 15 an error occurred while creating the media file an invalid argument"

This was after I had rendered several projects.

Rebooted.

Uninstalled/Reinstalled - same thing.

Had to reset settings to default using this "Press CTRL+SHIFT while double-clicking on the program’s icon to launch it.  Continue to hold the CTRL & SHIFT keys until the program is fully up and loaded."

And now it works again.

Thought I'd share in case someone else is having the same issue.

Comments

iggy097 wrote on 8/31/2017, 1:42 PM

Issue happened again, once again had to reset back to default and clear cache in order to render anything.

monoparadox wrote on 8/31/2017, 1:59 PM

I have this same issue. Rendering works if I use the batch script so I doubt it is an actual rendering issue.

-- tom

monoparadox wrote on 8/31/2017, 4:40 PM

Issue happened again, once again had to reset back to default and clear cache in order to render anything.


Resetting or clearing the cache makes no difference for me. A search of the forum archives doesn't reveal much about any solutions. Seems it could be an error handling exception flowing from a fairly obscure issue that is hard to replicate.

-- tom

NickHope wrote on 9/1/2017, 12:24 AM

Report it please guys at https://support2.magix.com/customer/en/vegas/form , including as much detailed information about the problem as you can.

iggy097 wrote on 9/1/2017, 2:05 PM

I have this same issue. Rendering works if I use the batch script so I doubt it is an actual rendering issue.

-- tom

Rendered a file. Then clicked render again - got the error. Wtf - as per your suggestion, I WAS able to batch render the project successfully. It's something to do with clicking the render button and or choosing to render.

I submitted the problem as Nick suggested as well.

iggy097 wrote on 9/4/2017, 9:57 AM

I would love for this to be patched as it is making work extremely annoying. Anyone know how long it takes back to hear from a support case?

NickHope wrote on 9/4/2017, 10:30 AM

I would love for this to be patched as it is making work extremely annoying. Anyone know how long it takes back to hear from a support case?

Days... to months... to never.

monoparadox wrote on 9/4/2017, 11:22 AM

I'd say the best bet is when an update is available. If that doesn't solve it, We're probably on our own. I don't see other people squawking about the same issue, so we may be in lonely territory. However, it's possible they already know about the issue and it's easier to just fix it than put the effort into reaching us. I'm sure they're backed up with support requests . . . some going back for years. :-(

NickHope wrote on 9/4/2017, 10:02 PM

Another case reported here, which makes it 3. Please add further information here to see if there's a common factor:

  • Vegas version and build
  • Windows version
  • GPU model and driver version
  • GPU acceleration on or off?
  • Rendering format
  • Rendering to what type of device?
     
iggy097 wrote on 9/5/2017, 6:33 AM

15.0 Build 177

Win 10 Pro

GTX 1080 - 385.41

GPU Acceleration on

Render Format N/A - the error occurs the second you click render - you never make it to the screen to choose format - you CAN use Batch Render to work around this and render your project.

Rendering to what type - N/A - see above

My issue is always resolved when holding down CTR + Shift to reset Vegas back to default. And then it will error again sometime later. Maybe 1 render - maybe 10. - Also - clicking the "delete cache" when resetting back to default values is NOT needed.

monoparadox wrote on 9/5/2017, 10:55 AM

15.0 Build 177

Win 10 Pro

Radeon R9 200

GPU Acceleration on

Render dialog won't open because of error. However, using Vegasaur transcoder or the batch script, rendering itself works fine. Resetting Vegas to defaults on startup makes no difference whatever for me. Also, Vegas 14 (still installed) works just fine.

-- tom

monoparadox wrote on 9/5/2017, 1:15 PM

Just an addendum. My WAG is it has nothing to do with the rendering process. It's an error the program is returning when the code is calling for the render as dialog. I might add it also occurs when selecting to "Render to new track" in the tools menu.

-- tom

NickHope wrote on 9/5/2017, 10:27 PM

I think it could be to do with whatever Vegas is trying to load as the default or last-used settings in the Render As dialog. Perhaps something about the folder or filename that it doesn't like.

Or it might just be affected by the choice of temporary file location in the general preferences.

@iggy097 Please keep a note of your render settings, especially folder and filename, to see if there is something different about the last render you made before the error occurred.

NickHope wrote on 9/5/2017, 10:28 PM

Adding a link to @thiaguitoszwarc's post on the same issue.

iggy097 wrote on 9/7/2017, 1:49 PM

This issue affects two seperate computers that I have Vegas 15 installed on. Two completely different machines with different hardware.

To add to this - I heard back from magix

Hello

Thank you for your message.

As a troubleshooting step, click Options > preferences > video tab, turn “GPU acceleration of video processing” to off, and set “dynamic RAM preview” to 0, click apply and OK. 
--
Best regards,
E*** ***

*** - Germany

Managing Director: *** ***, *** ***, *** ***
Commercial Register: ***

http://www.magix.net

*****************************************************************
* Please make sure to include your original correspondence and  *
* leave the e-mail's subject line unchanged when replying. It's *
* necessary to properly assign your message and process it more *
* quickly and effectively.                                      *
*****************************************************************

Dan M <***>

2:20 PM (28 minutes ago)

to MAGIX

That did not make a difference

MAGIX Support

2:30 PM (18 minutes ago)

to me

Thank you for your mail.

Unfortunately, we can't process your request, since your ticket has
already been closed. Please create a new ticket via the support form on
our website:

http://support.magix.net

--
Magix Support System

*** - Germany

monoparadox wrote on 9/7/2017, 5:33 PM

The standard template response for any issue with the word "render" in it.

-- tom

monoparadox wrote on 9/8/2017, 1:51 AM

This issue affects two seperate computers that I have Vegas 15 installed on. Two completely different machines with different hardware.

 

What do you know? I installed Vegas 15 on a totally different box and voila!, same issue. Either there are a ton of people who must have the same issue or we're running something weird ;-) Maybe we're the only one's who have actually tried to "render as" with 15. Maybe we're the only two (or three) that actually installed Vegas 15. Sure are a lot of phonies on this forum pretending they actually installed 15 :-).

Peter_P wrote on 9/8/2017, 2:44 AM

What type of footage are you using and what project settings?

On my system I have no problem to open the render dialog and select and render to various formats.

iggy097 wrote on 9/8/2017, 6:39 AM

What type of footage are you using and what project settings?

On my system I have no problem to open the render dialog and select and render to various formats.

On my main computer it's the raw MTS files from my C100. On my batch computer it is the rendered footage (mp4) that I then batch render to a few different formats.

The issue is that I can spend a day or two rendering projects ( maybe 5 may be 12 maybe only 1 ) and then just randomly the error will pop up and I have to reset all preferences.

Project settings are the default vegas settings.

Peter_P wrote on 9/8/2017, 7:36 AM

Strange. I did not see it any time, mostly using UHDp30 AXVC-S 100Mbps footage in 1920x1080 p30 project to improve preview smotthness.

monoparadox wrote on 9/8/2017, 9:31 AM

My footage is all standard stuff out of Sony Cams: mts mp4 avchd. On my second computer it was a mainconcept mp4 outputted from Vegas 13. Everything works fine in Vegas 14. I don't believe it's a "rendering" problem at all. It is something incorrectly functioning in Vegas or possibly some screwy permission problem. I keep all of my projects on a NAS, so I moved one to the desktop just to make sure it wasn't a network issue. No go.

-- tom

Peter_P wrote on 9/8/2017, 10:18 AM

Did you try this ?

monoparadox wrote on 9/8/2017, 11:15 AM

I don't believe this is a "rendering" issue per se. Rendering via batch script or Vegasaur's transcoder works just fine. In other words, it isn't that Vegas 15 can't render. The problem is the render dialog option window doesn't even open, just returns the error this thread is addressing. Same with rendering to a track. Immediate error thrown. I've never even been able to get the "render as" dialog box to open to make a change. I believe Vegas is throwing an error code and can't figure out how to handle it. Perhaps a permission pulling a file needed to start the "render as" dialog. Perhaps a faulty registry entry, but that doesn't make sense considering iggy's ability to get it to work by resetting to defaults (I can't even do that). My hope is the coders already know what the problem is and will correct it with the next release. Otherwise, it makes working in Vegas 15 a PIA. I will say I'm discovering all the advantages of using Vegasaur's transcoder, but something as simple as "render as" isn't something a person should have to put up with.

BTW, I think I probably put in a support request before iggy and still haven't received a response. Not sure how Magix handles requests.

-- tom

Peter_P wrote on 9/8/2017, 11:45 AM

The reason I asked about the So4 disabling is the text of the mentioned error message “an error occurred while creating the media file...”. It seems to me that Vegas is trying to do some thing with your footage and this may fail with the So4 dll. So please just give it a try 😉