Recherche avancée

Sur d’autres sites (15431)

• Copy m3u8 segment files on a single mp4 format

  26 juin 2018, par parsa

  Hi I used below command for copy m3u8 segment files to a single mp4 file :
  I run this command on c# Process class.

      -y -i "D:\OtherProjects\ConvertProj\video\2018\4\1\m3u8\200p\out.m3u8"  
  
      -y -i "D:\OtherProjects\ConvertProj\video\2018\4\1\m3u8\360p\out.m3u8"  
  
      -y -i "D:\OtherProjects\ConvertProj\video\2018\4\1\m3u8\480p\out.m3u8"  
  
      -y -i "D:\OtherProjects\ConvertProj\video\2018\4\1\m3u8\720p\out.m3u8" 
  
  -map 0 -c:v copy -c:a copy -threads 0 "D:\OtherProjects\ConvertProj\video\2018\4\1\1-200.mp4" 
  
  -map 1 -c:v copy -c:a copy -threads 0 "D:\OtherProjects\ConvertProj\video\2018\4\1\1-360.mp4" 
  
  -map 2 -c:v copy -c:a copy -threads 0 "D:\OtherProjects\ConvertProj\video\2018\4\1\1-480.mp4" 
  
  -map 3 -c:v copy -c:a copy -threads 0 "D:\OtherProjects\ConvertProj\video\2018\4\1\1.mp4" 

  I get this Error :

  [hls,applehttp @ 00000000047e3400] Failed to open segment of playlist 0
  
      Last message repeated 353 times
  
  [hls,applehttp @ 00000000047e3400] Error when loading first segment 'out0.ts'
  
  D:\OtherProjects\ConvertProj\video\2018\4\6208-3905956\m3u8\200p\out.m3u8: Invalid data found when processing input

  What is the problem ? Waht I must be do ? Is this a bug ?

