Misleading Label/Help Text when specifying default display under Configuration>Audio/Video tabs.

[GrantAbell]

Is there an existing issue for this?

• I have searched the existing issues

Is your issue described in the documentation?

• I have read the documentation

Is your issue present in the latest beta/pre-release?

This issue is present in the latest pre-release

Describe the Bug

Issue

Under the Configuration tab, and then under the Audio/Video sub-tab, help text and labels suggest that the integer display ID should be used as far as specifying which default display to use upon initiating a session.

Configuration setting with Integer:

Troubleshooting log:

Following the help text and using the integers supplied from the Logs under the troubleshooting tab, does not yield the expected behavior of new sessions initiating on the specified display.

Solution

If instead the monitor's name is supplied as a string, new sessions do indeed start on the specified monitor corresponding to the supplied string.

Configuration setting with string

Expected Behavior

The backend mechanism which supplies the user-inputted value from the Display ID field should either:

A - Use the Display ID rather than the Display Name
or
B - Have it's corresponding frontend input label and help text updated to accurately depict the fact that the Display Name is what's required here, rather than the current label/help text which describes using the Display ID.

Additional Context

No response

Host Operating System

Linux

Operating System Version

Arch Rolling - 7.0.3-arch1-2

Architecture

amd64/x86_64

Package

Linux - LizardByte/pacman-repo

GPU Type

AMD

GPU Model

AMD RX 6800xt

GPU Driver/Mesa Version

1:26.0.6-1

Capture Method

None

Apps

Log output

Online logs

No response

[Kishi85]

The problem here is that this value is dependent on the Capture Method used. This is especially confusing/inconsistent when using capture method auto detection. Also for some methods the numeric id value is not persistent hence the connector name (e.g. DP-1) is used instead (e.g. portalgrab/kwingrab).

I agree that the UI is misleading or rather out-dated here and needs to be updated but I've no idea on what the best thing to change this to would be. Internally the variable is just called output_name so maybe something like that? Documentation also needs some updates for this as that is likely also a bit dated (especially after recent changes for linux capture methods).