From: Clemens Ladisch <clemens@ladisch.de>
To: Srinivasan S <srinivasan.s@tataelxsi.co.in>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-audio-dev@lists.linuxaudio.org"
<linux-audio-dev@lists.linuxaudio.org>
Subject: Re: Using loopback card to Connect GSM two way call to the real sound card UDA1345TS
Date: Mon, 09 Mar 2015 09:09:16 +0100 [thread overview]
Message-ID: <54FD552C.7020902@ladisch.de> (raw)
In-Reply-To: <1425878360800.70892@tataelxsi.co.in>
Srinivasan S wrote:
> Could you please provide any inputs w.r.t the loopback card using
> snd-aloop & alsaloop, how this loopback card can be used to connect
> the GSM two way call simultanoeusly to the UDA1345TS codec on MCASP0
> of the am335x (UDA1345TS ie., real sound card)
snd-aloop creates a virtual sound card; it is not used with a real sound
card.
> The codec has two output channels VOUTL, VOUTR & two input channels VINL , VINR
>
> With this am able to achieve only one way call at a time by running
> only one application at a time
To allow a capture device to be shared, you need to use dsnoop. Your
asound.conf already does this.
To allow a playback device to be shared, you need to use dshare or dmix.
(dshare allows to use _different_ channels; dmix allows mixing multiple
sources into the same channels.) Your asound.conf does not do this; it
uses "hw" instead.
Regards,
Clemens
next prev parent reply other threads:[~2015-03-09 8:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1425878251963.1340@tataelxsi.co.in>
2015-03-09 5:18 ` Using loopback card to Connect GSM two way call to the real sound card UDA1345TS Srinivasan S
2015-03-09 8:09 ` Clemens Ladisch [this message]
[not found] ` <1425922601141.50130@tataelxsi.co.in>
[not found] ` <1425964490006.15084@tataelxsi.co.in>
[not found] ` <1425964490006.15084-Ig93jE4/MIihbFNETrL9Qw@public.gmane.org>
2015-03-10 10:50 ` [LAD] Fw: [alsa-devel] " Clemens Ladisch
2015-03-28 2:43 ` Fw: " Srinivasan S
2015-03-30 11:40 ` Fw: " Srinivasan S
2015-04-01 8:38 ` Srinivasan S
[not found] ` <1427510661706.37789-Ig93jE4/MIihbFNETrL9Qw@public.gmane.org>
2015-04-02 9:43 ` [LAD] [alsa-devel] " Clemens Ladisch
2015-04-02 10:36 ` Srinivasan S
2015-04-02 15:08 ` Clemens Ladisch
2015-04-22 6:11 ` Srinivasan S
2015-04-24 6:26 ` Srinivasan S
2015-04-24 6:26 ` Srinivasan S
[not found] ` <1429683117651.11394-Ig93jE4/MIihbFNETrL9Qw@public.gmane.org>
2015-04-24 8:06 ` [LAD] [alsa-devel] " Clemens Ladisch
2015-04-24 12:05 ` Srinivasan S
[not found] ` <1429877130444.23317-Ig93jE4/MIihbFNETrL9Qw@public.gmane.org>
2015-04-24 12:45 ` [LAD] [alsa-devel] " Clemens Ladisch
2015-05-29 11:20 ` Srinivasan S
2015-06-01 6:01 ` Srinivasan S
[not found] ` <HKXPR04MB277B58064C140058C37487EC3B60-T1ls2vrYf5VLAZUorM51PQfhPeD8jYilXA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2015-06-01 14:39 ` [LAD] [alsa-devel] " Clemens Ladisch
2015-06-03 6:05 ` Srinivasan S
[not found] ` <SIXPR04MB2530654AB664B2CE19B4665C3A80@SIXPR04MB253.apcprd04.prod.outlook.com>
2015-07-01 7:34 ` Srinivasan S
[not found] ` <SIXPR04MB2531DB716093D09C156BEA0C3A80-gTWnircbfuxAKSrPHYfF6gfhPeD8jYilXA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2015-07-01 14:11 ` [LAD] [alsa-devel] " Clemens Ladisch
2015-07-08 15:25 ` Srinivasan S
2015-07-09 5:25 ` Srinivasan S
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=54FD552C.7020902@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-audio-dev@lists.linuxaudio.org \
--cc=srinivasan.s@tataelxsi.co.in \
/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;
as well as URLs for NNTP newsgroup(s).