Sounds like some hardware issues.

sounds like an .MOV issue.

sounds like an .MOV issue.

yup....

Cheers all. Only really had issues since upgrading to 15 a while back - never had problems like this on previous versions. I'll try the latest build but nothing on the 'fix list' seemed to suggest any bugs like this are sorted. Seen lots of reports of similar issues to mine but no solutions as yet. If 387 fixes it will post back.

I have issues 1 and 2 as well with Vegas 15. Submit a support request to Magix- posting here won't solve anything. I didn't have issues with 12.

I'm waiting to see if any of the 16 bug fixes address these issues.

You're using an older version that was plagued with memory leaks. Another thing that helps is going into windows winphics options and setting Vegas to "high performance". Give that a shot (after making sure you have the latest version). And yes, 16 is more stable. Try the demo.

Just a quick update, latest build hasn't fixed the problems. Still crashes, still have rogue Vegas processes, still have occasional black screens on render. BUT...

I spotted something today that could be related. I work with 'quantize to frames' always switched on. I also regularly speed footage up using time-stretch (holding down ctrl and dragging end of event). I noticed today that when doing this the time-stretched video doesn't always snap or quantize to a frame. Sometimes the time-stretched events can end mid-frame. With ripple-edit on this causes all subsequent events to have a start and end mid-frame throughout the project. Vegas only significantly started crashing in this scenario (only noticed this today). Once I corrected all the mid-frame events the crashing seemed to stop.

Anyone else familiar with this issue? Or it could just be a coincidence that the crashes stopped...

Andy

What is windows winphics options ??

robert

@ andy-mac. I always switched to quantize on frames. It also happens to me that suddenly everything comes out of step. Since I always run the Auditor of Vegasaur before rendering, I can detect and fix the error.
In order to recognize that immediately, I have set the internal preferences "Show unquantized event start" and "Show unquantized event end" to TRUE. I think. that should be the default setting of Vegas, as there are a few causes of unquantized frames.

Sorry to hear that you have troubles.

But to set the internal preferences "Show unquntized Event start/end" both to TRUE is a good idea, if you think that this may cause the Troubles.

To update to the latest version of the software is another good idea.

The third good idea is to check the guide by Nick About Troubleshooting with Vegas:

https://www.vegascreativesoftware.info/de/forum/vegas-pro-faqs-and-troubleshooting-guides--104787/-ski

And sure, it can be different issues that was mentioned here too. Hard to explore without sitting at your machine.

Just thought I'd give a quick update on this one on the off-chance anyone else is experiencing similar issues. I've read multiple posts of people having random system crashes since VP15. Sadly, Vegas support has been terrible. Cases have been raised, partially investigated and then just closed without warning. I can't then re-open the case so I'll raise a new case with Magix and they'll just close it with zero response.

