Plug-ln Chooser is extremely slow to open.
Ok, did you try anything else? Anything good to say about any of it? lol...
Impress someone, they might tell a friend. Piss them off, they'll tell 10.
@fr0sty - Yeah. Working very fast here. The speed is faster than I can type!
After the update, every time I add a video to the timeline and attempt to click on the video in the video track, Vegas proceeds to hang "Not responding" and one of my CPU cores is on 100% utilization. (EDIT: Once I started complaining here, it has resolved itself... after 5 restarts...)
That's that new AI-assisted error fixer that they snuck in, 😂
Haha, that would be a nice feature 😁
Unfortunately, the crashing does keep coming back...
Oh no, this not responding issue is still not fixed? :(
I won't upgrade to 20 from 19 until this is shorted 100% out.
Yes, my pc is old, but the issue is exist on my daughter's pc too (ryzen5, 16GB, RX480 not the latest but with the recommended, stable 22.5.1 driver) My wife is crazy because he edited a 3 cam concert (all with standard avc 1080p files), and Vegas freezed in every 20-30 minutes of editing. So not responding issue exist on 2 totally different system by us :(
After the update, every time I add a video to the timeline and attempt to click on the video in the video track, Vegas proceeds to hang "Not responding" and one of my CPU cores is on 100% utilization. (EDIT: Once I started complaining here, it has resolved itself... after 5 restarts...)
That's that new AI-assisted error fixer that they snuck in, 😂
Haha, that would be a nice feature 😁
Unfortunately, the crashing does keep coming back...
Oh no, this not responding issue is still not fixed? :(
I won't upgrade to 20 from 19 until this is shorted 100% out.
Yes, my pc is old, but the issue is exist on my daughter's pc too (ryzen5, 16GB, RX480 not the latest but with the recommended, stable 22.5.1 driver) My wife is crazy because he edited a 3 cam concert (all with standard avc 1080p files), and Vegas freezed in every 20-30 minutes of editing. So not responding issue exist on 2 totally different system by us :(
Looking into their problem deeper, in the thread they made about it, it seems as it is a problem with their system, as no other users are able to reproduce the same crash using the exact same media files, and even they reported that the crashing stopped after rebooting a certain number of times. You can always be sure by downloading the VEGAS 20 demo and seeing how it works on your system.
That's 24 hours and only 2 crash reports on these forums, with one of them being a user that said the problem resolved itself after a few reboots... The other complaining the VEGAS.exe desktop icon was malfunctioning, which could have been a system error or an improper installation, we won't know until we can diagnose it. Out of the hundreds of VEGAS users on this forum, I'd say that's pretty stable. We also had one complaint about slow loading plugins... that's about it. Not to say this version is 100% perfect, no version is or ever will be of any software ever... but it has been stable enough for me to edit multiple 4K multicamera concert productions in 4K HDR using 10 bit 4:2:2 AVC media, without a single crash.
I do apologise if this question has been answered multiple times, but for my own benefit and possible others as well, is it possible to upgrade from VEGAS Pro 18 to VEGAS Post 20? Thanks in advance for the answer.
Sure, users of any perpetual non-Steam version of Vegas Pro can upgrade to Post 20. Login to your account and you should qualify for upgrade pricing at the store.
impressive list of crashes bugs and broken features for me so far. Maybe start with getting Vegas to reliably open when you click the icon, guys? I mean that much, at least ?? What happened to Frosty's vaunted beta testers?
Might want to have a look at this:
Issue details
January 2023
Application shortcuts might not work from the Start menu or other locations
StatusOriginating updateHistory
ResolvedN/A
Resolved: 2023-01-18, 19:28 PT
Opened: 2023-01-13, 13:40 PTAfter installing security intelligence update build 1.381.2140.0 for Microsoft Defender, application shortcuts in the Start menu, pinned to the taskbar, and on the Desktop might be missing or deleted. Additionally, errors might be observed when trying to run executable (.exe) files which have dependencies on shortcut files. Affected devices have the Atack Surface Reduction (ASR) rule "Block Win32 API calls from Office macro" enabled. After installing security intelligence build 1.381.2140.0, detections resulted in the deletion of certain Windows shortcut (.lnk) files that matched the incorrect detection pattern.
Windows devices used by consumers in their home or small offices are not likely to be affected by this issue.
Workaround: Changes to Microsoft Defender can mitigate this issue. The Atack Surface Reduction (ASR) rules in Microsoft Defender are used to regulate software behavior as part of security measures. Changing ASR rules to Audit Mode can help prevent this issue. This can be done through the following options:
Using Intune: Enable attack surface reduction rules | Defender for Endpoint: Microsoft Endpoint Manager
Using Group Policy: Enable attack surface reduction rules | Defender for Endpoint: Group Policy
Microsoft Office applications can be launched through the Microsoft 365 app launcher. More details on the Microsoft 365 app launcher can be found in Meet the Microsoft 365 app launcher
Next steps: This issue is resolved in security intelligence update build 1.381.2164.0. Installing security intelligence update build 1.381.2164.0 or later should prevent the issue, but it will not restore previously deleted shortcuts. You will need to recreate or restore these shortcuts through other methods. For additional information and help recovering missing shortcuts, see Recovering from Attack Surface Reduction rule shortcut deletions (updated on January 17, 2023 to include additional guidance and scripts to help with recovery).
Affected platforms:
Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB
Server: None
https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-21h2
Here is the error report
Problem Description
Application Name: VEGAS Pro
Application Version: Version 20.0 (Build 326)
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\WINDOWS\SYSTEM32\amdxc64.dll
Fault Address: 0x00007FFA074EDDE2
Fault Offset: 0x000000000059DDE2
Fault Process Details
Process Path: C:\Program Files\VEGAS\VEGAS Pro 20.0\vegas200.exe
Process Version: Version 20.0 (Build 326)
Process Description: VEGAS Pro
Process Image Date: 2023-01-16 (Mon Jan 16) 17:03:24
It seems the problem lies with the amdcx,dll
What does that mean?
Thanks
https://www.freefixer.com/library/file/amdxc64.dll-258130/
AMD graphics driver.
May need to update this driver version.
@David-Dalton ... From your earlier post, your comment and computer's specs were:
As soon as the flash screen appears I get the message "Not working" before the program opens.
Before the update, I was running the program without any problems,
If it helps, here are my computer specsDell Precision T3610
Processor Intel(R) Xeon(R) CPU E5-1650 v2 @ 3.50GHz 3.50 GHz
Installed RAM 32.0 GB
System type 64-bit operating system, x64-based processor
AMD FirePro W7000 Fire GL V, 2x
Edition Windows 10 Pro
Version 22H2
OS build 19045.2486
Experience Windows Feature Experience Pack 120.2212.4190.0
Please correct me if I am in error, but is that computer not from circa 2013 - almost 10 years ago? The current minimum requirements for Vegas Pro 20 are outlined here.
Given that Vegas Pro has been evolving version-by-version and update-by-update - including GPU usage - it may be that Vegas Pro 20 b326 has now passed the capabilities of your computer's GPU - that relating to the 'Fault Module: C:\WINDOWS\SYSTEM32\amdxc64.dll' message - AMD being the computer's GPU.
If you have installed the Deep Learning Models (DLM) - which heavily relies on GPU usage - try uninstalling the DLM program and see how Vegas Pro 20 goes after the uninstall of the DLMs.
Otherwise, you might need to revert to VP20's previous build which worked for you - or consider updating to a modern computer that is much better capable of taking advantage of 2023 software especially in the computer intensive field of video editing.
Thanks for adding Flemish to the text to speech! As you can see the the Vegas team is not deaf to user requests. Very much appreciated!
@Grazie @Reyfox @bitman Did you test it in the same condition that I presented in this video?
Here, too, it does not present slowness in other situations. But specifically as I showed in the video. Dragging the effect through the Plug-in Manager and then going to add it through the Plug-in Chain, the Plug-in Chooser window takes a long time to load the effects. At least on my machine :(
It would be interesting if possible. You can test it the way I showed you to see if the same thing happens to you.
It would be interesting that when we choose the project orientation on the welcome screen the layout changes accordingly. Or even a button (on the welcome screen) to choose our saved layouts.
And I'm sure you're already thinking about it. But could have project resolution 1080p, 2K, 4K etc
Setting the project parameters through the welcome screen makes it a lot easier, I really liked it!
I find a really bad bug in the new update and i am so angry because the previous update was fine and now it ruins everything again, and the bug that 2 frames at the end of the clip got bugged sound annoying me more... Fix all bugs please... and why the hell when i use auto ripple the colour is changing to orange?
impressive list of crashes bugs and broken features for me so far. Maybe start with getting Vegas to reliably open when you click the icon, guys? I mean that much, at least ?? What happened to Frosty's vaunted beta testers?
Might want to have a look at this:
It is absolutely insane that folks are expected to change settings within Windows Defender just to get a program to open when clicked. This isn't an isolated case, it's happening to multiple users.
I really appreciate the work that goes into new features and I love learning how to use new features too, but I'd prefer an update that got the basics right.
While I agree that my computer is ageing, and I wouldn't attempt to edit 4K material on it, it was running well on V20. Something in the upgrade installation caused this error to arise.
I am running V19 without problems.
@m3lquixd I tried your procedure, but with other fx's as I do not have s_glow; plug-in-chooser speed is almost instantaneous (and I have plenty of effects to load, such as Boris Cont. lots of newBL etc..)
Just a question: did you have that issue with other versions of Vegas like 19 or prior builds? If so, it could be due to some bottleneck in your hardware.
The autoripple color is a feature in response to years of user requests to make it more obvious what ripple is affecting as it can break projects. I think it's a little too subtle though and wish the icon were also the same color to stand out from the other confusing-looking icons down there.
Just a question: did you have that issue with other versions of Vegas like 19 or prior builds? If so, it could be due to some bottleneck in your hardware.
@bitman Neither in versions 19 nor in the previous 20.
And this slowdown is only happening in the way I mentioned.
Dragging the effect through the Plug-in Manager and then going to add it through the Plug-in Chain, the Plug-in Chooser window takes a long time to load the effects.