public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Anssi Hannula <anssi.hannula@iki.fi>
To: Raymond Yau <superquad.vortex2@gmail.com>
Cc: lukasz.wojnilowicz@gmail.com, tiwai@suse.de,
	ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: Fwd: Front speakers doesn't work in multichannel output, regression in ALC888
Date: Thu, 14 May 2015 10:45:30 +0300	[thread overview]
Message-ID: <5554529A.4040202@iki.fi> (raw)
In-Reply-To: <CAN8ccibM+PoboaTXoHqg=dCbe-3+ijQZ6xL_Q1J=H9ovZ8gzkQ@mail.gmail.com>

14.05.2015, 09:26, Raymond Yau kirjoitti:
>>>> I started MS Windows and without externals speakers plugged in I
>>>
>>> could test
>>>  > 5.1 configuration and it seemed that sound was coming from
>>> different directions.
>>>
>>>  >
>>>  > What I managed to determine:
>>>  > I've got 3 stacks:
>>>  > 1 ST: Headphone, Line-out (FL and FR), SPDIF
>>>  > 2 ST: Microphone, Line-out (CLFE)
>>>  > 3 ST: Line-in, Line-out (RL and RR)
>>>  >
>>>  > I've got 5 responsive output pins
>>>  > PIN 0x14: Internal FL FR
>>>  > PIN 0x15: External FL FR
>>>  > PIN 0x17: Internal LFE
>>>  > PIN 0x18: External CLFE
>>>  > PIN 0x1a: External RL RR
>>>  >
>>>  > How can we make it work with these information?
> 
> speaker-test -Dhw:0,0 -c6 -t wav
>  
>>>
>>>
>>>
> https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/plain/Documentation/sound/alsa/Channel-Mapping-API.txt
>>> [1]
>>>
>>> seem chnmap type _FIXED , _VAR and _PAIRED does not fit when LFE and
>>> FC can be swapped for internal speaker and external speaker
>>
>>
>> Right, you can't do it with a single map of one of those types.
> 
> http://git.alsa-project.org/?p=alsa-utils.git&a=search&h=HEAD&st=commit&s=chmap
> 
> do chmap of internal speakers need {FL FR RL RR LFE NA} ?

>From above it looks like there are 3 internal speakers, so I guess e.g.
{FL FR LFE NA} might be in order (or just {FL FR LFE} if 3-channel
playback is supported).

> http://git.alsa-project.org/?p=alsa-lib.git&a=search&h=HEAD&st=commit&s=chmap
> 
> as set_chmap() still not yet implemented in pcm_route.c
> 
> do speaker-test need to specify channel map when using those odd number
> channels ?
> 
> speaker-test -D surround21  -c3 -t wav
> speaker-test -D surround41  -c5 -t wav -mFL,FR,RL,RR,LFE
> speaker-test -D surround50  -c5 -t wav

Well, the driver should provide the correct chmap.

> http://git.alsa-project.org/?p=alsa-utils.git;a=commitdiff;h=7b14c00b56784f69ecc954a2de36e0a058fc8849;hp=000bf230cfb3b0abe88d27701dd77982675126ec
> 
> this example seem not working
> 
> speaker-test -c2 -t wav -Dplug:front -mFR,FL

You are getting an error?
If so, that is expected if the underlying device does not support the
wanted channel map.

>>
>>
>>>
> https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda?id=0fb87bb474f978446786263deff6263284e6e011
>>> [2]
>>>
>>> How do the driver implement channel map when codec has  swap
>>> center/lfe switch ?
>>>
>>> Do chmap contain both {FL FR RL RR FC LFE} and {FL FR RL RR LFE FC} ?
>>
>>
>> If you want to provide support for userspace doing it both ways, then
> yes, you need those two _FIXED maps.
> 
> Can chmap contain two _FIXED maps of same number of channels ?

Sure.

-- 
Anssi Hannula

  reply	other threads:[~2015-05-14  7:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-02  5:42 Front speakers doesn't work in multichannel output, regression in ALC888 Łukasz Wojniłowicz
2015-05-02  8:05 ` Takashi Iwai
2015-05-02  9:36 ` Raymond Yau
     [not found]   ` <7993879.9dprRWFvNQ@luklap.workgroup>
2015-05-03  7:53     ` [alsa-devel] " Raymond Yau
     [not found] ` <29807127.PULdKhJLmi@luklap.workgroup>
2015-05-06 18:23   ` Raymond Yau
     [not found]     ` <1736431.dmQFUpE69t@luklap.workgroup>
2015-05-08  6:49       ` [alsa-devel] " Raymond Yau
     [not found]   ` <CAN8cciapcbygVjS20+Ln6aDJbd3poieo6-8Zq3x69brsqr+Raw@mail.gmail.com>
     [not found]     ` <4324603.tPLEjaP5mH@luklap.workgroup>
2015-05-05 16:47       ` Raymond Yau
     [not found]         ` <4678913.FpDgrA5u1d@luklap.workgroup>
2015-05-11  2:34           ` Raymond Yau
     [not found]             ` <CAN8cciZS8MhXWy5anxMSgtLdDYHQtURXJ2iEoL0YMpb41EifHg@mail.gmail.com>
     [not found]               ` <d3bbb31411796d9f835396d30dcaa309@mail.onse.fi>
2015-05-14  6:26                 ` Fwd: " Raymond Yau
2015-05-14  7:45                   ` Anssi Hannula [this message]
2015-05-17  1:49                     ` Raymond Yau
2015-05-09  6:00       ` [alsa-devel] " Raymond Yau
2015-06-07 12:44 ` Raymond Yau
     [not found] ` <8386507.uauZCcniqC@luklap.workgroup>
     [not found]   ` <CAN8cciaTZYOQAkaE2aquzcZ_a1QkJAz7u+ff2ceTyrXnKr50RQ@mail.gmail.com>
     [not found]     ` <5853893.pVbPai8A2z@luklap.workgroup>
2015-06-09  2:23       ` Fwd: " Raymond Yau
     [not found]       ` <CAN8ccib5rgh2UjNG9isbAkTgMM7MhwL+FMxdd-4Z79Qng5hRNA@mail.gmail.com>
     [not found]         ` <CAN8cciY=bSpebNXqzYc+Q+MDd9Gr3+KGnpS0GBQpES+-XTY0Dw@mail.gmail.com>
2015-06-09  4:03           ` Fwd: " Raymond Yau
     [not found]             ` <31911886.6mcodbBrA7@luklap.workgroup>
2015-07-11  1:18               ` Raymond Yau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5554529A.4040202@iki.fi \
    --to=anssi.hannula@iki.fi \
    --cc=alsa-devel@alsa-project.org \
    --cc=lukasz.wojnilowicz@gmail.com \
    --cc=superquad.vortex2@gmail.com \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox