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 21:33:54 +0200 [thread overview]
Message-ID: <20100818193354.GM17833@buzzloop.caiaq.de> (raw)
In-Reply-To: <AANLkTi=EO295r9BpmR105gYLRsjFhG3_kiD81mHTSLKP@mail.gmail.com>
(please never remove any people from the list of recipients when
replying, and please do not top-post)
On Wed, Aug 18, 2010 at 09:27:36PM +0200, Olof wrote:
> I want to connect my smartphone to my amplifier and then use it as a
> virtual soundcard. The actual sound data shall be transmitted over
> wireless TCP/IP from my laptop to the smartphone, enabling me to move
> around in the flat without wiring.
I still don't understand where the actual audio material has its origin,
or where it should be sent to, respectively.
> Thought a virtual soundcard was a
> good idea since it the whole system then would be independent of
> application playing sound on the laptop. I intended to do the
> compressing & transmission in user space, but perhaps everything can
> be done in user space? I wasn't aware of the possibility. Where can I
> read more?
I think the easiest API to access your existing sound cards and to
create virtual sinks and sources is offered by PulseAudio:
http://pulseaudio.org/wiki/DeveloperDocumentation
In case your distribution uses PulseAudio natively, you souldn't even
need to set up anything.
HTH,
Daniel
next prev parent reply other threads:[~2010-08-18 19:33 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 [this message]
2010-08-18 19:44 ` Olof
2010-08-18 20:00 ` Daniel Mack
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=20100818193354.GM17833@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 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.