Here's my File IO tab. I've been getting full speed previews in most cases using Good (Full) and in other cases get real good preview rates at Good (Preview).

Main differences - Uncheck the "Legacy AVC" option and turn on GPU Acceleration.

Thank you for your answer. I already tested it, but when I tried uncheck the AVC the video started stuttering even more, especially when I selected my graphics card. I noticed that when I disabled it, the preview became smoother.

What is a "high end" PC?

Hi, I have a RTX 4060 and am having a good experience with VP 23. Please uncheck legacy AVC decoding and set the hardware decoder to NVIDIA NVDEC. I recommend a recent studio driver for your GPU.

Beyond that can you share details for your media?

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

For Handbrake use the production standard template to start with and limit the keyint to your framerate (keyint=60).

There is one known issue with VP 23 and that's overlapping media with itself (cutting and fading, etc.) can significantly reduce performance with the new decoder. One workaround is to create a copy of the original media so that A overlaps/fades into B instead of A with A.

Hi, I have a RTX 4060 and am having a good experience with VP 23. Please uncheck legacy AVC decoding and set the hardware decoder to NVIDIA NVDEC. I recommend a recent studio driver for your GPU.

Beyond that can you share details for your media?

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

For Handbrake use the production standard template to start with and limit the keyint to your framerate (keyint=60).

There is one known issue with VP 23 and that's overlapping media with itself (cutting and fading, etc.) can significantly reduce performance with the new decoder. One workaround is to create a copy of the original media so that A overlaps/fades into B instead of A with A.

I already tried uncheck the AVC the video started stuttering even more, especially when I selected my graphics card. I noticed that when I disabled it the preview became smoother.

I have exactly the same GPU as you and can confirm that it works fine with Vegas, on my current PC I have V20,21,22 and 23 all fine with the RTX 4080 Super. Following Roger's comment about over laping clip here is what I find comparing V22 and V23 using a 6 second overlap between two clips using render Magix H264 GPU NVENC:

V22 Ave fps 48.74

V23 Ave fps 42.47

ie, V23 15% slower.

In a longer comparison with various FX included with a 7 min project I get with same render H264 NVENC:

V22 Ave fps 63.52

V23 Ave fps 40.00

I have exactly the same GPU as you and can confirm that it works fine with Vegas, on my current PC I have V20,21,22 and 23 all fine with the RTX 4080 Super. Following Roger's comment about over laping clip here is what I find comparing V22 and V23 using a 6 second overlap between two clips using render Magix H264 GPU NVENC:

V22 AVE fps 48.74

V23 Ave fps 42.47

ie, V23 15% slower.

Yeah, this makes me feel really bad. I don’t even know where the problem is coming from, my setup should handle it fine

Hi, I have a RTX 4060 and am having a good experience with VP 23. Please uncheck legacy AVC decoding and set the hardware decoder to NVIDIA NVDEC. I recommend a recent studio driver for your GPU.

Beyond that can you share details for your media?

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

For Handbrake use the production standard template to start with and limit the keyint to your framerate (keyint=60).

There is one known issue with VP 23 and that's overlapping media with itself (cutting and fading, etc.) can significantly reduce performance with the new decoder. One workaround is to create a copy of the original media so that A overlaps/fades into B instead of A with A.

General
Complete name                            : I:\RECORD\2025-10-30 19-23-32.mp4
Format                                   : MPEG-4
Format profile                           : Base Media
Codec ID                                 : iso4 (iso4/isom/obs1/iso2/avc1/mp41)
File size                                : 252 GiB
Duration                                 : 4 h 8 min
Overall bit rate mode                    : Variable
Overall bit rate                         : 145 Mb/s
Frame rate                               : 60.000 FPS
Encoded date                             : 2025-10-30 18:23:32 UTC
Tagged date                              : 2025-10-30 18:23:32 UTC
Writing application                      : OBS Studio (32.0.2)

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L5.1
Format settings                          : CABAC / 4 Ref Frames
Format settings, CABAC                   : Yes
Format settings, Reference frames        : 4 frames
Format settings, GOP                     : M=3, N=120
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 4 h 8 min
Bit rate mode                            : Variable
Bit rate                                 : 145 Mb/s
Maximum bit rate                         : 10 000 kb/s
Width                                    : 2 560 pixels
Height                                   : 1 440 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 60.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.655
Stream size                              : 252 GiB (100%)
Title                                    : advanced_video_recording
Writing library                          : obs_nvenc_h264_tex
Encoded date                             : 2025-10-30 18:23:32 UTC
Tagged date                              : 2025-10-30 18:23:32 UTC
Color range                              : Limited
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709
Codec configuration box                  : avcC

