Re: [pulseaudio-tickets] [PulseAudio] #626: Some nvidia hdmis now supports more than 2 channels

2009-08-15 Thread PulseAudio
#626: Some nvidia hdmis now supports more than 2 channels
-+--
  Reporter:  howl|   Owner:  lennart  
  Type:  defect  |  Status:  new  
 Milestone:  |   Component:  module-alsa-*
Resolution:  |Keywords:   
-+--

Comment(by howl):

 Could not be mapped to a defaul channel-map = front-left,front-right,rear-
 left,rear-right,front-center,lfe,side-left,side-right like the analog 7.1?
 following the same rule analog 5.1 or 7.1 should be automapped as some
 cards can have switched the center and lfe analog channels.

 Mine is using the default or at least the more used mapping, could be
 interesting to know what combination is the most used by hdmi manufactures
 and use it by default.

 This is the mapping I have done as should be usable for all the nvidia
 hdmis, if people with 8-ch amd or intel hdmis can test if it works with
 them I thinks that this could be the default mapping.

 [Mapping hdmi-surround-71]
 description = Digital Surround 7.1 (HDMI)
 device-strings = hdmi:%f
 channel-map = front-left,front-right,rear-left,rear-right,front-center,lfe
 ,side-left,side-right
 priority = 6
 direction = output

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets


Re: [pulseaudio-tickets] [PulseAudio] #626: Some nvidia hdmis now supports more than 2 channels

2009-08-15 Thread PulseAudio
#626: Some nvidia hdmis now supports more than 2 channels
-+--
  Reporter:  howl|   Owner:  lennart  
  Type:  defect  |  Status:  new  
 Milestone:  |   Component:  module-alsa-*
Resolution:  |Keywords:   
-+--

Comment(by howl):

 Sorry I writed the code wrong:
 {{{
 [Mapping hdmi-surround-71]
 description = Digital Surround 7.1 (HDMI)
 device-strings = hdmi:%f
 channel-map = front-left,front-right,rear-left,rear-right,front-center,lfe
 ,side-left,side-right
 priority = 6
 direction = output
 }}}

 I put the description to match the other outputs because without it in the
 profile selector hdmi-surround-71 is shown instead.

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets


Re: [pulseaudio-tickets] [PulseAudio] #619: Autodetection always shows one device per sound card but sometimes could have more tha one

2009-08-15 Thread PulseAudio
#619: Autodetection always shows one device per sound card but sometimes could
have more tha one
--+-
  Reporter:  howl |   Owner:  lennart  
  Type:  enhancement  |  Status:  reopened 
 Milestone:   |   Component:  module-hal-detect
Resolution:   |Keywords:   
--+-

Comment(by howl):

 I have been messing arround with /usr/share/pulseaudio/alsa-mixer/profile-
 sets/default.conf and yes, it's very easy to configure multiple i/o per
 card, but, while doing it I was thinking another way to do it.

 When someone have the possibility to have multiple outputs at the same
 time usually someone wants to use this feature of his/her sound card and
 when someone have a sound card that have some outputs or inputs that
 cannot be at the same time it's more likely that he or she is going to use
 only one and are not going to be switching between the outputs.

 So, what about to list the user all the inputs and outputs available
 detected by pulseaudio, and let the user, with a checkbox per i/o to
 enable or disable what he or she wants. I think that this can solve the
 issue and also make much cleaner the configuration tab of pulseaudio's
 volume control.

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets


Re: [pulseaudio-tickets] [PulseAudio] #619: Autodetection always shows one device per sound card but sometimes could have more tha one

2009-08-15 Thread PulseAudio
#619: Autodetection always shows one device per sound card but sometimes could
have more tha one
--+-
  Reporter:  howl |   Owner:  lennart  
  Type:  enhancement  |  Status:  reopened 
 Milestone:   |   Component:  module-hal-detect
Resolution:   |Keywords:   
--+-

Comment(by howl):

 Also some cases like the analog outputs for the same card (stereo, 4.0,
 4.1, 5.0, 5.1...) can be shown with a radiobutton to select the desired
 channels setup and all of the controlled by a global checkbox that enables
 or disables the analog output.

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets


Re: [pulseaudio-tickets] [PulseAudio] #619: Autodetection always shows one device per sound card but sometimes could have more tha one

2009-08-15 Thread PulseAudio
#619: Autodetection always shows one device per sound card but sometimes could
have more tha one
--+-
  Reporter:  howl |   Owner:  lennart  
  Type:  enhancement  |  Status:  reopened 
 Milestone:   |   Component:  module-hal-detect
Resolution:   |Keywords:   
--+-

Comment(by lennart):

 First, I doubt that driving SPDIF and analog out at the same time is
 really a much needed feature. I mean, really, how many ears do you have?
 4? I am pretty sure some people do want to make sure of that, but I doubt
 it's a non-trivial number.

 Now, the big problem here is that we cannot auto detect whether spdif and
 analog are exclsuive to each other or not. Currently we try every
 combinatin of input and output and if it works add it to our list of
 working profiles. However, if we change this logic to also test every
 combination of analog out and spdif out then we have a problem: we cannot
 distuingish the case where the card supports hw mixing but only one output
 at a time and where the card supports two simultaneous and independant
 outputs. That means on some hardware we'd expose a profile "spdif out +
 analog out" which would actuallly mix and output to one, or to both
 outputs. And we certainly don't want to expose that.

 So, as mentioned, the alsa enumeration API is just too simple. It does not
 include information about which devices of a card can be used together and
 which devices cannot.

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets


Re: [pulseaudio-tickets] [PulseAudio] #626: Some nvidia hdmis now supports more than 2 channels

2009-08-15 Thread PulseAudio
#626: Some nvidia hdmis now supports more than 2 channels
-+--
  Reporter:  howl|   Owner:  lennart  
  Type:  defect  |  Status:  new  
 Milestone:  |   Component:  module-alsa-*
Resolution:  |Keywords:   
-+--

Comment(by lennart):

 For analog, ALSA provides device strings like "surround51:xx" which can be
 used to imply a very specific channel order. However, there is only one
 "hdmi:" device string which does not imply any channel order. HDMI on
 the hw level is very flexible in the selection of channel maps.  For every
 number of channels it supports a number of different number of maps --
 which is negotiated between the PC and the hdmi receiver.

 If we'd add a 'default' mapping for multichannel here then this might work
 for you, but won't work people with dfferent hardware.

 To support this properly we need to wait until ALSA introduces a proper
 channel map negotiation API, or at least hdmi device strings that imply a
 channel order (i.e. 'hdmi-surround51:' or something like that. But it
 doesn't do that right now.

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets