Crashing ALL the time

michel-plante wrote on 4/22/2024, 4:29 PM

Hi,

Just purchased Vegas Pro Edit 21. I was crashing left and right with that new version, never have I crashed with this new version than any other from version 6 to 20. I contacted Support and after one day they asked I send them a SI text file, which I did. After I received a ton of emails, at least 5, were they were asking me via a survey if I was satisfied with the Support provided. Could not answer since no support has yet been provided after me sending the SI text file.

After consultation someone on this site suggested I use build 208 and not 300. Did that this morning and started to work on a project. I crashed 2 times within my first hour of work and some effects did not work. I did provide info on the window that appears just after a crash as I did a few times when crashing with build 300. Never had any feedback from Support following those emails.

I had problems with version 19 a few years ago after purchase. I bought version 20 but I was getting the nasty sound after every clips on the timeline with no patch in view to correct that issue. So I decided that version 21 would, without a doubt, be just perfect...??? I'm out of means!!!

I'm using Windows 11, 64 bit. Using graphics card G246HYL on AMD Radeon RX 6600 with 16g. of Ram...thanks for help.

Michel

Back to post

Comments

RogerS wrote on 4/28/2024, 9:55 AM

This is interlaced media. Try making sure the project is progressive (project properties has settings for deinterlacing methods). Interlaced projects don't work with GPU renders and might cause issue with some Fx.

Otherwise in 20 if it doesn't work well with the so4compound decoder you can check "enable legacy AVC" to use an even older one (compoundplug) that was around when media like this was common. Still make sure the project is progressive. These are my best guesses- it really should work!

michel-plante wrote on 4/28/2024, 9:57 AM

Hi,

This a follow up to my recent Post concerning the info pertaining to a file scanned with the MediaInfo app. I just played the same clip responsible for my last crash with Version 21 and it works perfect with Version 20.

Hope this helps

Michel

fr0sty wrote on 4/28/2024, 10:58 AM

In that case, try to go into preferences, under the file i/o tab, and check the "enable legacy AVC decoder" checkbox. Reboot VEGAS, and report back to us if it now runs stable for you.

Also, If your camera is capable of it, you may consider setting it to 1080p instead of 1080i, you get double the image quality that way. 1080i only records half the rows of pixels per frame, alternating between even and odd rows with each frame.

michel-plante wrote on 4/29/2024, 7:06 AM

Hi Frosty and others who contribute to find a solution to my never ending problem,

I did apply the proposed correction without ''unchecking'' any other items on that tab. It did work for the clip in question, the one for which I sent a MediaInfo text file. I continued working on my timeline trying to replace clips in the order I wanted, had to go back to the beginning of that Timeline 2 minutes before, the screen suddenly became black, pressed Escape and the attached file shows the error message accompanying that frozen screen.

My frustration level has reached a pinnacle. I just invested, 100$ US a little bit more than a week ago to purchase that app. I was using Version 20 with the nasty sound at the end of clips on the Timeline, hopping that a patch would be provided, seems like it wont happen so I bought Version 21.

If I want to advance with this project I must restart for the fifth time and I will use version 20 and deal with the nasty sound hopping that eventually a patch for either build 300 or 208 for Version 21 is provided to correct the problem I'm dealing with for the last week and a half.

Voilà...thanks for the help Frosty

Michel

Dr Zen wrote on 4/30/2024, 5:41 AM

Hi again Michel

Here are the correct links for updating your ASUS Motherboard and AMD 5800X CPU:

1. Download and install this Chipset Driver for Windows 11:
https://www.amd.com/en/support/downloads/drivers.html/chipsets/am4/b350.html

2. Here is link to download latest BIOS version for ASUS Prime 350-PLUS:
Latest version is 6203
https://www.asus.com/supportonly/prime%20b350-plus/helpdesk_bios/

To discover which BIOS version your Motherboard currently uses, go to the Search box in Windows 11 in bottom taskbar and type "System Information". Select System Information to open window. Look for BIOS version/date.

I also found a video on YouTube, that shows how to install a new BIOS for your Motherboard. The guy does not speak, but does show what to do. After you download BIOS, right-click to extract file from zip folder. I recommend placing the BIOS files on an empty USB Drive. The BIOS file will end in .cap

