@chris-minchin - Ugly..... Did you update the GPU Driver? Something is banjaxing VP18. As I said, VP18 working for me and with 4k too.

@chris-minchin - Ah! You can open VP18, try rescanning your VST Folders?

I can't reproduce this, I can't find the Standard with drop shadow option. Twist in works fine with no crash.

OK, here is where the worst bug that for me makes it unusable. It does this every single time, with text or solid colour it makes no difference, it will always crash.

I have no uninstalled it and reinstalled it (as Administrator), and that makes no difference either, same result.

I have turned my antivirus off and my firewall as well, same thing, crash.

I still have V17 on my machine, and if I try the same test, no problem, same with V16 no crashes.

Please see my video:

The video shows the problem

 

Isn't that the same problem that is described here?

More ram is always nice but that's not your problem with a timeline that just has a bit of text on it.

So you are not having crashes in other situations now?

I think Walter's on to something- others are having issues with keyframing and pan/crop.
If you are working with a text box, why not go to location in the text box and just hit animate to keyframe there? I just did that with no issues on my 1050 using the regular and twist in text.
(I did animate with pan/crop and it doesn't crash, though)

Other workarounds- if you have text on its own track could you try track motion to move it instead of crop? Alternatively I think you could also use the picture in picture Fx (just reset scale back to 100%)? Those are workarounds until this gets resolved.

I noticed there is a new NVIDIA driver out a day or two ago so update to that if you haven't already.

@chris-minchin - Ugly..... Did you update the GPU Driver? Something is banjaxing VP18. As I said, VP18 working for me and with 4k too.

Every new version is the same. There are those with crashes and those for whom it works perfectly. And you think "Why me?" And you update the graphics drivers, maybe buy a new graphics card and some more RAM. All good improvements, but its only after one or two updates that you can really start to enjoy crash-free editing for a few months. And then the whole cycle begins again. With VP17 working perfectly at last I think "do I need all this hassle again?". Usually I wait until the first update but I am so keen to get my mouse pointer on the new love handles - long overdue - that I've gone for it. Surprise surprise the crashes are all in the new features like motion tracking and plugin favorites. I'm sure it'll be worth it in the end.

@paul-marshall - Wise words.

@chris-minchin - Ugly..... Did you update the GPU Driver? Something is banjaxing VP18. As I said, VP18 working for me and with 4k too.

Every new version is the same. There are those with crashes and those for whom it works perfectly. And you think "Why me?"

Crashing allot for me too on 2 different systems with AMD boards that are rock-solid with v17. Turning on Live Save minimizes lockups but does not prevent them... but it does prevent losing anything on return. All my systems have up-to-date drivers down to the motherboard chip sets and bios. Don't know if Magix does any beta testing but they should do more of it. It certainly will be counter-productive if we chill reporting by berating the messengers. I love Vegas but can't really recommend v18 to others yet without a boatload of provisos.

OK, for a start I want Vegas Pro 18 to work, because I like the ease of use, but seriously, there are so many crash's.

I also have found bugs, that to be honest should have been picked up before release of version 18.

What I want to know is when they will make a update/bug fix available, even if they do an interim fix for some of the many bugs.

Build (284) is quite frankly a bloody mess, please do something about it, and quickly!!

I'm using version 14 and it is pretty stable. I upgraded to Vegas 16 after it was released at it was an unstable mess and I quickly got a refund. This time I downloaded the trial version of 18 today. After installation I was surprised that it didn't crash immediately when I tried to place a video clip on the time line like version 16 did. I was even able to use 10 bit 422 4K video clips from my Lumix G9. One big red flag with version 18 is that in plays back 4K clips much slower than Version 14. That should not be happening. I have the latest drivers installed. I ran CC Cleaner before installing. I updated all my codecs. I was so happy that I could use my 10 bit video clips without transcoding but as before the problems started when I attempted to render an eight second 10 bit video clip and as soon as I clicked "render as", it crashed (ntdll.dll exception). I disabled all the GPU acceleration and went though the list of solutions posted by others to this problem but nothing worked. I then tried to render a 5 second 8 bit 4K clip and I had the same problem. I then tried to render a checkerboard pattern from the media generator and it crashed with the same issue. Then I looked at the big picture and thought, do I really want to be a beta tester for buggy software from Magix ... No! If I resolved this problem how many other problems would I encounter when I actually tried to edit my videos? I don't want to find out. After about 4 hours of playing with Version 18, I decided to uninstall it and move on.

If our company released software this unstable, we wouldn't be in business very long.

Don't know if Magix does any beta testing but they should do more of it. 

VEGAS 18 went through months of testing with one of the largest and most active beta teams ever used for a VEGAS product. That said, other ideas are being discussed to remedy this.

My VP18 crashes when i check for driver updates and (even if i already have the latest nvidia studio driver) click on the driver link. Already sent two bug reports to Magix via the integrated VP tool.

But seriously.. crash at a simple driver check window.. ? Seriously..

@chris-minchin - Ugly..... Did you update the GPU Driver? Something is banjaxing VP18. As I said, VP18 working for me and with 4k too.

Every new version is the same. There are those with crashes and those for whom it works perfectly. And you think "Why me?" And you update the graphics drivers, maybe buy a new graphics card and some more RAM. All good improvements, but its only after one or two updates that you can really start to enjoy crash-free editing for a few months. And then the whole cycle begins again

A public beta program could work or at minimum a release candidate version is made available publicly to current owners before next release as an opt in. This private beta testing thing they do doesn't catch the bugs that users of this forum find in hours after it is released in it's final form. It just stands to reason that more eyes and more computer systems would better find the problems and then less people complaining at official public release

OK everybody, it seems that I will have to go back and use V17 again. The one thing that is now clear to me these problems with V18 are wide spread, but a lucky few seem to have no problems.

My sideline income is derived from software that I write (mainly for the aviation industry). I am not saying that my software is bug free on release, but if I had been part of the Vegas team that wrote this version I would be very embarrassed by how many bugs slipped through.

No doubt they will get this under control eventually, and all will be well, but, looking back this will not happen for a few months.

So the end game is from now I will not be purchasing any new version until it has been on the market for at least six months and there are no longer reports of bugs.

Vegas will still be my NLE of choice, but they need to up their game considerably if this to remain the case.

Happy editing everybody.

A public beta program could work or at minimum a release candidate version is made available publicly to current owners before next release as an opt in.

@Former user - Makes sense.

This private beta testing thing they do doesn't catch the bugs that users of this forum find in hours after it is released in it's final form.

@Former user - Why do you think that this is?

It just stands to reason that more eyes and more computer systems would better find the problems and then less people complaining at official public release

@Former user - I agree. However, I suppose it’s to do with the amount of resources=engineers=cash that that’s available to do it. It’s a tough call.

This private beta testing thing they do doesn't catch the bugs that users of this forum find in hours after it is released in it's final form.

@Former user - Why do you think that this is?

A wide variance in what a user is doing, their media, what they're encoding to, operating system, hardware. The broader the sample, the more likely a bug is seen.

It just stands to reason that more eyes and more computer systems would better find the problems and then less people complaining at official public release

@Former user - I agree. However, I suppose it’s to do with the amount of resources=engineers=cash that that’s available to do it. It’s a tough call.

I was thinking about that. Negative promotion must have a dollar value too, how many don't buy Vegas due to unhappy customers talking about problems with the software. It would still be a similar operation except the release candidate version is offered to Vegas owners to test instead of staying private. You see that happen with Premiere and Resolve and what can happen is due to user feedback there could be 3 release candidates where they find problems they did not know about before final release

@chris-minchin - Ugly..... Did you update the GPU Driver? Something is banjaxing VP18. As I said, VP18 working for me and with 4k too.

Every new version is the same. There are those with crashes and those for whom it works perfectly. And you think "Why me?" And you update the graphics drivers, maybe buy a new graphics card and some more RAM. All good improvements, but its only after one or two updates that you can really start to enjoy crash-free editing for a few months. And then the whole cycle begins again

A public beta program could work or at minimum a release candidate version is made available publicly to current owners before next release as an opt in. This private beta testing thing they do doesn't catch the bugs that users of this forum find in hours after it is released in it's final form. It just stands to reason that more eyes and more computer systems would better find the problems and then less people complaining at official public release

It's impossible to reproduce the thousands of different types of media, drivers, hardware configs, etc that are present out in the wild. A public beta really is the only way (and even it won't get them all, only what can be reproduced and tended to by the team in the time they have), especially since VEGAS is one of the more versatile NLEs when it comes to what formats it accepts, renders to, and what hardware it supports. That creates a massive amount of complexity where bugs can hide.

