Recording with AMF shows 100% encoder activity

[Tony359]

Hi all,

I'm testing OBS on an AMD laptop, Ryzen 7 6800HS and its iGPU. I selected the options as attached and I see 100% utilisation of the GPU - which is in fact 100% of the encoder.

I'm used to nVidia and I don't remember seeing the same high utilisation with an RTX.
I'm just trying to ascertain whether what I see is normal.

Can someone please confirm? The recording resolution is 3071x1920

Thanks!

 

[rockbottom]

Not all encoders are created equally. As far as the overload, use a faster Preset, like Balanced or Speed if necessary.

 

[Tony359]

of course, I just wanted to make sure that what I am experiencing is expected.

Indeed for a screen capture of old PCs a faster setting might work the same! :)

 

[rockbottom]

I never tested the resolution you're running but it's going to place more load on the encoder than a 1080p encode. 3072 x 1920 might yield better results than the current 3071 x 1920.

 

[Tony359]

I'm not sure why I set it to 3071 - thanks! - but unfortunately no change even at 3072.

The same laptop has a 3050 on it - which I have now disabled as the "switchable graphic" is a disaster of implementation. I've used the 3050 so far, I don't remember seeing the GPU running at 100% - though it's a 3050 and as you say, not every encoder is created the same!

 

[rockbottom]

You should be using the 3050. There's a massive performance gap between it & that 680M iGPU.

 

[Tony359]

I know - but the implementation of the switchable graphic is so bad in Windows. The laptop is so much more responsive and deals with sleep sessions so much better without the 3050 enabled (even though Windows was told not to use unless told so).
I was about to get a different laptop until I discovered how much better the laptop works without the 3050.

 

[Tony359]

I've just realised that with the encoder at 100% OBS is dropping a lot of frames - it's really unusable. OBS does not report frame drop though. What is going on?

Yes, I can reduce the quality profile but I thought even an iGPU was ok for a screen recording in Hardware, even at high-ish resolution?

 

[Tony359]

Sorry for the triple post, editing time has expired.

In Balanced mode, I have all sort of encoding glitches on the picture. (random video from youtube)

 

[prgmitchell]

hi, in order to troubleshoot an issue you'd need to include a log that captures the issue you are having.

 

[Tony359]

Hi @prgmitchell

Of course!

This is a session with the AMF encoder running in Quality mode. Resulting video is more than choppy, it just freezes at times.

https://obsproject.com/logs/ABnlNv2BZo6UDCuk

This is a session with the AMF encoder running in Balanced mode. No missing frames but lots of corruption as shown above
https://obsproject.com/logs/ruFoTAFBaEnemIBh balanced

I've also tried running in CPU mode and I have a similar stuttering than using Quality mode - just the recording accounts for 7% of the CPU so I am not sure I understand.

With the 3050 I've never had issues (unfortunately).

Please do let me know if you need more details!

 

[rockbottom]

If HDR is enabled on your system, disable it. If it's not enabled, go into the AMD Control Panel & change the Color Depth setting from 10 to 8-bit. Lag should go away with the correct setting.

19:36:28.035: Initializing D3D11...
19:36:28.035: Available Video Adapters:
19:36:28.040: Adapter 0: AMD Radeon(TM) Graphics
19:36:28.040: Dedicated VRAM: 4220985344 (3.9 GiB)
19:36:28.040: Shared VRAM: 14867206144 (13.8 GiB)
19:36:28.040: PCI ID: 1002:1681
19:36:28.040: HAGS Status: Disabled (Default: No, Driver status: Unsupported)
19:36:28.040: Driver Version: 32.0.13031.3015
19:36:28.040: output 0:
19:36:28.040: name=
19:36:28.040: pos={0, 0}
19:36:28.040: size={3072, 1920}
19:36:28.040: attached=true
19:36:28.040: refresh=60
19:36:28.040: bits_per_color=10
19:36:28.040: space=RGB_FULL_G22_NONE_P709

