From: Alban Peignier <alban@tryphon.eu>
To: alsa-devel@alsa-project.org
Subject: Looking for ideas to solve ruby alsa duplex problem
Date: Sat, 30 Oct 2010 12:19:33 +0200 [thread overview]
Message-ID: <4CCBF135.9030507@tryphon.eu> (raw)
Hi alsa guys,
We're working on a ruby binding for alsa :
http://projects.tryphon.eu/ruby-alsa/. PCM Playback and Capture are
supported for a long time (and used in production for several months).
Ruby developers can find the gem on http://rubygems.org/gems/ruby-alsa.
But we're trying to investigate a problem with "duplex mode" :
http://projects.tryphon.eu/ruby-alsa/ticket/4. We can't find a way to
record and playback simple stereo streams in the same process without
dummy hackings :-/ We don't need an extreme latency, just a simple
process to add/receive streams on network (our LinkStream/LinkBox project).
I hopes it's only a misusage of the ALSA API or a mistake in
hardware/software configurations. But after several weeks on this
problem, we need fresh ideas :)
Even if you have no idea about ruby, the Playback [0] and Capture [1]
are very simple wrappers around the native ALSA API [2] (mapped with
ruby ffi [3]). The alsa device is opened and configured using a shared
open method in Stream [4]. Very few code in fact.
I hope an expert eye will find a beginning of solution ;)
Kind regards,
0. http://projects.tryphon.eu/ruby-alsa/browser/lib/alsa/pcm/playback.rb
1. http://projects.tryphon.eu/ruby-alsa/browser/lib/alsa/pcm/capture.rb
2. http://projects.tryphon.eu/ruby-alsa/browser/lib/alsa/pcm/native.rb
3. http://github.com/ffi/ffi
4. http://projects.tryphon.eu/ruby-alsa/browser/lib/alsa/pcm/stream.rb
--
Alban Peignier - alban@tryphon.eu
Tryphon : Radio, Web and Free Software
http://www.tryphon.eu
reply other threads:[~2010-10-30 10:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4CCBF135.9030507@tryphon.eu \
--to=alban@tryphon.eu \
--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;
as well as URLs for NNTP newsgroup(s).