Vegas crashes when exporting to quick time .mov

[Stuart Bower]

Its funny that you suggested the guy go buy the “new and improved” vegas pro 12. Funny because i bought pro 12 about a week ago as a first time user of vegas and have already experienced the same exact stupid problem the original poster is. I rendered around 350 png stills in Blender so that i could have the alpha channel when editing in Vegas. Opened them fine, editted them into a short movie fine,….. go to render as a .mov and Vegas crashes around 70% every time for the 11 second video. Noticed it WILL render shorter videos into a .mov file (like in 4 second increments). So i split up the 11 second video as three different short clips to render. Worked. Go to combine and render them into 1 .mov file, and again Vegas crashes like 3/4 the way through. So…. Long story short. Paying $400 for Vegas Pro 12 dosnt fix the problem…… lol. Any real suggestions for fixing the problem other than say “wait til pro 13”?

[John Rofrano]

[Stuart Bower] “Opened them fine, editted them into a short movie fine,….. go to render as a .mov and Vegas crashes around 70% every time for the 11 second video.”

Can you render to another format like MainConcept AVC or Sony AVC? QuickTime is an Apple technology that is developed by Apple for Windows and Sony has no control over how good or bad it is.

Having said that, I just experienced a similar strange problem with MOV files in Vegas Pro 12.0. A client gave me QuickTime footage and at 70% of rendering to MPEG2, Vegas Pro 12.0 would render black frames. No amount of re-rendering would fix it and it turned black at different places each time but always around 70% of a 15 minute timeline. I got around it by rendering to CineForm, then made a timeline selection slightly before the black frames and rendered just that selection to CineForm again and finally dropping both CineForm files onto the timeline and rendering the whole project and it worked. So it had something to do with MOV files as a source because using CineForm as a source solved the problem.

I think there may be a pattern here but I’m not sure. Definitely a bug of some kind.

[Stuart Bower] “Long story short. Paying $400 for Vegas Pro 12 dosnt fix the problem…… lol. Any real suggestions for fixing the problem other than say “wait til pro 13″?”

Or waiting for Apple to fix QuickTime. I know you said you are new to this but those of us who have been around remember when QuickTime totally broke Vegas Pro and all other Windows NLE’s (and I believe even their own Final Cut Pro) a while back so it hasn’t been the most dependable software and you will always here the question, “A new version of QuickTime just came out should I install it?” because of the fear of it breaking things again.

Bottom line: QuickTime + Vegas Pro has had it’s history of problems. You did not waste $400 because Vegas Pro 12.0 is an awesome NLE and if you purchased Vegas Pro just to produce QuickTime files then IMHO you should have bought a Mac because QuickTime is the native Mac format not the native Windows format.

~jr

http://www.johnrofrano.com
http://www.vasst.com