obs-studio icon indicating copy to clipboard operation
obs-studio copied to clipboard

Settings -> Output with Output Mode "Advanced": cannot view or edit encoder properties in Streaming tab when profile has encoder in it that is no longer available

Open YorVeX opened this issue 5 years ago • 8 comments

Platform

Operating system and version: Windows 10 Pro Build 2004 (x64) OBS Studio version: 26.0.0

Expected Behavior

In the Output settings in "Advanced" Output Mode when only the x264 encoder is available the encoder properties should still be shown and editable in the below window section.

Current Behavior

The encoder properties section just says "No properties available" and there doesn't seem to be any way to bring these settings up.

Steps to Reproduce

Run OBS 26.0.0 on a computer that only supports the x264 encoder (i.e. doesn't have any graphics device or QuickSync capable CPU), go to Settings -> Output and set "Output Mode" to "Advanced".

Additional information

On computers that offer more than one encoding option this problem doesn't occur. This issue also existed in 25.0.8.

YorVeX avatar Oct 01 '20 01:10 YorVeX

Please provide a log file.

Fenrirthviti avatar Oct 01 '20 01:10 Fenrirthviti

Here is a log of a session where I started OBS, did the reproduction steps as mentioned above, then closed everything again: 2020-10-01 03-42-33.txt

Here's also a screenshot of the result: Advanced-Output

YorVeX avatar Oct 01 '20 01:10 YorVeX

It looks like you have imported or copied a profile from a system with an encoder selection that does not exist on this PC:

03:42:34.850: Encoder ID 'amd_amf_h264' not found
03:42:34.850: Encoder ID 'amd_amf_h264' not found

You can fix this by simply creating a new profile from the profile menu, but I agree that this is a bug we should address when an encoder is no longer available. It's a pretty rare edge case where this can actually happen.

Fenrirthviti avatar Oct 01 '20 01:10 Fenrirthviti

Right, using a new profile fixes it. Thanks a lot for the quick help with this!

When I last used AMF that must have been 4 years ago or so, on a completely different computer even. But since I am lazy I always just copied the profiles over.

I changed the title to reflect that this was in fact the cause of the problem. Would be good if this could still be fixed, even when I agree that probably not many people will run into this.

YorVeX avatar Oct 01 '20 01:10 YorVeX

Note for others running into this: if you don't want to recreate all your profiles like me you can simply edit \config\obs-studio\basic\profiles\your_profile_name\basic.ini with a text editor and in the [AdvOut] section delete the lines that say "Encoder=amd_amf_h264" and "RecEncoder=amd_amf_h264" (or whatever other invalid encoder you might have set there).

This has worked for me to fix this issue and still keep the other profile settings, no guarantees that it will work for anyone else, create backups of your profile files before you do this if you want to be on the safe side.

YorVeX avatar Oct 01 '20 02:10 YorVeX

I can help fix this issue. What properties should we expected to show in this case?(when there is an encoder which is not found)

offthegrid-mike avatar Nov 30 '20 10:11 offthegrid-mike

I don't know whether the question is directed at me or the main contributors of this project, but IMHO you should keep the behavior consistent with the rest of the UI. For example if an audio device is configured that went missing it looks like this: image

So it should be similar if an encoder is configured that went missing.

YorVeX avatar Dec 01 '20 21:12 YorVeX

Are there any more fixes needed. I'm looking for first contribution. Thank you!

Mahas1234 avatar Apr 22 '24 10:04 Mahas1234