Recherche avancée

Sur d’autres sites (4326)

• Is it possible to force ffmpeg to use hardware decoding with H.264 input stream ?

  27 août 2018, par Ryan Griggs

  I am running a raspberry pi 3B with ffmpeg compiled with the —enable-omx-rpi option. I am trying to do frame-capture from a webcam stream (h.264, 1920x1080) to JPG files at 5 frames per second. This operation currently causes the board to show very high CPU utilization and get very hot. For this reason, I am assuming hardware decoder is not being utilized.

  Is there a way to 1) determine whether ffmpeg is using hardware decoding, and 2) force it to be enabled ?

  EDIT : here’s the log :

  ffmpeg -probesize 4096 -analyzeduration 10000 -threads 1 -i rtsp://192.168.1.88:554/11 -vf fps=fps=5 -y test%03d.png
  
  ffmpeg version 3.2.10-1~deb9u1+rpt1 Copyright (c) 2000-2018 the FFmpeg developers
  
    built with gcc 6.3.0 (Raspbian 6.3.0-18+rpi1) 20170516
  
    configuration: --prefix=/usr --extra-version='1~deb9u1+rpt1' --toolchain=hardened --libdir=/usr/lib/arm-linux-gnueabihf --incdir=/usr/include/arm-linux-gnueabihf --enable-gpl --disable-stripping --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libebur128 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmp3lame --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx-rpi --enable-mmal --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264 --enable-shared
  
    libavutil      55. 34.101 / 55. 34.101
  
    libavcodec     57. 64.101 / 57. 64.101
  
    libavformat    57. 56.101 / 57. 56.101
  
    libavdevice    57.  1.100 / 57.  1.100
  
    libavfilter     6. 65.100 /  6. 65.100
  
    libavresample   3.  1.  0 /  3.  1.  0
  
    libswscale      4.  2.100 /  4.  2.100
  
    libswresample   2.  3.100 /  2.  3.100
  
    libpostproc    54.  1.100 / 54.  1.100
  
  [rtsp @ 0x1d9b630] Stream #0: not enough frames to estimate rate; consider increasing probesize
  
  [rtsp @ 0x1d9b630] decoding for stream 0 failed
  
  Guessed Channel Layout for Input Stream #0.1 : mono
  
  Input #0, rtsp, from 'rtsp://192.168.1.88:554/11':
  
    Metadata:
  
      title           : 10
  
    Duration: N/A, bitrate: 64 kb/s
  
      Stream #0:0: Video: h264 (Main), yuv420p(progressive), 1920x1080, 90k tbr, 90k tbn, 180k tbc
  
      Stream #0:1: Audio: pcm_alaw, 8000 Hz, mono, s16, 64 kb/s
  
  [swscaler @ 0x1e50a80] No accelerated colorspace conversion found from yuv420p to rgb24.
  
  Output #0, image2, to 'test%03d.png':
  
    Metadata:
  
      title           : 10
  
      encoder         : Lavf57.56.101
  
      Stream #0:0: Video: png, rgb24, 1920x1080, q=2-31, 200 kb/s, 5 fps, 5 tbn, 5 tbc
  
      Metadata:
  
        encoder         : Lavc57.64.101 png
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 (native) -> png (native))
  
  Press [q] to stop, [?] for help
  
  [rtsp @ 0x1d9b630] max delay reached. need to consume packetN/A speed=   0x
  
  [rtsp @ 0x1d9b630] RTP: missed 13 packets
  
  [h264 @ 0x1dfb650] error while decoding MB 24 3, bytestream -5
  
  [h264 @ 0x1dfb650] concealing 7825 DC, 7825 AC, 7825 MV errors in P frame
  
  [rtsp @ 0x1d9b630] max delay reached. need to consume packet
  
  [rtsp @ 0x1d9b630] RTP: missed 88 packets
  
  [h264 @ 0x1dfb650] error while decoding MB 38 41, bytestream -11
  
  [h264 @ 0x1dfb650] concealing 3251 DC, 3251 AC, 3251 MV errors in P frame
  
  frame=    4 fps=2.2 q=-0.0 size=N/A time=00:00:00.20 bitrate=N/A speed=0.111x   [h264 @ 0x1dfb650] Increasing reorder buffer to 1
  
  frame=    4 fps=0.8 q=-0.0 size=N/A time=00:00:00.20 bitrate=N/A speed=0.0413x  [rtsp @ 0x1d9b630] max delay reached. need to consume packet
  
  [rtsp @ 0x1d9b630] RTP: missed 30 packets
  
  [h264 @ 0x1dfb650] error while decoding MB 37 5, bytestream -9
  
  [h264 @ 0x1dfb650] concealing 7572 DC, 7572 AC, 7572 MV errors in P frame
  
  frame=    5 fps=0.9 q=-0.0 size=N/A time=00:00:00.40 bitrate=N/A speed=0.069x   [rtsp @ 0x1d9b630] max delay reached. need to consume packet
  
  [rtsp @ 0x1d9b630] RTP: missed 34 packets
  
  [h264 @ 0x1dfb650] error while decoding MB 98 4, bytestream -9
  
  [h264 @ 0x1dfb650] concealing 7631 DC, 7631 AC, 7631 MV errors in P frame
  
  frame=    6 fps=0.9 q=-0.0 size=N/A time=00:00:00.60 bitrate=N/A speed=0.0894x  [rtsp @ 0x1d9b630] max delay reached. need to consume packet
  
  [rtsp @ 0x1d9b630] RTP: missed 30 packets
  
  [h264 @ 0x1dfb650] error while decoding MB 20 10, bytestream -9
  
  [h264 @ 0x1dfb650] concealing 6989 DC, 6989 AC, 6989 MV errors in P frame
  
  frame=    6 fps=0.8 q=-0.0 size=N/A time=00:00:00.60 bitrate=N/A speed=0.0808x  [rtsp @ 0x1d9b630] max delay reached. need to consume packet
  
  [rtsp @ 0x1d9b630] RTP: missed 3357 packets
  
  [rtsp @ 0x1d9b630] RTP: PT=60: bad cseq 0fed expected=02d0
  
  [rtsp @ 0x1d9b630] max delay reached. need to consume packet
  
  [rtsp @ 0x1d9b630] RTP: missed 3358 packets
  
  [h264 @ 0x1dfb650] concealing 3400 DC, 3400 AC, 3400 MV errors in P frame
  
  frame=    8 fps=1.0 q=-0.0 size=N/A time=00:00:01.00 bitrate=N/A speed=0.124x   [rtsp @ 0x1d9b630] max delay reached. need to consume packet
  
  [rtsp @ 0x1d9b630] RTP: missed 5 packets
  
  [h264 @ 0x1dfb650] error while decoding MB 33 42, bytestream -5
  
  [h264 @ 0x1dfb650] concealing 3136 DC, 3136 AC, 3136 MV errors in P frame
  
  frame=    8 fps=0.9 q=-0.0 size=N/A time=00:00:01.00 bitrate=N/A speed=0.117x   frame=   41 fps=0.9 q=-0.0 size=N/A time=00:00:07.40 bitrate=N/A speed=0.156x   [rtsp @ 0x1d9b630] max delay reached. need to consume packet
  
  [rtsp @ 0x1d9b630] RTP: missed 6 packets
  
  [h264 @ 0x1dfb650] error while decoding MB 72 17, bytestream -5
  
  [h264 @ 0x1dfb650] concealing 6097 DC, 6097 AC, 6097 MV errors in P frame
  
  frame=   42 fps=0.9 q=-0.0 size=N/A time=00:00:07.60 bitrate=N/A speed=0.155x   frame=   44 fps=0.9 q=-0.0 size=N/A time=00:00:08.00 bitrate=N/A speed=0.162x   [rtsp @ 0x1d9b630] max delay reached. need to consume packet
  
  [rtsp @ 0x1d9b630] RTP: missed 19325 packets
  
  [rtsp @ 0x1d9b630] RTP: PT=60: bad cseq 5c13 expected=1096
  
  [rtsp @ 0x1d9b630] max delay reached. need to consume packet
  
  [rtsp @ 0x1d9b630] RTP: missed 19326 packets
  
  [h264 @ 0x1dfb650] cabac decode of qscale diff failed at 5 15
  
  [h264 @ 0x1dfb650] error while decoding MB 5 15, bytestream 14471
  
  [h264 @ 0x1dfb650] concealing 6404 DC, 6404 AC, 6404 MV errors in P frame
  
  [rtsp @ 0x1d9b630] max delay reached. need to consume packet
  
  [rtsp @ 0x1d9b630] RTP: missed 32 packets
  
  [h264 @ 0x1dfb650] error while decoding MB 40 13, bytestream -11
  
  [h264 @ 0x1dfb650] concealing 6609 DC, 6609 AC, 6609 MV errors in P frame
  
  frame=   44 fps=0.9 q=-0.0 size=N/A time=00:00:08.00 bitrate=N/A speed=0.159x   

  Here’s the output of ffmpeg -decoders | grep -i h264 :

   ffmpeg -decoders | grep -i h264
  
  ffmpeg version 3.2.10-1~deb9u1+rpt1 Copyright (c) 2000-2018 the FFmpeg developers
  
    built with gcc 6.3.0 (Raspbian 6.3.0-18+rpi1) 20170516
  
    configuration: --prefix=/usr --extra-version='1~deb9u1+rpt1' --toolchain=hardened --libdir=/usr/lib/arm-linux-gnueabihf --incdir=/usr/include/arm-linux-gnueabihf --enable-gpl --disable-stripping --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libebur128 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmp3lame --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx-rpi --enable-mmal --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264 --enable-shared
  
    libavutil      55. 34.101 / 55. 34.101
  
    libavcodec     57. 64.101 / 57. 64.101
  
    libavformat    57. 56.101 / 57. 56.101
  
    libavdevice    57.  1.100 / 57.  1.100
  
    libavfilter     6. 65.100 /  6. 65.100
  
    libavresample   3.  1.  0 /  3.  1.  0
  
    libswscale      4.  2.100 /  4.  2.100
  
    libswresample   2.  3.100 /  2.  3.100
  
    libpostproc    54.  1.100 / 54.  1.100
  
   VFS..D h264                 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
  
   V..... h264_mmal            h264 (mmal) (codec h264)
  
   V....D h264_vdpau           H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (VDPAU acceleration) (codec h264)

