Upgraded GPU from Nvidia 3070Ti to Nvidia 5080 Now VP22 slow crashes

terry54321 wrote on 6/19/2025, 6:08 PM

I upgraded GPU from Nvidia 3070Ti to Nvidia 5080 so I could preview Canon 4K 10bit 422 MP4 video files smoothly on the Vegas Pro 22 time line and to speed up rendering of 4k video. With the 3070 Ti gpu I had to create proxies in VP 22 to preview smoothly on the time line and rendering of 4k video was slow. However, with the new Nvidia 5080, VP 22 is sluggish, takes a full minute for me to drag a file from VP Explorer to the time line and gives message Vegas Pro 22 Not Responding. Frequently the video file has no video just audio. So now VP 22 is unusable for me unless I can find a fix.

Intel i9-12900KS, 64GB RAM, RTX 5080 with 16 GB Vram, C: drive 2 TB SSD, Windows 10 64 bit.

Back to post

Comments

johnny-s wrote on 6/21/2025, 12:38 PM

@terry54321 I downloaded the 5 second and 35 second 3.16 GB files. Bit of a nightmare trying to use as is in VP.

Creating proxies within VP takes forever so doing it external is best bet. However you would still have to use the original for final render.

IMHO the best way to go is convert all source DJI files to Prores 422 HQ. You then still retain 422 10 bit and VP plays nice with prores. I then got with the 29.97 frame rate Prores file .. 24 - 25 fps playback using best/full..

The 35s 3.16GB clip converted to Prores in ~ 27 seconds.on my main PC.

The Prores file was 6016 x 3384 with AR of 1.78. I used ffmpeg to convert external to VP, there are plenty of utils, Handbrake etc to do that.

Howard-Vigorita wrote on 6/22/2025, 10:42 AM

Fwiw, I have no problem decoding 4k 4:2:2 hevc from my Canon xf605 and c70 with Intel Arc gpus and although a little quicker than cpu, it's quite a bit slower than 4:2:0 which all my gpus including 4090 decode. So I use 4:2:0 instead. I don't think any of my Intel igpus decode 4:2:2 hevc, however, so I disable them and drop in an Arc. Since all my 4k camera sensors capture only the pixel elements used in 4:2:0, synthetic upscaling to 4:2:2 in the camera adds nothing that cannot be done better later and just slows down editing. So all my 4k shooting has been 4:2:0 hevc for years.

The Nvidia 5000-series are the only gpus claiming to decode 4:2:2 AVC. I've always avoided that format like the plague and would be surprised if Vegas 22 supported it yet. But I think ffmpeg might...ffmpeg is always the 1st to get new Nvidia updates. If someone sent me 4:2:2 avc or hevc to edit, I'd transcode it to 4:2:0 hevc with ffmpeg 1st. Shutter Encoder uses ffmpeg libs so that might work just as well.

Reyfox wrote on 6/27/2025, 8:31 AM

A different slant. With my hardware in my Signature below, @terry54321 Canon footage played back fine, Best>Full.

I wonder if @John-Callahan can play back this footage on his new AMD GPU....

John-Callahan wrote on 6/27/2025, 10:26 AM

I looked through this thread and found 2 files mentioned with problems:

TD009544.mp4
DJI 20250510135655 0200 D TRUNC.mp4

Both of these do not playback using VLC. All I could do was use Handbrake to create 2 new files:

TD009544.mp4 was 277MB and bitrate 464605kbps - Converted using best settings, but was 22MB and 36878kbps
DJI_20250510135655_0200_D_TRUNC was 467MB 784039kbps resolution 3384x6016 - Converted using best settings, but has errors attempting resolution same as source. Instead I was able to get it to convert it at resolution 3840x2160 945332kbps and 563MB. It looks OK. In Handbrake the preview shows what appears to be a 16:9 ration, not the 3384x6016 resolution found in the originals properties. The final 4K video appears to be OK

Reyfox wrote on 6/27/2025, 11:44 AM

@John-Callahan whille VLC is good with most files, I find that MPC-BE plays everything I've tossed at it. While the Windows player will not play back 10bit 422 video, MPC-BE does.

I haven't downloaded the DJI file yet.... I was curious as to how your AMD card handled it. As I wrote, the TD009544.mp4 file played back Best>Full on my computer with my "old" 6700XT. I'll look for the DJI file and see what happens.

Downloaded the DJI file and MPC-BE will not play it. VP22 locks up. Resolve Studio 20 plays the file.

Which drone shot the footage?

Howard-Vigorita wrote on 6/27/2025, 12:44 PM

I use both MPC-BE and MPC-HC. I like them because they are so similar but can be configured differently for limited-range footage. I can configure HC with a view-transform to automatically convert limited-range to full-range on display, so I can match it side-by-side to a Vegas full-range project preview, as well as side-by-side with YouTube which burns the transform into all uploads whether they need it or not. But I use BE to see limited-range the way others will see it with any viewer if I give them my render file.