Constant crashing with VP18

justin-w wrote on 8/12/2020, 5:45 PM

This is very frustrating. I have been using movie studio platinum for years without issue, and decided to take the plunge and upgrade. I was one of the ones to have purchased VP17 which included the VP18 update. VP17 gave me no problems, but after updating to 18 the program constantly locks up, crashes randomly, locks on renders and other awful unstable behavior. Every time I try to submit a support ticket I get "internal server error" which is only adding to my frustration.

Here's my computer specs:

Ryzen 7 3700x CPU, NVIDIA 1660Ti GPU, 32GB RAM, all SSD storage.

Here's what I've tried to resolve the problem, none of which have worked:

Upgrading and downgrading my graphics driver
uninstalling and reinstalling VP18
turning off GPU rending
turning off Optimize GPU in preview device
setting dynamic ram preview to 0, as well as 10k, both make no difference

The performance of VP18 is basically like an Alpha software and I'm going insane trying to do my job. I'm not happy with Magix at all right now and almost switched over to Adobe until I got a taste of their pitifully slow UI.

Please tell me this will be fixed soon, or if you have some kind of clue how to make VP18 go more than 10 minutes without crashing.

Back to post

Comments

justin-w wrote on 10/28/2020, 3:16 PM

@j-v Doesn't help. Vegas Pro 18 has to be the worst "Pro" software I've ever used in my life. This has been ongoing for months since it came out. My system is plenty powerful enough, has all the latest drivers, great video card, and this is literally the ONLY software that does not function correctly and crashes on my entire system. I've tried multiple solutions, nothing works. The software just crashes constantly. My only alternative now is to find a replacement software and tell everyone I know not to waste their money on a crappy product like VP18.

vkmast wrote on 10/28/2020, 3:55 PM

@justin-w while you're looking for a replacement to "a crappy product like VP18" you might be able to wait for the next update (promised soon) to see if it would help before telling "everyone [you] know not to waste their money" . You did see the comment linked here next to j-v's comment?

justin-w wrote on 10/28/2020, 4:02 PM

Is it really worth it? Once it finally gets updated, then still doesn't work, I'll just be more outraged. I'd rather just start learning something new so I can quit wasting my time on this junk that I already wasted time and MONEY on.

j-v wrote on 10/28/2020, 4:32 PM

Bye and hopefully you are happy with other software, but I doubt if that is possible with you.😬

justin-w wrote on 10/28/2020, 5:02 PM

@j-v it's crazy how people on this forum defend this software like it's a family member. When someone spends $400 on software and it fails to function even basically without constant issues, how can you NOT expect that person to be angry? I used to always give praises to Vegas for years, I've been a user since the Sonic Foundry days. I went through a few Sony versions, but since Magix took ownership it as become a complete Sh**show. I've decided to go with Davinci Resolve for the time being.

RogerS wrote on 10/28/2020, 10:05 PM

Did you ever follow up with Vegas staff and file the support request?

Stephen-Shelton wrote on 10/30/2020, 1:31 PM

It's crashing way more than just during renders. For me it just locks up and I just have to kill the program, no error messages at all. And honestly, if VP18 can't run with the latest Windows updates, that's a Vegas issue, not a Windows one. I'm just going to switch back to VP17 until they iron out the bugs on 18, because right now it's basically unusable.

fyi and level of reassurance and analysis - I have been having exactly the same problems as you are having, EXACTLY the same, and it wasn't happening in V17 either. While some people on here are incredibly helpful, esp as doing it in their free time, to me it seems it has to be a magix software V18 issue, as it happened immediately on the exact same files that render absoultely fine on V17 a few hours before update to V18. We can supply all the mediadata info in the world but it still doesn't get away from the fact there was clearly a bug in the V18 that wasn't in V17 (maybe specific to some users' hardward or type of raw files imported, but still a bug as V17 worked ok) and the frustration is that I seem to have spent a lot of money to buy a bug! And despite all my crash reports sent to them the latest update, out today, crashed with 5 mins of installing!

j-v wrote on 10/30/2020, 1:49 PM

@Stephen-Shelton
Did you also tried the latest update to version 18 build 373?

Stephen-Shelton wrote on 10/30/2020, 2:25 PM

Yep, crashed within 5 mins of installing the latest update. This time from being so reckless as moving the cursor in the edit/pan/crop window of a video file in the timeline. It really doesn't seem to like that happening in V18, can't remember the same problem in V17 tbh.