Sur d’autres sites (8645)

• Burn subtitles in a stop motion video, with hardware acceleration

  9 février 2020, par Belinde

  I’m trying to make a year long stop motion video with the images taken from a webcam. I’ve created a input.txt file with this format inside :

  ffconcat version 1.0
  
  
  
  file 'amianthe201909031230.jpg'
  
  duration 0.093034825870647
  
  
  
  file 'amianthe201909031330.jpg'
  
  duration 0.093034825870647

  The command I’ve crafted (mostly taken from the example in the official ffmpeg documentation) is :

  ffmpeg \
  
      -y \
  
      -hwaccel vaapi \
  
      -hwaccel_device /dev/dri/renderD128 \
  
      -hwaccel_output_format vaapi \
  
      -f concat \
  
      -i input.txt \
  
      -vf 'hwmap=mode=read+write+direct,format=nv12,ass=subtitles.ass,hwmap' \
  
      -c:v h264_vaapi \
  
      ~/amianthe.mp4

  But it badly fails with this output :

  ffmpeg version 4.1.4-1build2 Copyright (c) 2000-2019 the FFmpeg developers
  
    built with gcc 9 (Ubuntu 9.2.1-4ubuntu1)
  
    configuration: --prefix=/usr --extra-version=1build2 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-avresample --disable-filter=resample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librsvg --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared
  
    libavutil      56. 22.100 / 56. 22.100
  
    libavcodec     58. 35.100 / 58. 35.100
  
    libavformat    58. 20.100 / 58. 20.100
  
    libavdevice    58.  5.100 / 58.  5.100
  
    libavfilter     7. 40.101 /  7. 40.101
  
    libavresample   4.  0.  0 /  4.  0.  0
  
    libswscale      5.  3.100 /  5.  3.100
  
    libswresample   3.  3.100 /  3.  3.100
  
    libpostproc    55.  3.100 / 55.  3.100
  
  Input #0, concat, from 'input.txt':
  
    Duration: 00:00:18.70, start: 0.000000, bitrate: 5 kb/s
  
      Stream #0:0: Video: mjpeg, yuvj420p(pc, bt470bg/unknown/unknown), 1920x1080 [SAR 1:1 DAR 16:9], 25 tbr, 25 tbn, 25 tbc
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (mjpeg (native) -> h264 (h264_vaapi))
  
  Press [q] to stop, [?] for help
  
  [Parsed_ass_2 @ 0x5557f4ec4ac0] Shaper: FriBidi 0.19.7 (SIMPLE) HarfBuzz-ng 2.6.1 (COMPLEX)
  
  [Parsed_ass_2 @ 0x5557f4ec4ac0] Using font provider fontconfig
  
  [Parsed_ass_2 @ 0x5557f4ec4ac0] Added subtitle file: 'subtitles.ass' (4 styles, 2 events)
  
  [Parsed_hwmap_3 @ 0x5557f5381ec0] Unsupported formats for hwmap: from nv12 (vaapi_vld) to vaapi_vld.
  
  [Parsed_hwmap_3 @ 0x5557f5381ec0] Failed to configure output pad on Parsed_hwmap_3
  
  Error reinitializing filters!
  
  Failed to inject frame into filter network: Invalid argument
  
  Error while processing the decoded data for stream #0:0
  
  Conversion failed!

  I’m honestly lost : from my understanding, all the elaboration should be done directly in the video card memory, so I don’t understand why it’s converting the surface format. Is there some other parameter I must put in format ? What am I missing ?

