alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: Olof <olof@baah.se>
Cc: alsa-devel@alsa-project.org
Subject: Re: Information request - writing a driver for a virtual soundcard
Date: Wed, 18 Aug 2010 22:00:37 +0200	[thread overview]
Message-ID: <20100818200037.GN17833@buzzloop.caiaq.de> (raw)
In-Reply-To: <AANLkTimkXD-LMULa4vdMHMSw7Q2aLjHZTuEgm2ts7fYs@mail.gmail.com>

On Wed, Aug 18, 2010 at 09:44:05PM +0200, Olof wrote:
> > I still don't understand where the actual audio material has its origin,
> > or where it should be sent to, respectively.
> 
> Origin is anything the user would choose to play on a "normal" system.
> Pure sound from CD, mp3, ogg, wma played with xmmls, totem movie
> player etc. Any application used to play sound on a Linux box. The PCM
> stream would be compressed and transmitted over TCP/IP to the
> smartphone which would play it on its output.

Jup. You can easily do that by capturing the PulseAudio master monitor
and do whatever you like with the data inside your PulseAudio client.

Another option - in case you have full control over the code running on
the smart phone - is to make the phone act as PulseAudio network
service, so multiple other network members could send audio to it, or
receive audio from it. With or without authentication, compressed or
uncompressed and all that, depending on your implementation.

Daniel

      reply	other threads:[~2010-08-18 20:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18 17:53 Information request - writing a driver for a virtual soundcard Olof
2010-08-18 19:15 ` Daniel Mack
     [not found]   ` <AANLkTi=EO295r9BpmR105gYLRsjFhG3_kiD81mHTSLKP@mail.gmail.com>
2010-08-18 19:33     ` Daniel Mack
2010-08-18 19:44       ` Olof
2010-08-18 20:00         ` Daniel Mack [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=20100818200037.GN17833@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=olof@baah.se \
    /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).