On Sat, 2012-05-12 at 12:52 +0200, Kurt Roeckx wrote: > On Sun, Apr 15, 2012 at 07:17:34PM +0300, Uoti Urpala wrote: > > This is expected behavior with ALSA dmix. It has a fixed hardware output > > frequency, in your case 48000 Hz. > > As far as I know this is just a default and has nothing at all to > do with what the hardware supports, it's just a value in a config > file.
I meant it's fixed for each dmix instance; when ALSA dmix is using a hardware frequency of 48000 Hz, everything will be resampled to that. You can configure dmix to use a different frequency, but it won't adapt based on source audio. > I know all this. That doesn't mean things can't be improved. Well, it certainly sounded like you didn't know all this; if you did, I can't see why you wrote "The problem now is that mplayer does this in libao2/ao_alsa.c:" in the original message, or reported this against mplayer2 at all (in addition to libasound2). What could be improved in mplayer2? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org