dca parser fails for DTS-MA

[Carl Eugen Hoyos]

A user uploaded a DTS-MA sample for which the parser fails:

$ ffmpeg -i LFEScaleIndex-larger-than-127-is-not-implemented-example_cut.dts -f null -
ffmpeg version N-71497-gedbb9b5 Copyright (c) 2000-2015 the FFmpeg developers
  built with gcc 4.7 (SUSE Linux)
  configuration: --enable-gpl
  libavutil      54. 22.101 / 54. 22.101
  libavcodec     56. 34.100 / 56. 34.100
  libavformat    56. 30.100 / 56. 30.100
  libavdevice    56.  4.100 / 56.  4.100
  libavfilter     5. 14.100 /  5. 14.100
  libswscale      3.  1.101 /  3.  1.101
  libswresample   1.  1.100 /  1.  1.100
  libpostproc    53.  3.100 / 53.  3.100
Input #0, dts, from 'LFEScaleIndex-larger-than-127-is-not-implemented-example_cut.dts':
  Duration: N/A, start: 0.000000, bitrate: N/A
    Stream #0:0: Audio: dts (DTS-HD MA), 48000 Hz, 5.1(side), fltp
Output #0, null, to 'pipe:':
  Metadata:
    encoder         : Lavf56.30.100
    Stream #0:0: Audio: pcm_s16le, 48000 Hz, 5.1(side), s16, 4608 kb/s
    Metadata:
      encoder         : Lavc56.34.100 pcm_s16le
Stream mapping:
  Stream #0:0 -> #0:0 (dts (dca) -> pcm_s16le (native))
Press [q] to stop, [?] for help
[dca @ 0x36a9ca0] LFEScaleIndex larger than 127 is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
[dca @ 0x36a9ca0] If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/incoming/ and contact the ffmpeg-devel mailing list. (ffmpeg-devel@ffmpeg.org)
[dca @ 0x36a9ca0] error decoding block
Error while decoding stream #0:0: Invalid data found when processing input
size=N/A time=00:00:00.29 bitrate=N/A
video:0kB audio:48kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown

The first frame of the file has size 5192 bytes which the parser correctly reports, the second and third frame should be 5176 and 5220 bytes, the parser instead reports 4308 and 6088. Decoding fails for the third frame (the one with the incorrect start position).

[Michael Niedermayer]

Fixed in e80b2b9c81716a5d9f559c04cfe69d76b04e4cd3 by foo86