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.

if VP18 can't run with the latest Windows updates, that's a Vegas issue, not a Windows one.

This isn't true at all, solid apps get broken by windows updates all the time. If that app relies on something in windows to work, and windows updates it poorly, therefore breaking it, that app is too going to break with it. I've had windows updates mess my day up in many commonly used creative apps, none are immune to it.

That said, that probably isn't the cause, I was just curious to experiment.

well, that's true, but VP18 ran horribly since the moment I installed it. Also, no I didn't try the suggestion, because the crash he is describing in this post is not at all what I am experiencing.

What media are you using? DJI or GoPro?

Maybe try enabling legacy AVC decoding if you're really having issues.

That can be done in the file I/O tab in preferences.

What media are you using? DJI or GoPro?

Maybe try enabling legacy AVC decoding if you're really having issues.

Oh yeah, I forgot to mention I tried that already too. I'm shooting with a Canon SL2 full HD, and an iPhone 11.

Is the iphone 11 shooting HEVC? Perhaps try proxy files for it. SL2 is just a 1080p Rebel, right? That footage ought to work fine.

Is the iphone 11 shooting HEVC? Perhaps try proxy files for it. SL2 is just a 1080p Rebel, right? That footage ought to work fine.

No, I have the iPhone set to most compatible which makes it shoot in H.264

Just for testing, can do you make a project with just Canon footage and see if it works any better? Something is strange here (I haven't yet seen a Vegas 18 crash with Canon footage), but we haven't figured out what yet.

Just for testing, can do you make a project with just Canon footage and see if it works any better? Something is strange here (I haven't yet seen a Vegas 18 crash with Canon footage), but we haven't figured out what yet.

No offense guys, but no. I didn’t spend hundreds of dollars to do testing. This should be done by the software developers before it’s released to the public. I’ve just switched back to 17 for now and if that gives me any crap I’ll just go back to 16 in movie studio. I edit and upload on average 5 videos a week and don’t have time, nor the interest to mess around with this stuff. Sorry, I just feel very ripped off at this point and would like some kind of real answer or update from Magix. So until then I’ll be using what works.

I just finished editing for hours in VEGAS with no issue, editing 4k HDR video from multiple cameras, so while I can relate to your frustrations, as I've had my share of headaches with various versions of this software, your issue is not widespread. Many of us are using VEGAS 18 mostly without issue.

If you want any more help, we're going to need you to work with us. Otherwise, good luck finding the solution to your problem.

Well, if you want individualized support from Magix, file a support request.

It's unusual that an older version works well and a new one does not- generally it's getting more stable with less user intervention.

Well, if you want individualized support from Magix, file a support request.

It's unusual that an older version works well and a new one does not- generally it's getting more stable with less user intervention.

Thanks for trying to help guys, but like I mentioned, I did try to do a support request, but was met with "internal server error" every time I would hit submit" this went on for a few days, only fueling my fire of anger. All of this was happening. I eventually gave up and came here to the forums.

I just finished editing for hours in VEGAS with no issue, editing 4k HDR video from multiple cameras, so while I can relate to your frustrations, as I've had my share of headaches with various versions of this software, your issue is not widespread. Many of us are using VEGAS 18 mostly without issue.

If you want any more help, we're going to need you to work with us. Otherwise, good luck finding the solution to your problem.

Given that VP18 has only been out about a week, and looking through the forums just briefly I see a lot of complaints. So I might argue that you having 'no issues' is the rare case in this for VP18.

I know you guys are trying to help and I appreciate it, but with the amount of money I've given Magix since they took over the Vegas product is quite high and I feel like I'm using an unstable Linux app. So I'll cool off a bit, go back to using 17, and maybe come back in a few weeks. Or maybe I'll just cut my losses and learn Premeire Pro.

@justin-w
In order to help, we really need more information than you have provided. Also, if VEGAS Pro 18 is crashing for you, please send in the error reports with a description in the text field indicating what you where doing when you saw the crash. Also adding your username "justin-w" to the end of the description will allow us easily search for your problem.

Or, to make the process more streamlined, please submit a support ticket.

@justin-w
In order to help, we really need more information than you have provided. Also, if VEGAS Pro 18 is crashing for you, please send in the error reports with a description in the text field indicating what you where doing when you saw the crash. Also adding your username "justin-w" to the end of the description will allow us easily search for your problem.

Or, to make the process more streamlined, please submit a support ticket.

What information specifically do you need? As I have stated twice in this post already, your support ticket system appears to be broken and returns a "internal server error" every time I try to submit one.

Here's what we usually ask users to submit to get us started with chasing down the cause of a bug:

1. Run a mediainfo report on the two types of media you have in your project (one for the iphone, one for the canon), and paste the results into this thread.

2.We need your project settings. A snapshot works best. Can take that using the windows snip tool and then upload to here.

3. Which build/version of windows 10 you are using. This can be found in system information.

4. The GPU driver version you have installed.

5. Which format you are rendering to when having issues.

This should be enough.

@justin-w Please PM me your email address and I will get a support ticket created for you.

Multiple driver updates and this still hasn't been resolved. Every time I use VP I have constant crashes and issues. This is literally the only piece of software on my computer I have this many issues with. It's completely astounding a program that is this expensive can have this many problems.

@j-v Yeah, it's 334. I'll try out your suggestions and post back here. Honestly I've basically lost all hope though. This has been ongoing for months and honestly I feel like I deserve a refund. I hope you're right and this fixes it.

@j-v, the link you provided is dead

I wrote

Do you use now build 334?

If so, do a clean reset of the program following exactly this: https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/
After that change nothing in the settings for Preferences/Video and Preference File I/O.
And than after a new start of Windows try again the same things as tried before.

@j-v, the link you provided is dead

And the one in this comment?

The OP please note also this comment.