[FFmpeg-trac] #9864(avcodec:open): DolbyED2 track cannot be decoded

FFmpeg trac at avcodec.org
Fri Feb 17 14:27:09 EET 2023


#9864: DolbyED2 track cannot be decoded
-------------------------------------+-------------------------------------
             Reporter:  Francesco    |                    Owner:  (none)
  Bucciantini                        |
                 Type:  enhancement  |                   Status:  open
             Priority:  wish         |                Component:  avcodec
              Version:  git-master   |               Resolution:
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Comment (by Balling):

 https://github.com/MediaArea/MediaInfoLib/pull/1299#issuecomment-1434471782

 For 29.97 fps content, sampling rate is not an integer: 1792 * 30 / 1.001
 = 53706.24 Hz

 Is this true? cause if it is there is a bug in ffmpeg, it just uses 53706.

 https://github.com/FFmpeg/FFmpeg/commit/44e27d937d88f3e7cdc83f4de1b9d3a590bcaa04
 #diff-ec791aea00ab0f331287a3ffd7765c130b63f9b57d8bc62cd55be8611a5ab29aL85

 >you play it on a DolbyE compatible hardware decoder, it will almost
 always be brought to 48'000Hz upon decoding

 Is that a good idea for 53706 Hz, e.g.? Are there garantees Dolby E
 encoder cannot accept >48000 Hz wav to encode? Also what is up with Dolby
 E decoder in ffmpeg decoding to 32 bit? Is that because lossy 24 bit
 already needs 32 bits to preserve itself? Does Dolby E encoders even allow
 32 bit integer wavs?
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/9864#comment:25>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list