All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Måns Rullgård" <mru@inprovide.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: [Fwd: Re: [MPlayer-dev-eng] AV out of sync with "-ao alsa" in gmplayer, mplayer works ok]
Date: Wed, 29 Dec 2004 11:19:12 +0100	[thread overview]
Message-ID: <yw1x1xd976fz.fsf@inprovide.com> (raw)
In-Reply-To: 1104311474.2984.2.camel@krustophenia.net

Lee Revell <rlrevell@joe-job.com> writes:

> OK, I trolled the mplayer dev list, and got this response. ;-)
>
> Are Reimar's statements about memory leaks valid?

No.  I regularly run my player under valgrind, and it reports no ALSA
related leaks.  I also run the same player for weeks on end, and the
memory usage stays below 4MB, after opening, playing a bit, and
closing the sound device thousands of times.

> Hi,
> On Tue, Dec 28, 2004 at 10:55:33PM -0500, Lee Revell wrote:
>> Using 1.0pre6, "gmplayer -ao alsa" results in the sound and video being
>> out of sync.  "mplayer -ao alsa" works fine, as does "-ao oss" with
>> either mplayer or gmplayer.
>
> Are you sure this isn't caused either by different settings in gmplayer
> or because the computer is too slow? Please provide a full -v log.
>
>> This is quite annoying, as I was expecting to FINALLY have a gmplayer
>> release usable with ALSA.  Previous versions were unusable due to that
>> stupid "/dev/mixer" bug.
>> 
>> What's the deal?  Why is it so hard for the mplayer developers to get
>> ALSA support right?  I hack on ALSA a lot, so if there is some problem
>> with the ALSA API, we would like to hear about it on the mailing list.
>
> Yes, please fix the huge memory leak with ALSA output,

Never seen that one.  Could be a leak in mplayer's ALSA support, of
course.

> especially when changing the volume (it is cause by the call to
> snd_mixer_load, but I couldn't find an ALSA function that frees that
> memory again snd_mixer_free has absolutely no effect :-( ).  Also
> the problem is more that the Gui is not well supported.
>
>> Or do you all just use OSS still?
>
> The OSS interface is actually a lot nicer, so yes it is supported better.

LOL

>> From the users perspective things like this make ALSA look bad, while
>> the problem is really with gmplayer's shoddy ALSA support.
>
>>From what I saw of ALSA as a developer it is bad, but that's a bit of
> personal opinion of course. What I refer to is very slow software

Who said what here?

> mixing, no way to use it without getting into synchronization hell
> because it uses threads,

Oh, never forget that the mplayer folks hate threads.

> hundreds of function calls to initialize it, and those memory leaks
> that to my best knowledge seem to come from the alsa lib (my best
> guess is that this is because like in conf.c, in _snd_config_make
> pointers are overwritten without being freed first).  What makes it
> a bit difficult to use it that it's quite difficult to find the
> function that is supposed to free things again, they e.g.  often
> aren't located directly below the allocation function in the
> headers, and that there is a snd_mixer_load function but no
> snd_mixer_unload as I would expect it.

OK, the documentation could be better.

> All these things together made me give up on ALSA.

I'll skip the insult this time.

-- 
Måns Rullgård
mru@inprovide.com



-------------------------------------------------------
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://productguide.itmanagersjournal.com/

  reply	other threads:[~2004-12-29 10:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-29  9:11 [Fwd: Re: [MPlayer-dev-eng] AV out of sync with "-ao alsa" in gmplayer, mplayer works ok] Lee Revell
2004-12-29 10:19 ` Måns Rullgård [this message]
2004-12-29 10:25   ` Lee Revell
2005-01-13 15:10   ` Reimar Döffinger
2005-01-13 20:11     ` Lee Revell
2005-01-18 20:23       ` Reimar Döffinger
2005-01-19  9:35         ` Takashi Iwai

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=yw1x1xd976fz.fsf@inprovide.com \
    --to=mru@inprovide.com \
    --cc=alsa-devel@lists.sourceforge.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.