Thought this was going well for a while. Now I can't even open up a simple project with one video track and no grading when this happens every single time. I'm really upset and discouraged about this. Vegas... are you listening? Been trying to learn Davinci and it's never crashed once.
What's the media so we can test? If it worked in the past, reset VEGAS?
Most likely no one is listening at the moment it's a holiday period.
@Roger Bansemer, the best way to make sure our tech support guys are "listening" is to submit a support ticket with a bit more information than, "a simple project with one video track and no grading" and "Davinci...never crashed once." Have you submitted a ticket? If so, please post the ticket number here and I'll be happy to check up on it for you and have them contact you.
@Roger Bansemer, the best way to make sure our tech support guys are "listening" is to submit a support ticket with a bit more information than, "a simple project with one video track and no grading" and "Davinci...never crashed once." Have you submitted a ticket? If so, please post the ticket number here and I'll be happy to check up on it for you and have them contact you.
Hi Gary, Where do I submit a ticket? I must have restarted Vegas 15 times yesterday so you can imagine being frustrated. Vegas very, very seldom comes up with that submit problem window so if that's where to submit a problem I hardly ever get that. Instead the screen just turns whiteish and eventually I have to hit ctrl alt del.
I would think Vegas would know about the "not responding" issues as I think many of us has been having them for years and years. I give Vegas a 10 if it were not for the "not responding" issues. I was doing a yacht club project the other day and the people came over to take a look and just crash after crash and made me look like a fool that didn't know what I was doing. You can understand that.
Thanks Gary.
Roger
Unfortunately, when you click that link, and then click "VEGAS Pro", the first FAQ you see on the next page shows you the document on how you to Contact Support for MAGIX software.
Ignore the references to MAGIX and note only this: According to the selected category, you will first be offered a number of common suggestions. If none of the suggestions meet your requirements, scroll down the page and select "Contact Support" to proceed.
See also the VEGAS Support Team's advice here: https://www.vegascreativesoftware.info/us/forum/support-system-upgrade--137601/ (It starts from the products website but leads you to the same "Contact Support" link at the bottom of the page.)
You can understand that.
@Roger Bansemer, I completely understand the frustration, and I'm sorry. Let's see if the support guys can help figure out what's odd about your situation and help you resolve it. The other users here on this forum are also a great resource if you share the specifics for them. The devs will be back in the office after holiday break next week and can also potentially offer some advice. But let's start with a support ticket.
@Roger Bansemer I feel your pain, I also get a lot of "not responding" hangs, and try to get to the bottom of it if I have some time. Some questions:
I successfully identified and solved another type of crash (not the "hang" type, but an immediate Vegas crash with the option to send a report). That type of crash was related to CPU thermal throttling, something that should get more attention, as this is a sneaky one (not everyone examines their BIOS), anyone can experience it, especially if you have a modern CPU and/or inadequate cooling. You can read about it in my post: https://www.vegascreativesoftware.info/us/forum/solution-to-vegas-crashes-on-modern-high-end-cpu-s-e-g-i9-13900k--144004/
@Roger Bansemer I feel your pain, I also get a lot of "not responding" hangs, and try to get to the bottom of it if I have some time.
@bitman Did you see an increase in crashes with 208 or similar to 187?
@Former user to answer your question about more "hang" crashes in in 208 vs 187: hard to tell, in all honesty I do not know, these things are hard to compare anyway, I prefer hard facts as opposed to "the feeling more or less", I do tend to edit more in the winter time (on the northerly hemisphere!), and as such much more in build 208 than in any other build of Vegas 21...
One thing I do know, if you can successfully make it "hang" to the unavoidable crash in a controlled manner (as being reproducible each time) then this is a first and very important step to a solution. Do report here and to the developers in case you find a way to reproduce the hangs. Very few issues get solved if they cannot be reproduced.
@Roger Bansemer I feel your pain, I also get a lot of "not responding" hangs, and try to get to the bottom of it if I have some time. Some questions:
- Do you have your Vegas project (where the edit updates are stored) under Microsoft OneDrive?
- Does it still hang in edit when all sound is disabled? - there is a button for that
- Is there an antivirus running?
- Is the option close media files (and close audio ports) when not the active application in preference enabled?
I successfully identified and solved another type of crash (not the "hang" type, but an immediate Vegas crash with the option to send a report). That type of crash was related to CPU thermal throttling, something that should get more attention, as this is a sneaky one (not everyone examines their BIOS), anyone can experience it, especially if you have a modern CPU and/or inadequate cooling. You can read about it in my post: https://www.vegascreativesoftware.info/us/forum/solution-to-vegas-crashes-on-modern-high-end-cpu-s-e-g-i9-13900k--144004/
That's an interesting and in depth piece you wrote about the thermal throttling. I have to say that's way above me though. Maybe Vegas programers can dive into it some more. hopefully.
Unfortunately, when you click that link, and then click "VEGAS Pro", the first FAQ you see on the next page shows you the document on how you to Contact Support for MAGIX software.
Ignore the references to MAGIX and note only this: According to the selected category, you will first be offered a number of common suggestions. If none of the suggestions meet your requirements, scroll down the page and select "Contact Support" to proceed.
See also the VEGAS Support Team's advice here: https://www.vegascreativesoftware.info/us/forum/support-system-upgrade--137601/ (It starts from the products website but leads you to the same "Contact Support" link at the bottom of the page.)
I left the support team a note about the "not responding" issue but I would think they certainly must know about this issue. We'll see what happens.
One really strange thing about this "not responding" issue is that on some projects Vegas works pretty well with only a crash or two every hour. Then on some projects, it crashes so often that it's impossible to work with. Doesn't matter how simple or complex the project is.
Exxxxxxxxxxactly my experience Roger!!
Sometimes i can edit for 1-2 hours, sometimes only a few minutes!
(with the same camera files and without any fx)
Exxxxxxxxxxactly my experience Roger!!
Sometimes i can edit for 1-2 hours, sometimes only a few minutes!
(with the same camera files and without any fx)
Yes... That's what makes this so frustrating. If we were doing something different that's one thing but if all the settings in Vegas haven't been changed then why does this happen. And it happens so often.
Just got a hang...
from the event viewer:
EventData
ModulePath C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_effe9612081e9042\libmfx64-gen.dll
Not sure what affinity "amd64" has with my system, as I do not have AMD in my system.
As suggested, I submitted a ticket to Vegas about the "not responding" problem which has been going on and on for years and years. They asked me for certain information, quite a bit actually... and they got back to me and here's what they said.....
As a troubleshooting step, click Options > Preferences > Video tab, then turn “GPU acceleration of video processing” to off, and set “dynamic RAM preview” to 0, click apply and OK.
Do they really think this is going to solve the issue! Give me a break! Besides I like a little dynamic ram to render a clip or two to view. I don't think they even realize what an issue this "not responding" thing is. To me, it's pretty obvious it's a programming or coding issue, not a simple turn off dynamic ram. As NASA would say, Vegas, we have a problem...
agreed
@Roger Bansemer Here's what a developer suggested to another user in order to get more details on why Vegas may be "not responding"...
https://www.vegascreativesoftware.info/us/forum/crashes-all-the-time--143650/#ca898939
The internal setting causes a "Working" message to be displayed when Vegas thinks it might be stuck and after a couple attempts to continue it gives the option to terminate. Which presents the Crash Report screen where you can check all the boxes to provide the most info.
Do they really think this is going to solve the issue! Give me a break!
No, of course they don't. But do you really think they will instantly be able to solve all issues without first going through a series of trouble-shooting steps to rule out certain things? This is the nature of trouble shooting, and we all experience the "you must be kidding...I'm not an idiot" reaction to their questions--just like when the IT guy asks you if you already tried shutting down and rebooting. They don't mean to imply that you are, but they do need to rule things out systematically to work toward figuring out what's going on. I ask for your patience with that. They are not trying to waste your time. In fact, ruling out basic things will help save time in the long run.
@Roger Bansemer Here's what a developer suggested to another user in order to get more details on why Vegas may be "not responding"...
https://www.vegascreativesoftware.info/us/forum/crashes-all-the-time--143650/#ca898939
The internal setting causes a "Working" message to be displayed when Vegas thinks it might be stuck and after a couple attempts to continue it gives the option to terminate. Which presents the Crash Report screen where you can check all the boxes to provide the most info.
99% of the time that crash screen where you can forward the issue does not appear. Whenever it does, I do send it in but have never heard back.
Do they really think this is going to solve the issue! Give me a break!
No, of course they don't. But do you really think they will instantly be able to solve all issues without first going through a series of trouble-shooting steps to rule out certain things? This is the nature of trouble shooting, and we all experience the "you must be kidding...I'm not an idiot" reaction to their questions--just like when the IT guy asks you if you already tried shutting down and rebooting. They don't mean to imply that you are, but they do need to rule things out systematically to work toward figuring out what's going on. I ask for your patience with that. They are not trying to waste your time. In fact, ruling out basic things will help save time in the long run.
Hi Gary, I'm really not trying to be a jerk about this nor is my goal to be rude. I think most of us who have this problem just want it to be fixed and not have a client come by and think we're the jerks for not being able to show them an edit as Vegas crashes. It's not like this is a new problem. Again Gary, I don't mean to be mean... just would like a stable platform on which to work. I think we should expect that. Setting Ram to 0 is no solution I'm sure so when they say that I feel like they aren't really taking it seriously.
I do send it in but have never heard back.
Most of the time you won't hear directly back when you send these reports, but it's still important data that does not get ignored. Also, it helps very much to identify yourself in those reports so that if the team does want to contact you directly, they know how to find you. As I understand it, we are prevented by law from collecting data in that report that will identify a specific user, but if you voluntarily include your email address, then the team has a way to know who sent the report and contact you if they feel it's necessary.
Setting Ram to 0 is no solution I'm sure so when they say that I feel like they aren't really taking it seriously.
Again, I seriously doubt that they are presenting that as an acceptable solution to your obviously unacceptable problem. It's a trouble-shooting step. If it did happen to somehow affect your experience, then they have an important clue that the team can follow in hunting down the core problem.
But, what your comments do tell me is that perhaps the support team isn't make that clear enough to you and other users. I will discuss this with them because maybe better communication about why they're asking you to do this or that would have been enough to at least not add to your frustration.
Setting Ram to 0 is no solution I'm sure so when they say that I feel like they aren't really taking it seriously.
Again, I seriously doubt that they are presenting that as an acceptable solution to your obviously unacceptable problem. It's a trouble-shooting step. If it did happen to somehow affect your experience, then they have an important clue that the team can follow in hunting down the core problem.
But, what your comments do tell me is that perhaps the support team isn't make that clear enough to you and other users. I will discuss this with them because maybe better communication about why they're asking you to do this or that would have been enough to at least not add to your frustration.
Thanks Gary.