All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <ossman@cendio.se>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org, mzcbylcnhqvb@0pointer.de
Subject: Re: [RFC][PATCH] Transparent network support through polypaudio
Date: Tue, 14 Feb 2006 11:35:26 +0100	[thread overview]
Message-ID: <43F1B26E.5@cendio.se> (raw)
In-Reply-To: <20060214094741.GA8943@turing.informatik.uni-halle.de>

Clemens Ladisch wrote:
> Pierre Ossman wrote:
> 
>>I've implemented an ALSA plugin that allows any well-behaved ALSA 
>>application transparently use the Polypaudio network protocol.
>>
>>It is my desire to have this included in ALSA (-lib preferably) so that 
>>it will be included in most dists.
> 
> 
> It's dependent on polypaudio, so it should better go into the
> alsa-plugins package.
> 

I suppose. Then it's just the matter of getting that packaged into the 
dists (fedora doesn't).

> 
>>Since some applications do not use these in a sane manner
> 
> 
> Nothing in the ALSA API requires applications to use poll() (or to use
> blocking writes).
> 
> 
>>(I'm looking at you mplayer)
> 
> 
> And you're speaking with mplayer's ALSA driver maintainer.
> Is there anything wrong with mplayer?  ;-)
> 

Technically no. It's just that it does things in way that makes my life 
more difficult. :)

Btw, mplayer seems to call snd_pcm_prepare() twice. Not sure if that's 
valid behaviour.

> 
>>the mainloop abstraction is also run on most of the ALSA plugin
>>callbacks.
> 
> 
> When an applicatioh disables the stop_threshold, the device is supposed
> to continue playing with the current buffer contents (which _is_ a
> rather extreme case).
> 

The ring buffer design is very difficult to emulate when you have a 
simple queue. Since few (if any) application will rely on this 
behaviour, I've decided to ignore it for now.

> I think you may be required to use a timer for the mainloop.  What does
> polypaudio actually do in this callback?  How often must it be called?
> 

Primarily updates to available buffer space on the server. As for how 
often, I don't really know. Once every period would be a safe guess.

A timer wouldn't be that easy to implement. I want to avoid putting more 
stuff in another thread since the current solution allows me to avoid locks.

Rgds
-- 
Pierre Ossman                Telephone: +46-13-21 46 00
Cendio AB                    Web: http://www.cendio.com


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642

  reply	other threads:[~2006-02-14 10:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-13 14:53 [RFC][PATCH] Transparent network support through polypaudio Pierre Ossman
2006-02-14  9:47 ` Clemens Ladisch
2006-02-14 10:35   ` Pierre Ossman [this message]
2006-02-14 14:35     ` Clemens Ladisch
2006-02-14 15:48       ` Pierre Ossman
2006-02-14 20:24   ` latency issue with mplayer ALSA plugin Thierry Vignaud
2006-02-15  9:30     ` Clemens Ladisch
2006-03-01  4:09   ` [RFC][PATCH] Transparent network support through polypaudio Lee Revell
2006-03-01  8:32     ` Clemens Ladisch
2006-03-01 17:00       ` Lee Revell
2006-03-07 14:01   ` Pierre Ossman
2006-02-15  9:44 ` Pierre Ossman
2006-02-17 19:05 ` Pierre Ossman
2006-02-21 16:15   ` Takashi Iwai
2006-02-21 16:38     ` Pierre Ossman
2006-02-21 16:41       ` Takashi Iwai
2006-02-22  9:48         ` Pierre Ossman
2006-02-22 15:41           ` Takashi Iwai
2006-02-23 13:02             ` Pierre Ossman
2006-02-23 14:34               ` Takashi Iwai
2006-02-24 13:22                 ` Pierre Ossman
2006-02-24 13:57                   ` Takashi Iwai
2006-02-24 14:03                     ` Pierre Ossman
2006-02-27  8:09                 ` Pierre Ossman
2006-02-27 19:22                   ` Takashi Iwai
2006-02-28  8:11                     ` Pierre Ossman

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=43F1B26E.5@cendio.se \
    --to=ossman@cendio.se \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=mzcbylcnhqvb@0pointer.de \
    /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.