I am back to version 636. I added a slow motion effect to the video, and after a few adjustments, version 643 simply closed itself. So I took it down and am waiting for a newer version.

I know this is such a small issue, but can we figure out a way to update that doesn't constantly remove my taskbar icon and log me out of Vegas Hub?

Hi everyone, today i've upgrated to the last version and now I can't work anymore with Vegas pro 19...

There is anybody that can help me? Or I've to search a point to repristinate my windows 11 PC? Thank you so much

I can tell you from experience that if you have already started a project in the previous build, then do the update, your project will have this issue. Never update in the middle of a project. Do the update when you've finished.

@Paolo-Mattotti I have the same problem, over and over, and I tried a clean install of windows and Vegas 19 but it made no difference. If you can just find a restore point for now, then great.

I can tell you from experience that if you have already started a project in the previous build, then do the update, your project will have this issue. Never update in the middle of a project. Do the update when you've finished.

Since upgrading to 636 I have experience nothing but crashes. Some of these are large programs that take hrs to render. One made it to 98% before it crashed. Why did I ever waste my time. I have been with Sony for a long time but am ready to dump this software since Magix took over.

643 is the latest version...

@don-schmidt Try 643 which fixes issues that affect some users with 643. Beyond that share media, system specs, etc. What's towards the end of the project when you render?

@RogerS Do you or anyone know what is the difference between 643 and 636?

It's becoming a problem now that Magix is routinely pretending previous versions never existed. I assume the release notes for 643 are in relation to 550, and not 636. Does 643 still reset settings, templates etc?

When I manually check 636 release it goes to 643 https://www.vegascreativesoftware.info/us/forum/vegas-19-build-636-update-5--135607/

Yes, Nick Hope is on top of this. https://www.vegascreativesoftware.info/us/forum/vegas-pro-vegas-post-release-history--104998/

For recalled releases they are just overwriting everything as it's the same basic "update." I agree it is confusing.

There is no reset of settings going to 643 from 636.

Will try the 643 appreciate your help.

Please note also @NickHope's update of Direct (download) links. See here

What Magix has done with the simple overwriting of version 636 with 643 contradicts all basic rules of quality management and document control.
You can see from this example once again very clearly how much confusion something like this causes.
I sincerely hope that they learn from this and that this is the last time they make such a bullshit.

@walter-i.

A further comment re "update 5" added here.

@walter-i.

A further comment re "update 5" added here.

I've read all that, and I know that, but it doesn't change the fact that it wasn't done professionally at all.
The result is quite easy to understand from the many questions, uncertainties and comments here.

@walter-i. agreed on that point.

Just tried build 643. Noticed that aspect ratio of HDR footage is not respected in the preview window. See capture.

@gmtmtfilms so true. Never update in the middle of working on a project. Early on with VP19 builds, it was recommended (and there is warning if you plan on saving), that it will not be backwards compatible to previous builds in VP19. Doing a "Save As" of your project to a new name reflecting the build number is what I do, "just in case."

I am personally an incremental save person, never far behind if the project gets corrupted.

What Magix has done with the simple overwriting of version 636 with 643 contradicts all basic rules of quality management and document control.
You can see from this example once again very clearly how much confusion something like this causes.
I sincerely hope that they learn from this and that this is the last time they make such a bullshit.

They hadn't learned in years, so rest assured - you will see similar "updates" again and again.

After preforming the latest update on my desktop PCI could not use the software until I deactivated one of my copies. Strange as I only have 2 working copies 1 on my laptop and one on my Desktop. Nevertheless I deactivated my laptop copy and then activated my Desktop copy. Only to find I now have two working copies on my Desktop. I am reluctant to deactivate one of these copies as it might mess up my installation. The only thing I can put it down to is that I have recently upgraded to Win 11. Looking at my account it states two copies installed on my desktop (win10 64bit) both installations are identical. Any advice on how to best overcome this would be most helpful. thank you John

Deactivate both desktop from the web and then activate it again the next time you run the desktop copy. Otherwise it's a 50/50 guess which is which.

Maybe maybe I’m the odd man out, but I don’t seem to be having any issues with 643, including working on a project started in previous builds. In fact I’m pretty sure 643 is the FIRST time it’s started correctly after a boot on Windows 11.

With that said, the only bug I’m getting is, after working for some hours on a very complex project, now and again when I UNDO it fails and comes up with a warning to save the project to a new file immediately and restart the software. So far I’ve been able to do this with no loss of work.

Question for all... Before the update, I used to import all footage from file 1. Vegas would auto highlight the imported footage. I would then drop this footage straight to timeline. I would then import all footage from file 2 (sometimes with the same file names but different footage). This again would be highlighted and i would drop it straight into the timeline.

Since the update, Vegas has stopped highlighting the imported footage which takes me much longer to know what files have been imported (especially if they have the same file names) and select all required files to drop into timeline.

I hope this makes sense to some, but any idea how to fix or solve this?