Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jonas Holmberg <jonashg@axis.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: route and chmap
Date: Fri, 27 Mar 2020 17:23:36 +0100	[thread overview]
Message-ID: <s5h5zepeph3.wl-tiwai@suse.de> (raw)
In-Reply-To: <20200327155013.GA593298@axis.com>

On Fri, 27 Mar 2020 16:50:13 +0100,
Jonas Holmberg wrote:
> 
> CC Takashi.
> 
> On Thu, Mar 26, 2020 at 02:41:11PM +0100, Jonas Holmberg wrote:
> > Hi,
> > I use the route plugin to copy mono to both FL and FR (front left and 
> > front right stereo) of the slave during playback. When get_chmap() is 
> > called in the route plugin it will call get_chmap() of the slave, 
> > which returns 2 channels with FL and FR positions, and then route 
> > itself returns 1 channel with FL position. But the application that 
> > called snd_pcm_get_chmap() on the playback device expected to get 
> > position MONO instead of FL since the number of channels is 1.
> > 
> > Is the application wrong in not accepting the chmap or should the 
> > route plugin have changed position from FL to MONO? Is it possible to 
> > add something to the config (asound.conf) to make FL become MONO in 
> > the reply of get_chmap() or solve the problem in any other way?

Well, that's a small missing piece in the route plugin
implementation.  It may have a capability to translate the destination
channel map, e.g. by extending the config syntax.

If anyone has a patch proposal, I'm willing to apply :)


thanks,

Takashi

      reply	other threads:[~2020-03-27 16:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 13:41 route and chmap Jonas Holmberg
2020-03-27 15:50 ` Jonas Holmberg
2020-03-27 16:23   ` Takashi Iwai [this message]

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=s5h5zepeph3.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=jonashg@axis.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