From: Takashi Iwai <tiwai@suse.de>
To: Juan Zapatero <jazc@gmvsistemas.es>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Use a plughw device inside the dmix plugin.
Date: Wed, 19 Apr 2006 13:33:54 +0200 [thread overview]
Message-ID: <s5hd5fdu7dp.wl%tiwai@suse.de> (raw)
In-Reply-To: <1145445860.9402.1.camel@jazc.fedora>
At Wed, 19 Apr 2006 13:24:20 +0200,
Juan Zapatero wrote:
>
> By doing so, I would not be able to use dmixing...
> The problem is that capture must be configured in 1 channel, and
> playback in two, but, 1 channel setup can only be made through plughw.
Then I don't understand your requirment at all...
You just want to wrap plug over dmix for channel shrink/expansion?
Takashi
> El mié, 19-04-2006 a las 13:19 +0200, Takashi Iwai escribió:
> > At Wed, 19 Apr 2006 12:53:18 +0200,
> > Juan Zapatero wrote:
> > >
> > > I am using a VoIP application which uses different devices for capturing
> > > and playback, because some audio processing is needed between audio
> > > reception and playback. I have configured my default to use dmix plugin,
> > > because it is required to be able to play different audio streams at
> > > once. I can force the capture device to use 'default' plugin, but the
> > > playback device only works under plughw. So, is there a way to use a
> > > plughw device inside the dmix plugin?
> >
> > You can override the definition of plughw, such as
> >
> > pcm.!plughw "default"
> >
> > But, fixing the app would be a better option, of course.
> >
> >
> > Takashi
>
>
> ______________________
> Este mensaje, y en su caso, cualquier fichero anexo al mismo,
> puede contener informacion clasificada por su emisor como confidencial
> en el marco de su Sistema de Gestion de Seguridad de la
> Informacion siendo para uso exclusivo del destinatario, quedando
> prohibida su divulgacion copia o distribucion a terceros sin la
> autorizacion expresa del remitente. Si Vd. ha recibido este mensaje
> erroneamente, se ruega lo notifique al remitente y proceda a su borrado.
> Gracias por su colaboracion.
> ______________________
> This message including any attachments may contain confidential
> information, according to our Information Security Management System,
> and intended solely for a specific individual to whom they are addressed.
> Any unauthorised copy, disclosure or distribution of this message
> is strictly forbidden. If you have received this transmission in error,
> please notify the sender immediately and delete it.
> ______________________
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
>
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
next prev parent reply other threads:[~2006-04-19 11:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 10:53 Use a plughw device inside the dmix plugin Juan Zapatero
2006-04-19 11:19 ` Takashi Iwai
2006-04-19 11:24 ` Juan Zapatero
2006-04-19 11:33 ` Takashi Iwai [this message]
2006-04-19 11:39 ` Juan Zapatero
2006-04-19 11:46 ` Takashi Iwai
2006-04-19 11:51 ` Juan Zapatero
2006-04-19 12:36 ` Takashi Iwai
2006-04-20 7:54 ` Juan Zapatero
2006-04-20 10:21 ` Takashi Iwai
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=s5hd5fdu7dp.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=jazc@gmvsistemas.es \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.