SONY VEGAS PRO 12 RENDERING PROBLEMS

tara-z wrote on 1/3/2017, 12:34 PM

Hi! I’ve had Sony Vegas Pro 12 for a while with no problems, especially with rendering. I’ve also had sapphire and new blue fx and rendered a video with those effects with NO problem. But suddenly, after editing a new video for 6 hours and the video is only 2 min, the rendering won’t work. It takes 3 hours (does not take that long for me usually) to render, but it stops halfway saying my computer does not have any space left which is pure bullshit. I’m really upset and I really want this video to render perfectly as it did before so I can upload it. Can anybody help? It turns black for like 5 min before it renders with a clip from my video but the min/sec goes far up to 3 hours and then it freezes at maybe 28% and says my computer does have not any space. I even tried to cut the video to 30 seconds and it will still not work. HELP!!

http://i68.tinypic.com/9057kl.jpg here does it look like. It has been on 0% and going to over 4 hours of rendering for a 2 min video. HELP MEEE

Comments

3POINT wrote on 1/3/2017, 2:55 PM

Go to File/Properties (Project Settings) and set Pixel format to 8-bit, this will probably solve your problem.

NickHope wrote on 1/3/2017, 9:32 PM

Troubleshoot with this post: https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-stop-vegas-pro-hanging-during-rendering--104786/

Go to File/Properties (Project Settings) and set Pixel format to 8-bit, this will probably solve your problem.

That's a very specific piece of advice. There's a myriad of other things that could be causing the problem. Any particular reason you focused on that? If this is something that has been shown to help hung renders then I'll add it to the FAQ post I linked to.

Red Prince wrote on 1/3/2017, 9:43 PM

Hi, Nick. This reminds me of something. I wrote an OFX plug-in which required the host to use the 32-bit format (and of course it told the host so). I was testing it on Vegas 12 at the time and everything worked fine. Then I tried switching to the 8-bit mode, and much to my shock Vegas was happily sending 8-bit data to the OFX plug-in. That is a violation of the OFX specification. Vegas should have either converted the data to 32-bit before passing it on to the plug-in (and converted it back to 8 bits after the plug-in returned it) or rejected the plug-in.

I have not tested it with VP14 because my health has been poor lately and this is just too much work for me. But that may be the reason for that specific piece of advice: Perhaps it is an 8-bit plug-in and Vegas just ignores that and sends it 32-bit data when editing in the 32-bit mode?

EDIT: Edited for grammar.