Recherche avancée

Sur d’autres sites (13026)

• ffmpeg error - number of bands (X) exceeds limit (Y) [closed]

  2 juin 2013, par sasa

  I'm trying to convert MP4 to AAC and here is log :

  ffmpeg -i in.mp4 outa.aac
  
  ffmpeg version 0.8.1-4:0.8.1-0ubuntu1, Copyright (c) 2000-2011 the Libav developers
  
    built on Mar 22 2012 05:09:06 with gcc 4.6.3
  
  This program is not developed anymore and is only provided for compatibility. Use avconv instead (see Changelog for the list of incompatible changes).
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'in.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 0
  
      compatible_brands: isom3gp4
  
      creation_time   : 1946-09-19 13:06:17
  
    Duration: 00:04:56.81, start: 0.000000, bitrate: 157 kb/s
  
      Stream #0.0(eng): Audio: aac, 48000 Hz, stereo, s16, 156 kb/s
  
      Metadata:
  
        creation_time   : 1946-09-19 13:06:17
  
  Output #0, adts, to 'outa.aac':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 0
  
      compatible_brands: isom3gp4
  
      creation_time   : 1946-09-19 13:06:17
  
      encoder         : Lavf53.21.0
  
      Stream #0.0(eng): Audio: libfaac, 48000 Hz, stereo, s16, 200 kb/s
  
      Metadata:
  
        creation_time   : 1946-09-19 13:06:17
  
  Stream mapping:
  
    Stream #0.0 -> #0.0
  
  Press ctrl-c to stop encoding
  
  [aac @ 0x17eede0] Number of bands (64) exceeds limit (46).
  
  Error while decoding stream #0.0
  
  size=    5994kB time=296.81 bitrate= 165.4kbits/s
  
  video:0kB audio:5994kB global headers:0kB muxing overhead 0.000000%

  This audio file cannot be played in some players and I think it is

  [aac @ 0x17eede0] Number of bands (64) exceeds limit (46).
  
  Error while decoding stream #0.0

  What that mean and how can I avoid this ?

  Update :
  If you want to help, you may want to test that MP4 file, so, here is link - https://dl.dropbox.com/u/34111231/in.mp4

• different results in different environments (AWS Lambda vs Local) using the same ffmpeg command

  10 août 2017, par bitterman

  I am getting to my wit’s end here. So I have an AWS lambda that is just some Java code that runs an ffmpeg command on a video file. When I download this video file and ffprobe it, the metadata looks different from what it looks like when I grab the same file and run the same ffmpeg command locally from the command line. I have no idea why this is. I made sure to have the same ffmpeg versions and all, but the file resulting from the lambda running the command is missing things compared to the other one. The reason I’m looking at this is the fact that this file resulting from the lambda running the command is not playable on certain players (has issues with android exoplayer and the android/mobile version of Chrome, for instance) while the one resulting from me running the command is playable everywhere that I’ve tried. Here are the different metadatas :

  As run locally :

  Metadata:
  
    service_name    : Service01
  
    service_provider: FFmpeg
  
  Stream #0:0[0x100]: Video: h264 (Main) ([27][0][0][0] / 0x001B), yuv420p(tv, progressive), 1280x720 [SAR 1:1 DAR 16:9], 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc
  
  Stream #0:1[0x101]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 44100 Hz, stereo, fltp, 95 kb/s

  vs as run by the lambda :

  Metadata:
  
    service_name    : Service01
  
    service_provider: FFmpeg
  
  Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(progressive), 1280x720, 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc
  
  Stream #0:1[0x101]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 44100 Hz, stereo, fltp, 95 kb/s

  As you can see, one has DAR and SAR explicitly stated next to the resolution and also has "tv" next to progressive in parentheses next to yuv420p. I’ve tried tweaking the command by adding more filters and flags, but the end result is the same... I’m not sure this would fix my playability issue, but could someone explay why the end results are different despite using the same version (and both are 64 bit) of ffmpeg and all ?

• different results in different environments (AWS Lambda vs Local) using the same ffmpeg command

  21 mars 2017, par bitterman

  I am getting to my wit’s end here. So I have an AWS lambda that is just some Java code that runs an ffmpeg command on a video file. When I download this video file and ffprobe it, the metadata looks different from what it looks like when I grab the same file and run the same ffmpeg command locally from the command line. I have no idea why this is. I made sure to have the same ffmpeg versions and all, but the file resulting from the lambda running the command is missing things compared to the other one. The reason I’m looking at this is the fact that this file resulting from the lambda running the command is not playable on certain players (has issues with android exoplayer and the android/mobile version of Chrome, for instance) while the one resulting from me running the command is playable everywhere that I’ve tried. Here are the different metadatas :

  As run locally :

  Metadata:
  
    service_name    : Service01
  
    service_provider: FFmpeg
  
  Stream #0:0[0x100]: Video: h264 (Main) ([27][0][0][0] / 0x001B), yuv420p(tv, progressive), 1280x720 [SAR 1:1 DAR 16:9], 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc
  
  Stream #0:1[0x101]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 44100 Hz, stereo, fltp, 95 kb/s

  vs as run by the lambda :

  Metadata:
  
    service_name    : Service01
  
    service_provider: FFmpeg
  
  Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(progressive), 1280x720, 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc
  
  Stream #0:1[0x101]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 44100 Hz, stereo, fltp, 95 kb/s

  As you can see, one has DAR and SAR explicitly stated next to the resolution and also has "tv" next to progressive in parentheses next to yuv420p. I’ve tried tweaking the command by adding more filters and flags, but the end result is the same... I’m not sure this would fix my playability issue, but could someone explay why the end results are different despite using the same version (and both are 64 bit) of ffmpeg and all ?