Error processing WAV audio file

[Paul Butcher]

Summary of the bug:
WAV files that have worked fine for years as input to ffmpeg are now failing with latest version with following error:
% [wav @ 0003cee0] too big INFO subchunk
% input.wav: Invalid data found when processing input

This is with ffmpeg version N-45279-g1a104bf
Worked fine up to ffmpeg version N-35057-g2c44aed which is the last version I was using before upgrading.

How to reproduce:
% ffmpeg -i input.wav -ab 96k out.mp3

If you need a small sample WAV file let me know. (WAV file produced by Ashampoo Burning Studio as rip from audio CD)

[Carl Eugen Hoyos]

Please provide complete, uncut console output of your failing command line together with the failing command line and please provide a sample.

[Paul Butcher]

7zip of short (30sec) wav file from Ashampoo Burning Studio

[Paul Butcher]

Full console dump from ffmpeg with attached wav file as input:

$ /c/dev/audio/ffmpeg-20121010-git-1a104bf-win32-shared/bin/ffmpeg -i input.wav
 -ab 96k output.mp3
ffmpeg version N-45279-g1a104bf Copyright (c) 2000-2012 the FFmpeg developers
  built on Oct 10 2012 19:21:13 with gcc 4.7.2 (GCC)
  configuration: --disable-static --enable-shared --enable-gpl --enable-version3
 --disable-pthreads --enable-runtime-cpudetect --enable-avisynth --enable-bzlib
--enable-frei0r --enable-libass --enable-libcelt --enable-libopencore-amrnb --en
able-libopencore-amrwb --enable-libfreetype --enable-libgsm --enable-libmp3lame
--enable-libnut --enable-libopenjpeg --enable-librtmp --enable-libschroedinger -
-enable-libspeex --enable-libtheora --enable-libutvideo --enable-libvo-aacenc --
enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libx264 --enab
le-libxavs --enable-libxvid --enable-zlib
  libavutil      51. 74.100 / 51. 74.100
  libavcodec     54. 65.100 / 54. 65.100
  libavformat    54. 31.100 / 54. 31.100
  libavdevice    54.  3.100 / 54.  3.100
  libavfilter     3. 19.102 /  3. 19.102
  libswscale      2.  1.101 /  2.  1.101
  libswresample   0. 16.100 /  0. 16.100
  libpostproc    52.  1.100 / 52.  1.100
[wav @ 00032a20] too big INFO subchunk
input.wav: Invalid data found when processing input

[Carl Eugen Hoyos]

(The sample can be tested with mplayer -softvol -softvol-max 700 -volume 100)

Regression since 12bc205 / 1e19927

[Elon Musk]

Replying to cehoyos:

(The sample can be tested with mplayer -softvol -softvol-max 700 -volume 100)

Regression since 12bc205 / 1e19927

Not really, it was introduced recently.

problems:
1st: creator of this files puts INFO chunk id at end (instead of start of file).
2nd: size of INFO chunks ids are not word aligned - and any other info on web states it should be word aligned, like how it is done in avi.

[Carl Eugen Hoyos]

Replying to richardpl:

Replying to cehoyos:

Regression since 12bc205 / 1e19927

Not really, it was introduced recently.

Could you elaborate?

[Elon Musk]

Regression was not introduced in such commits you mentioned.
Tag reading in wav was added recently.

[Carl Eugen Hoyos]

$ ffmpeg -i input.wav
ffmpeg version N-35243-gca55606, Copyright (c) 2000-2011 the FFmpeg developers
  built on Oct 18 2012 00:10:13 with gcc 4.7.1 20120723 [gcc-4_7-branch revision 189773]
  configuration:
  libavutil    51. 29. 1 / 51. 29. 1
  libavcodec   53. 38. 1 / 53. 38. 1
  libavformat  53. 22. 0 / 53. 22. 0
  libavdevice  53.  4. 0 / 53.  4. 0
  libavfilter   2. 50. 0 /  2. 50. 0
  libswscale    2.  1. 0 /  2.  1. 0
[wav @ 0x2ae37e0] parser not found for codec pcm_s16le, packets or times may be invalid.
[wav @ 0x2ae37e0] max_analyze_duration 5000000 reached at 5015510
Input #0, wav, from 'input.wav':
  Duration: 00:00:30.42, bitrate: 1411 kb/s
    Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 44100 Hz, 2 channels, s16, 1411 kb/s
At least one output file must be specified

$ ffmpeg -i input.wav
ffmpeg version N-35255-g1e19927, Copyright (c) 2000-2011 the FFmpeg developers
  built on Oct 18 2012 00:08:35 with gcc 4.7.1 20120723 [gcc-4_7-branch revision 189773]
  configuration:
  libavutil    51. 29. 1 / 51. 29. 1
  libavcodec   53. 38. 1 / 53. 38. 1
  libavformat  53. 22. 0 / 53. 22. 0
  libavdevice  53.  4. 0 / 53.  4. 0
  libavfilter   2. 50. 0 /  2. 50. 0
  libswscale    2.  1. 0 /  2.  1. 0
[wav @ 0x26fd7e0] too big INFO subchunk
input.wav: Invalid data found when processing input

[Elon Musk]

uh, yes I'm blind and ignorant.

[Carl Eugen Hoyos]

Fixed by Michael.

[Bartłomiej Pater]

I have slightly different wav file (with adpcm inside) and also get this error message. It still works fine with very old 0.6.1 (that was in debian stable) but fails with version built from git.

[Bartłomiej Pater]

Wave file with ADPCM data that fails the same way.

[Bartłomiej Pater]

The file plays fine in VLC (linux) and QT Player (mac).