this bug still exists.
200% opacity

it comes very rare in some cases. but should be fixed.

please someone explain me why this thing for..

we use Ctrl + Down Arrow on audio event, to normalize the audio.

but if you will apply select and use Ctrl + Down Arrow on video event then it will make it of 0 opacity.

if it is a function then please elaborate. maybe It is new for me.

thankyou.

No more random "pause crashes" on my bigger projects after this update, uncertain what solved it but this is very welcome. 👍

Hi, came today to happily find this release and thread, read it throughout. Then went to the news forum and all looks good and nice there.
Could someone enlighten me? Forgetting about release 237 and solely talking about 239, are there audio-video sync issues not present before as affirmed in this very thread, or were these fixed in the two days renewed patch?

And it could be too soon for a conclusion, but is there a firm base to move into 239 patch release for most user cases? Or if you suggest to wait, what would be the usage cases affected so far by obvious issues at 239 update (that were unaffected at previous versions)?

@Cielspacing The audio/visual sync issues caused by 237 are resolved in 239. I would highly recommend moving to 239 if you are on 194, especially if you have an NVIDIA GPU.

I just updated from 194 to 239 and unfortunately the flickering problem is back in exported videos, when working in a 10 bit project (on AMD GPUs).

The problem was massive in Vegas 20, fixed in Vegas 22 (I skipped 21) and it's back with the latest update. Please fix this - once and for all... :D

@N1truX Just to be clear, a 10-bit project means 32-bit full? Are you using ACES or HDR (maybe share a screenshot of project settings so we can see exactly where the problem lies.)

Thanks for the quick reply. Since Vegas (still) don't offer the ability to change the UI language, we have to stick with German (sorry for that).

Hardware: AMD Ryzen 5900X + 32 GB RAM + Radeon RX 6800 XT (16 GB).

10 bit: The flickering occurs in both 32-bit full and video. No HDR, no log, no LUTs involved. Just 10 bit video from end to end (4:2:2 10 bit from the Lumix S5 IIx; 32 bit editing; export in 10 bit HEVC).

Since Vegas (still) don't offer the ability to change the UI language, we have to stick with German (sorry for that)

??????????????????

You have to set the language on install, obviously if this user wants to use it in German there's no reason to install it in English.

Since Vegas (still) don't offer the ability to change the UI language, we have to stick with German (sorry for that)

??????????????????

I don't want to re-install Vegas Pro for a screenshot ;)

this bug still exists.
200% opacity

it comes very rare in some cases. but should be fixed.

Confirmed! b239!!

@N1truX it doesn't take long to uninstall/reinstall Vegas Pro. I can not see a reason not to do this.

As for your flickering video, and you provide a small sample in the cloud that can be tested? I shoot often in 10bit 422 with a Lumix G9 and have never had any flickering.

After being away for awhile, I would like to jump back in to the world of video editing. I have as new system, now all I need is the software. The Vegas Pro 22 Suite looks Awesome! Will my old licensed version of Vegas Movie Studio 9 Qualify me for the Vegas Pro 22 Suite Perpetual License Upgrade version? Sorry if I'm in the wrong thread.

@DaveYbarra 

 In the website's Online Shop click "Information regarding the upgrade" and you'll see this text: "You can upgrade at a reduced price with a previous version or other authorized product. Please have your login details or serial number ready." You'll be informed if it does not qualify.

If you "upgrade", maybe best to test with the free trial first "to check compatibility with your system and to avoid disappointment in case you dislike any new features or restrictions".

this bug still exists.
200% opacity

it comes very rare in some cases. but should be fixed.

Confirmed!

Currently using RTX 2080 Ti (RTX 5090 arrives in a week) with Ryzen 9950x, and I have to have the preview at the lowest possible settings if I work with nested files. I have my facecam + facecam border, and that nest alone makes Vegas preview playback at basically 2fps at quarter preview quality, and takes about an hour to render a 10 minute video with basically all render options (including custom ones). Same issue since Vegas 13 to be honest. Tried premiere, and there I could do nests within nests with 8k footage without an issue and a complete render within 2 minutes. In Vegas, a single nested 1080p file makes it unusable, sadly.

Hello everyone. I was just wondering why the driver update faciity was removed, is there a specific reason?

@Graham-Hilton it was too difficult to maintain as the video card companies kept changing how to find things on their website. I used it mainly to quickly tell what driver I had installed instead of relying on it to tell me if a new driver was available.

Masking has gone MAD in the latest update, the masking in my preview wind dose not align with the one in the pan crop window and its causing a muck with my work. I rely on masking a lot for my work please let me know if there is anything that can be done to sort this out without an update! Urgent!

Try using the bezier mask effect instead of pan/crop.

I had to remove vb239 and re-install b122 - both b194 and b239 crashes with two of my projects.