Odd Crash

Red Prince wrote on 7/14/2018, 2:56 PM

Occasionally, I experience a rather odd crash. Like today. I created a new project, added media to it, arranged everything on the time line, added some titles, and when was satisfied with everything, I saved the project and rendered it. After that, I clicked on the little x in the upper right of almost every Windows program, telling Vegas to quit. It was then that Vegas complained it had just stopped working and popped up the report window. I was off line, so I had to turn on my Internet “modem” just to allow Vegas to send the report.

So, what is odd about it? That Vegas complains about it stopping to work, when that is exactly what I want it to do. The project was saved and even rendered, so there was nothing else to do, yet if moans, hahaha! 😲

And yes, this is the current version VP 15.

Comments

Grazie wrote on 7/14/2018, 3:04 PM

I’ve learnt so save, exit, Reboot PC, reopen project and then Render.

Musicvid wrote on 7/14/2018, 3:45 PM

It's happened to me with some QT, I just ignore it because the files are ok

Red Prince wrote on 7/14/2018, 10:33 PM

I generally ignore it, too. I just find it weird. Once I’ve told it to quit, what’s the point of saying it stopped to work?

I’ve learnt so save, exit, Reboot PC, reopen project and then Render.

Reboot? I usually have no problems with Vegas. I just mentioned this one because I find it kind of redundant. And in a way humorous.

EricLNZ wrote on 7/14/2018, 10:49 PM

The "error" on shutting down has featured in previous threads. If I recall correctly developers have tried to find the problem and fix it but without success. It occurred for me with several versions of Movie Studio but disappeared after I removed the NewBlue Titler that came with one MS version. So possibly it's one of your plugins that's causing the problem.

Red Prince wrote on 7/14/2018, 11:11 PM

So possibly it's one of your plugins that's causing the problem.

Well, all I did in this particular project was show a static image followed by a single ProRes video clip, and finally several instances of Vegas Titles & Text. No third party plug-ins, no color grading/correction, nothing complicated.

At any rate, I did click to send the report, so they should have all the information they need to find the problem (I mean in this particular case, not for all other such occurrences). And the video is the one I have just posted in this thread.

EricLNZ wrote on 7/14/2018, 11:22 PM

I meant the existence of a plugin on your system might be causing the problem, not that you were using it. I never used NB Titler which is why I removed it.

As for sending the report my impression from comments on this forum is that it's a waste of time. You need to lodge a ticket with Magix for it to get looked at. This thread refers. https://www.vegascreativesoftware.info/us/forum/how-to-send-error-reports-using-the-problem-reporting-service-prs--103727/

Red Prince wrote on 7/14/2018, 11:47 PM

Well, I’m not going to do that. If they can’t be bothered to read the reports they have programmed into Vegas, why should I do their job for them?

As for there being a plug-in that causes the problem by merely existing, if so, the problem would be happening consistently, not just once in a blue Moon. Besides, Vegas knows which plug-in it is telling to that it is closing down when the crash happens, so it is trivial (yes, trivial, I know, I write software, been doing it since 1965) for them to find out what causes the problem by just reading those reports.

EricLNZ wrote on 7/15/2018, 4:49 AM

Well, I’m not going to do that. If they can’t be bothered to read the reports they have programmed into Vegas, why should I do their job for them?

I read somewhere a few years ago that the reports go to Microsoft, who then pass them on. I don't know how true that was or if it's still the case.

ritsmer wrote on 7/15/2018, 9:17 AM

Well, I’m not going to do that. If they can’t be bothered to read the reports they have programmed into Vegas, why should I do their job for them?

I read somewhere a few years ago that the reports go to Microsoft, who then pass them on. I don't know how true that was or if it's still the case.

Being a software developer/programmer like Red Prince I fully agree with his views.

I sincerely do hope that my time used for filling in hundreds of crash reports has not made a complete fool of me: It is simply inconceivable that a software company knowingly lets their software urge their users to use the users time to describe the circumstances, give ideas etc. about all the crashes - if the company does not take proper care of the answers.

So I respectfully urge Magix to return here and officially tell us that they do receive and scrutinize the crash reports - or say "Sorry for your wasted time, folks" and tell us that the crash reporting is no longer a part of very next update - please.