From: Gerd Hoffmann <kraxel@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org, "\"Kővágó, Zoltán\"" <dirty.ice.hu@gmail.com>
Subject: Re: [Qemu-devel] [PATCH 00/12] Audio backend cleanup
Date: Tue, 02 Jun 2015 11:28:56 +0200 [thread overview]
Message-ID: <1433237336.1637.28.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <556D7370.5020303@msgid.tls.msk.ru>
Hi,
> Yes, I use sdl audio with sdl ui, sdl1 version (since
> sdl2 had its shortcomings in qemu, not all functionality
> worked).
Does it work equally well with the gtk ui?
Possibly it makes sense to use keep sdl audio and default to it only in
case sdl ui is active (simliar to how spice audio is handled).
> I also tried alsa, oss and pa, with these audio was more
> distorted than with sdl. Sdl version sounds cleanly, while
> alsa and pa, at least in the past, and at least if memory
> serves me right, sounded like a if a good portion of noize
> has been mixed in with sound, or like when sound is with
> quick monmentary drops which happens at high frequency
> (maybe 200Hz).
Buffer overruns and underruns maybe? Possibly this is simply due to
different default values for sound buffer sizes.
> SDL audio has been the default in Debian for at least two
> debian releases because of that, we explicitly used
> --audio-drv-list=sdl,... to list sdl first. Now we have
> pa first, but I don't really remember why we changed it.
Useful data point. sdl state can't be that bad if it was default in
debian until recently ...
cheers,
Gerd
next prev parent reply other threads:[~2015-06-02 9:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 13:23 [Qemu-devel] [PATCH 00/12] Audio backend cleanup Kővágó, Zoltán
2015-06-01 13:23 ` [Qemu-devel] [PATCH 01/12] audio: remove esd backend Kővágó, Zoltán
2015-06-01 13:23 ` [Qemu-devel] [PATCH 02/12] audio: remove fmod backend Kővágó, Zoltán
2015-06-01 13:23 ` [Qemu-devel] [PATCH 03/12] audio: remove sdl backend Kővágó, Zoltán
2015-06-01 13:23 ` [Qemu-devel] [PATCH 04/12] audio: remove winwave audio driver Kővágó, Zoltán
2015-06-01 13:23 ` [Qemu-devel] [PATCH 05/12] audio: expose drv_opaque to init_out and init_in Kővágó, Zoltán
2015-06-02 7:56 ` Gerd Hoffmann
2015-06-02 10:03 ` Kővágó Zoltán
2015-06-02 15:24 ` Gerd Hoffmann
2015-06-01 13:23 ` [Qemu-devel] [PATCH 06/12] alsaaudio: do not use global variables Kővágó, Zoltán
2015-06-01 13:23 ` [Qemu-devel] [PATCH 07/12] paaudio: " Kővágó, Zoltán
2015-06-01 13:23 ` [Qemu-devel] [PATCH 08/12] ossaudio: " Kővágó, Zoltán
2015-06-01 13:23 ` [Qemu-devel] [PATCH 09/12] wavaudio: " Kővágó, Zoltán
2015-06-01 13:23 ` [Qemu-devel] [PATCH 10/12] dsoundaudio: " Kővágó, Zoltán
2015-06-01 13:23 ` [Qemu-devel] [PATCH 11/12] paaudio: fix possible resource leak Kővágó, Zoltán
2015-06-01 13:23 ` [Qemu-devel] [PATCH 12/12] coreaudio: do not use global variables where possible Kővágó, Zoltán
2015-06-01 13:38 ` [Qemu-devel] [PATCH 00/12] Audio backend cleanup Michael Tokarev
2015-06-01 13:48 ` Kővágó Zoltán
2015-06-02 8:08 ` Gerd Hoffmann
2015-06-02 9:12 ` Michael Tokarev
2015-06-02 9:28 ` Gerd Hoffmann [this message]
2015-06-02 10:33 ` Paolo Bonzini
2015-06-02 10:45 ` Peter Maydell
2015-06-02 11:40 ` Michael Tokarev
2015-06-02 12:42 ` François Revol
2015-06-02 15:28 ` Gerd Hoffmann
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=1433237336.1637.28.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=dirty.ice.hu@gmail.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).