Recherche avancée

Sur d’autres sites (6577)

• Player downloads all moof part of a fragment mp4 file before playing

  28 mars 2023, par happyz90

  I converted a mp4 to fragment mp4 with the following command :

  


  ffmpeg -i ./input.mp4 -y -b:a 32k -vcodec libx265 -b:v 320k -bufsize 320k -tag:v hvc1 -color_primaries bt709 -color_trc bt709 -colorspace bt709 -c:a libfdk_aac -profile:a aac_he_v2 -movflags faststart+frag_keyframe+empty_moov+dash+global_sidx -chunk_duration 500000000 -max_muxing_queue_size 1024 ./output.mp4


  


  But when playing, the player send many http requests to download all the moof part :

  


  

  


  

  


  But I think in normal case the player only need to download the head part of the video file to play.

  


  So is there anything wrong with my ffmpeg parameters ? Please help me. Thank you.

  


• Julia FFMPEG string not recognizing format specifier

  12 janvier 2024, par veryverde

  I have this code :

  


  using Pkg
#Pkg.add("FFMPEG")
using FFMPEG

imagesdirectory = "my/paths/images"
framerate = 30
gifname = "my/paths/images/my-animation-name.gif"
FFMPEG.ffmpeg_exe(`-framerate $(framerate) -f image2 -i $(imagesdirectory)/%07d.png -y $(gifname)`)


  


  This code is taken from here
In it, FFMPEG is supposed to match those files that have 7 digits, which is what the %07d . That is, of the format 0000123.png, for example.

  


  This is, for whatever reason, not parsing it correctly, and reading the string directly :

  


  [image2 @ 0x7fc9fb00a000] Could find no file with path '/my/paths/images/%07d.png' and index in the range 0-4
/my/paths/images/%07d.png: No such file or directory


  


  I am not sure how to input this matching so that it is read properly, i.e., so that it matches all those files with exactly 7 digits, and a .png extension. For others, from the source of the code, it seems to be working, but I have no idea why it would parse it incorrectly. I've downloaded FFMPEG specifically for this task, so it ought to be up-to-date.

  


• GDPR compliance for Matomo’s Premium Features like Heatmaps & Session Recording, Form Analytics, Media Analytics & co

  27 avril 2018, par InnoCraft

  The General Data Protection Regulation (EU) 2016/679, also referred to as RGPD in French, Datenschutz-Grundverordnung, DS-GVO in German, is fast-approaching. It is now less than 30 days until GDPR applies to most businesses around the world on 25th May 2018. If you haven’t heard of this new regulation yet, I recommend you check out our GDPR guide which we continue to expand regularly to get you up to speed with it.

  GDPR compliance in Matomo

  We are currently adding several new features to Matomo to get you GDPR ready. You will have for example the possibility to delete and export data for data subjects, delete and anonymize previously tracked data, anonymize the IP address and location, ask for consent, and more. A beta version with these features is already available. We will release more blog posts and user guides about these features soon and just recently published a post on how to avoid collecting personal information in the first place soon.

  If you are still using Piwik, we highly recommend you update to a recent version of Matomo as all versions of Piwik will NOT be GDPR compliant.

  GDPR compliance for premium features

  InnoCraft, the company of the makers of Matomo, are offering various premium features for your self-hosted Matomo so you can be sure to make the right decisions and continuously grow your business. These features are also available on the cloud-hosted version of Matomo.

  If you are now wondering how GDPR applies to these features, you will be happy to hear that none of them collect any personal information except for possibly Heatmaps & Session Recording and the WooCommerce integration. All of them also support all the new upcoming GDPR features like the possibility to export and delete data. It is important that you update your Matomo Premium Features to the latest version to use these features.

  Making Heatmaps & Session Recording GDPR compliant

  We have added several new features to make it easy for you to be GDPR compliant and in many cases you might not even have to do anything. Some of the changes include :

  • Keystrokes (text entered into form fields) are no longer captured by default.
  • You may enable the capturing of keystrokes, and all keystrokes will be anonymized by default.
  • You may whitelist certain form fields to be recorded in plain text. However, fields that likely contain personal or sensitive information like passwords, phone numbers, addresses, credit card details, names, email addresses, and more will be always anonymized to protect user privacy. (this has always been the case but we have now included many more fields).

  How personal information may still be recorded

  Nevertheless, Heatmaps and Session Recordings may still record personal or sensitive information if you show them as part of the regular website as plain text (and not as part of a form field). The below example shows an email address for a paypal account as well as a name and VAT information as a regular content.

  

  To anonymize such information, simply add a data-matomo-mask attribute to your website :

  <span data-matomo-mask>example@example.com</span>

  You can read more about this in the developer guide “Masking content on your website”.

  WooCommerce Integration

  The WooCommerce integration may record an Order ID when a customer purchases something on your shop. As the Order ID is an identifier which could be linked with your shop to identify an individual, it may be considered as personal information. Matomo now offers an option to automatically anonymize this Order ID so it is no longer considered as personal information. To enable this feature, log in to your Matomo and go to “Administration => Anonymize Data”.

  GDPR compliance for third party plugins on the Matomo Marketplace

  The Matomo Marketplace currently features over 80 free plugins. Over 50 of them are compatible with the latest Matomo 3.X version and most of them should support Matomo’s new GDPR features out of the box. If you are concerned by GDPR and are not sure if a third party plugin stores any personal information, we highly recommend you ask the developer of this plugin about the compliance.

  You can find a link to the plugin’s issue tracker by going to a plugin page and then clicking on “Github” on the bottom right.

  

  If you are a plugin developer, please read our developer guide “GDPR & How do I make my Matomo plugin compliant”.

  The post GDPR compliance for Matomo’s Premium Features like Heatmaps & Session Recording, Form Analytics, Media Analytics & co appeared first on Analytics Platform - Matomo.