All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pieter Palmers <pieterp@joow.be>
To: Clemens Ladisch <cladisch@fastmail.net>
Cc: Andrea Guzzo <xant@xant.net>,
	linux1394-devel@lists.sourceforge.net,
	Stefan Richter <stefanr@s5r6.in-berlin.de>,
	alsa-devel@lists.sourceforge.net
Subject: Re: alsa userspace interface
Date: Mon, 19 Mar 2007 12:36:29 +0100	[thread overview]
Message-ID: <45FE75BD.8040101@joow.be> (raw)
In-Reply-To: <1174298934.28822.1180148355@webmail.messagingengine.com>

Clemens Ladisch wrote:
> Andrea Guzzo wrote:
>> we are wondering if it's possible to register an alsa device from
>> userspace.
> 
> It is not possible to register a kernel device from userspace, but it is
> possible to write a plugin that is used by the alsa library like a
> kernel device.
> 
> Have a look into the alsa-plugins package.
Might I raise the documentation issue here? Last time I checked (1.0.9) 
it was very difficult to understand what exactly was going on.

Glancing at the current alsa-lib-plugins I see that there are some new 
ones that might help.

> 
>> Is there any working or experimental one?
> 
> The FreeBoB project is writing an ALSA plugin for some IEEE1394 devices.


We could implement iSight support in our framework, it wouldn't be that 
much work I guess. The only issue could be that we have a more pro-audio 
point of view. However it is probably beneficial to both parties to use 
FreeBoB, as we have tried to make device support as easy as possible, 
abstracting everything related to audio API's and FireWire. If you know 
the device & the framework, implementing support is a matter of days.

Note however that unless somebody starts to help out, the FreeBoB ALSA 
plugin might take some time.

One major issue with userspace audio drivers is that stock/distro 
kernels are not good enough to make it work reliably with acceptable 
latencies (we're talking a videoconferencing device here). Having to 
install a RT kernel is IMHO only justifiable for (dedicated) 'audio' 
boxes, and should not be something that is required for 
videoconferencing. And if you would want to use them on stock kernels, 
you need a way to get SCHED_FIFO as an ordinary user, which again is not 
available on stock distro's.

Pieter
FreeBoB

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

      reply	other threads:[~2007-03-19 11:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-18  2:10 alsa userspace interface Andrea Guzzo
2007-03-19 10:08 ` Clemens Ladisch
2007-03-19 11:36   ` Pieter Palmers [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=45FE75BD.8040101@joow.be \
    --to=pieterp@joow.be \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=cladisch@fastmail.net \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=xant@xant.net \
    /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.