Last good build for me was 341. I skipped the 4xx build. Both 550 and now 636.

HW

Windows 10
AMD 5950X
RTX 3090
128GB
Dual 4K monitors
Only extra software is Photoshop.

Frequently latest two build crash on building icons in explorer window (nvcuda64.dll)
I have updated to latest studio drivers and also tried older ones, always clean install and reboot.

Options always show my GPU as active for both options - video and file I/O.

If it does start, it will not decode video using the GPU.  

On render sometimes it will not show the GPU options for rendering.  However sometimes it will, and then it does render using Encode via GPU, but still does not use it for decode.

Any suggestions other than rolling back to 341, which I do all the time.
 

Reading all the comments and problems that users are having, something is wrong. For "me", B550 is wonderful, stable and works great on my computer. B636 is a "different kettle of fish". First, if you save anything in 636 and want to go to a previous build, you can't open that project. I can deal with preferences having to be redone (there should have been a warning/text file saying this), but not being able to go back after saving a project is a big one for me. Graide Color Match from B550 crashes B636 and won't play properly.

I do like the search box for Video FX is much faster now. Still have trouble seeing all the buttons in the hamburger menu when they are enabled on various track colors.

With all these issues, I am glad I have not updated to b636 yet. Is there a way to stop the nag on updating each time I open Vegas? I always wait about at least 1 month before trying a new update - until it's stable.

You should be able to avoid this by changing the Preferences > General box and unticking "Use Newsfeed to stay informed about Vegas product updates". See it in the attached JPEG

I updated to 636 before seeing all the issues in this forum. That gave me some concerns. I found a comment by Dape on page one of this thread :

"Just made the update: for all of us that found the settings reset: View - Window Layouts - Organize Layouts and then you should find your old preset(s) there."

That worked for me.

All my personal Render choices were intact. Some of my main Preferences were not as before e.g. I don't usually have the last project open automatically and under Deprecated Features the Quicktime plugin had not been enabled (but I think that also happened on updating from 18 to 19.

I had to completely redo the "Customise Toolbar" and "Customise Timeline Toolbar" but I was not over concerned as I needed to revise them anyway.

My personal Media Generator Titles and Text stayed intact.

My personal Project Properties options changed slightly so I updated and saved those.

I opened Vegas 18 and cross-referenced the Preferences with the new 19 Preferences to double check.

Usually I would use Vegasaur to save and update Vegasaur Presets Manager to export / import but had not thought it was going to be necessary this time. I was relieved to find that both Vegasaur and Pluraleyes are available in 636. Phew!

what has happened to the IMPORT footage section. Normally when you imported a few video clips it highlights them all in the project media window so you can drag them all on the timeline if needed. Not it doesn't highlight them. when you import media now my system does a weird graphic thing and the media flashes.

That's the bit I don't understand. There are beta testers here, apparently they're not allowed to tell us when they're testing a new release but they hint at it, @fr0sty is such a case. How would he not say "Guys the update just deleted all my personal settings, fix this before release or place a huge warning when loading the install file"

The same thing happened with version 532 of Vp19, I don't think it exists anymore replaced by version 550. The problems with 532 were immediately picked up by forum users. There has to be a problem with the beta testers themselves(seems unlikely) or the mechanism for giving feedback. The right people never see it?

The answer is quite simple. It didn't delete anything on my systems, or the systems of other testers. There's nothing wrong with the reporting process, and we talk to the dev team every day, all the right people see it and chat directly with us about the issues we report. This isn't a universal bug, it only affects some users.

