[FFmpeg-trac] #8770(undetermined:new): SACD DST (dff extension) sometimes produces errors

[FFmpeg]

#8770: SACD DST (dff extension) sometimes produces errors
-------------------------------------+-------------------------------------
             Reporter:  MelkorLord   |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
                                     |  undetermined
              Version:  git-master   |               Resolution:
             Keywords:  dst          |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------

Comment (by MelkorLord):

 The uploaded DFF file very interesting on many levels.

 It produces 1630 decoding errors with `ffmpeg-git-20200616` but '''none'''
 with another FFMPEG version I have on another computer with a very old OS.
 Here is the info about this other FFMPEG version which came from
 https://launchpad.net/~jonathonf/+archive/ubuntu/ffmpeg-4 but it's not
 available anymore due to deprecation :

 {{{
 # ffmpeg -version
 ffmpeg version 4.1.3-0york1~14.04 Copyright (c) 2000-2019 the FFmpeg
 developers
 built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04.4)
 configuration: --prefix=/usr --extra-version='0york1~14.04'
 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu
 --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl
 --disable-stripping --enable-avresample --disable-filter=resample
 --enable-avisynth --enable-gnutls --enable-ladspa --enable-libaom
 --enable-libass --enable-libbluray
 --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2
 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-
 libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-
 libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libmodplug
 --enable-libopus --enable-libpulse --enable-librsvg --enable-librubberband
 --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex
 --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab
 --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp
 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq
 --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opengl
 --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883
 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared
 libavutil      56. 22.100 / 56. 22.100
 libavcodec     58. 35.100 / 58. 35.100
 libavformat    58. 20.100 / 58. 20.100
 libavdevice    58.  5.100 / 58.  5.100
 libavfilter     7. 40.101 /  7. 40.101
 libavresample   4.  0.  0 /  4.  0.  0
 libswscale      5.  3.100 /  5.  3.100
 libswresample   3.  3.100 /  3.  3.100
 libpostproc    55.  3.100 / 55.  3.100
 }}}

 The resulting WAV files are very different :

 ffmpeg-git-20200617 => 872629760 bytes => 4:34.826 ('''1630 decoding
 errors''')
 ffmpeg 4.1.3 York => 941679776 bytes => 4:56.576 ('''no decoding error''')

 On the working file (4:56.576), there's silence at the 3:58.125 mark which
 lasts ~20 seconds.

 On the bugged file (4:34.826), the silence part was stripped and the next
 song part is directly glued at the end of the first part.

 So, maybe the decoding errors have something to do with near zero samples.
 This of course a wild guess based on empiric observation.

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