[FFmpeg-trac] #4426(undetermined:closed): RIFF WAVE 24-bit WAVE_FORMAT_PCM files are not properly supported

[FFmpeg]

#4426: RIFF WAVE 24-bit WAVE_FORMAT_PCM files are not properly supported
-------------------------------------+-------------------------------------
             Reporter:  rsn10100     |                    Owner:
                 Type:  defect       |                   Status:  closed
             Priority:  normal       |                Component:
              Version:  unspecified  |  undetermined
             Keywords:  wav          |               Resolution:  invalid
  WAVEFORMATEX WAVE_FORMAT_PCM       |               Blocked By:
  output 24bit                       |  Reproduced by developer:  0
             Blocking:               |
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Changes (by rsn10100):

 * keywords:  wav => wav WAVEFORMATEX WAVE_FORMAT_PCM output 24bit
 * component:  ffmpeg => undetermined


Comment:

 Ok, so the format picks its own default value when one is not specified?
 That's new information to me.

 Well, you're right about WAVEFORMATEX.  It is WAVEFORMATEX that does not
 support anything other then 8 or 16 bits.  However, PCMWAVEFORMAT still
 does and is supported even though the structure has been superseded by
 WAVEFORMATEX.

 https://msdn.microsoft.com/en-us/library/dd743663(v=vs.85).aspx

 All wav files still using PCMWAVEFORMAT are still valid and supported with
 any number of channels in Windows and many applications.  I believe
 PCMWAVEFORMAT should be the default PCM integer format for wav files when
 the number of channels is 1 or 2 regardless of the number of sample bits
 in the stream.  You may disagree, but 24 years of files and software
 written in this way makes it an issue of backward compatibility.  I see no
 reason that 1 and 2 channel 24-bit and 32-bit WAVE_FORMAT_PCM files can't
 be written using PCMWAVEFORMAT as they have been for more than 20 years.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/4426#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker