-
This is a new one.. error during rendering, any ideas?
I completed a project, my deadline is Wednesday which is when I’m supposed to hand the finished video over to my client. I am trying to render the footage tonight in mpeg2 to import into DVDA.. when I render I continually get this error message. “An error occurred while creating the media file.. The reason for the error could not be determined” (see image below) This is a new one, I’ve been with pro since 6 and I’ve NEVER encountered any issues with Vegas while it’s rendering a project. So I’ve come to the experts.. any ideas of whats going on???
-
12 Replies
-
What version of Vegas are you on and are you using x64?
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
pro 11 and yes 64bit.. and I installed the newest update
“Film is a dramatized reality and it is the director’s job to make it appear real… an audience should not be conscious of technique.” – David Lean
-
A possibility exists that a file exists that the encode process wants to create, and another process has it locked. Try encoding to a different filename.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Yeah I’ve tried that and didn’t help any. Only thing that helps is shutting it down and rebooting Vegas. But I shouldn’t have to do that everytime I edit a project.
I may try to uninstall and reinstall Vegas see if that helps“Film is a dramatized reality and it is the director’s job to make it appear real… an audience should not be conscious of technique.” – David Lean
-
Here are some things to try.
1. Verify that your TEMPORARY FILES folder for Vegas has enough space. See PREFERENCES.
Shutdown Vegas. Then go delete everything in the Vegas TEMPORARY FILES folder before restarting Vegas.
If for some reason, you can’t delete all of Vegas’ temporary files, then see #2.
2. Is Vegas crashing on you? Some times when an app crashes, the process doesn’t completely die and get cleaned up by Windows. So some of the files it creates and uses, including temporary files, cannot be released back to Windows. So even if you restart Vegas, the new Vegas process may not be able to read and write to some of the files it needs.
3. Maybe one of the effects plugins or codecs you are using is having problems with Vegas. Perhaps you are using plugins and codecs that are incompatible with your 64-bit Vegas. Update all plugins and codecs Vegas maybe depending on. Ensure they are 64-bit compatible.
-
Have you made any changes to the template you are using to render with? I know that some changes I’ve made, like increasing the bit-rate too much in Sony AVC using 1280×544, it will give this error. Try rendering with a standard template that was installed by Vegas, such as “Program Stream NTSC Widescreen”.
-Jim.
-
I only render in mpeg2 16:9
“Film is a dramatized reality and it is the director’s job to make it appear real… an audience should not be conscious of technique.” – David Lean
-
Paul,
Make sure you are using a DVD Architect template. Make sure you are not rendering out the audio too (make sure audio is disable in the rendering options).
For DVD Architect, you need to render out the video and audio separately into two different files. I’m not sure, but Vegas might complain if you are trying to render your video with audio when you are using a DVD Architect template. So check this first. If your audio is stereo, you can choose either PCM or AC3-stereo. Go with PCM (uncompressed) and if you don’t have enough DVD space, then decide later in DVD Architect to convert it to AC3-stereo.
If it is still no go for you, you can try to let DVD Architect render it to MPEG-2 for you if Vegas is being a pain in the arse.
From Vegas, render out your file as an AVI using either a LOSSLESS or VISUALLY LOSSLESS codec. Hopefully, Vegas won’t complain here as well.
For LOSSLESS, I use Lagarith. There’s also Huffyuv as well. To reduce colorspace conversions errors, set your LOSSLESS codec to RGB and whatever bit-depth your project is currently in. I usually work in 32-bit, so I set it Lagarith to RGB-32bit.
A VISUALLY LOSSLESS codec will take up less space than a LOSSLESS codec if hdd space is a concern. A VISUALLY LOSSLESS codec will be just as good as a LOSSLESS codec, since humans won’t be able to tell the difference anyways.
Lagarith and Huffyuv are free open source codecs. Google it if you don’t already have the codecs.
Cineform and Avid’s DNxHD codecs are excellent VISUALLY LOSSLESS codecs. Your version of Vegas might already have Cineform. If I am not mistaken, both these codecs are *free* as well. You’ll have to Google them to find where to download them if you don’t already have them installed.
Then DVD Architect can encode your AVI to MPEG-2 with the highest quality that it can.
Cheers!
-
OK, but we have been asking if you’ve tried to use a template that Sony provided on the install and you haven’t let us know if this works or not. Some changes to templates have been known to cause Vegas to hang or give errors on renders, in my experience.
-Jim.
-
sorry i’ve been sick…
Yes I do everything that Sony provides with Vegas“Film is a dramatized reality and it is the director’s job to make it appear real… an audience should not be conscious of technique.” – David Lean
Reply to this Discussion! Login or Sign Up