Recherche avancée

Sur d’autres sites (4394)

• ffmpeg : error on large input file [duplicate]

  1er octobre 2016, par ingenious

  This question already has an answer here :

  • ffmpeg convert from H.264 (High 4:4:4 Profile) to H.264 (Main Profile)
    
    1 answer
    

  I have a large Mov file with this info :

  

  I want convert it to mp4 by this ffmpeg command :

  ffmpeg -i 57d5092f59418.mov -codec:v libx264 -profile:v high -preset slow 
  
  -b:v 360k -maxrate 424k -bufsize 720k -vf scale=-1:360 -threads 0 -b:a 64k
  
  out.mov

  But I get this error :

  Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height

  detail :

          ffmpeg version N-81784-g92de2c2 Copyright (c) 2000-2016 the FFmpeg developers
  
        built with gcc 5.4.0 (GCC)
  
        configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-dx
  
      va2 --enable-libmfx --enable-nvenc --enable-avisynth --enable-bzlib --enable-lib
  
      ebur128 --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --ena
  
      ble-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfree
  
      type --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enab
  
      le-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-lib
  
      openh264 --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschr
  
      oedinger --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheor
  
      a --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvo
  
      rbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --ena
  
      ble-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --e
  
      nable-decklink --enable-zlib
  
        libavutil      55. 30.100 / 55. 30.100
  
        libavcodec     57. 58.100 / 57. 58.100
  
        libavformat    57. 51.100 / 57. 51.100
  
        libavdevice    57.  0.102 / 57.  0.102
  
        libavfilter     6. 63.100 /  6. 63.100
  
        libswscale      4.  1.100 /  4.  1.100
  
        libswresample   2.  2.100 /  2.  2.100
  
        libpostproc    54.  0.100 / 54.  0.100
  
      Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '57d5092f59418.mov':
  
        Metadata:
  
          major_brand     : qt
  
          minor_version   : 537199360
  
          compatible_brands: qt
  
          creation_time   : 2016-02-09T07:33:27.000000Z
  
        Duration: 00:00:13.71, start: 0.000000, bitrate: 72247 kb/s
  
          Stream #0:0(eng): Video: qtrle (rle  / 0x20656C72), bgra, 1920x1080, 72242 k
  
      b/s, SAR 1:1 DAR 16:9, 29.97 fps, 29.97 tbr, 30k tbn, 30k tbc (default)
  
          Metadata:
  
            creation_time   : 2016-02-09T07:33:27.000000Z
  
            handler_name    : Apple Alias Data Handler
  
            encoder         : Animation
  
            timecode        : 00:00:08;17
  
          Stream #0:1(eng): Data: none (tmcd / 0x64636D74), 0 kb/s (default)
  
          Metadata:
  
            creation_time   : 2016-02-09T07:33:46.000000Z
  
            handler_name    : Apple Alias Data Handler
  
            timecode        : 00:00:08;17
  
      File 'out.mov' already exists. Overwrite ? [y/N] y
  
      No pixel format specified, yuv444p for H.264 encoding chosen.
  
      Use -pix_fmt yuv420p for compatibility with outdated media players.
  
      x264 [error]: high profile doesn't support 4:4:4
  
      [libx264 @ 00000000006f2f20] Error setting profile high.
  
      [libx264 @ 00000000006f2f20] Possible profiles: baseline main high high10 high42
  
      2 high444
  
      Output #0, mov, to 'out.mov':
  
        Metadata:
  
          major_brand     : qt
  
          minor_version   : 537199360
  
          compatible_brands: qt
  
          Stream #0:0(eng): Video: h264, none, q=2-31, SAR 1:1 DAR 0:0, 29.97 fps (def
  
      ault)
  
          Metadata:
  
            creation_time   : 2016-02-09T07:33:27.000000Z
  
            handler_name    : Apple Alias Data Handler
  
            timecode        : 00:00:08;17
  
            encoder         : Lavc57.58.100 libx264
  
      Stream mapping:
  
        Stream #0:0 -> #0:0 (qtrle (native) -> h264 (libx264))
  
      Error while opening encoder for output stream #0:0 - maybe incorrect parameters
  
      such as bit_rate, rate, width or height

  What shoud I do ?

  thanks

• How to convert VP8 track with different frame resolution to h264

  13 septembre 2016, par Nikita

  I have a .webm file with VP8 track, recorded from WebRTC stream by external service (TokBox Archiving). The stream is adaptive, so each frame in track could have different resolution. Most players (in webkit browsers) use video resolution from track description (which is always 640x480) and scale frames to this resolution. Firefox and VLC player uses real frame resolution, changing video resolution respectively.

  I want to achieve 2 goals :

  1. play this video in Internet Explorer 9+ without additional plugin installation.
  2. change frames resolution to one fixed resolution, so the video will look identically in different browsers.

  So, my plan is :

  • extract frames from source webm file to images with real frame resolution (e.g. PNG or BMP) (how could I do that ?)
  • find max width and max height of images
  • add black padding to images, so smaller frames will be in the center of a new frame (of size MAX_WIDHTxMAX_HEIGHT)
  • combine images to h264 track using ffmpeg

  Is all correct ? How can I achieve this ? Can this algorithm be optimized some way ?

  I tried ffmpeg to extract images, but it does not parse real frame resolution, using resolution from track header.
  I think some libwebm functions can help me (to parse frame headers and extract images). Maybe someone has some code snippets to do this ?

  Example .webm (download source, do not play google-converted version) : https://drive.google.com/file/d/0BwFZRvYNn9CKcndhMzlVa0psX00/view?usp=sharing

  Official description of adaptive stream from TokBox support : https://support.tokbox.com/hc/en-us/community/posts/206241666-Archived-video-resolution-is-supposed-to-be-720x1280-but-reports-as-640x480

• Wowza : Live stream detected but does not play

  2 septembre 2016, par searcot jabali

  This is the command I use to being the stream on my hardware device
  ffmpeg -i /dev/video0 -f rtsp rtsp ://[user] :[password]@52.66.64.136:1935/test/myStream

  I can see that there is an input coming in from the Incoming Streams section of the Wowza Engine Manager.
  The IP, Stream name & Application name are correct.
  

  However when I try to play the stream using the Test Players, I dont see anything. Just a black screen.
  An error message at the bottom of Adobe HDS says Source stream or file could not be found or access was denied.

  

  When I try to use the RTSP wowza link on VLC I get an error stating that the "Input Cannot Be opened"

  Source security for RTSP has been set to open.

  When I stream through the GoCoder App there are no issues.
  This leads me to believe the server is functioning correctly.

  When I use the same command but change the output to write to file (ffmpeg -i /dev/video0 out.mp4) it works perfectly fine !!
  So even the base command is correct.

  Am I missing some arguments from the FFMPEG command ?
  Do I need to provide the username & password even though RTSP Source Security has been set to open ?