Recherche avancée

Sur d’autres sites (9509)

• 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.

• Import FFMPEG Library to Android

  2 juin 2017, par Gio Vanno

  First, I’m new in this Import thing

  I’ve compiled latest version of ffmpeg with NDK r14b,
  and managed to get some Library after compiling(like libavutil.so,libavcodec.so,libavfilter.so,etc)

  Click here for pic

  but im a bit confused importing it to my android project.

  First, I want to make an Audio editing app that can merge several mp3 file at specific time, and adjust volume (Increase or Decrease its sound) mp3 file.

  I’ve read about ffmpeg recently, since most people recommended to use this Library.

  For merging :

  -https://superuser.com/questions/1092291/merge-many-audio-files-with-specific-positions/1092346#1092346

  For adjust volume :

  -Decode MP3, then increase the audio volume, and then encode the new audio

  What i want to ask is :

  -from guardian’s ffmpeg project and WritingMinds ffmpeg lib (can’t post the link since i got not enough rep and this 2 are often mentioned in stackoverflow), does this 2 Libraries have what i needed ? I’m a bit confused in this thing. An explanation would be a help.

  -from http://ffmpeg-android.blogspot.co.id/ i cant run the ndk-build command at the last part. How should i use it ?

  Thank you in advance !

• FFmpeg - selecting appropriate bitrate for VP9 encoding

  11 janvier 2018, par fastily

  I am looking to encode a 4k video shot with iPhone 6s in VP9 in the best quality possible.

  For reference, stream data of the video I would like to encode, via ffprobe :

  Duration: 00:00:10.48, start: 0.000000, bitrate: 46047 kb/s
  
      Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 3840x2160, 45959 kb/s, 29.98 fps, 29.97 tbr, 600 tbn, 1200 tbc (default)
  
      Metadata:
  
        creation_time   : 2017-03-13T21:12:56.000000Z
  
        handler_name    : Core Media Data Handler
  
        encoder         : H.264
  
      Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, mono, fltp, 79 kb/s (default)
  
      Metadata:
  
        creation_time   : 2017-03-13T21:12:56.000000Z
  
        handler_name    : Core Media Data Handler

  I am using the following FFmpeg commands, based on these instructions (see Best Quality (Slowest) Recommended Settings section).

  1. ffmpeg -i INPUT.mov -c:v libvpx-vp9 -pass 1 -b:v 46000K -threads 4 -speed 4 -g 9999 -an -f webm -y /dev/null
  2. ffmpeg -I INPUT.mov -c:v libvpx-vp9 -pass 2 -b:v 46000K -threads 4 -speed 0 -g 9999 -an -f webm OUTPUT.webm

  Is there a best practice to select an optimal -b:v value such that the resulting video is visually indistinguishable from the original ? I have tried values ranging from 36000K-46000K, but these result in massive files with an overall bitrate exceeding the target bitrate.

  Thanks in advance !