All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: External PCM plugin SDK
Date: Thu, 10 Feb 2005 19:30:52 +0100	[thread overview]
Message-ID: <s5hvf90z2qr.wl@alsa2.suse.de> (raw)
In-Reply-To: <s5hwttgz36p.wl@alsa2.suse.de>

At Thu, 10 Feb 2005 19:21:18 +0100,
I wrote:
> 
> At Thu, 10 Feb 2005 19:06:01 +0100,
> Marcel Holtmann wrote:
> > 
> > Hi Takashi,
> > 
> > > > > > > > Problem now is that XMMS closes the device and re-opens it when changing
> > > > > > > > the track and even when switching to its next track. This is problematic
> > > > > > > > when using Bluetooth, because I need to keep the underlaying connection
> > > > > > > > alive. Any idea?
> > > > > > > 
> > > > > > > Yeah, that's bad behavior of xmms.
> > > > > > > I'll try a hack later...
> > > > > > 
> > > > > > Another way is that I implement somekind of keep alive mechanism inside
> > > > > > the plugin, but what I have seen so far is that it is directly unloaded
> > > > > > when it is no longer used. So the 1:1 mapping of open/close is not a
> > > > > > good thing and maybe there should be some keep alive and reset inside
> > > > > > the ALSA library to help here out.
> > > > > 
> > > > > The delayed close in the plugin is of course good to have.
> > > > > My only concern is that the code would be complicated to handle
> > > > > races.
> > > > 
> > > > actually I see a lifetime race inside the plugin if I try to handle it
> > > > by myself. When the close() callback is called, I must free all of my
> > > > allocated resources, because the shared object will be unloaded, right?
> > > 
> > > Yes, the close callback should clean up everything since there is no
> > > distinction between close and unload, so far.
> > 
> > if the ALSA core is not handling the XMMS behaviour for us, I really
> > need something to distinguish between close and unload.
> > 
> > What do you think about doing it like with kernel modules? Means we add
> > an init and an exit entry point inside the plugin. The rest is done via
> > callbacks. With this we should be able to register a PCM and also the
> > mixer controls for it within the same plugin.
> 
> That's a good idea.

... and doesn't work as it is, unfortunately :-<

dlcose() is called after snd_pcm_close().
We may need to build object caches in alsa-lib.
This will improve the perfomance eventually, too.


Takashi


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-02-10 18:30 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08 21:30 External PCM plugin SDK Takashi Iwai
2005-02-09 14:14 ` Marcel Holtmann
2005-02-09 14:20   ` Takashi Iwai
2005-02-09 14:37     ` Marcel Holtmann
2005-02-09 15:19       ` Takashi Iwai
2005-02-09 17:27         ` Marcel Holtmann
2005-02-09 17:32           ` Takashi Iwai
2005-02-09 17:48             ` Marcel Holtmann
2005-02-10 11:51               ` Takashi Iwai
2005-02-10 12:29                 ` Marcel Holtmann
2005-02-10 17:29                   ` Takashi Iwai
     [not found]                     ` <1108057507.15974.97.camel@pegasus>
2005-02-10 17:51                       ` Takashi Iwai
2005-02-10 18:06                         ` Marcel Holtmann
2005-02-10 18:21                           ` Takashi Iwai
2005-02-10 18:30                             ` Takashi Iwai [this message]
2005-02-10 19:04                               ` Marcel Holtmann
2005-02-11 10:50                                 ` Takashi Iwai
2005-02-11 12:15                                   ` Marcel Holtmann
2005-02-11 13:28                                     ` Takashi Iwai
2005-02-11 17:26                                       ` Takashi Iwai
2005-02-12  2:18                                         ` Marcel Holtmann
2005-02-14 15:33                                           ` Takashi Iwai
2005-02-09 17:38         ` Thierry Vignaud
2005-02-09 17:35           ` Takashi Iwai
2005-02-09 15:25     ` Jaroslav Kysela
2005-02-09 15:39       ` Takashi Iwai
2005-02-09 17:36   ` Thierry Vignaud
2005-02-09 17:38     ` Marcel Holtmann
2005-02-09 15:28 ` Alexander E. Patrakov
2005-02-09 15:29   ` Takashi Iwai
2005-02-09 17:40 ` Thierry Vignaud

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=s5hvf90z2qr.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.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 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.