• FFmpeg Concatenate multiple videos with crossfade

  21 juillet 2018, par Jack

  I’m very new to FFmpeg, so any help is much appreciated.

  I’m trying to create a batch file that can take all the videos in a folder and concatenate them with 1 sec crossfade between each video. The amount of videos in the folder isn’t set, nor is the length of these videos, which is where my issue is.

  I have gotten as far as importing the videos using dir /b *.mp4 > list.txt so that i don’t have to import each file individually.

  One idea I had was to find a pattern in crossfading videos with ffmpeg, then using python to edit a secondary batch file to fit the amount of videos. However, I haven’t been able to determine any pattern with my lack of ffmpeg experience.

• Game Music Appreciation, One Year Later

  1er août 2013, par Multimedia Mike — General

  I released my game music website last year about this time. It was a good start and had potential to grow in a lot of directions. But I’m a bit disappointed that I haven’t evolved it as quickly as I would like to. I have made a few improvements, like adjusting the play lengths of many metadata-less songs and revising the original atrocious design of the website using something called Twitter Bootstrap (and, wow, once you know what Bootstrap is, you start noticing it everywhere on the modern web). However, here are a few of the challenges that have slowed me down over the year :

  Problems With Native Client – Build System
  The technology which enables this project — Google’s Native Client (NaCl) — can be troublesome. One of my key frustrations with the environment is that every single revision of the NaCl SDK seems to adopt a completely new build system layout. If you want to port your NaCl project forward to newer revisions, you have to spend time wrapping your head around whatever the favored build system is. When I first investigated NaCl, I think it was using vanilla GNU Make. Then it switched to SCons. Then I forgot about NaCl for about a year and when I came back, the SDK had reverted back to GNU Make. While that has been consistent, the layout of the SDK sometimes changes and a different example Makefile shows the way.

  The very latest version of the API has required me to really overhaul the Makefile and to truly understand the zen of Makefile programming. I’m even starting to grasp the relationship it has to functional programming.

  Problems With Native Client – API Versions and Chrome Bugs
  I built the original Salty Game Music Player when NaCl API version 16 was current. By the time I published the v16 version, v19 was available. I made the effort to port forward (a few APIs had superfically changed, nothing too dramatic). However, when I would experiment with this new player, I would see intermittent problems on my Windows 7 desktop. Because of this, I was hesitant to make a new player release.

  Around the end of May, I started getting bug reports from site users that their Chrome browsers weren’t allowing them to activate the Salty Game Music Player — the upshot was that they couldn’t play music unless they manually flipped a setting in their browser configuration. It turns out that Chrome 27 introduced a bug that caused this problem. Not only that, but my player was one of only 2 known NaCl apps that used the problematic feature (the other was developed by the Google engineer who entered the bug).

  After feeling negligent for a long while about not doing anything to fix the bug, I made a concerted and creative effort to work around the bug and pushed out a new version of the player (based on API v25). My effort didn’t work and I had to roll it back somewhat (but still using the new player binaries). The bug was something that I couldn’t work around. However, at about the same time that I was attempting to do this, Google was rolling out Chrome 28 which fixed the bug, rendering my worry and effort moot.

  Problems With Native Client – Still Not In The Clear
  I felt reasonably secure about releasing the updated player since I couldn’t make my aforementioned problem occur on my Windows 7 setup anymore. I actually have a written test plan for this player, believe it or not. However, I quickly started receiving new bug reports from Windows users. Mostly, these are Windows 8 users. The player basically doesn’t work at all for them now. One user reports the problem on Windows 7 (and another on Windows 2008 Server, I think). But I can’t see it.

  I have a theory about what might be going wrong, but of course I’ll need to test it, and determine how to fix it.

  Database Difficulties
  The player is only half of the site ; the other half is the organization of music files. Working on this project has repeatedly reminded me of my fundamental lack of skill concerning databases. I have a ‘production’ database– now I’m afraid to do anything with it for fear of messing it up. It’s an an SQLite3 database, so it’s easy to make backups and to create a copy in order to test and debug a new script. Still, I feel like I’m missing an entire career path worth of database best practices.

  There is also the matter of ongoing database maintenance. There are graphical frontends for SQLite3 which make casual updates easier and obviate the need for anything more sophisticated (like a custom web app). However, I have a slightly more complicated database entry task that I fear will require, well, a custom web app in order to smoothly process hundreds, if not thousands of new song files (which have quirks which prohibit the easy mass processing I have been able to get away with so far).

  Going Forward
  I remain hopeful that I’ll gradually overcome these difficulties. I still love this project and I have received nothing but positive feedback over the past year (modulo the assorted recommendations that I port the entire player to pure JavaScript).

  You would think I would learn a lesson about building anything on top of a Google platform in the future, especially Native Client. Despite all this, I have another NaCl project planned.