Error Creating Media File - No reason

Jim H wrote on 11/3/2014, 4:40 PM

I just updated my rig with a new processor, RAM and GPU. See specs below.
Using Vegas V11 that's up to date.

I've tried rendering previous veg files and a new one but I get the following message almost immediately after hitting the render button:

"An error occurred while creating the media file XYZ.mp4 The reason for the error could not be determined."

Any ideas where to start? I tried rendering with and without GPU.
Everything else seems to run fine. Video Previews are nice and fast but I'm surprised that it still stutters a bit under Good and Best when lots of effects are applied.
I'm eager to see how fast she renders with those 8 cores and 16 thread but I'm stuck. :(

System #1
Computer Brand/Model:
Operating System: Windows 7 64-bit
RAM: 16GB DDR4 @2800 MHz
Processor: i7-5960 @ 3.00GHz
Video Card: Nvidia GTX 980
Sound Card: 8 channel on board
Video Capture:
CD Burner: PX 708A
DVD Burner: PX 708A
Camera: Nikon D7000, Sony HD-HC1

Comments

Jim H wrote on 11/3/2014, 4:54 PM

OK, so I searched on the error message and this nice young man has posted this video on youtube:

His suggestion is to go into Custom Settings turn off Automatic Encode Mode and render with CPU only. And yeah, it seems to be rendering fine now.

But 16 threads are only peaking at less than 25%. And I can't say it's speeding along. Could my hard drive be a bottle neck? I'll have to render to one of my SSDs and see what that does.

Also, what problems could I be having with my GPU and rendering? Anyone got any experience with the new 8 core CPU? Is it faster than rendering on GPU? It's a pretty fast GPU and CUDA compliant.

**Edit: Just rendered a sample veg to SSD and HD. HD wins by a few seconds. So I don't think I have a media bottleneck.

johnmeyer wrote on 11/3/2014, 5:42 PM

His suggestion is to go into Custom Settings turn off Automatic Encode Mode and render with CPU only. And yeah, it seems to be rendering fine now.The hard drive is almost never a bottleneck these days unless you are rendering to uncompressed.

I would recommend that you turn off ALL GPU-related settings, and forget that Vegas even has this feature. A few people say that it works for them, and I'm sure it does, but there sure have been a LOT of problems reported here over the last several years which, like your problem, are solved by turning off GPU.

Nice idea; horrible implementation.

Thought for the day: you don't save time if you have to re-render because of some GPU bug.

OldSmoke wrote on 11/3/2014, 5:58 PM

[I]Also, what problems could I be having with my GPU and rendering?[/I]

And here we go again. You bought the latest and greatest GPU without checking if VP does actually support it. If you want to stay with Nvidia, the GTX580 is the last model that was/is fully supported. There is one tweak you may want to try to get the GTX980 working, it helped some people with GTX780 cards. Go into the internal settings of Vegas Pro by holding down SHIFT while pressing Preferences under Options. This will bring up the Internal tab. On the internal tab, at the bottom type in "opencl memory" which bring up the "OpenCL Memory Filter Size" field. Change the value to 2048. Save it and restart VP. If that did the trick, try and see how high you can go with this value. If not, you are stuck.
Aside from Nvidia, the ATI/AMD R9 290 is another great card that works well with Vegas.
In general, those that cant get GPU acceleration going have the wrong hardware...sorry to be so blunt.

Logan5 wrote on 11/18/2014, 9:29 PM

Thanks for posting the fix Jim - that was just want I was trying to fix.