https://www.amd.com/en/resources/support-articles/faqs/DH3-008.html

Next, clean up your Scenes. All of them have multiple Display, Game or Window captures. There should only be (1) per Scene due to potential interference. Lots of device failures too.

19:36:29.464: Loaded scenes:
19:36:29.464: - scene 'Microscope-Lapsun 1080p':
19:36:29.464: - source: 'Display Capture' (monitor_capture)
19:36:29.464: - source: 'Joyalens' (dshow_input)
19:36:29.464: - source: 'Microscope' (dshow_input)
19:36:29.464: - source: 'Scope-VNC' (window_capture)
19:36:29.464: - source: 'Elgato' (dshow_input)
19:36:29.464: - source: 'Window Capture 2' (window_capture)
19:36:29.464: - scene 'Microscope-Lapsun':
19:36:29.464: - source: 'Display Capture' (monitor_capture)
19:36:29.464: - source: 'Joyalens' (dshow_input)
19:36:29.464: - source: 'Microscope' (dshow_input)
19:36:29.464: - source: 'Scope-VNC' (window_capture)
19:36:29.464: - source: 'Elgato' (dshow_input)
19:36:29.464: - source: 'Window Capture 2' (window_capture)
19:36:29.464: - scene 'Screen Capture only':
19:36:29.464: - source: 'Display Capture' (monitor_capture)
19:36:29.464: - source: 'Microscope' (dshow_input)
19:36:29.464: - source: 'Scope-VNC' (window_capture)
19:36:29.464: - source: 'Elgato' (dshow_input)
19:36:29.464: - source: 'Focusrite 12' (wasapi_input_capture)
19:36:29.464: - source: 'Focusrire 34' (wasapi_input_capture)
19:36:29.464: - source: 'Focusrite 56' (wasapi_input_capture)
19:36:29.464: - source: 'Focusrite 78' (wasapi_input_capture)
19:36:29.464: - scene 'Scope Web':
19:36:29.464: - source: 'Display Capture' (monitor_capture)
19:36:29.464: - source: 'Microscope' (dshow_input)
19:36:29.464: - source: 'Scope-VNC' (window_capture)
19:36:29.464: - source: 'Elgato' (dshow_input)
19:36:29.464: - source: 'Edge Scope' (window_capture)
19:36:29.464: - scene 'Oscilloscope VNC':
19:36:29.464: - source: 'Display Capture' (monitor_capture)
19:36:29.464: - source: 'Joyalens' (dshow_input)
19:36:29.464: - source: 'Microscope' (dshow_input)
19:36:29.464: - source: 'Scope-VNC' (window_capture)
19:36:29.464: - source: 'Elgato' (dshow_input)
19:36:29.464: - scene 'OSCC 4:3':
19:36:29.464: - source: 'Joyalens' (dshow_input)
19:36:29.464: - source: 'Microscope' (dshow_input)
19:36:29.464: - source: 'Scope-VNC' (window_capture)
19:36:29.464: - source: 'Elgato' (dshow_input)
19:36:29.464: - source: 'OSSC 4:3 on FHD' (dshow_input)
19:36:29.464: - monitoring: monitor and output
19:36:29.464: - source: 'Display Capture' (monitor_capture)
19:36:29.464: - source: 'Window Capture' (window_capture)
19:36:29.464: - source: 'Window Capture 4' (window_capture)
19:36:29.464: - source: 'Focusrite 12' (wasapi_input_capture)
19:36:29.464: - source: 'Focusrire 34' (wasapi_input_capture)
19:36:29.464: - source: 'Focusrite 56' (wasapi_input_capture)
19:36:29.464: - source: 'Focusrite 78' (wasapi_input_capture)
19:36:29.464: - source: 'Focusrite 2i2' (wasapi_input_capture)
19:36:29.464: - scene 'OSCC 16:9':
19:36:29.464: - source: 'Joyalens' (dshow_input)
19:36:29.464: - source: 'Microscope' (dshow_input)
19:36:29.464: - source: 'Scope-VNC' (window_capture)
19:36:29.464: - source: 'Elgato' (dshow_input)
19:36:29.464: - source: 'OSSC 4:3 on FHD' (dshow_input)
19:36:29.464: - monitoring: monitor and output
19:36:29.464: - source: 'Display Capture' (monitor_capture)
19:36:29.464: - source: 'Window Capture' (window_capture)
19:36:29.464: - scene 'StarTech':
19:36:29.464: - source: 'Joyalens' (dshow_input)
19:36:29.464: - source: 'Microscope' (dshow_input)
19:36:29.464: - source: 'Scope-VNC' (window_capture)
19:36:29.464: - source: 'Elgato' (dshow_input)
19:36:29.465: - source: 'OSSC 4:3 on FHD' (dshow_input)
19:36:29.465: - monitoring: monitor and output
19:36:29.465: - source: 'Display Capture' (monitor_capture)
19:36:29.465: - source: 'Window Capture' (window_capture)
19:36:29.465: - source: 'StarTech USB' (dshow_input)
19:36:29.465: - scene 'scope and VNC':
19:36:29.465: - source: 'Display Capture' (monitor_capture)
19:36:29.465: - source: 'Joyalens' (dshow_input)
19:36:29.465: - source: 'Microscope' (dshow_input)
19:36:29.465: - source: 'Scope-VNC' (window_capture)
19:36:29.465: - source: 'Elgato' (dshow_input)
19:36:29.465: - scene 'Elgato only':
19:36:29.465: - source: 'Joyalens' (dshow_input)
19:36:29.465: - source: 'Microscope' (dshow_input)
19:36:29.465: - source: 'Elgato' (dshow_input)
19:36:29.465: - source: 'Scope-VNC' (window_capture)
19:36:29.465: - source: 'OSSC 4:3 on FHD' (dshow_input)
19:36:29.465: - monitoring: monitor and output
19:36:29.465: - source: 'Display Capture' (monitor_capture)
19:36:29.465: - source: 'Window Capture' (window_capture)
19:36:29.465: - scene 'Scene 2':
19:36:29.465: - source: 'Window Capture 3' (window_capture)
19:36:29.465: - scene 'OSSC 4:3 and scope':
19:36:29.465: - source: 'Joyalens' (dshow_input)
19:36:29.465: - source: 'Microscope' (dshow_input)
19:36:29.465: - source: 'Scope-VNC' (window_capture)
19:36:29.465: - source: 'Elgato' (dshow_input)
19:36:29.465: - source: 'OSSC 4:3 on FHD' (dshow_input)
19:36:29.465: - monitoring: monitor and output
19:36:29.465: - source: 'Display Capture' (monitor_capture)
19:36:29.465: - source: 'Window Capture' (window_capture)
19:36:29.465: - source: 'Window Capture 4' (window_capture)
19:36:29.465: - scene 'E10':
19:36:29.465: - source: 'Display Capture' (monitor_capture)
19:36:29.465: - source: 'Microscope' (dshow_input)
19:36:29.465: - source: 'Scope-VNC' (window_capture)
19:36:29.465: - source: 'Elgato' (dshow_input)
19:36:29.465: - source: 'Sony E10' (dshow_input)
19:36:29.465: - monitoring: monitor and output
19:36:29.465: - source: 'HDMI' (dshow_input)
19:36:29.465: - source: 'logitech' (dshow_input)
19:36:29.465: - scene 'Electron':
19:36:29.465: - source: 'Joyalens' (dshow_input)
19:36:29.465: - source: 'Microscope' (dshow_input)
19:36:29.465: - source: 'Scope-VNC' (window_capture)
19:36:29.465: - source: 'Elgato' (dshow_input)
19:36:29.465: - source: 'OSSC 4:3 on FHD' (dshow_input)
19:36:29.465: - monitoring: monitor and output
19:36:29.465: - source: 'Display Capture' (monitor_capture)
19:36:29.465: - source: 'Window Capture' (window_capture)
19:36:29.465: - source: 'Window Capture 4' (window_capture)
19:36:29.465: - scene 'Microscope and Oscilloscope':
19:36:29.465: - source: 'Joyalens' (dshow_input)
19:36:29.465: - source: 'Microscope' (dshow_input)
19:36:29.465: - source: 'Scope-VNC' (window_capture)
19:36:29.465: - source: 'Elgato' (dshow_input)
19:36:29.465: - source: 'OSSC 4:3 on FHD' (dshow_input)
19:36:29.465: - monitoring: monitor and output
19:36:29.465: - source: 'Display Capture' (monitor_capture)
19:36:29.465: - source: 'Window Capture' (window_capture)
19:36:29.465: - source: 'Window Capture 4' (window_capture)
19:36:29.465: - source: 'Thermal Camera' (window_capture)
19:36:29.465: ------------------------------------------------
19:36:30.008: Joyalens: data.GetDevice failed
19:36:30.008: Joyalens: Video configuration failed
19:36:30.424: Microscope: data.GetDevice failed
19:36:30.424: Microscope: Video configuration failed
19:36:30.631: StarTech USB: data.GetDevice failed
19:36:30.631: StarTech USB: Video configuration failed
19:36:30.836: Sony E10: data.GetDevice failed
19:36:30.836: Sony E10: Video configuration failed
19:36:31.239: logitech: data.GetDevice failed
19:36:31.239: logitech: Video configuration failed
19:36:31.430: OSSC 4:3 on FHD: data.GetDevice failed
19:36:31.431: OSSC 4:3 on FHD: Video configuration failed

 

