From: Takashi Iwai <tiwai@suse.de>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Peer Chen <pchen@nvidia.com>, Marek Vasut <marek.vasut@gmail.com>,
Wei Ni <wni@nvidia.com>,
alsa-devel@alsa-project.org, Alan Alan <alanwww1@gmail.com>
Subject: Re: ALSA patch Nvidia 8 channel hdmi audio
Date: Fri, 05 Jun 2009 07:40:58 +0200 [thread overview]
Message-ID: <s5hbpp31bmd.wl%tiwai@suse.de> (raw)
In-Reply-To: <20090605042829.GA14167@localhost>
At Fri, 5 Jun 2009 12:28:29 +0800,
Wu Fengguang wrote:
>
> On Thu, Jun 04, 2009 at 08:29:25AM +0200, Takashi Iwai wrote:
> > At Thu, 4 Jun 2009 14:05:52 +0800,
> > Wei Ni wrote:
> > >
> > > Yes, my test wav file is from Windows.
> > >
> > > I had used different player to test with my test wav file.
> > > The mplayer has no mapping problem, but other players map channels
> > > wrong.
> > > As you said, it seems that is caused by the difference of the ALSA and
> > > Windows.
> >
> > I guess mplayer corrects the channel mapping automatically.
> >
> > > Unfortunately, our nvidia codec doesn't support channel-slot assignment
> > > yet.
> >
> > OK.
> >
> > > How could we fix this problems, do you have any suggestions?
> >
> > It's a bit difficult issue right now. Usually we could "fix" the
> > channel mapping in alsa-lib configuration. But, HD-audio has currently
> > a single alsa-lib configuration, and others may use the right channel
> > mapping.
> >
> > I don't remember how is the case of Intel HDMI... Can anyone check?
>
> The codecs I tested - G35/G45/GM45 - does not support the channel-slot
> assignment. I guess future hardwares may support that.
OK, and the channel assignment is also FL/FR/C/LFE/RL/RR, right?
thanks,
Takashi
next prev parent reply other threads:[~2009-06-05 5:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <410e92830906021458x3d47a1d6jebba8bbe1150e76d@mail.gmail.com>
2009-06-02 22:22 ` ALSA patch Nvidia 8 channel hdmi audio Marek Vasut
[not found] ` <410e92830906021530l767478c4tae72c4b161583b6@mail.gmail.com>
2009-06-03 0:00 ` Marek Vasut
2009-06-03 7:14 ` Wei Ni
2009-06-03 7:22 ` Clemens Ladisch
2009-06-03 7:45 ` Takashi Iwai
2009-06-03 8:00 ` Alan Alan
2009-06-03 8:14 ` Takashi Iwai
2009-06-03 9:34 ` Alan Alan
2009-06-03 9:50 ` Takashi Iwai
2009-06-03 23:28 ` Alan Alan
2009-06-03 23:38 ` Takashi Iwai
[not found] ` <410e92830906032318v4ed6987cr41c8f73a8a54a9e6@mail.gmail.com>
2009-06-04 6:33 ` Takashi Iwai
2009-06-04 6:39 ` Wei Ni
2009-06-04 6:50 ` Takashi Iwai
2009-06-04 23:20 ` Alan Alan
2009-06-05 2:38 ` Wei Ni
2009-06-07 21:43 ` Alan Alan
2009-06-08 5:20 ` Takashi Iwai
2009-06-06 9:13 ` Takashi Iwai
2009-06-03 10:25 ` Wei Ni
2009-06-03 11:02 ` Takashi Iwai
2009-06-04 6:05 ` Wei Ni
2009-06-04 6:29 ` Takashi Iwai
2009-06-05 4:28 ` Wu Fengguang
2009-06-05 5:40 ` Takashi Iwai [this message]
2009-06-05 6:14 ` Wu Fengguang
2009-06-03 11:07 ` Alan Alan
2009-07-01 4:47 Pau Rodriguez-Estivill
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=s5hbpp31bmd.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alanwww1@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=fengguang.wu@intel.com \
--cc=marek.vasut@gmail.com \
--cc=pchen@nvidia.com \
--cc=wni@nvidia.com \
/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