Audio #1
ID                                       : 2
Format                                   : AAC LC
Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 4 h 8 min
Bit rate mode                            : Constant
Bit rate                                 : 117 kb/s
Nominal bit rate                         : 320 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 48.0 kHz
Frame rate                               : 46.875 FPS (1024 SPF)
Compression mode                         : Lossy
Stream size                              : 209 MiB (0%)
Title                                    : Mic
Default                                  : Yes
Alternate group                          : 1
Encoded date                             : 2025-10-30 18:23:32 UTC
Tagged date                              : 2025-10-30 18:23:32 UTC

Audio #2
ID                                       : 3
Format                                   : AAC LC
Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 4 h 8 min
Bit rate mode                            : Constant
Bit rate                                 : 320 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 48.0 kHz
Frame rate                               : 46.875 FPS (1024 SPF)
Compression mode                         : Lossy
Stream size                              : 554 MiB (0%)
Title                                    : GAME SOUND
Default                                  : Yes
Alternate group                          : 1
Encoded date                             : 2025-10-30 18:23:32 UTC
Tagged date                              : 2025-10-30 18:23:32 UTC

Audio #3
ID                                       : 4
Format                                   : AAC LC
Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 4 h 8 min
Bit rate mode                            : Constant
Bit rate                                 : 2 275 b/s
Nominal bit rate                         : 320 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 48.0 kHz
Frame rate                               : 46.875 FPS (1024 SPF)
Compression mode                         : Lossy
Stream size                              : 4.05 MiB (0%)
Title                                    : DISCORD
Default                                  : Yes
Alternate group                          : 1
Encoded date                             : 2025-10-30 18:23:32 UTC
Tagged date                              : 2025-10-30 18:23:32 UTC
 

In addition to the overlapping clip issue (you could just make a copy of it in Windows explorer- copy and paste the file back into the same folder) in OBS try setting the GOP (keyframe interval) to 1 (second). That should be all you need to edit smoothly in VEGAS with NVDEC.

In addition to the overlapping clip issue (you could just make a copy of it in Windows explorer- copy and paste the file back into the same folder) in OBS try setting the GOP (keyframe interval) to 1 (second). That should be all you need to edit smoothly in VEGAS with NVDEC.

Thanks, I’m not sure I fully understand the overlapping clip issue you mentioned. I usually move clips around a lot, I can easly notice if duplicates when I’m rearranging things during heavy edits. Also I don’t use NVDEC for recording, I record in H.264, which I believe is AVC in MP4 format.

The issue is if you take one long recording, split it and then fade it or overlap it with another piece of the same original media the performance is much worse in VP 23.
If you had one recording, made a copy of it (A and B) and split A and B and overlapped or faded A with B the performance should be good.

NVDEC= NVIDIA decoding or playback. You already re-enabled this in preferences/ file io. It's what makes your GPU help speed playback of media.

MediaInfo confirms you are recording AVC in an MP4 container; try limiting the GOP as I suggested if you don't already do that.

The issue is if you take one long recording, split it and then fade it or overlap it with another piece of the same original media the performance is much worse in VP 23.
If you had one recording, made a copy of it (A and B) and split A and B and overlapped or faded A with B the performance should be good.

NVDEC= NVIDIA decoding or playback. You already re-enabled this in preferences/ file io. It's what makes your GPU help speed playback of media.

MediaInfo confirms you are recording AVC in an MP4 container; try limiting the GOP as I suggested if you don't already do that.

Ah okay, so next time I should record with Keyframe Interval = 1 second in OBS, right? About the overlapping part: since I edit gaming videos and cut a lot of scenes, will that affect performance? Are you saying I should make separate copies of the original footage, like one named "A" and another named "B" and use them in the timeline so that clip A is for the first scene, clip B for the next, then back to A again, instead of overlapping cuts from the same original file? Sorry if my explanation isn’t perfect, English is not my native :D

I can confirm the vp23 problem @RogerS mentioned with overlaps of video split from the same camera-clip on disk. The RedCar 4k benchmarks I have listed in my signature all use the same clip on disk overlapped up to 3 at a time and perform very poorly in vp23. Did not do that when I created them with earlier versions of Vegas. Hope they fix this at some point.

Ah okay, so next time I should record with Keyframe Interval = 1 second in OBS, right? About the overlapping part: since I edit gaming videos and cut a lot of scenes, will that affect performance? Are you saying I should make separate copies of the original footage, like one named "A" and another named "B" and use them in the timeline so that clip A is for the first scene, clip B for the next, then back to A again, instead of overlapping cuts from the same original file? Sorry if my explanation isn’t perfect, English is not my native :D