• ffmpeg : How to dowmix from 2 channels 5.1 to 2 stereo streams

  26 avril 2018, par spiceemeup

  I have a mov file with a video stream and several audio streams in two different languages. Here is the output of ffprobe :

  ffprobe version N-89525-gb178278 Copyright (c) 2007-2017 the FFmpeg developers
  
   built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  
   configuration: --prefix=/home/ubuntu/ffmpeg_build --pkg-config-flags=--static 
  
  --extra-cflags=-I/home/ubuntu/ffmpeg_build/include --extra-ldflags=- 
  
  L/home/ubuntu/ffmpeg_build/lib --extra-libs='-lpthread -lm' -- 
  
  bindir=/home/ubuntu/bin --enable-gpl --enable-libass --enable-libtwolame -- 
  
  enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora -- 
  
  enable-libvorbis --enable-libx264 --enable-nonfree
  
  libavutil      56.  6.100 / 56.  6.100
  
  libavcodec     58.  8.100 / 58.  8.100
  
  libavformat    58.  3.100 / 58.  3.100
  
  libavdevice    58.  0.100 / 58.  0.100
  
  libavfilter     7.  7.100 /  7.  7.100
  
  libswscale      5.  0.101 /  5.  0.101
  
  libswresample   3.  0.101 /  3.  0.101
  
  libpostproc    55.  0.100 / 55.  0.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'sony_trim2.mov':
  
  Metadata:
  
  major_brand     : qt
  
  minor_version   : 0
  
  compatible_brands: qt
  
  creation_time   : 2018-04-24T11:15:52.000000Z
  
  com.apple.finalcutstudio.media.uuid: BEF32C67-F7C2-4D6C-B4AD-B79255E1414B
  
  Duration: 00:01:26.32, start: 0.000000, bitrate: 197731 kb/s
  
  Stream #0:0(eng): Video: prores (apch / 0x68637061), yuv422p10le(bt709, 
  
  progressive), 1920x1080, 179299 kb/s, SAR 1:1 DAR 16:9, 25 fps, 25 tbr, 25 tbn, 25 tbc (default)
  
  Metadata:
  
    creation_time   : 2018-04-24T11:15:52.000000Z
  
    handler_name    : Core Media Data Handler
  
    encoder         : Apple ProRes 422 (HQ)
  
    timecode        : 00:58:32:15
  
  Stream #0:1(fra): Audio: pcm_s24le (lpcm / 0x6D63706C), 48000 Hz, 1 channels (FL), s32 (24 bit), 1152 kb/s (default)
  
  Metadata:
  
    creation_time   : 2018-04-24T11:15:52.000000Z
  
    handler_name    : Core Media Data Handler
  
  Stream #0:2(fra): Audio: pcm_s24le (lpcm / 0x6D63706C), 48000 Hz, 1 channels (FR), s32 (24 bit), 1152 kb/s (default)
  
  Metadata:
  
    creation_time   : 2018-04-24T11:15:52.000000Z
  
    handler_name    : Core Media Data Handler
  
  Stream #0:3(fra): Audio: pcm_s24le (lpcm / 0x6D63706C), 48000 Hz, mono, s32 (24 bit), 1152 kb/s (default)
  
  Metadata:
  
    creation_time   : 2018-04-24T11:15:52.000000Z
  
    handler_name    : Core Media Data Handler
  
  Stream #0:4(fra): Audio: pcm_s24le (lpcm / 0x6D63706C), 48000 Hz, 1 channels (LFE), s32 (24 bit), 1152 kb/s (default)
  
  Metadata:
  
    creation_time   : 2018-04-24T11:15:52.000000Z
  
    handler_name    : Core Media Data Handler
  
  Stream #0:5(fra): Audio: pcm_s24le (lpcm / 0x6D63706C), 48000 Hz, 1 channels (BL), s32 (24 bit), 1152 kb/s (default)
  
  Metadata:
  
    creation_time   : 2018-04-24T11:15:52.000000Z
  
    handler_name    : Core Media Data Handler
  
  Stream #0:6(fra): Audio: pcm_s24le (lpcm / 0x6D63706C), 48000 Hz, 1 channels (BR), s32 (24 bit), 1152 kb/s (default)
  
  Metadata:
  
    creation_time   : 2018-04-24T11:15:52.000000Z
  
    handler_name    : Core Media Data Handler
  
  Stream #0:7(eng): Audio: pcm_s24le (lpcm / 0x6D63706C), 48000 Hz, 1 channels (FL), s32 (24 bit), 1152 kb/s (default)
  
  Metadata:
  
    creation_time   : 2018-04-24T11:15:52.000000Z
  
    handler_name    : Core Media Data Handler
  
  Stream #0:8(eng): Audio: pcm_s24le (lpcm / 0x6D63706C), 48000 Hz, 1 channels (FR), s32 (24 bit), 1152 kb/s (default)
  
  Metadata:
  
    creation_time   : 2018-04-24T11:15:52.000000Z
  
    handler_name    : Core Media Data Handler
  
  Stream #0:9(eng): Audio: pcm_s24le (lpcm / 0x6D63706C), 48000 Hz, mono, s32 (24 bit), 1152 kb/s (default)
  
  Metadata:
  
    creation_time   : 2018-04-24T11:15:52.000000Z
  
    handler_name    : Core Media Data Handler
  
  Stream #0:10(eng): Audio: pcm_s24le (lpcm / 0x6D63706C), 48000 Hz, 1 channels (LFE), s32 (24 bit), 1152 kb/s (default)
  
  Metadata:
  
    creation_time   : 2018-04-24T11:15:52.000000Z
  
    handler_name    : Core Media Data Handler
  
  Stream #0:11(eng): Audio: pcm_s24le (lpcm / 0x6D63706C), 48000 Hz, 1 channels (BL), s32 (24 bit), 1152 kb/s (default)
  
  Metadata:
  
    creation_time   : 2018-04-24T11:15:52.000000Z
  
    handler_name    : Core Media Data Handler
  
  Stream #0:12(eng): Audio: pcm_s24le (lpcm / 0x6D63706C), 48000 Hz, 1 channels (BR), s32 (24 bit), 1152 kb/s (default)
  
  Metadata:
  
    creation_time   : 2018-04-24T11:15:52.000000Z
  
    handler_name    : Core Media Data Handler
  
  Stream #0:13(fra): Audio: pcm_s24le (lpcm / 0x6D63706C), 48000 Hz, 1 channels (DL), s32 (24 bit), 1152 kb/s (default)
  
  Metadata:
  
    creation_time   : 2018-04-24T11:15:52.000000Z
  
    handler_name    : Core Media Data Handler
  
  Stream #0:14(fra): Audio: pcm_s24le (lpcm / 0x6D63706C), 48000 Hz, 1 channels (DR), s32 (24 bit), 1152 kb/s (default)
  
  Metadata:
  
    creation_time   : 2018-04-24T11:15:52.000000Z
  
    handler_name    : Core Media Data Handler
  
  Stream #0:15(eng): Audio: pcm_s24le (lpcm / 0x6D63706C), 48000 Hz, 1 channels (DL), s32 (24 bit), 1152 kb/s (default)
  
  Metadata:
  
    creation_time   : 2018-04-24T11:15:52.000000Z
  
    handler_name    : Core Media Data Handler
  
  Stream #0:16(eng): Audio: pcm_s24le (lpcm / 0x6D63706C), 48000 Hz, 1 channels (DR), s32 (24 bit), 1152 kb/s (default)
  
  Metadata:
  
    creation_time   : 2018-04-24T11:15:52.000000Z
  
    handler_name    : Core Media Data Handler
  
  Stream #0:17(eng): Data: none (tmcd / 0x64636D74) (default)
  
  Metadata:
  
    creation_time   : 2018-04-24T11:15:52.000000Z
  
    handler_name    : Core Media Data Handler
  
    timecode        : 00:58:32:15

  I’d like to downmix audio streams #0:1 -> #0:6 to one stereo stream and in the same time downmix audio streams #0:7 -> #0:12 to another stereo stream.
  I tried to map streams and use -ac 2 command but it didn’t work.

  ffmpeg -i myfile.mov -filter:v scale=854x480 -ac 2 -af "pan=stereo| FL < FL + 0.5*FC + 0.6*BL + 0.6*SL | FR < FR + 0.5*FC + 0.6*BR + 0.6*SR" -map 0:1 -map 0:2 -map 0:3 -map 0:4 -map 0:5 -map 0:6 -acodec libmp3lame -b:a 256k -ar 48000 -y -strict experimental -map 0:0 -x264opts bitrate=2000:vbv-maxrate=2000:vbv-bufsize=166 -vcodec libx264 -profile:v high -level:v 4.0 -pix_fmt yuv420p -aspect 16:9 -r 25 -g 50 -f mpegts -muxrate 2000K -y myfile.ts

  Any idea ?
  Thanks in advance for your help.

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