[plasma-pa] [Bug 459493] Multi-device view is visually overwhelming
https://bugs.kde.org/show_bug.cgi?id=459493 --- Comment #9 from KING --- (In reply to KING from comment #8) > (In reply to KING from comment #7) > > (In reply to Nate Graham from comment #6) > > > If only we had it as easy as they have it. :) We have to deal with all > > > sorts > > > of weird hardware that exposes its audio hardware in weird ways, with > > > manufacturers that provide stupid technical gibberish for their device > > > names > > > instead of user-comprehensible text. > > > > Yes, I can imagine, but the Mac displays the monitors the same way "KDE > > Display configuration" does. in my case "C27F..." and for the microphone, > > Mac presents it as RODE USB. > > > > Also, the Mac knows the built-in devices from the external and mention > > (MacBook Pro speaker/Mic or something like that). I think that can be done > > too > > > > > Are those monitors actively connected? If not, that's a clear bug we can > > > fix. If so, I guess we should try to map the monitor's device to a better > > > name for it. But be aware that the monitor names that come from > > > manufacturers often aren't any better than the names that audio devices > > > have. > > > > The monitors are connected and they are identical monitors, same brand, same > > model. > > > > > An easy fix might be to get rid of the device name entirely, so that we > > > don't have weird long technical mumbo-jumbo in parentheses). > > Until then, is there a way to manually configure a friendly name for the > > devices without hacking into the kernel :D? > > When I run `hwinfo command, I found that there is a readable field can be > used, which is "Model" > > ``` > Hardware Class: monitor > Model: "SAMSUNG C27F591" > > Hardware Class: sound > Model: "RODE Microphones RODE NT-USB" > ``` Here is an example of the command ``` ❯ hwinfo --monitor --short monitor: SAMSUNG C27F591 SAMSUNG C27F591 CMN LCD Monitor ❯ hwinfo --sound --short sound: Intel Comet Lake PCH cAVS nVidia Audio device RODE Microphones RODE NT-USB ``` -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 459493] Multi-device view is visually overwhelming
https://bugs.kde.org/show_bug.cgi?id=459493 --- Comment #8 from KING --- (In reply to KING from comment #7) > (In reply to Nate Graham from comment #6) > > If only we had it as easy as they have it. :) We have to deal with all sorts > > of weird hardware that exposes its audio hardware in weird ways, with > > manufacturers that provide stupid technical gibberish for their device names > > instead of user-comprehensible text. > > Yes, I can imagine, but the Mac displays the monitors the same way "KDE > Display configuration" does. in my case "C27F..." and for the microphone, > Mac presents it as RODE USB. > > Also, the Mac knows the built-in devices from the external and mention > (MacBook Pro speaker/Mic or something like that). I think that can be done > too > > > Are those monitors actively connected? If not, that's a clear bug we can > > fix. If so, I guess we should try to map the monitor's device to a better > > name for it. But be aware that the monitor names that come from > > manufacturers often aren't any better than the names that audio devices > > have. > > The monitors are connected and they are identical monitors, same brand, same > model. > > > An easy fix might be to get rid of the device name entirely, so that we > > don't have weird long technical mumbo-jumbo in parentheses). > Until then, is there a way to manually configure a friendly name for the > devices without hacking into the kernel :D? When I run `hwinfo command, I found that there is a readable field can be used, which is "Model" ``` Hardware Class: monitor Model: "SAMSUNG C27F591" Hardware Class: sound Model: "RODE Microphones RODE NT-USB" ``` -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 459493] Multi-device view is visually overwhelming
https://bugs.kde.org/show_bug.cgi?id=459493 --- Comment #7 from KING --- (In reply to Nate Graham from comment #6) > If only we had it as easy as they have it. :) We have to deal with all sorts > of weird hardware that exposes its audio hardware in weird ways, with > manufacturers that provide stupid technical gibberish for their device names > instead of user-comprehensible text. Yes, I can imagine, but the Mac displays the monitors the same way "KDE Display configuration" does. in my case "C27F..." and for the microphone, Mac presents it as RODE USB. Also, the Mac knows the built-in devices from the external and mention (MacBook Pro speaker/Mic or something like that). I think that can be done too > Are those monitors actively connected? If not, that's a clear bug we can > fix. If so, I guess we should try to map the monitor's device to a better > name for it. But be aware that the monitor names that come from > manufacturers often aren't any better than the names that audio devices have. The monitors are connected and they are identical monitors, same brand, same model. > An easy fix might be to get rid of the device name entirely, so that we > don't have weird long technical mumbo-jumbo in parentheses). Until then, is there a way to manually configure a friendly name for the devices without hacking into the kernel :D? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 459493] Multi-device view is visually overwhelming
https://bugs.kde.org/show_bug.cgi?id=459493 Nate Graham changed: What|Removed |Added Keywords||usability Summary|Make the volume list easy |Multi-device view is |and intuitive |visually overwhelming CC||n...@kde.org --- Comment #6 from Nate Graham --- > If you have a look at the Mac volume setting, you don't need to figure it > out, input devices > are separate from output devices, and simple and short device names If only we had it as easy as they have it. :) We have to deal with all sorts of weird hardware that exposes its audio hardware in weird ways, with manufacturers that provide stupid technical gibberish for their device names instead of user-comprehensible text. > For example, two of these devices in the screenshot are just monitors(HDMI) > why I don't see just the monitors' names? Are those monitors actively connected? If not, that's a clear bug we can fix. If so, I guess we should try to map the monitor's device to a better name for it. But be aware that the monitor names that come from manufacturers often aren't any better than the names that audio devices have. An easy fix might be to get rid of the device name entirely, so that we don't have weird long technical mumbo-jumbo in parentheses). -- You are receiving this mail because: You are watching all bug changes.