I've brought it up multiple times, but as mentioned above, it's difficult for a small team of devs to manage bug reports from everyone at once. I have proposed a solution, though, we'll see if it takes root.

I've brought it up multiple times, but as mentioned above, it's difficult for a small team of devs to manage bug reports from everyone at once.

@fr0sty - If you meant me, then I was considering just how much revenue that could possibly be diverted to deal with the plague of awakening Bugs, that had been quietly sleeping, warm within their cocoons, only to be stirred by a new VP iteration.

I have proposed a solution, though, we'll see if it takes root.

@fr0sty - Ooooo, you tease, do tell! 👂

Vegas Pro is a staggeringly impressive achievement. A video NLE system must be the most complex program anyone is going to run on a PC. A huge range of different protocols, standards and disciplines all to work on different hardware in a fast and efficient manner. Incredible.
But for the program to crash while using the new plugin favorites is not good enough. That aspect is surely not rocket science!

@paul-marshall - “But for the program to crash while using the new plugin favorites is not good enough. That aspect is surely not rocket science!”

I’m truly not getting crashing. My Favourites include Magic Bullet Looks, MERCALLI, TWIXTOR, NewBlue ColorFast2, NEAT VIDEO.

We will keep going over the same Territory, this has to be a Local Issue, this doesn’t mean there isn’t a Bug, but what Bug there is isn’t affecting me. What can I say?

