I just open Vegas Pro 23 and was presented with2 updates. 1 update was for Smart Mask 2.0. The 2nd update is for VP23 build 356. What is fixed in this update? There's nothing in Vegas Hub about it.
It's long been a case where I've got in the Australasian region an update alert when opening Vegas Pro but the update announcement under the forum's News section doesn't appear until many hours later, probably based on EU time zone. In that regard, be patient, the forum's News announcement which is usually accompanied by updates details will no doubt appear in the next half day or less.
Aaaaannnnnnd ... we're back to crashing! I haven't had a single crash since the nVidia driver update about a week ago. Update 356 installed and not even 5 minutes and it locked up.
Timeline playhead no longer moving during playback. It just stays static. Ugh.
Edit: I would highly recommend not upgrading to this build version, and remaining on 302.
Having literally the same issue. Anyone know a way to downpatch to 302? This is unusable.
EDIT: Issue seems to be on larger files. I have one project that's roughly a minute and it's fine, but another that's two hours, and it's broken there.
@anthony-chiappette It is a freeze-hang I suppose? If so, I have the occasional hang too. I have legacy AVC decoding enabled due to a decoding issue on playing the timeline not fixed yet, but the hang-freeze is probably a different and separate bug. We do share a 50xx series GPU however...
@anthony-chiappette Just out of curiosity, when you hang-freeze, did your timeline perhaps had no audio on the audio track (like deleted the audio from the clip)? Or, working with a lot of stills (which have obviously no audio either)? I like to figure out the main reason for these freezes.
@anthony-chiappette Just out of curiosity, when you hang-freeze, did your timeline perhaps had no audio on the audio track (like deleted the audio from the clip)? Or, working with a lot of stills (which have obviously no audio either)? I like to figure out the main reason for these freezes.
No there was audio. it does the same thing. The program freezes, but the audio still plays.
@anthony-chiappette Sorry to hear that! Any clue as to what triggered it? (Fx?) Anything in Windows Reliability History?
I have no idea what caused it. As stated, when I updated the nVidia driver, I had not a single crash in many days. I was working on a project which had no issues. When I went into VP23 to continue, I got the update prompt, so I updated. When I opened the project I was testing the timeline. I dragged the cursor to various parts of the timeline and hit play. When I did this near the end of the video, the program just locked and froze while the audio continued. I was able to hit the stop button and the audio stopped, but that was it, Vegas was frozen solid.
At first I had thought it might be a GPU issue. @anthony-chiappette, and @bitman have 5000 series Nvidia GPU's, until I saw that @jacknsb does use an AMD GPU, the same series as mine. @8-BitRobin has nothing in the user profile saying what type of hardware is used and should fix this by adding it to the Signatures like everyone else, to see if there is some commonality of hardware.
Me? No problems so far. I found B302 to be "ok", and this current update build is working pretty good for me on my computer spec'ed below working mostly with UHD4K from my Panasonic cameras. Oh, and using Boris FX, proDAD, and NBFX from time to time.
@anthony-chiappette Just out of curiosity, when you hang-freeze, did your timeline perhaps had no audio on the audio track (like deleted the audio from the clip)? Or, working with a lot of stills (which have obviously no audio either)? I like to figure out the main reason for these freezes
i have an audio track with music, as well as several tracks with lots of stills using pan/crop and FX. Any type of motion blur FX that uses ML/motion detection especially causes the program to hang, but it can be any combo of FX that require heavy resources. Really disappointed to see this new build hasn’t fixed it and I am continuing to edit with GPU acceleration disabled. It’s not a good experience at all but I have no choice currently.