[FFmpeg-trac] #5941(avformat:closed): Dolby E corrupted when remuxed

FFmpeg trac at avcodec.org
Sun Nov 20 18:13:55 EET 2016

#5941: Dolby E corrupted when remuxed
             Reporter:  leoenc      |                    Owner:
                 Type:  defect      |                   Status:  closed
             Priority:  normal      |                Component:  avformat
              Version:  git-master  |               Resolution:  wontfix
             Keywords:  wav         |               Blocked By:
             Blocking:              |  Reproduced by developer:  0
Analyzed by developer:  0           |
Changes (by cehoyos):

 * keywords:   => wav
 * resolution:   => wontfix
 * status:  new => closed
 * component:  undetermined => avformat
 * version:  unspecified => git-master


 Replying to [comment:20 leoenc]:
 > I'm not sure about the float part, but I was told by the Dolby vendor
 that the waveformatextensible structure is not required for storing Dolby
 E as it is encoded in 2 channels, 24-bit and no channel mask data is
 But your vendor isn't Microsoft, the company that defined the wav format
 decades ago and - iirc - requires waveformatextensible if bps > 16?
 There is a major bug in the software you use to read the wav files, it
 does not support waveformatextensible. Or is this a hardware decoder that
 does not read these files? How are the files sent to the hardware decoder?

 > I've tested many Dolby E files which came from the same source as my
 sample. The files were properly identified and decoded in pro Dolby
 hardware. MediaInfo also identified them properly, so I think it's safe to
 assume that the sample that I've provided is the correct way to store
 Dolby E.

 Note that FFmpeg does not claim to support Dolby E - on the contrary,
 sadly! Your command line requests to mux pcm_s24 into wav.

 Until Dobly E gets supported, this will not be fixed afaict, several very
 similar requests were refused in the past because we don't want to write
 invalid wav files.

Ticket URL: <https://trac.ffmpeg.org/ticket/5941#comment:21>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker

More information about the FFmpeg-trac mailing list