Ryzen vs Intel for 4:2:2 10bit decoding

MarkAnthony121 wrote on 1/11/2023, 2:28 AM

Decoding 4:2:2 10bit HEVC (I believe it's HEVC) footage from my Canon R5 specifically shot in 60fps in Vegas is nearly impossible. Sluggish performance and constant crashes. 24fps is fine. Based on help I've received in this forum in the past I believe the issue is that Vegas itself is not optimized for this type of footage in general, or not optimized for Intel CPUs, as someone mentioned. Can anyone else confirm, perhaps someone with a Ryzen system? Or even a 13900K? Any performance difference when trying to decode this type of footage specifically in the timeline? Or is this just a typical Vegas lack of optimization thing regardless of what platform you're on? And yes I know I can transcode or make proxies, I'm just trying to see if it can be avoided.

Back to post

Comments

RogerS wrote on 1/12/2023, 6:39 PM

Turn the GPU back on especially if you have LUTs or any Fx. It helps at the render stage too. Stick to QSV decoding as you discovered as it works great in Vegas.

Former user wrote on 1/12/2023, 9:29 PM

Here's an ALL-I from the R5 for Intel and AMD users to try

https://www.dropbox.com/s/dxryixo9l72xjp9/R5T_9417_Video_Cut.MP4?dl=0

Actually this is only 1080P, I can find another version later, or the OP can test using his own files and maybe upload something

MarkAnthony121 wrote on 1/12/2023, 9:36 PM

Here's an ALL-I from the R5 for Intel and AMD users to try

https://www.dropbox.com/s/dxryixo9l72xjp9/R5T_9417_Video_Cut.MP4?dl=0

Keep in mind that my specific concern was CLOG3 60fps footage in ALL-I.

Former user wrote on 1/12/2023, 10:47 PM

@MarkAnthony121 This is 60fps ALL-I https://www.amazon.com/photos/shared/vIHk6X78RbmqXzcH7xO04g.y-fWp3Jn3hzlgH_64MjLNf Click the three dots to reveal download option

I don't imagine the encoding will change due to your choice of CLOG3, but will get slower in Vegas with 32bit cclor mode with color correction. There is HQ and non HQ modes, the higher bitrates of HQ will most likely cause a slow down in Vegas, as it seems sensitive to AVC/HEVC bitrates

MarkAnthony121 wrote on 1/12/2023, 10:52 PM

@MarkAnthony121 This is 60fps ALL-I https://www.amazon.com/photos/shared/vIHk6X78RbmqXzcH7xO04g.y-fWp3Jn3hzlgH_64MjLNf Click the three dots to reveal download option

I don't imagine the encoding will change due to your choice of CLOG3, but will get slower in Vegas with 32bit cclor mode with color correction. There is HQ and non HQ modes, the higher bitrates of HQ will most likely cause a slow down in Vegas, as it seems sensitive to AVC/HEVC bitrates

Yes but no where did I say I was having performance issues with any footage aside from CLOG3 footage. Please keep in mind that my entire reason for this post is because recording on the R5 in CLOG3 automatically creates 10bit 4:2:2 files. And I didn't even have performance issues with this footage unless it was very specifically 60fps. BUT now that I was told to try recording in 4:2:2 CLOG3 10bit 60fps in ALL-I I'm getting MUCH better playback performance. Just rendering the ALL-I footage is like 20% slower now, that's all

Former user wrote on 1/12/2023, 11:12 PM

My misunderstanding. Good to hear 👍

RogerS wrote on 1/13/2023, 12:00 AM

Hi Mark, I just had a chance to test the file on my desktop (Intel with iGPU). On a 60fps @ best full with legacy HEVC disabled on file i/o it played back but never at full framerate.

For normal video editing I'd assume NTSC framerates with the 60fps capture there for slow motion and speed ramps. At best / full dropping the 60fps clip on a 29.97 timeline and just playing back is at full framerate here (29.97). When cutting and moving clips around it can drop substantially with crossfades, etc. as Vegas gets bogged down.

At preview/auto it's mostly full framerate. When added at project framerate (so for slow motion) it's full framerate for playing back at best/full dropping at cuts. At preview/auto it's mostly 29.97 though a long crossfade will slow it down.

I'd still shoot all-I and not bother with a new PC with QSV which will still struggle for fluid editing.

Former user wrote on 1/13/2023, 1:12 AM

@RogerS If you're talking about Marc's IPB file, could you also test my ALL-I 4K upload, and make comparisons. It seems no better on an AMD cpu without GPU decode (The Amazon link)

RogerS wrote on 1/13/2023, 1:44 AM

Hi Todd, I was testing the file from Mark.

I just tested your upload and it plays great (it is 1080p though). At 1080p60 and best full it's at full framerate throughout, with slight dips during a fade transition.

Healthy decode activity:

Edit: I see there's a second file. I'll download it but so far it's slow to download.

Former user wrote on 1/13/2023, 1:49 AM

@RogerS Thanks for that confirmation about the slowness. I knew it was slow to upload, and suspected it could be a slow download. Will try other options where available

RogerS wrote on 1/13/2023, 2:06 AM

For the new UHD 60p file just playing back at best full I only get about 20fps.

Preview auto on a 29.97p timeline gets full framerate playback including when chopped up for editing. Preview full is around 20fps.

Former user wrote on 1/13/2023, 2:36 AM

@RogerS That's interesting so you are seeing the editing advantages of ALL-I, but not seeing any advantage in ease of processing. In other editors I can edit 4K 422 HEVC 60fps IPB, but not this ALL-I version, 100% CPU and lagging preview.

Howard-Vigorita wrote on 1/13/2023, 6:11 PM

Another trick you can try is to temporarily set the project to 30p for editing, making sure the frame rate is an exact multiple. Maybe your Nvidia is spinning its wheels trying to preview 60p and that's compromising it's ability to process luts and fx. I don't have a high-end Nvidia but I thought it was better than the cpu at that.