"What, specifically, are these "serious bugs in their code?" I mean actual bugs that anyone can reproduce on any machine. I'm not being sarcastic or flip, let's list the actual known bugs."

If you mean reproduceable at will then apart from what others have mentioned above and which one could simply dismiss as limitations or that can be worked around, then well, none.

However that does not mean that Vegas is fit for purpose. There remains a bug that is not reproduceable at will. It was the subject of a recent thread and one that I have been affected by at least twice in two end to end projects.

For some obscure reason Vegas will change the file the timeline references. All efforts to replace the file being referenced fail. The only fix is to delete the file from the project and import it again. This can result in considerable loss of work or reputation if the problem is not detected and on a large project the latter is quite probable.

One user posted that his attempts to report this problem resulted in a somewhat curt reply that it was "impossible" and "we've never heard of any such thing". In a recent conversation with the departed Lars he too has encountered this problem in his remaining Vegas project.
What makes this problem even more difficult is it's quite possible a user might encounter it and assume they'd made a mistake. I may well have seen it before and simply deleted the errant event and redone it. It was only by chance that on these two projects I had one piece of media that was over 1 hour long split into many events that I realised I could not have repeated the same mistake that many times and realising the considerable work if I simply deleted the file from the project that I tried replacing it, which simply would not work. It was only then that I realised something very serious had gone wrong with the project.

I still have the mangled project files backed up. I will try submitting a ticket although I don't hold out much hope of the problem getting any attention.

In regard to the overall stability issue with large projects that I started a thread about much to my initially pleasant surprise support raised a trouble ticket for me. I held high hopes, I even followed to the letter their advice to totally remove all traces of any SCS code or registry entries. Needless to say it made no differences. As clearly this was a live problem I offered to ship a copy of the entire project to SCS at my own expense. One would think a business that takes their products seriously would jump at the offer but no, they never replied.

Others I have been in contact with have had the same sorts of reponse. Of all the laughable replies the classic was "we don't have the hardware to run such projects". One can only hope that going forward there's a few of those $7K Supermicro PCs made available to the folks in Maddison.

Bob.