diff options
| author | wm4 <wm4@nowhere> | 2015-06-21 18:32:38 +0200 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2015-06-21 18:32:38 +0200 |
| commit | 872b19dfcb56a19fcfed13509cef833db07653f6 (patch) | |
| tree | 4983ea2d05e294cbbe97ca53923b731a66e3ed5f /player | |
| parent | dbbac7b3e18495faf137b3e7546676f947b48983 (diff) | |
| download | mpv-872b19dfcb56a19fcfed13509cef833db07653f6.tar.bz2 mpv-872b19dfcb56a19fcfed13509cef833db07653f6.tar.xz | |
ao_alsa: fix a log message
So apparently, this essentially happens when the kernel driver doesn't
implement write accesses in the channel map control. Which doesn't
necessarily mean that the channel map is unsupported, or that there is a
bug - it's just lazyness and a consequence of the terrible ALSA kernel
API for the channel mapping stuff.
In these cases, the channel count implicitly selects the channel map,
and snd_pcm_set_chmap() always fails with ENXIO.
I'm actually not sure what happens if dmix is on top of e.g. HDMI, which
actually lets you change the channel mapping.
I'm also not sure why commit d20e24e5d1614354e9c8195ed0b11fe089c489e4
(alsa-lib git repository) does not take care of this.
Diffstat (limited to 'player')
0 files changed, 0 insertions, 0 deletions