[pulseaudio-tickets] [PulseAudio] #691: provide real names in cards and connectors

[PulseAudio]

#691: provide real names in cards and connectors
--------------------------+-------------------------------------------------
  Reporter:  yelo3        |       Owner:  lennart
      Type:  enhancement  |      Status:  closed 
 Milestone:               |   Component:  core   
Resolution:  wontfix      |    Keywords:         
--------------------------+-------------------------------------------------

Comment(by lennart):

 Replying to [comment:7 yelo3]:
 > Thanks for your explanations[[BR]]
 >
 > 1) I mainly asked for the name to be shown, just because whenever a user
 has a problem with his card, he'll be able to know his card model when
 experts ask for it, without having to execute some strange commands on the
 terminal[[BR]]
 > You could add the model name in a tooltip or refactoring the treeview
 model. For example:
 >
 > {{{
 > Internal Audio (Intel HDA STAC9XX)
 > 1 Input/1 Output
 > Analog Stereo Duplex
 > }}}
 > Or
 > {{{
 > Internal Audio
 > Intel HDA STAC9XX
 > 1 Input/1 Output (Analog Stereo Duplex)
 > }}}
 > So you don't change the card name, but add only the model in the
 Hardware tab. This will help users with problems.
 > [[BR]][[BR]]

 I can tell you as upstream for PA that the device name might give a hint
 but is almost never sufficient for tracking down a problem. Almost always
 at least the output of "pacmd ls" or something like thatis necessary to
 track things down.

 Also, our primary objective when designing UIs is to make them simple and
 easy to use. If things are easy to debug, then this is certainly good too,
 but only as long as it doesn't conflict with our first goal. And I think
 in this case it does.

 > 2) I thought that Internal meant inside the computer (internal vs
 external). In this case "Internal" should be renamed to "Integrated"[[BR]]

 That is nitpicking.

 > [[BR]]
 > 3) I'm not asking to show the difference between front or rear mic. Just
 the difference between "internal microphone" and "external microphone
 plug". Is it possible to detect this?[[BR]]

 As mentioned, some drivers export that info, but I don't trust that
 labelling, since it is purely labelling, no physical differences, and
 vendors tend to solder things in weird ways.

 > [[BR]]
 > 3.1) If you can correctly distinguish the speakers connector, why don't
 you just use "analog speakers/headphones" instead of "analog output"?
 Users will better understead.[[BR]]

 I don't follow?

 > [[BR]]
 > 3.2) Is the word "alalog" really necessary in the output connectors? I
 know it's analog because I selected "analog duplex" in the hardware
 tab[[BR]]

 Yes, that is valid criticism. The reason why we add the prefix "Analog"
 there is that when we have both an analog and a digital port we need to
 distuingish that in the UI. Now almost always there is no digital port
 since digital ports are only really available in the spdif profiles. Which
 makes this kinda pontless indeed. Not sure how to fix this though, since
 that would require filtering common prefixes of all ports. Not sure I
 really want to do that.

 > [[BR]]
 >
 > Thanks for your support.

 Welcome!

-- 
Ticket URL: <http://pulseaudio.org/ticket/691#comment:8>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server