More than one AAC RDB per ADTS frame is not implemented

[tincanfury]

Summary of the bug:
How to reproduce:

ffmpeg-git-20220910-i686-static/ffmpeg -i Stray_Pop2022_07_16_02_59_03.aac -c copy Stray_Pop2022_07_16_02_59_03.m4a
ffmpeg version N-63101-gc92edd969a-static ​https://johnvansickle.com/ffmpeg/ Copyright (c) 2000-2022 the FFmpeg developers

built with gcc 8 (Debian 8.3.0-6)
configuration: --enable-gpl --enable-version3 --enable-static --disable-debug --disable-ffplay --disable-indev=sndio --disable-outdev=sndio --cc=gcc --enable-fontconfig --enable-frei0r --enable-gnutls --enable-gmp --enable-libgme --enable-gray --enable-libfribidi --enable-libass --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librubberband --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libvorbis --enable-libopus --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg
libavutil 57. 36.101 / 57. 36.101
libavcodec 59. 42.104 / 59. 42.104
libavformat 59. 30.101 / 59. 30.101
libavdevice 59. 8.101 / 59. 8.101
libavfilter 8. 48.100 / 8. 48.100
libswscale 6. 8.108 / 6. 8.108
libswresample 4. 9.100 / 4. 9.100
libpostproc 56. 7.100 / 56. 7.100

[aac @ 0xd87b4c0] More than one AAC RDB per ADTS frame 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.
[aac @ 0xd87b4c0] Multiple frames in a packet.
[aac @ 0xd87b4c0] Sample rate index in program config element does not match the sample rate index configured by the container.
[aac @ 0xd87b4c0] Number of scalefactor bands in group (58) exceeds limit (40).
[aac @ 0xd87b4c0] Number of scalefactor bands in group (47) exceeds limit (43).
[aac @ 0xd87b4c0] channel element 1.14 is not allocated
[aac @ 0xd87a7c0] Estimating duration from bitrate, this may be inaccurate

happens on several streamripper streaming radio station rips I have, but not all of them.

[Balling]

We need a sample.

[tincanfury]

requested sample

[tincanfury]

I was unable to connect to the ftp site listed at

https://ffmpeg.org/bugreports.html

so I uploaded the sample here. I hope that is ok.

[Carl Eugen Hoyos]

Decoding works fine, several error messages are shown though for a file that may just be cut badly but not otherwise damaged.

$ ffmpeg -i Stray_Pop____2022_07_16_02_59_03_small.aac -t 150 out.wav
ffmpeg version N-108466-g5f02a261a2 Copyright (c) 2000-2022 the FFmpeg developers
  built with clang version 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
  configuration: --enable-gpl --cc=clang
  libavutil      57. 38.100 / 57. 38.100
  libavcodec     59. 49.100 / 59. 49.100
  libavformat    59. 33.100 / 59. 33.100
  libavdevice    59.  8.101 / 59.  8.101
  libavfilter     8. 49.100 /  8. 49.100
  libswscale      6.  8.112 /  6.  8.112
  libswresample   4.  9.100 /  4.  9.100
  libpostproc    56.  7.100 / 56.  7.100
[aac @ 0x2544580] More than one AAC RDB per ADTS frame 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.
[aac @ 0x2544580] Multiple frames in a packet.
[aac @ 0x2544580] Sample rate index in program config element does not match the sample rate index configured by the container.
[aac @ 0x2544580] Number of scalefactor bands in group (58) exceeds limit (40).
[aac @ 0x2544580] Number of scalefactor bands in group (47) exceeds limit (43).
[aac @ 0x2544580] channel element 1.14 is not allocated
[aac @ 0x2543400] Estimating duration from bitrate, this may be inaccurate
Input #0, aac, from 'Stray_Pop____2022_07_16_02_59_03_small.aac':
  Duration: 00:02:33.11, bitrate: 133 kb/s
  Stream #0:0: Audio: aac (HE-AAC), 44100 Hz, stereo, fltp, 133 kb/s
Stream mapping:
  Stream #0:0 -> #0:0 (aac (native) -> pcm_s16le (native))
Press [q] to stop, [?] for help
[aac @ 0x256a0c0] More than one AAC RDB per ADTS frame 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.
[aac @ 0x256a0c0] Multiple frames in a packet.
[aac @ 0x256a0c0] channel element 0.3 is not allocated
Error while decoding stream #0:0: Invalid data found when processing input
[aac @ 0x256a0c0] Sample rate index in program config element does not match the sample rate index configured by the container.
[aac @ 0x256a0c0] Number of scalefactor bands in group (58) exceeds limit (40).
Error while decoding stream #0:0: Invalid data found when processing input
[aac @ 0x256a0c0] Number of scalefactor bands in group (47) exceeds limit (43).
Error while decoding stream #0:0: Invalid data found when processing input
[aac @ 0x256a0c0] channel element 1.14 is not allocated
Error while decoding stream #0:0: Invalid data found when processing input
Output #0, wav, to 'out.wav':
  Metadata:
    ISFT            : Lavf59.33.100
  Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 44100 Hz, stereo, s16, 1411 kb/s
    Metadata:
      encoder         : Lavc59.49.100 pcm_s16le
size=   25808kB time=00:02:29.95 bitrate=1409.9kbits/s speed= 499x
video:0kB audio:25808kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.000295%

[tincanfury]

Is there something I can do to get my original command to work, or does this need "changes under the hood"?

Thanks!

[Balling]

It was reported many times

happens on several streamripper streaming radio station rips I have, but not all of them.

SDR requires a good active, i.e. with magnetic field on it, antenna. Buy one on aliexpress.

[tincanfury]

Replying to Balling:

It was reported many times

happens on several streamripper streaming radio station rips I have, but not all of them.

SDR requires a good active, i.e. with magnetic field on it, antenna. Buy one on aliexpress.

I don't understand what an antenna has to do with an internet stream?
I didn't find anything matching this when I did a Google search, so I'm still curious if there is a fix for this or something still has to be developed?