[prgmitchell]

use the AMD settings from this guide but with the balanced preset instead of quality

Advanced Recording Settings Guide | OBS

OBS Knowledge Base. Recommended settings when using Advanced Output mode

obsproject.com

 

[Tony359]

Thanks @prgmitchell
It works with those settings. Really thank you for your help!

is MKV a critical part of the settings? macOS preview doesn't support it, I'd rather use a different container.

@rockbottom
I hate that I had to disable so many things on this laptop to make it work properly. HDR is pointless unless you have an OLED screen, which I don't have.

In any case, I don't seem to have an option in my AMD drivers to set the bit depth. Are you aware of a way to do it anyways? See below.

Yes, I am aware my scenes are a mess. I really feel I need to stop and understand how that works!
Device failures is because they're all disconnected.
But yes, I need to tidy up that mess, sorry.

Thank you also for your help!

 

[prgmitchell]

is MKV a critical part of the settings? macOS preview doesn't support it, I'd rather use a different container.

no

 

[rockbottom]

OLED is not needed for HDR, just a monitor that supports it.

Not sure. You may need to dig around in there to find it. I don't bother to pay attention to AMD drivers but the fact that it may be missing could be a driver thing. The 10 > 8 bit conversion that is currently going on is un-necessary & also a performance hit.

 

[Tony359]

I understand why you asked me to reduce the bit depth to 8 bit - on a laptop is more or less marketing.

The fact that the panel supports HDR doesn't mean it can reproduce it well. HDR on an average LCD laptop panel is 100% marketing

I'll look into that, for now I haven't found a way - someone seems to suggest that that is the only supported mode by the panel/connection itself and that's why it's not in the driver. Who knows.

It could also be that I am using the latest AMD drivers and not the ones Lenovo supplies - which are pretty old. I'll keep searching.

Thanks again!

 

[rockbottom]

Yep, HDR has different levels of support. The top end models support the highest levels of HDR, Dolby Vision IQ, Dolby Vision, HDR10+, HDR10.

The installed AMD driver most likely is the reason for the missing Bit Depth setting.

 

[Tony359]

I tried updating them but it's unchanged.

 

[rockbottom]

Sorry I can't offer much help with those drivers. No AMD anything in any of my current systems to test. I do know that certain laptops like those from Dell run best on the graphics driver(s) they release. Might want to check & see what Lenovo recommends.