The number of OS, driver, software, and hardware configurations out there is absolutely huge, and replicating every single one just isn't possible. It doesn't matter how many beta testers you use, when you release the software for many thousands of people (or tens of thousands? Hundreds of thousands? No idea what VEGAS' install base is) to install, there's always going to be something that the various combinations of system configurations in the testing pool didn't catch. Yes, sometimes that even means bugs that have major detrimental effects. Not even a multi-billion dollar company like Microsoft or Apple can release updates they don't have to occasionally quickly patch to overcome some system-breaking bug.

And of course, once such a bug does surface, where's the first place that users affected by it are going to go for help? Either official support or these forums, which is why the forum users pick up on it so fast. That's what this forum is here for, to offer tech support. I would hope that such bugs would surface quickly if there are any. If they don't, it means there's users out there not getting help.

That's the bit I don't understand. There are beta testers here, apparently they're not allowed to tell us when they're testing a new release but they hint at it, @fr0sty is such a case. How would he not say "Guys the update just deleted all my personal settings, fix this before release or place a huge warning when loading the install file"

The same thing happened with version 532 of Vp19, I don't think it exists anymore replaced by version 550. The problems with 532 were immediately picked up by forum users. There has to be a problem with the beta testers themselves(seems unlikely) or the mechanism for giving feedback. The right people never see it?

The answer is quite simple. It didn't delete anything on my systems, or the systems of other testers. There's nothing wrong with the reporting process, and we talk to the dev team every day, all the right people see it and chat directly with us about the issues we report. This isn't a universal bug, it only affects some users.

The number of OS, driver, software, and hardware configurations out there is absolutely huge, and replicating every single one just isn't possible. It doesn't matter how many beta testers you use, when you release the software for many thousands of people (or tens of thousands? Hundreds of thousands? No idea what VEGAS' install base is) to install, there's always going to be something that the various combinations of system configurations in the testing pool didn't catch. Yes, sometimes that even means bugs that have major detrimental effects. Not even a multi-billion dollar company like Microsoft or Apple can release updates they don't have to occasionally quickly patch to overcome some system-breaking bug.

And of course, once such a bug does surface, where's the first place that users affected by it are going to go for help? Either official support or these forums, which is why the forum users pick up on it so fast. That's what this forum is here for, to offer tech support. I would hope that such bugs would surface quickly if there are any. If they don't, it means there's users out there not getting help.

 

Any Beta testers on Windows 11? You can't test all scenarios, but testing Windows 11 seems reasonable.
I lost my settings and I'm on Windows 11 latest version.

Hi, I mainly use VegasPro 19 to edit a radiovision program, but since I installed the new release 636 when I render for example only the Mp3 or Wav audio file it seems to work, but then once finished at some point the music freezes with a continuous annoying noise. This is a big problem because having to supply the files to 6 radio stations I had to fall back on other software. Support ... please solve it. Hello and thanks

@Andrea-Berfio  ... If you have Sound Forge Audio Studio (or Sound Forge Pro for that matter), please see the first comment - from rraud - in this post about a similar issue regarding mp3 files and distortion.

I had a similar issue with mp3 files a while ago and the workaround worked even though I only had Sound Forge Pro installed, not SFAS.

That it also affects your wav files might mean that the cause of the problem is different to that described above

@Andrea-Berfio I opened a project that I finished in Build 550. It went wonderful. Playback on the timeline was great. Rendering it out, there were zero problems.

I bring in the same project from Build 550 into Build 636, and at the end of some clips, there is a LOUD scratch noise. Expanding the timeline to see what was there, 636 seemed to have added that waveform noise in some clips, and other clips which had no waveform still produced the noise during playback. Mind you, this was not on every clip, just some, and it was extremely annoying. Going back to 550, no problems.

I lost my settings and I'm on Windows 11 latest version.

Fwiw: I lost all my settings and I'm on Windows 10 (also fully up to date). So it is definitely not just a Win 11 issue.

I wrote a big post about it and then deleted it. But no harm in passing on this part of the info I guess.

It was actually quite funny, now I look back... I was updating Vegas and I though "oh I will have a look at the forum while it is installing"... Starting reading through this thread and got to the part about folks losing settings... "Noooooo... oh well, it is too late now install has finished, and it probably won't happen to me"...

It did. :-)

Project of about 1 hour, working with 7 camera tracks (2 UHD and 5 HD), all videos have proxies, and were then put on 1 track by 'create multicamera track'.  Many, many crashes on all kind of actions, e.g. just playing a preview : the sound goes on and on but the preview freezes and the system hangs, needs the task manager to kill it.

I used the task manager to monitor what happens with the memory, but Vegas never goes higher than 5 GByte, the automatic backups are a lifesaver, nevertheless it is very annoying and time consuming.

My system : AMD Ryzen 7 3700X 8-Core Processor 4.20 GHz, Nvidia Geforce RTX 2070 super, 32 Gbyte.  Windows 11 pro version 21H2.
Vegas 19 build 636.

@Bruggeling
No problem with my VPRO 19 b 636.
6 tracks with all UDH files out of my DJI pocket and in an UDH project on my laptop from signature, look

That's the bit I don't understand. There are beta testers here, apparently they're not allowed to tell us when they're testing a new release but they hint at it, @fr0sty is such a case. How would he not say "Guys the update just deleted all my personal settings, fix this before release or place a huge warning when loading the install file"

The same thing happened with version 532 of Vp19, I don't think it exists anymore replaced by version 550. The problems with 532 were immediately picked up by forum users. There has to be a problem with the beta testers themselves(seems unlikely) or the mechanism for giving feedback. The right people never see it?

The answer is quite simple. It didn't delete anything on my systems, or the systems of other testers. There's nothing wrong with the reporting process, and we talk to the dev team every day, all the right people see it and chat directly with us about the issues we report. This isn't a universal bug, it only affects some users.

The number of OS, driver, software, and hardware configurations out there is absolutely huge, and replicating every single one just isn't possible. It doesn't matter how many beta testers you use, when you release the software for many thousands of people (or tens of thousands? Hundreds of thousands? No idea what VEGAS' install base is) to install, there's always going to be something that the various combinations of system configurations in the testing pool didn't catch. Yes, sometimes that even means bugs that have major detrimental effects. Not even a multi-billion dollar company like Microsoft or Apple can release updates they don't have to occasionally quickly patch to overcome some system-breaking bug.

And of course, once such a bug does surface, where's the first place that users affected by it are going to go for help? Either official support or these forums, which is why the forum users pick up on it so fast. That's what this forum is here for, to offer tech support. I would hope that such bugs would surface quickly if there are any. If they don't, it means there's users out there not getting help.

 

Any Beta testers on Windows 11? You can't test all scenarios, but testing Windows 11 seems reasonable.
I lost my settings and I'm on Windows 11 latest version.

Yes, there are Windows 11 machines in the testing pool... that doesn't seem to be the common denominator that is causing this issue with presets, unfortunately. The team is actively investigating the cause and will be working hard to correct it as soon as possible.

I'm not going to go much more into the testing process, but please be aware that we do have a large number of testers, many utilizing multiple systems and multiple operating systems, and we're all doing the best we can. The development team works very closely with us, listens to our input and suggestions, and they're doing their best to give you the best product they possibly can.

"All of our company presets are gone and everything went to default settings! Please think of this when you release all-new versions and builds. When this happens it costs small companies like our thousands of $$$ fixing, researching how to fix, and making new templates. It's killing us each time you do it. How do we get back our project video presets? We have a LOT for each client. PLUS nothing works as it did before because all the settings we had, like "enable .mov", are all reset. spent an hour today just trying to figure out how to fix that."

 

Unless I'm mistaken you need to do the following. Before you upgrade to a new version install of Vegas use the now aging but fully functional Sony Preset Manager. Either v 1.0 or 2.0. This will allow you to export all your Vegas presets that you have painstakingly created and then import them into your next Vegas upgrade install. No pain!

https://sony-preset-manager.software.informer.com/2.0/

Plenty of "How to do it" vids on Youtube

Chris Young

 

@Bruggeling
No problem with my VPRO 19 b 636.
6 tracks with all UDH files out of my DJI pocket and in an UDH project on my laptop from signature, look

 

That is a 3 minute project. Mine is more than an hour. Had no problems in the first few minutes. Further into the video it crashes very often. Well if you follow this thread you will notice that I am not the only one to have this problem !

By now I am desperate. Have a project that must be finished before wednesday 8th of June. Rendering seems often to go wrong when Vegas writes the file from the tmp-file to the mp4-file (but not only then). Yesterday rendering worked without problems. The only change I made was some colorgrading, can't remove the colorgrading because essential.

I tried different disks, normally all SSD, and a normal hard drive, sometimes it works, and I think that I am saved, just to see that the next sequence crashes again. When I try to overwrite a file that has 0 bytes (because of the last crash) it will always crash again, so I have to (permanently) delete the file first.

More crashes with HEVC than with AVC, still I can't render all my work.

I started this project with build 636 so I can't go back.

@Bruggeling do you have an earlier version of Vegas? 18, 17? Open your project in 636, copy it to one of the other versions and save it with a different name. If you still want VP19, for "me", I've found build 550 pretty good.

As an fyi, I've been bit by Vegas settings resets many a time over the years. It's an issue that seems to come and go. Video driver updates occasionally reset video driver preferences too. I work around problems like that by trying to stick to defaults and writing down my customized preferences. VP19 does have a feature to save preferences to a file and I do that too. But it doesn't cover every setting. Would be really helpful if it covered all the preferences including internal ones.

Did a little digging to try and figure out were the Vegas project templates are saved. Found them in the registry here which I suppose could be saved into a .reg file in case an update blasted them:

Computer\HKEY_CURRENT_USER\Software\Sony Creative Software\Vegas Pro\19.0\Metrics\VideoProProfiles

Just did the update to build 636 and Vegas just hangs on start up. I can't even open vegas now. It appears to get stuck on my VSTi Is there away to stop vegas from scanning for plugins? I believe this might fix the issue.

FYI I did change the names of my VST plug in folder to zzzVSTs then vegas 636 started just fine. I then returned the vst folders to it original name removing the zzz and then started vegas again and it start no problem.

I have been working on computers for years and have a ton of different software so i know how to get around most tech issues. Vegas Pro is new to me. So maybe there is already away to open vegas without it having to scan through all third party VSTs?

@Andrea-Berfio I opened a project that I finished in Build 550. It went wonderful. Playback on the timeline was great. Rendering it out, there were zero problems.

I bring in the same project from Build 550 into Build 636, and at the end of some clips, there is a LOUD scratch noise. Expanding the timeline to see what was there, 636 seemed to have added that waveform noise in some clips, and other clips which had no waveform still produced the noise during playback. Mind you, this was not on every clip, just some, and it was extremely annoying. Going back to 550, no problems.

I just wanted to verity what is said above, a LOUD scratch at the end of "some" video clips. It is very noticeable and annoying. I loaded the file into Adobe Audition, the scratch is NOT there. With all due respect to the software developers, I would call 636 DOA.

In my career, I have been a software developer and a software test engineer, I know what frosty is saying about the complexity of developing and testing software on a near infinite number of platforms, nevertheless, with all due respect to my brother software engineers, 636 is DOA, IMO.

No one asked my opinion, but I would avoid this release. In 15+ years of using VP, some releases had flaws, but none were show stoppers and there was usually a workaround. That changed for me with 636. I updated as always do, this time I paid the price.

I'm not upset, video editing is a hobby for me, I'm just trying to help.

BTW, If I read the above, I would probably still upgrade to 636 thinking this guy is crazy and doesn't know what he is talking about. 😀

YMMV,

Rich

i updated to 636 without issues. Also my presets i created before were uneffected. I've also loaded a project from 550 which total lenght is 35min, done out of 3 files ~3h 4k video, also no problem. Todays computers are very piccy, wrong driver and the hardware does not work! I just had that with my HP reverb G2 VR googles, AMD version 22.5.1 works perfect, but 22.5.2 everything flickers, blackscreens and so on.

• ryzen 5950
• x570 mb Asrock
• 6900xt
• 64gb ddr4 3600
• 2x .m2 each 2tb
• 1x sandisk extreme pro ssd
• 2x toshiba hdd 3tb
• 1x seagate 8tb hdd
• Windows 10 pro

A sequence that would crash always when rendering, does render when I disable the colorgrading that had put on the whole track (to correct too much red). Enabling colorgrading again made it crash again during rendering.