I will defend anybody’s right to post Bugs. Also, I reserve the right, because it’s also helpful and proof of a False Positive/Negative, to post when something is going correctly.

I suspect it comes down to error checking. The users system doesnt conform in some way they hadnt thought of so instead of an error message it just crashes. .

“I suspect it comes down to error checking.”

@paul-marshall - OK. Is that for the User to check or is this part of the Install Program?

“The users system doesnt conform in some way they hadnt thought of so instead of an error message it just crashes.”

@paul-marshall - This so way above my pay grade. Are you implying that the vegascreativesoftware engineers would have had to have thought of it to implement such an error correction routine? So, each and every Error has to be recorded and THEN a routine would need to be instigated? Wow! 😯

So, our chum here, might be getting an error that wasn’t, wouldn’t have been lodged with vegascreativesoftware engineers, so in any event both User, our chum, and vegascreativesoftware engineers would be left in the dark. Have I got this right?

Error checking is not that hard: example below, (vb.net)

Try FromFile.CopyTo(ToFileName, True)

Catch ex As System.IO.IOException

If ex.HResult = -2147024863 Or ex.HResult = -2147024864

Then Else MsgBox(ex.HResult & " - " & ex.Message)

End If

End Try

The hard part is remembering to apply it to every process.

What I think would help would be a section in preferences with a tab that gave the user a list of CPU, GPU, Ram, etc that they could click on to set their machine up.

It is also possible to write code that would determine all of the above and configure Vegas accordingly.