• Chrome struggles to play videos

  11 décembre 2017, par Cameron

  I have some video files I want to display on a webpage using the HTML5 video player. The videos were sent to me at 1920x1080 in H.254 MP4 format.

  Using FFMPEG I have converted them so I have a smaller Mp4 file, an OGV file, and a WebM file using the following commands :

  ffmpeg -i FILE.mp4 -vcodec h264 FILE.mp4
  
  
  
  ffmpeg -i FILE.mp4 -acodec libvorbis -vcodec libtheora -f ogv FILE.ogv
  
  
  
  ffmpeg -i FILE.mp4 -c:v libvpx -crf 10 -b:v 1M -c:a libvorbis FILE.webm

  And then the video is embedded into the page like so :

  <video preload="metadata" crossorigin="anonymous" poster="poster.jpg" controls="controls" playsinline="playsinline">
  
      <source src="FILE.webm" type="video/webm">
  
      <source src="FILE.ogv" type="video/ogv">
  
      <source src="FILE.mp4" type="video/mp4">
  
  </source></source></source></video>

  However when I click to play the video in Chrome, it stops after a few seconds and then if I click play again it restarts. If I right click and open the video in a new tab I just see a tiny player and not the video e.g.
  

  The same happens for all three formats. But if I refresh the browser enough times I can get the MP4 file to show up in the new tab though it still suffers from the aforementioned bug of playing for a few seconds before failing.

  I have tested this in Firefox and Safari and it works fine ! In fact it even works in IE and Edge :D And I can also play the videos in a player on the machine itself... e.g. QuickTime.

  Any ideas why Chrome is acting this way ? Or any resolutions ? I’m seeing the same behaviour on Chrome for Windows and Mac. Is the way I have converted the videos using FFMPEG in anyway a cause that could affect Chrome but not other browsers ?

  Chrome version tested on : Version 63.0.3239.84 (Official Build) (64-bit)

  Output from ffprobe as per the comments on the one of the webm files :

  ffprobe version 3.4 Copyright (c) 2007-2017 the FFmpeg developers
  
    built with Apple LLVM version 7.3.0 (clang-703.0.31)
  
    configuration: --prefix=/usr/local/Cellar/ffmpeg/3.4 --enable-shared --enable-pthreads --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-gpl --enable-ffplay --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxvid --enable-opencl --enable-videotoolbox --enable-openssl --disable-lzma --enable-libopenjpeg --disable-decoder=jpeg2000 --extra-cflags=-I/usr/local/Cellar/openjpeg/2.3.0/include/openjpeg-2.3 --enable-nonfree
  
    libavutil      55. 78.100 / 55. 78.100
  
    libavcodec     57.107.100 / 57.107.100
  
    libavformat    57. 83.100 / 57. 83.100
  
    libavdevice    57. 10.100 / 57. 10.100
  
    libavfilter     6.107.100 /  6.107.100
  
    libavresample   3.  7.  0 /  3.  7.  0
  
    libswscale      4.  8.100 /  4.  8.100
  
    libswresample   2.  9.100 /  2.  9.100
  
    libpostproc    54.  7.100 / 54.  7.100
  
  Input #0, matroska,webm, from 'FILE.webm':
  
    Metadata:
  
      COMPATIBLE_BRANDS: mp42mp41
  
      MAJOR_BRAND     : mp42
  
      MINOR_VERSION   : 0
  
      ENCODER         : Lavf57.83.100
  
    Duration: 00:00:52.57, start: 0.000000, bitrate: 910 kb/s
  
      Stream #0:0(eng): Video: vp8, yuv420p(progressive), 1920x1080, SAR 1:1 DAR 16:9, 25 fps, 25 tbr, 1k tbn, 1k tbc (default)
  
      Metadata:
  
        HANDLER_NAME    : Alias Data Handler
  
        ENCODER         : Lavc57.107.100 libvpx
  
        DURATION        : 00:00:52.563000000
  
      Stream #0:1(eng): Audio: vorbis, 48000 Hz, stereo, fltp (default)
  
      Metadata:
  
        HANDLER_NAME    : Alias Data Handler
  
        ENCODER         : Lavc57.107.100 libvorbis
  
        DURATION        : 00:00:52.568000000

• Mobile Analytics SDK : beta release of Piwik iOS SDK

  30 octobre 2013, par Piwik team

  Mattias Levin, a Mobile developer enthusiast from Sweden, has released the first public beta version of the official Piwik SDK for iOS !

  If you are building apps for iOS or OSX, you will be able to track your App usage with Piwik. Learn more in this blog post.

  Apps & Mobile apps Analytics

  Using Piwik to track your app usage would give interesting statistics usage such as :

  • number of active users (per day, week, month, …) of my mobile or desktop app,
  • how long users spend in the app,
  • track which icons, buttons are clicked (or any other custom event),
  • record device info, operating system,
  • reports on any Custom Variables you that are relevant to your app (see examples below),
  • how often is the app opened ? When and how long is the app opened ?
  • number of new users, active users, total users,
  • record errors or exception thrown

  Piwik SDK for iOS
  

  The PiwikTracker is an Objective-C framework (for iOS and OSX) designed to send app usage data to a Piwik analytics server. It is realeased under MIT license. Piwik server is a downloadable, Free/Libre (GPLv3 licensed) real time analytics platform.

  Getting started

  1. Create a new website in the Piwik web interface called “My App”. Copy the Website ID and the token_auth.
  2. Download the PiwikTracker SDK.
  3. Add the PiwikTracker files to your project.
  4. Create and configure the PiwikTracker.
  5. Add code in your app to track screen views, events, exceptions, goals and more
  6. Let the dispatch timer dispatch pending events to the Piwik server, or dispatch events manually.

  For more info, check out the Readme.

  Requirements

  The latest PiwikTracker version uses ARC and support iOS6+ and OSX 10.7+.

  • iOS tracker depends on : Core Data, Core Location, Core Graphics, UIKit and AFNetworking.
  • OSX tracker depends on : Core Data, Core Graphics, Cocoa and AFNetworking.

  Demo project

  The workspace contains an iPhone demo app that uses and demonstrates the features available in the SDK.

  

  Feedback needed

  If you use the iOS SDK to track your app, we would like to hear your suggestions, bug reports or general feedback.

  We hope to work with you to improve the SDK and move it out of beta !

  Please report suggestions, bugs, feature requests in the Github Issues at Piwik iOS SDK.

  Happy App Analytics !