From: Hans-Kristian Arntzen <maister@archlinux.us>
To: alsa-devel@alsa-project.org
Subject: Re: redirecting audio to another desktop machine
Date: Mon, 21 Jun 2010 12:51:12 +0200 [thread overview]
Message-ID: <4C1F4420.3060904@archlinux.us> (raw)
In-Reply-To: <mailman.1.1277114401.21597.alsa-devel@alsa-project.org>
On 06/21/2010 12:00 PM, alsa-devel-request@alsa-project.org wrote:
> Date: Mon, 21 Jun 2010 14:57:00 +0530
> From: Viral Mehta<Viral.Mehta@lntinfotech.com>
> Subject: [alsa-devel] redirecting audio to another desktop machine
> To: "alsa-devel@alsa-project.org"<alsa-devel@alsa-project.org>
> Message-ID:
> <70376CA23424B34D86F1C7DE6B9973430254343B3E@VSHINMSMBX01.vshodc.lntinfotech.com>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi list,
>
> I have an embedded device running linux kernel and a minimal filesystem.
>
> I want to access this device remotely which means I should be able to connect to the device just like we do Remote Desktop over ethernet.
> I am able to do this. I am able to send key-event and framebuffer data whenever my desktop machine connects to the device.
>
> But, I am not able to send audio data on remote side.
> I am really not sure which device file (/dev/snd/ ???) I should read and capture the data and should send across....
> Or can I read the playback device ? I think NO.
> Do I need to create some kind of virtual sound device ?
>
> Any pointers/suggestions are appreciated.
>
> Thanks,
> Viral
>
>
>
If you want to reroute an ALSA application over the network, you can use
output plugins. Afaik, both PulseAudio and RSound provides plugins for
this. You generally want to set up a virtual device in .asoundrc or
similar.
-- Hans-Kristian Arntzen
next parent reply other threads:[~2010-06-21 10:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1277114401.21597.alsa-devel@alsa-project.org>
2010-06-21 10:51 ` Hans-Kristian Arntzen [this message]
2010-06-21 12:10 ` redirecting audio to another desktop machine Viral Mehta
2010-06-21 13:51 ` Hans-Kristian Arntzen
2010-06-25 8:53 ` Viral Mehta
2010-06-25 9:34 ` Colin Guthrie
2010-06-25 10:26 ` Hans-Kristian Arntzen
[not found] <70376CA23424B34D86F1C7DE6B9973430254343B29@VSHINMSMBX01.vshodc.lntinfotech.com>
[not found] ` <70376CA23424B34D86F1C7DE6B9973430254343B2B@VSHINMSMBX01.vshodc.lntinfotech.com>
2010-06-21 9:27 ` Viral Mehta
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=4C1F4420.3060904@archlinux.us \
--to=maister@archlinux.us \
--cc=alsa-devel@alsa-project.org \
/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