Within about 90 seconds of opening VP21 Build 187, doing anything or doing nothing, the program causes the computer to lock up. That means completely unresponsive...mouse won't move pointer; keyboard inputs ignored; power cycle is the only way to get the computer back up.
I have had this behavior a few times while in VP21 187. Nearly every time while running Mocha Vegas.
These lockups occur no matter what I do in VP21 187; even doing nothing...it locks in about 90 seconds from starting the program. Power Cycle is the only way out.
VEGAS Pro 21 Build 187 is unusable, and is likely harming my computer.
@IAM4UK I've edited without a single crash/white screen of death/lockup for 6 hours straight with B187 on my computer spec'ed in my signature. The video was UHD 4K 50P with color grading/correcting, Pan/Crop doing exactly that, 20MP images, Boris FX DeHaze, Smartsound music, and Vegas ttiles.
That's lovely, Reyfox. Nevertheless, it is locking up my computer, although the previous Build did not. I have asked MAGIX for an installation link for the previous build, but their support autoreply says to wait 2-4 days for a response.
@IAM4UK yes it is lovely that B187 has been quite stable for me and others. But you do not list any hardware in your profile to see where the difference between say, your computer, and mine is.
Intel Core i7-11700K at 3.60 GHz (stock speed)
64 GB DDR-4 RAM
Intel ARC 770 with 32 GB VRAM, most current driver 31.0.101.3616
Windows 11 Pro, Build 22635.2700 (23H2)
Yep, my "187" has "murdered" any projects I try to get under way. The previous version was one of the most stable I used in quite some time. Immediately after installing the new version? Freezing up my computer.
I do have integrated i750 graphics as an option within VEGAS Pro 21... I never use it because I got the ARC, but I will point VP21 to it and see what happens...
@sean-giordano do not hijack someone else's thread. While you might have the same issue, it can be caused by different circumstances. Start your own and give the necessary information from this POST, specifically "B" and "C". .
@IAM4UK
Thanks for this info, looks all normal to me, but I have one question:
Do you see at File I/O at hardware decoder also a possibility to use your Intel 750 as a part of your processor?
If so, try the use that one and look if you see changes.
Changing the "RAW" processor to i750 and keeping the Hardware Decoder set to ARC 770 seems to have worked!
How I hate random nonsense that causes versions to go from working to crashing... Thank you for giving me this path to the solution, @j-v
Raw processor shouldn't do anything unless the footage is raw. The hardware decoder setting is the next one.
Can you share MediaInfo your particular footage? https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/
In that case I don't think you fixed anything. I'd expect the problem to return.
Even ctrl-alt-del doesn't work? Windows key? Driver problem!
In that case I don't think you fixed anything. I'd expect the problem to return.
... Unless the problem was the Intel ARC driver being somehow incompatible with 187, which seems probable (as bvideo noted).
That's lovely, Reyfox. Nevertheless, it is locking up my computer, although the previous Build did not. I have asked MAGIX for an installation link for the previous build, but their support autoreply says to wait 2-4 days for a response.
I went back in the forums about the first release Vegas 21 and Build 108 is there. Mine was crashing to desktop when opening VP 21 with 187. I used those links to download 108
In that case I don't think you fixed anything. I'd expect the problem to return.
... Unless the problem was the Intel ARC driver being somehow incompatible with 187, which seems probable (as bvideo noted).
What did you do to fix that? Changed drivers? Disabled the Arc GPU in preferences/video and file io under decoding? Pretty sure the raw decoder is for formats like Blackmagic Raw which you aren't using.
Yes, but the nature of some bugs can have seemingly unrelated issues causing problems where they shouldn't sometimes... Like all the issues we had with dynamic ram preview back in the day, which should not have affected anything but just that, dynamic ram preview.
At least we have a possible cause we can point the developers towards so they know where to start looking for the issue.
I'd suggest more time and testing to really determine if raw decoder has any relevance or if it's coincidence or some third factor that occurred at the same time. Hopefully other Intel Arc users can also report problems if any.
@Howard-Vigorita Did you see any similar issues as the OP here? You also have an 11th gen Intel K CPU with Arc 770?