Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lennart Poettering <mznyfn@0pointer.de>
To: Jaroslav Kysela <perex@perex.cz>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: Disable conversions
Date: Sat, 22 Dec 2007 23:37:01 +0100	[thread overview]
Message-ID: <20071222223701.GB13486@tango.0pointer.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0711261638320.24363@tm8103.perex-int.cz>

On Mon, 26.11.07 16:55, Jaroslav Kysela (perex@perex.cz) wrote:

> 1) Proposal - one argument specifying multiple disabled conversions:
> 
>    plughw:CARD=0,DEV=0,DISABLECONV=cfr
> 
>    c = channels
>    f = format
>    r = rate
> 
>    And add 'disableconv' to pcm/pcm_plug.c configuration parser.

Works for me. However, abbreviating things too brutally doesn't seem
like a good idea, I'd thus vote for your proposal #2:

> 2) Proposal - multiple arguments
> 
>    plughw:CARD=0,DEV=0,DISABLECHANNELS=1,DISABLERATE=1,DISABLEFORMAT=1
> 
> I prefer first proposal (I don't think that it will be widely used), but I 
> have no objections for second, too.
> 
> This can be applied to plug: device as well.

It would be great if something like this would be available. I am
happy with either, as long as I can make use of it!

Lennart

-- 
Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net         ICQ# 11060553
http://0pointer.net/lennart/           GnuPG 0x1A015CC4

  reply	other threads:[~2007-12-22 22:37 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20  0:51 [lennart@poettering.net: Status of ALSA "simple" mixer interface] Lennart Poettering
2007-11-21 11:09 ` Takashi Iwai
2007-11-21 11:11 ` Takashi Iwai
2007-11-21 15:23   ` Clemens Ladisch
2007-11-25 19:56     ` The sense or non-sense of the device listing API (was: Status of ALSA "simple" mixer interface]) Lennart Poettering
2007-11-25 20:38       ` Jaroslav Kysela
2007-11-21 11:14 ` Mono device definition Takashi Iwai
2007-11-21 11:20 ` Analog-SPDIF dup Takashi Iwai
2007-11-21 11:22 ` Softvol controls Takashi Iwai
2007-11-29 23:28   ` Lennart Poettering
2007-11-29 23:46     ` John Utz
2007-11-30  0:08       ` Lennart Poettering
2007-11-30  0:34         ` John Utz
2007-11-30  8:59     ` Takashi Iwai
2007-12-04 15:42       ` Jaroslav Kysela
2007-12-13 10:39         ` Takashi Iwai
2007-12-22 22:54         ` Lennart Poettering
2007-12-23 10:21           ` Jaroslav Kysela
2007-12-22 22:48       ` Lennart Poettering
2007-11-21 11:40 ` Disable conversions Takashi Iwai
2007-11-21 14:29   ` Takashi Iwai
2007-11-21 15:16     ` Jaroslav Kysela
2007-11-21 14:51       ` Takashi Iwai
2007-11-25 20:41   ` Lennart Poettering
2007-11-26 15:55     ` Jaroslav Kysela
2007-12-22 22:37       ` Lennart Poettering [this message]
2007-11-21 11:42 ` Channel mapping Takashi Iwai
2007-11-21 15:17   ` Clemens Ladisch
2007-11-21 14:57     ` Takashi Iwai
2007-11-21 15:27     ` Jaroslav Kysela
2007-11-21 15:04       ` Takashi Iwai
2007-11-27 16:54         ` Takashi Iwai
2007-11-21 15:52       ` Clemens Ladisch
2007-11-21 15:36         ` Takashi Iwai
2007-11-21 18:37           ` Jaroslav Kysela
2007-11-22  9:17             ` Clemens Ladisch
2007-11-22  8:55           ` Clemens Ladisch

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=20071222223701.GB13486@tango.0pointer.de \
    --to=mznyfn@0pointer.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@perex.cz \
    /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