Recherche avancée

Sur d’autres sites (5640)

• How to get your Matomo plugin ready for GDPR

  24 avril 2018, par Matomo Core Team

  Are you developing a plugin for your self-hosted Matomo ? Have you maybe published a plugin on the Matomo Marketplace ? Then we highly recommend you read this article.

  On 25th May 2018, new privacy regulations become effective called GDPR (General Data Protection Regulation) which applies to businesses worldwide. It is also known under different wordings in other countries, for example to RGPD in French and Datenschutz-Grundverordnung, DS-GVO in German.

  If your plugin is storing any personal information or tracks or imports any data, we highly recommend you give the GDPR guide a read. You may also want to read our blog as we are releasing new content about GDPR regularly.

  In Matomo 3.5.0, we will introduce new features for GDPR and we implemented it in a way that most – but not all – plugins will support these features out of the box without having to do anything.

  Nevertheless, we recommend every plugin developer to check out our developer guide on how to make your plugin GDPR compliant to see what you need to do. A beta version of Matomo 3.5.0 is already available so you can test these new features. You can find them by logging in to your Matomo and going to “Administration => Privacy”.

  Please note that any version of Piwik will not be GDPR compliant, so it is recommended that your plugin supports the latest version of Matomo (3.5.0+).

  The post How to get your Matomo plugin ready for GDPR appeared first on Analytics Platform - Matomo.

• Cannot install ffmpeg via brew on macOS Mojave

  12 juillet 2018, par Savinggrace
  • Xcode 10 beta installed
  • Command line tool for macOS 10.14 installed
  • macOS_SDK_headers_for_macOS_10.14.pkg installed
  • brew update done ;

  When trying to install ffmpeg by brew install ffmpeg, I had un error below :

  tar: Error exit delayed from previous errors.
  
  Error: Failure while executing: tar xf /Users/myname/Library/Caches/Homebrew/texi2html-5.0.tar.gz -C /private/tmp/texi2html-20180712-39689-hmsh90

  Which seems like a problem of Homebrew texi2html-5.0.tar.gz.

  Then using brew info ffmpeg :

  ffmpeg: stable 4.0.1, HEAD
  
  Play, record, convert, and stream audio and video
  
  https://ffmpeg.org/
  
  Not installed
  
  From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/ffmpeg.rb
  
  ==> Dependencies
  
  Build: nasm ✔, pkg-config ✔, texi2html ✘
  
  Recommended: lame ✘, x264 ✘, xvid ✘
  
  Optional: chromaprint ✘, fdk-aac ✘, fontconfig ✘, freetype ✘, frei0r ✘, game-music-emu ✘, libass ✘, libbluray ✘, libbs2b ✘, libcaca ✘, libgsm ✘, libmodplug ✘, librsvg ✘, libsoxr ✘, libssh ✘, libvidstab ✘, libvorbis ✘, libvpx ✘, opencore-amr ✘, openh264 ✘, openjpeg ✘, openssl ✘, opus ✘, rtmpdump ✘, rubberband ✘, sdl2 ✘, snappy ✘, speex ✘, tesseract ✘, theora ✘, two-lame ✘, wavpack ✘, webp ✘, x265 ✘, xz ✔, zeromq ✘, zimg ✘, srt ✘

  As is not working, so I just downloaded static FFmpeg binaries for macOS 64-bit from https://evermeet.cx/ffmpeg/ and moved the exec file to /usr/local/bin/ and now ffmpeg works perfectly.

  But I’m still curious to know how to resolve this brew error.

  Thanks in advance if anyone has the solution.

• ffmpeg same bit rate in hls file

  2 août 2019, par Saurabh

  We are using following command to generate dash and hls file for a given video :

  ffmpeg -y -nostdin -loglevel error -i input.mp4 \
  
          -map 0:v:0  -map 0:v:0 -map 0:v:0  -map 0:v:0  -map 0:v:0  -map 0:v:0 -map 0:a\?:0  \
  
          -maxrate:v:0 350k -bufsize:v:0 700k  -c:v:0 libx264 -filter:v:0 "scale=320:-2"  \
  
          -maxrate:v:1 1000k -bufsize:v:0 2000k -c:v:1 libx264 -filter:v:1 "scale=640:-2"  \
  
          -maxrate:v:2 3000k -bufsize:v:0 6000k -c:v:2 libx264 -filter:v:2 "scale=1280:-2" \
  
          -maxrate:v:3 245k -bufsize:v:3 600k -c:v:3 libvpx-vp9 -filter:v:3 "scale=320:-2"  \
  
          -maxrate:v:4 700k  -bufsize:v:3 1400k -c:v:4 libvpx-vp9 -filter:v:4 "scale=640:-2"  \
  
          -maxrate:v:5 2100k -bufsize:v:3 4200k -c:v:5 libvpx-vp9 -filter:v:5 "scale=1280:-2"  \
  
          -use_timeline 1 -use_template 1 -adaptation_sets "id=0,streams=v  id=1,streams=a" \
  
          -threads 8 -seg_duration 5 -hls_playlist true -f dash output/output.mpd

  This works and generates hls files also as expected, one sample m3u8 file below :

  #EXTM3U
  
  #EXT-X-VERSION:7
  
  #EXT-X-MEDIA:TYPE=AUDIO,GROUP-ID="group_A1",NAME="audio_6",DEFAULT=YES,URI="media_6.m3u8"
  
  #EXT-X-STREAM-INF:BANDWIDTH=129663,RESOLUTION=320x168,CODECS="avc1.64000c,mp4a.40.2",AUDIO="group_A1"
  
  media_0.m3u8
  
  
  
  #EXT-X-STREAM-INF:BANDWIDTH=129663,RESOLUTION=640x336,CODECS="avc1.64001e,mp4a.40.2",AUDIO="group_A1"
  
  media_1.m3u8
  
  
  
  #EXT-X-STREAM-INF:BANDWIDTH=129663,RESOLUTION=1280x670,CODECS="avc1.64001f,mp4a.40.2",AUDIO="group_A1"
  
  media_2.m3u8
  
  
  
  #EXT-X-STREAM-INF:BANDWIDTH=330756,RESOLUTION=320x168,CODECS="vp09.00.11.08,mp4a.40.2",AUDIO="group_A1"
  
  media_3.m3u8
  
  
  
  #EXT-X-STREAM-INF:BANDWIDTH=329663,RESOLUTION=640x336,CODECS="vp09.00.21.08,mp4a.40.2",AUDIO="group_A1"
  
  media_4.m3u8
  
  
  
  #EXT-X-STREAM-INF:BANDWIDTH=329663,RESOLUTION=1280x670,CODECS="vp09.00.31.08,mp4a.40.2",AUDIO="group_A1"
  
  media_5.m3u8

  Now as you notice, the Bandwidth is same for resolution of 320x168, 640x336 and 1280x670, which might have happened because of nature of video.

  But the issue with this is in iOS’s AVPlayer it always picks the minimum resolution one and never picks the better resolution stream even if it is available because of same bitrate.

  So the question I want to ask is : is there some option available to ensure - I always have some difference in the bitrates of different resolutions or more specific, bit rate always increase(may be just by few bytes) for increasing resolutions.