Quantization of frames isn't the issue as I've been really careful on projects to ensure time-stretches are properly quantized (since Vegas doesn't quantize time stretches, which presumably is a bug). Still getting multiple crashes per editing session. The only thing all projects have in common is that they all have text overlays. It's very rare to have a crash if a project doesn't have overlays of text, but I'm not 100% this is the cause. It could equally be that by the time I start adding text the project is generally more complex at that stage.

Either way, VP15 still crashes. Magix support is really, really terrible. Don't want to have to switch editing platform after all these years but at the moment it's looking like the only option. :-(

I hear ya Andy. I'm using Resolve 90% of the time these days due to various issues like unexplained crashing when attempting to render as well as a broken secondary preview. My past attempts at trying to get Magix support for Vegas left me with the impression to never waste my time with that again. I still use Vegas for certain projects but have not upgraded to ver. 16. Will wait and see if 17 is a rewrite with faster previews, more stability and improved color correction tools.

NOTE: I have had good tech support experiences with the Sound Forge division.

FYI, Vegas Pro 15 Build 416 came out late November with fixes (after the release of Vegas 16.)

Never had V15, but both V14 and latest Vegas 16 are stable for me.

My v16 crashes more than v15.... I realize I'm using, various formats; mp4, m2ts, mov, but hey isn't that what the program is supposed to figure out? Seriously losing faith as well...

Most people use multiple formats. You need to do some troubleshooting. See FAQ's

I hear ya Andy. I'm using Resolve 90% of the time these days due to various issues like

marc-s - what's the learning curve like switching to Resolve? I hate the thought of 'starting again' but this is becoming unworkable.

Kinvermark - I jumped from v13 (which was perfectly stable) to v15 (which is a living hell). I refuse to pay for another upgrade since I feel so let down by support. Haven't tried 416 yet (on 384) but couldn't see anything in the release notes relating to crash fixes. Will give it a try but every time there's a new release I get excited that it will fix things... then it doesn't. I only upgraded to v15 since v13 couldn't cope with GoPro footage...

That v15 build is all about stability. You can always download a Vegas 16 trial to test first. I use both Resolve and Vegas: It does not replace Vegas and vice versa.

IMO, V15 was the most troublesome version. Also a big change from V13, which may have exposed elements of your system that Vegas does not play well with. If you don't have the "faith" and persistence to troubleshoot then you may be disappointed with any modern NLE - they all have long bug lists.

That v15 build is all about stability. You can always download a Vegas 16 trial to test first. I use both Resolve and Vegas: It does not replace Vegas and vice versa.

IMO, V15 was the most troublesome version. Also a big change from V13, which may have exposed elements of your system that Vegas does not play well with. If you don't have the "faith" and persistence to troubleshoot then you may be disappointed with any modern NLE - they all have long bug lists.

Yes, Resolve completely replaces VEGAS Pro, but not vice versa, due to Resolve's prowess as a Color Grading system, as well as it's native VFX and Motion Graphics capabilities.

It completely replaces VEGAS Pro for Video Editing and [Film] Audio Post Production.

It's media management is far more robust, and probably the best there is aside from Final Cut Pro X when it comes to Metadata, and organization.

Its workflow is more like a traditional NLE. VEGAS Pro feels more like a DAW :-P

In the end, different strokes for different folk. But Resolve's Video and Audio Editing are, at the very least, on par with VEGAS Pro, while VEGAS Pro lags it for Media Management and doesn't really compete with Resolve, at all, for VFX, Motion Graphics, and Color Correction. There are also dozens of Workflow Improvements and Quality of Life features present in Resolve that simply don't exist in VEGAS Pro.

VP15 is far more stable than VP14 ever was, and performs better with compressed media like H.264/HEVC due to QSV Decode Support. There is just no comparison between the two. VP14 was basically a glorified Audio Editor. The performance was so bad, it was practically unusable for me. VP15 and 16 are totally usable, but they're increasingly feeling like a low-end consumer editor (think Pinnacle Studio Ultimate) as the competition sprints away from them.

All NLEs have long bug lists. How many bugs is not really of great importance (in the general sense, since we know all software has bugs... many bugs). How quickly the developers react to squash them is more important, as that gives you an indicator to use when choosing whether or not you want to be beholden to them when you run into a bug that affects your work :-P

I'm not necessarily happy at the pace of "bug fixing" that gets done, given the ridiculously short support lifecycle of an individual VEGAS Pro version.

Additionally, I think it would be good if MAGIX would publish some cheap eBooks similar to this and this, because a lot of VEGAS Pro functionality is not very well documented (Timeline Compositing Features, for example, have very few decent tutorials available). There are some books that are, supposedly, quite decent for older versions... but old books tend to run very expensive (even in eBook form) and a lot of users will shy away from buying them due to price and age.

This is something BMD has been very good at, and it's probably a big reason why a lot of people are gravitating towards it. It makes the product seem a lot more approachable, even though it's a complex piece of software.

There are some "creatives" doing VEGAS Pro stuff on YouTube, but the quality of those tutorials leaves a lot to be desired.

How about setting up a Wiki, or something?

I realize it doesn't help when people say they aren't having the same problem, but as I write this right now, Vegas 15 is humming along and rendering out a 30 minute video no problem. There are so many variables as to what it could be, but if the issue can't be replicated by others, it does tend to suggest it might be some other issue besides the software. When I have had the occasional render problem, I tried a couple of things. First, I put my source files on a different hard drive from the one that was being rendered to. That worked for me so it made me almost superstitious about doing that. The other thing was to try rendering in other formats. Does it crash on every format? Can you render out an MXF or Sony AVC file or nothing at all? What I do if it doesn't crash on rendering a different file type is render out those files, then bring them back in and work on those, especially MFX files because they seem to keep their quality and sometimes don't even recompress. I've never had files that have been rendered out in mfx or avc and brought back in crash again. And of course, there is the thread on all the things you can do and simply work your way down that. But I'd also ck to make sure you graphics card is updated and you have most current build, but then I'm assuming you've probably already done that. Good luck either way!

Andy, Resolve definitely has a learning curve but there are lots of free tutorials and some great paid training on ripple training. One awesome thing is that the free version is extremely capable so you can learn on that and see if it fits your workflow. Resolve is not perfect and there are still some things that Vegas has that I wish Resolve did but what I love about the program is that they are improving it at lightning speed. Most updates (which come out usually once a month) have pages and pages of fixes as well as new features and improvements. I’ve heard they have a huge team working on it and it shows.

I realize it doesn't help when people say they aren't having the same problem, but as I write this right now, Vegas 15 is humming along and rendering out a 30 minute video no problem. There are

Top be clear, the crashing isn't a problem on render. The crashing is an application hang during general use. As I say, simpler projects rarely crash at at all. Once I get in to projects with 10-20+ separate tracks of video, audio, text overlays etc. that's when the problems seem to start - and even then it's very random. Only started since upgrading to 15. Never had any issues with 13 or any of the versions below that. This is on a very clean, very stable Windows 10 build.

This has been going on for some time, well over a year, so been through all the troubleshooting steps, all latest drivers etc. Fully accept it could be a rogue Windows update or anything but I'm out of options here. Raising a case with Magix was a last resort and their support has been dire. At least if they responded with "We don't want to help you anymore" that would be better. But to just close cases (on multiple occasions) with zero response is really bad. I've forked out a lot of money with them over the years so I don't think it's asking too much for them to at least reply when I raise a support case.

This is a real shame - I've been using Vegas for 7+ years. Their Trustmark reviews speak volumes though, really not looking good:

https://uk.trustpilot.com/review/www.magix.com

Time to jump ship. :-(

marc-s - had a quick look at a couple of YouTube 'crash course' vids - wow, it's a beast. And VERY different looking. Fusion nodes? WTF? :-) Looks amazing though - defo. going to check it out - cheers!