VEGAS Pro 23 build 302 General Discussion

Comments

Reyfox wrote on 11/12/2025, 6:02 AM

@Murat-Makoiev start a separate post. Include the information from this POST, especially "B" and "C".

How did you use a preset from VP22? There is a lot more information that needs to be asked and it will get "lost" in this thread.

 

Newbie😁

Vegas Pro 22 B250 (VP18-21 also installed)

Win 11 Pro 23H2 (Build 22631.6060)

AMD Ryzen 9 5950X 16 cores / 32 threads

64GB DDR4 3200 Patriot Viper

Sapphire RX6700XT 12GB Driver: 25.9.1

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

Boris FX Continuum Complete 2025.5.1, Newblue FX Total FX360, Ignite Pro V5, proDAD Vitascene V5 Pro and Mercalli V6.

Howard-Vigorita wrote on 11/12/2025, 12:28 PM

Hi. Excellent update (302) for quick editing and work, the transparency problem was fixed, but after rendering (I used a preset from 22 Vegas), when adding a file to a new project, it is impossible to work, the file does not play, the strobe plays at any place in the timeline at the first frame. When importing the same file into 22 Vegas, there is a freeze, the file is cached for a very long time, like 4K. Render settings: 1080p, 25 fps, 320 kbps audio, 14 Mbps bitrate, NV ENCODER, LOW LATENCY - HIGH QUALITY, RC-MODE - CBR - HIGH QUALITY

@Murat-Makoiev There seems to be a difference in gop-length rendering Nvenc between vp22 and vp23. With vp22 nvenc rendered 8bit Avc with your settings, I get gop=60. Compared to vp23, I get gop=250. I wouldn't ever use a vp23 nvenc render like that in a Vegas project till it gets fixed. If you have an Intel igpu, qsv yields gop=14 in either vp22 or 23, but is a little slower on my 12900h/3060 laptop. MainConcept is slowest unless you have very fast cpu/ram and yields gop=15 in both 22 & 23. The lower gops are the easiest editing.

_litz wrote on 11/14/2025, 10:29 AM

Hi. Excellent update (302) for quick editing and work, the transparency problem was fixed, but after rendering (I used a preset from 22 Vegas), when adding a file to a new project, it is impossible to work, the file does not play, the strobe plays at any place in the timeline at the first frame. When importing the same file into 22 Vegas, there is a freeze, the file is cached for a very long time, like 4K. Render settings: 1080p, 25 fps, 320 kbps audio, 14 Mbps bitrate, NV ENCODER, LOW LATENCY - HIGH QUALITY, RC-MODE - CBR - HIGH QUALITY

@Murat-Makoiev There seems to be a difference in gop-length rendering Nvenc between vp22 and vp23. With vp22 nvenc rendered 8bit Avc with your settings, I get gop=60. Compared to vp23, I get gop=250. I wouldn't ever use a vp23 nvenc render like that in a Vegas project till it gets fixed. If you have an Intel igpu, qsv yields gop=14 in either vp22 or 23, but is a little slower on my 12900h/3060 laptop. MainConcept is slowest unless you have very fast cpu/ram and yields gop=15 in both 22 & 23. The lower gops are the easiest editing.

I'd really like the ability to specifically *set* the GOP length ... currently the only way to fine tune that kind of thing is the forgo using Vegas entirely as the encoder, and use Voukoder instead.