FLAC 2.1 plays as 3.0

[GoogleCodeExporter]

Describe the issue you're having:
Playing a 2.1 (L, R, LFE) file that has been converted to FLAC using eac3to 
plays as 3.0 (L, C, R) in LAV Audio, regardless of whether it's muxed into a 
container (such as Matroska) or not.

How can the issue be reproduced? Sample File?
I attached a sample file.

What version of the product are you using? In which Player?
LAV Splitter/Audio 0.55.3, Haali Media Splitter 1.11.288.0
Media Player Classic Home Cinema 1.6.6.6957 (3975d54)

Please provide any additional information below.
I remember that eac3to writes the WAVEFORMATEXTENSIBLE channel mask into the 
FLAC headers when creating a FLAC file.  Also, eac3to itself will recognize the 
resulting file as 2.1 when asked to analyze the FLAC.
I believe that LAV Audio is responsible for this behavior because the file 
plays as 3.0 when muxed into Matroska and using Haali Splitter as well.
Of course, I made sure that this is not just some quirk of LAV Audio and its 
Mixing capabilities, so I disabled all Options that would change the Channel 
Mapping when testing.

Original issue reported on code.google.com by TheDarkS...@googlemail.com on 31 Mar 2013 at 5:40

Attachments:

• 21as30.flac

[GoogleCodeExporter]

FLAC itself has no official way to directly signal a channel layout, and the 
FLAC spec specifies 3 channels to be L/R/C.

It may be possible to read the channel layout metadata from the FLAC file 
itself, however muxed in a container, this information would probably not 
survive, and Matroska has no way to specify a channel layout, either.

Original comment by h.lepp...@gmail.com on 31 Mar 2013 at 6:55