Connect USB Drive
Re-start computer
Keep pressing the DELETE key, until the BIOS interface opens
Then follow what YT video shows. After the BIOS installs, the YouTube video shows other stuff you don't have to do! Only the first 1:45 is important. Changing other settings is for advanced users, if you know what you are doing.

I also posted a message on my forum for you, explaining/showing how to check for Optional Updates in Windows 11, so that you have the latest .NET Framework updates installed !!!

michel-plante wrote on 5/16/2024, 5:43 AM

Hi,

I presume I can still write under this subject, something has been resolved but not every thing.

Folowing the suggestion of one of many supporters in my quest to get VP 21 working properly, I updated my CPU and BIOS, crossed my fingers real tight and started a new project with Version 21 build 208. Always waiting for a crash to appear, after about five hours of work and an hour long video, not finished yet, I was astonished to find the joy of not crashing and that I could continue working with version 21 because my issue (s) was resolved. Great!

Yesterday morning while loading mt Vegas Pro, an update for build 314 appears...I do what has to be done to install it properly, load my hour long project. I had to adjust a clip on the Timeline and BANG, it crashed! No fussing around, I uninstall it and reinstall build 208.

I finally load my project and get an error message telling me that my project was made with an earlier version...blabla! So at this point, I can't load it and work with build 208.

Suggestion would be more than appreciated...thanks!

Michel.

Reyfox wrote on 5/16/2024, 5:54 AM

@michel-plante here is a little tip. When you continue to edit a project on a more recent update, and save it with the updated software, you can't go back to a previous version to edit if there are issues. I always will resave the project with the build number as part of the file name, just in case.

Now, if you have a previous version of Vegas (20, 19, etc.), you can load the project in VP21 and copy the entire timeline and paste it in a past Vegas version.

I'll never save a project in the current version without a file name change to represent the Vegas version build. Also, never ever update in the middle of editing a project. Finish the project first, then update.

EricLNZ wrote on 5/16/2024, 6:16 AM

@michel-plante If you only saved your project once with build 314 then your bak file is hopefully a build 208 version. Rename it to just ".veg" and try it.

RogerS wrote on 5/16/2024, 6:21 AM

What did "show problem details" say in the crash reporter?

Another workaround would be to go to preferences, file io and check "legacy AVC decoding" (assuming this file is using Mxcompound in VP 21).

Dexcon wrote on 5/16/2024, 6:27 AM

If the .veg.bak file pre-dates the build 314 episode, change the extension name to just .veg and try opening it in build 208.

If you have Advanced Save enabled in Vegas Pro, check the folder where those saves are held and see if there is a .veg file there which is earlier than the build 314 episode.

In addition to Reyfox's excellent advice - a procedure that I also follow and which takes so little time in comparison to having to re-edit a project - always keep copies of all the .veg files in another folder; or external devices such as an external HDD/SSD, memory card; or in the cloud (e.g. OneDrive) - or all of the above. If you've never had a harddrive or SSD fail or magically 'lose' the Windows installation, you are lucky - so far. Always think, "What do I do if the HDD/SDD fails or gets zapped by a power surge?".

michel-plante wrote on 5/16/2024, 6:51 AM

Hi,

Thanks for the tip on using a rename of a BAK file. Did not work, probably that out of desperation, I reinstalled a few moments ago build 314 and loaded my project hoping I could do something with it...it crashed instantly as soon as I loaded my Project and probably changed the name of the BAK file even though I never saved it??

I just uninstalled build 314 and went back to 208. I agree with everyone with having multiple back ups in different places. Maybe was I negligent in that matter?

I must say that after making more than 80 videos for the last 20 years, I never had to deal with a similar situation. But I'm lucky in a certain way. While I was having my Crashing issues a little more than a week ago, it is more than detailed on this post, as a Test for build 208 (I was using build 300 before) I completely imported ALL the clips (about 150) of my actual project on a Timeline, saved with another name and was, a few moments ago, able to recover it with build 208.

So now I simply have to add Titles a bit of color and the pictures (it's video of a trip my wife and I just made). It should take a fraction of the time it took me to create the original project.

Can't finish this story without telling everybody who wrote and provided with help and suggestions during the previous week with my ''Always crashing'' issue and today's problem, how I appreciate your very prompt responses and ideas...thanks again guys, really appreciate it!

Michel