Summary
When playing multichannel WAV or FLAC files, aplay ignores the
channel-layout metadata embedded in the file (WAV channel mask or FLAC
channel assignment). As a result, aplay always uses ALSA’s fallback
channel order (FL,FR,LFE,FC,RL,RR) unless the user manually specifies
--chmap.
This leads to incorrect channel routing (e.g., center/LFE swapped) even
when the file contains correct metadata describing the intended layout.
This appears to be a missing feature in aplay rather than an ALSA kernel
or alsa-lib issue, since ALSA’s design expects applications to interpret
metadata and call the chmap API accordingly.
Expected Behavior
When playing a WAV or FLAC file that contains channel-layout metadata:
- aplay should read the channel mask / channel assignment
- aplay should translate that metadata into an ALSA channel map
- aplay should call snd_pcm_set_chmap() automatically
- playback should follow the file’s intended channel order without
requiring the user to manually specify --chmap
Actual Behavior
- aplay ignores WAV channel masks
- aplay ignores FLAC channel layouts
- aplay does not call snd_pcm_set_chmap()
- aplay uses ALSA’s fallback order (FL,FR,LFE,FC,RL,RR)
- multichannel playback is incorrect unless the user manually provides
--chmap=FL,FR,FC,LFE,RL,RR (or another appropriate map)
Why This Matters
Most modern multichannel formats (WAV, FLAC, Blu-ray PCM, Dolby, DTS,
ffmpeg, etc.) use the standard 5.1 order:
FL, FR, FC, LFE, RL, RR
Since aplay does not use metadata, it produces incorrect output on any
system where the ALSA fallback order differs from the file’s intended
order.
This behavior is surprising to users and inconsistent with ALSA’s own
expectation that applications should interpret metadata and set the
channel map explicitly.
Reproduction
- Use any 5.1 WAV or FLAC file with correct channel metadata.
- Play with:
aplay -D hw: file.wav
- Observe incorrect channel routing (e.g., center and LFE swapped).
- Play again with:
aplay -D hw: --chmap=FL,FR,FC,LFE,RL,RR file.wav
- Playback is now correct.
Request
Please consider adding metadata parsing to aplay so that it:
- reads WAV channel masks
- reads FLAC channel layouts
- automatically sets the correct ALSA channel map
This would align aplay with ALSA’s documented expectation that
applications handle metadata and would greatly improve multichannel
playback correctness and usability.
Thank you for your time and consideration.
Summary
When playing multichannel WAV or FLAC files, aplay ignores the
channel-layout metadata embedded in the file (WAV channel mask or FLAC
channel assignment). As a result, aplay always uses ALSA’s fallback
channel order (FL,FR,LFE,FC,RL,RR) unless the user manually specifies
--chmap.
This leads to incorrect channel routing (e.g., center/LFE swapped) even
when the file contains correct metadata describing the intended layout.
This appears to be a missing feature in aplay rather than an ALSA kernel
or alsa-lib issue, since ALSA’s design expects applications to interpret
metadata and call the chmap API accordingly.
Expected Behavior
When playing a WAV or FLAC file that contains channel-layout metadata:
requiring the user to manually specify --chmap
Actual Behavior
--chmap=FL,FR,FC,LFE,RL,RR (or another appropriate map)
Why This Matters
Most modern multichannel formats (WAV, FLAC, Blu-ray PCM, Dolby, DTS,
ffmpeg, etc.) use the standard 5.1 order:
FL, FR, FC, LFE, RL, RR
Since aplay does not use metadata, it produces incorrect output on any
system where the ALSA fallback order differs from the file’s intended
order.
This behavior is surprising to users and inconsistent with ALSA’s own
expectation that applications should interpret metadata and set the
channel map explicitly.
Reproduction
aplay -D hw: file.wav
aplay -D hw: --chmap=FL,FR,FC,LFE,RL,RR file.wav
Request
Please consider adding metadata parsing to aplay so that it:
This would align aplay with ALSA’s documented expectation that
applications handle metadata and would greatly improve multichannel
playback correctness and usability.
Thank you for your time and consideration.