All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Thierry Vignaud <tvignaud@mandrakesoft.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: why do elements disappear?
Date: Wed, 16 Feb 2005 13:12:41 +0100	[thread overview]
Message-ID: <s5h8y5obt52.wl@alsa2.suse.de> (raw)
In-Reply-To: <m2ekfgpur7.fsf@vador.mandrakesoft.com>

At Wed, 16 Feb 2005 13:14:04 +0100,
Thierry Vignaud wrote:
> 
> Takashi Iwai <tiwai@suse.de> writes:
> 
> > > > > a mixer app of mine (you know, one of those controlling
> > > > > volumes) is updating itself (if other apps change settings) by
> > > > > continuously running get-volume (et al) on all mixer elements
> > > > > every once in a while (10Hz).
> > > > 
> > > > Well, this isn't a good idea.  You should do update passively via
> > > > poll().  The exception is a control with VOLATILE flag like VU
> > > > meter, which won't send change notification.  But normal controls
> > > > send notification if the value is changed, or the control is
> > > > created/deleted, so that the app can react.
> > > 
> > > is this the same bug that affects totem?
> > > 
> > > see totem's gdb trace at
> > > http://qa.mandrakesoft.com/show_bug.cgi?id=13045 and xine strace at
> > > http://qa.mandrakesoft.com/show_bug.cgi?id=13449
> > > (http://qa.mandrakesoft.com/attachment.cgi?id=2444)
> > 
> > They are slightly different problems.  I guess it's indeed a bug of
> > alsa-lib, which was fixed recently on CVS.
> 
> could you point to the relevant fix?
> 

alsa-lib/src/mixer/mixer.c:

	revision 1.70
	date: 2005/02/04 19:18:49;  author: tiwai;  state: Exp;  lines: +2 -2
	Summary: Use bag_for_each_safe() for event handling loop

	Use bag_for_each_safe() for event handling loop.
	Event callbacks may be destructive.


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-16 12:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-15 21:12 why do elements disappear? Ronald S. Bultje
2005-02-16 10:42 ` Takashi Iwai
     [not found]   ` <m2r7jgpvw9.fsf@vador.mandrakesoft.com>
2005-02-16 11:52     ` Takashi Iwai
2005-02-16 12:14       ` Thierry Vignaud
2005-02-16 12:12         ` Takashi Iwai [this message]
2005-02-16 12:31           ` Thierry Vignaud
2005-03-03  8:57   ` Ronald S. Bultje
2005-03-03  9:17     ` Jaroslav Kysela
2005-03-03 12:25       ` Ronald S. Bultje
2005-03-04  9:15     ` Giuliano Pochini

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=s5h8y5obt52.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=tvignaud@mandrakesoft.com \
    /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.