-
Odd Vegas & QT Issue & Solution
I’m posting this in case I can spare someone else my headache.
In short, I was attempting to render a very short spot to an uncompressed MOV. The render would hang everytime without rendering a single frame (Vegas didn’t crash – it simply sat still until I cancelled the render)
After uninstalling and reinstalling EVERYTHING related to production on my PC, on a whim I tried rendering to a different hard drive.
AND IT WORKED!
So, before you set about reinstalling things when a render breaks, try rendering to a different destination.
Question: can anyone explain why this issue arose in the first place? It seems strange to me.
Sean Robinson
-
3 Replies
-
Dude, you fell for the old separate-hard-drive-stalled-render trick! ha!
Just kidding man. That is handy to know. Thanks for posting.Jeff
2-Xeon X5680 @ 3.33 MSI Mobo 48GB DDR3 GTX 580 3072MB 16TB Attached Storage Win7 Vegas 11 x64
-
That seems odd. I do know that you need twice as much render space on your hard drive for MOV files because Vegas writes to a temporary file first and then makes a copy of that file to the final MOV file. Why it doesn’t just rename it .mov is anyones guess but it does require that you need 2x as much space and for uncompressed that could be huge.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
It was a 320GB drive that was nearly empty except for media for the project I was trying to render. I agree that it is odd – I hope someone has a suggestion about what I might investigate.
Reply to this Discussion! Login or Sign Up