Program update question

Daniel-Evans wrote on 2/8/2024, 9:31 PM

I'm currently running Vegas Pro 21.0.0.208. Since December, upon opening the program, I've been seeing a message to update to 21.1.0.0, which I have tried to do repeatedly. The files download and extract. The installation routine says it's deleting the previous version and installing the new version. That completes just fine and, finally, the registration routine pops up and I satisfy it's demands, ending with -- apparently -- a new install of 21.1.0.0. However, upon opening the program, I see the update message again, and the program is still 21.0.0.208.

So, what is happening with this update routine that, after about a half hour of downloads and installation steps, still leaves me with build 208? I've never even seen mention of 21.1.0.0 on forums or the Magix site.

One last issue, upon moving from Vegas Pro 19 to 21, I can no longer get my second monitor to work with the program. When I try to do so, the program freezes and crashes.

Thanks for anyone's help, who cares to weigh-in on these to issues.

Comments

RogerS wrote on 2/8/2024, 9:57 PM

The latest version of VEGAS Pro is 208.

It is likely prompting you to download "VEGAS Deep Learning Models 21.1.0.0" which is needed for the AI Fx. If this is failing in-program just download it directly here and install it: https://www.vegascreativesoftware.info/us/forum/faq-where-can-i-download-vegas-pro-and-other-vegas-software--104782/

The second monitor issue may be related to graphics drivers. In VEGAS go to help/driver update and see if there is a newer one to try.

Daniel-Evans wrote on 2/8/2024, 10:32 PM

RogerS, thank you so much for the quick and helpful response. It was, indeed, the DLM that required updating and I was able to do that and the Vegas update message has gone away upon startup. I also followed up on the driver update and I'm downloading a new version as we speak. So, hopeful that will fix the extended monitor issue. I'm very grateful for your help.

Daniel-Evans wrote on 2/9/2024, 12:35 AM

And, in conclusion, the video driver update also fixed the extended monitor problem. Thanks again.

RogerS wrote on 2/9/2024, 12:42 AM

Well that's excellent news! Now you can get back to editing.

Dexcon wrote on 2/9/2024, 3:26 AM

@Daniel-Evans  ... just a suggestion. It's usually forum etiquette to apply the 'The Solution' tag to the forum member who provided you with - or guided you to - the resolution to the issue. In your case, that forum member is RogerS.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

Daniel-Evans wrote on 2/9/2024, 4:11 AM

New here. Sorry for overlooking the solution tag. My thanks to RogerS for his help.

Cristinel-Neagu wrote on 2/9/2024, 5:34 AM

Hello, I need help! due to the problems encountered when editing with VegasPro 21, I uninstalled absolutely everything from Magix (versions 19, 20 and 21), cleaned the registries and all the traces left on the PC.
I downloaded the last update from Vegas pro 21, version 208, which I tried to reinstall and I have the unpleasant surprise to find that it won't let me install it. I tried several times, absolutely useless. The highlight is that I installed VegasPro19 without problems. I am in progress with a project started with VegasPro21, whose delivery deadline is already delayed due to program failures. I am attaching a print-screen with the messages received during the installation attempt. Thanks in advance

The project is not sophisticated, it is filmed in 4K with Sony A6500 with the following characteristics

Format                                   : XAVC
Codec ID                                 : XAVC (XAVC/mp42/iso2)
Overall bit rate mode                    : Variable
Overall bit rate                         : 59.2 Mb/s
Frame rate                               : 25.000 FPS 

My PC:

Operation System   Microsoft Windows 11 Pro
    Processor       12th Gen Intel(R) Core(TM) i7-12700K
    Memory       24,8 GB Free (31,8 GB Total)
    Graphics Card  Intel(R) UHD Graphics 770 (1,0 GB)
                   NVIDIA GeForce GTX 1070
    Monitor       Default Monitor (3840 x 2160 @ NULL Hz)
    Motherboard       Micro-Star International Co., Ltd. (MPG Z690 CARBON WIFI (MS-7D30))
 

vkmast wrote on 2/9/2024, 8:45 AM

@Cristinel-Neagu Please create a separate post ("New Post" clicking your avatar in the upper right corner) about your issue as this post was already solved. Thank you.

Cristinel-Neagu wrote on 2/9/2024, 11:07 AM

 

vkmast, thanks for the guidance, in the meantime I received an answer to [Ticket#2024020917001466] Installation problems. I want to thank the Magix team for their promptness, even if the first answer didn't help me. I want to share with other users who have encountered the same problem, the proposed solution that worked for me.

To be sure that the software is completely removed from your computer, please go to the link below:

Microsoft Fix: https://support.microsoft.com/en-us/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed

 

@Cristinel-Neagu Please create a separate post ("New Post" clicking your avatar in the upper right corner) about your issue as this post was already solved. Thank you.