@EricLNZ I was rendering UHD in my trials https://www.vegascreativesoftware.info/us/forum/vp22-vs-vp23-rendering-speed-vp23-slower-than-vp22--149593/ Maybe something changed because I've read that '720 max' in other posts .....?

Thanks @Gid. My trial is build 302. Maybe yours, and Robbies, was using the initial release build 278. In which case it would seem the 720 restriction was introduced with build 302.

@RobbieLad To see if it's something project-specific or system-specific could you try the VP 20 benchmark in my signature and submit the results? You should be near the top of the charts with hardware like that.

Did anything change from the trial? NVIDIA driver version (I stayed on 581.87 with my 5070)? It is possible recent builds of VEGAS are slower for certain Fx, I saw that with my own tests.

I'm still on NVIDIA driver 581.29, I normally update regularly but at the time to update to the next version, whenever that was, I didn't want to rock the boat & I'm still in the same boat, I'm coming to the end of a series of videos & everything is working fine with VP22. . That post I shared above was on the 9/9/2025, my Geforce app says NVIDIA driver 581.29 - Sept 2025 so I was prob up to date during that trial, I would have naturally updated everything to make sure I was getting a true test .. .

I updated yesterday to NVIDIA driver 591.44 (coming from 577.00) I don't see any difference in rendering speed with VP23.302. Which is still (much) faster as previous renderings with VP22.250 Of course now I also receive the error code in VP22 when using an NVENC supported rendertemplate.

But I'm still able to render with Voukoder in VP22.250 with the Voukoder NVENC supported rendertemplates....

3 frames per second on pan and crop stills. Very disappointing. Version 21 - 22 runs at 200 to 300 fps.

@Bofus could you provide a small test veggie with original footage with the issue so that others maybe can confirm? For me VP23 has the fastest render experience I ever had with Vegas. I'm rendering HEVC 4k50 10bit footage to HEVC NVENC with about 60fps average.

@3POINT there are several posts here indicating 591 breaks rendering on versions previous to 23. To get 22 to render again, you need to go back to driver version 581. nVidia broke it - it's not just older versions of VEGAS but other application as well.

@jetdv I know, but I have no purpose to go back to earlier versions of Vegaspro. The only thing I miss in VP23 is rendering with Voukoder classic, but as tested, Voukoder classic works also in VP22 with the latest NVIDIA driver.

@3POINT I also have 591 on my newest computer as I also have no need to go back to the older versions to render.

I'm guessing from Nvidia comments I've seen that the problem with the new driver might only affect apps which make the mistake of relying on Nvidia-provided render presets rather than specifying parameters explicitly. I didn't test ffmpeg before rolling back from 591.94, but if Voukoder classic works, ffmpeg and apps like Shutter Encoder are probably also unaffected. In which case apps like Vegas would be well advised to 86 unreliable Nvidia presets before history repeats itself.

For render FPS 23 is way slower with pan crop in use and that's been reported before. No connection to drivers that I know of.

For render FPS 23 is way slower with pan crop in use and that's been reported before. No connection to drivers that I know of.

Even that I cannot confirm, of course pan/crop animation is a little slower than no animation, but not extremely as reported by some users.

We've had a few threads on the topic and have been able to replicate and report it.

356 included this as a known issue:

Significant performance delays occur when using Pan/Crop in an event

We've had a few threads on the topic and have been able to replicate and report it.

356 included this as a known issue:

Significant performance delays occur when using Pan/Crop in an event

Was it reported as a 356 specific issue or a VP23 specific issue? I don't see any anomalies with pan/crop with video or stills in 302.

Here's my report with timing tests. V23 first edition was a lot slower vs V22 last edition.

https://www.vegascreativesoftware.info/us/forum/v23-worse-performance-on-pan-crop-of-stills--149869/

VP23 general issue.

VP23 general issue.

Or an Intel QSV? As @bvideo uses a QSV rendertemplate. VP23 renders definitely faster than VP22 with NVENC render templates, which I use. The annoying renderpauses every 70 frames or so, which all previous Vegas versions NVENC renders suffered from is gone in VP23. Again, I don't see any issues with pan/crop. Actually my latest 4k50 project contains also stills from a Samsung S24 smartphone, used as PIPs with a pan/crop zooming effect. Renders with 30fps.

Example:

It's not a good use of anyone's time to rehash this when there are plenty of other problems to uncover and report. No this isn't about QSV, it's about pan/crop including its timeline performance and lagginess.

While there may be situations in which the problem isn't apparent, we've gotten multiple feedback on this forum about pan/crop's performance drop since VP 22, users submitted test projects with issues, experienced users replicated those issues and then the developers acknowledged them. At this point it's out of our hands.

In the benchmarks I manage VP 23's performance has declined since its release with the complex VP 20 project (I've tested every build with 2 systems). In some cases it's slower than 22.250. The simpler VP 16 project stayed about the same. All testing is using MagixAVC with NVENC only. The lack of render hiccups can be outweighed by bottlenecks before the encoding stage.

Not to stray from this topic but for the border Fx issue, had you ever reported that to VEGAS support or had the developers acknowledge it? If not could I ask you to file a support request? I'd like to see that fixed.

It's not a good use of anyone's time to rehash this when there are plenty of other problems to uncover and report. No this isn't about QSV, it's about pan/crop including its timeline performance and lagginess.

While there may be situations in which the problem isn't apparent, we've gotten multiple feedback on this forum about pan/crop's performance drop since VP 22, users submitted test projects with issues, experienced users replicated those issues and then the developers acknowledged them. At this point it's out of our hands.

In the benchmarks I manage VP 23's performance has declined since its release with the complex VP 20 project (I've tested every build with 2 systems). In some cases it's slower than 22.250. The simpler VP 16 project stayed about the same. All testing is using MagixAVC with NVENC only. The lack of render hiccups can be outweighed by bottlenecks before the encoding stage.

Not to stray from this topic but for the border Fx issue, had you ever reported that to VEGAS support or had the developers acknowledge it? If not could I ask you to file a support request? I'd like to see that fixed.

See my screencapture previous post. I use my own real situation bench marks. The same results I get with Magix AVC.

The Border FX issue as also the annoying NVENC render hiccups I reported in the past several times.

Now I stop using your or anyone's time with my findings and keep on edting with VP23.302.