[pulseaudio-tickets] [PulseAudio] #618: Separate Input and Output profile selection

[PulseAudio]

#618: Separate Input and Output profile selection
--------------------------+-------------------------------------------------
  Reporter:  howl         |       Owner:  lennart      
      Type:  enhancement  |      Status:  closed       
 Milestone:               |   Component:  module-alsa-*
Resolution:  wontfix      |    Keywords:               
--------------------------+-------------------------------------------------

Comment(by coling):

 Well we automatically probe for all the possible combinations and only
 present the user with the ones that work together.

 Obviously this probing cannot know how a chipset is physically wired up
 but if the system lets us open both both input and output in the way we've
 requested then it'll be presented as an option to the user.

 For example on my laptop I'm offered IEX958 options but there are no
 physical ports on my machine to plug into this! It seems to work fine, but
 it's the equiv of piping to /dev/null.

 There is quite literally no way for us to detect this and IMO providing an
 editor interface is not going to help.

 While I'm no expert I would have thought that an optical connector would
 have had no problem with full duplex but hey ho.

 If a user has to configure things before auto-detection work, then there
 really is no point in having auto-detection at all! Either make it work
 automatically or give configuration options - you can't really do both
 without creating numerous support problems.

 In the latest versions (git master) of pulseaudio and pavucontrol there
 are also output "ports" that define which port a given input/output is
 wired up to which may go some way to solving the problem you refer to:
 http://colin.guthr.ie/2009/06/configuring-audio-ports-in-pulseaudio/

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