@AbdelhadiAfa English may not be your native language but you understood this perfectly!

Yes, with the OBS fix it will give VEGAS somewhat easier to edit footage.

By making copies of the footage you can work around this limitation with VP 23.

Do both and hopefully you will no longer have a laggy preview experience.

@RogerS @Howard-Vigorita It's a shame that the issue with crossfades made on split media hasn't been resolved in VP23, as that is my main gripe about VP22, but thanks for the info, I'm glad I didn't upgrade.

@AbdelhadiAfa I've turned to using proxies, for a long time I thought my PC was powerful enough to handle simple MP4 projects but no. For me cutting a piece of media, adding a 15fr crossfade & then playing it it would take several loop plays before it would play fluidly, that was a pain esp when just a few frames needed to be further removed during refinement of the crossfade.

Proxies are time consuming but they eliminate this crossfade issue when the preview is set to Preview (Full) 👍

I can confirm the vp23 problem @RogerS mentioned with overlaps of video split from the same camera-clip on disk. The RedCar 4k benchmarks I have listed in my signature all use the same clip on disk overlapped up to 3 at a time and perform very poorly in vp23. Did not do that when I created them with earlier versions of Vegas. Hope they fix this at some point.

To my knowledge this issue was/is also present in VP22, so not a VP23 only issue.

Proxies are time consuming but they eliminate this crossfade issue when the preview is set to Preview (Full) 👍

Easier and quicker is to do a selectively prerender (SHIFT+M) just for that crossfade.

Proxies are time consuming but they eliminate this crossfade issue when the preview is set to Preview (Full) 👍

Easier and quicker is to do a selectively prerender (SHIFT+M) just for that crossfade.

@3POINT As soon as you make any further edit that prerender is lost, I sometimes make 3,4 or 5 adjustments to a crossfade, prerendering every time is a pain.

An auto prerender would be a good solution, just like many other editors already have.

Ah okay, so next time I should record with Keyframe Interval = 1 second in OBS, right? About the overlapping part: since I edit gaming videos and cut a lot of scenes, will that affect performance? Are you saying I should make separate copies of the original footage, like one named "A" and another named "B" and use them in the timeline so that clip A is for the first scene, clip B for the next, then back to A again, instead of overlapping cuts from the same original file? Sorry if my explanation isn’t perfect, English is not my native :D

@AbdelhadiAfa English may not be your native language but you understood this perfectly!

Yes, with the OBS fix it will give VEGAS somewhat easier to edit footage.

By making copies of the footage you can work around this limitation with VP 23.

Do both and hopefully you will no longer have a laggy preview experience.

Ohh man, the work will only get harder if i need each time to make copies to fix the issue, but i will try if it works; thank u

@RogerS @Howard-Vigorita It's a shame that the issue with crossfades made on split media hasn't been resolved in VP23, as that is my main gripe about VP22, but thanks for the info, I'm glad I didn't upgrade.

@AbdelhadiAfa I've turned to using proxies, for a long time I thought my PC was powerful enough to handle simple MP4 projects but no. For me cutting a piece of media, adding a 15fr crossfade & then playing it it would take several loop plays before it would play fluidly, that was a pain esp when just a few frames needed to be further removed during refinement of the crossfade.

Proxies are time consuming but they eliminate this crossfade issue when the preview is set to Preview (Full) 👍

I tried using proxies with my 4-hour video even if i waitted so long, but I’m still having the same issue 😔 Honestly, my old version VG 18, performed better than VG 23. It’s disappointing, especially after they advertised it as “peak performance for new engine” I didn’t expect this at all. I’ve already requested a refund, but I’m not sure if they’ll approve it though.

Proxies are time consuming but they eliminate this crossfade issue when the preview is set to Preview (Full) 👍

Easier and quicker is to do a selectively prerender (SHIFT+M) just for that crossfade.

@3POINT As soon as you make any further edit that prerender is lost, I sometimes make 3,4 or 5 adjustments to a crossfade, prerendering every time is a pain.

An auto prerender would be a good solution, just like many other editors already have.

I used it frequently, not for crossfades because I know how a crossfade looks/will look, but mainly for other complex parts of the timeline. But I must admit that this is a workaround that shouldn't be necessary.

And also I don't know why the program create a lot of sfk files each time I opened the VG 23, as you can see sfk0, sfk1, sfk2

@AbdelhadiAfa The sfk0, sfk1, sfk2 files are created to draw audio waveforms for each of the audio tracks in your media. It's been done since Sound Forge days and probably will continue.