Not to be too pedantic here, but if the Vegas programmers could figure out what's causing the crashes enough to be able to predict when you'll have problems, they would fix the problem!
I think you'll find that your crashes are rather atypical and centered around your installation. Most of us successfully work on hours-long projects with no issues.
I am new to Vegas Pro 9 and been working on my first project with it. I finished, a 37min run-time HDV video which comprised mainly of HDV footage shot on my Canon XH-G1 and some still clips plus various sound bites and background music, certainly nothing major - indeed, I completed a similar project using Pinnacle's Studio 11 last year - Studio mmanaged it perfectly, first time - a product that cost me a mere 79 pounds.
Fastforward one year and I progress and shell out five times the cost of STudio to buy Vegas Pro 9. I also build a computer specifically for video editing (I am an A+ technician so quite competent in system building).
Then, the excitement(?) my first project begins. and after my second day working on it I noticed that a clip had disappeared off the timeline that I was sure I had put on the previous day. I thought nothing of it at the time. A few days later and I noticed a gap in my timeline, where a still image (.jpg) had been placed...again, I thought nothing off it and dragged it back from the Project Media.
Then, to render! Well, first I had to pander to Vegas' quirks and close every service in order for it (Vegas) to stop crashing or tellingme it was low on memory (2 mins into a render????).
It was getting late.... I decided to save the project and sleep on it. The next day, I opened Vegas and found 3video clips and one audio had disaapeared from the timeline - shame I didn't check before rendering! I foolishly thought Vegas would have done what I asked and actually 'saved' everything. After 2.5hrs of rendering I then discovered the missing clips/events!
I was so angered by this I replaced the missing clips, saved and left it another day before rendering again. The next day I opened it up and - you've guessed it - 3 still images and 2 audio events missing from the timeline. I replaced them again and immediately rendered after saving, closing and re-opening making sure all was well with the timeline - for some weird reason this now took 4hrs 41mins to render! - just video (Mainconcept Mpeg2).
I contacted Sony support - they imply this just doesn't happen and answer me as though I am the only person EVER to have this problem, they suggest I close all running programs and if necessary re-install Vegas - GREAT!
I have never had consistent results with MOV files. Vegas uses the separately installed version of Quicktime to handle the files and I just don't think Apple knows how to write decent PC software. The newer versions of Quicktime have been a well-documented disaster and I find that the v7.2 version of Quicktime has the fewest problems in general. Personally, I will not blame Vegas for any MOV related problems.
"Personally, I will not blame Vegas for any MOV related problems."
Who decided to use the free, separately installed version of Quicktime, SCS!
SCS chose to use it, if what they chose to use instead of writing their own code is broken they alone are to blame. As you said, it's been well known for a long time that Apple cannot write good code for Windows.
It would seem every other vendor of NLEs for Windows knows of this problem and dealt with by writing their own code.
Lars. I have a question and I promise its not meant to be rude. If you have access to these other NLEs, and you are having good success with them on your system, why are you bothering with Vegas at this point? Is it just a principle issue at this point? I could understand that. If you paid hundreds of dollars for a program, you're right to want it work properly. But it sounds like you are just beating a dead horse here. If you have access to tools that work for you. Why not just use them instead?