Recherche avancée

Sur d’autres sites (9790)

• How to make Matomo GDPR compliant in 12 steps

  3 avril 2018, par InnoCraft

  Important note : this blog post has been written by digital analysts, not lawyers. The purpose of this article is to briefly show you where Matomo is entering into play within the GDPR process. This work comes from our interpretation of the UK privacy commission : ICO. It cannot be considered as professional legal advice. So as GDPR, this information is subject to change. We strongly advise you to have a look at the different privacy authorities in order to have up to date information.

  The General Data Protection Regulation (EU) 2016/679, also referred to RGPD in French, Datenschutz-Grundverordnung, DS-GVO in German, is a regulation on data protection and privacy for all individuals within the European Union. It concerns organizations worldwide dealing with EU citizens and will come into force on the 25th May 2018.

  The GDPR applies to ‘personal data’ meaning any information relating to an identifiable person who can be directly or indirectly identified in particular by reference to an identifier. It includes cookies, IP addresses, User ID, location, and any other data you may have collected.

  We will list below the 12 steps recommended by the UK privacy commissioner in order to be GDPR compliant and what you need to do for each step.

  The 12 steps of GDPR compliance according to ICO and how it fit with Matomo

  As mentioned in one of our previous blog post about GDPR, if you are not collecting any personal data with Matomo, then you are not concerned about what is written below.

  If you are processing personal data in any way, here are the 12 steps to follow along with some recommendations on how to be GDPR compliant with Matomo :

  1 – Awareness

  Make sure that people within your organization know that you are using Matomo in order to analyze traffic on the website/app. If needed, send them the link to the “What is Matomo ?” page.

  2 – Information you hold

  List all the personal data you are processing with Matomo within your record of processing activities. We are personally using the template provided by ICO which is composed of a set of 30 questions you need to answer regarding your use of Matomo. We have published an article which walks you through the list of questions specifically in the use case of Matomo Analytics. Please be aware that personal data may be also tracked in non-obvious ways for example as part of page URLs or page titles.

  3 – Communicating privacy information

  a – Add a privacy notice

  Add a privacy notice wherever you are using Matomo in order to collect personal data. Please refer to the ICO documentation in order to learn how to write a privacy notice. You can learn more in our article about creating your privacy notice for Matomo Analytics. Make sure that a privacy policy link is always available on your website or app.

  b – Add Matomo to your privacy policy page

  Add Matomo to the list of technologies you are using on your privacy policy page and add all the necessary information to it as requested in the following checklist. To learn more check out our article about Privacy policy.

  4 – Individuals’ rights

  Make sure that your Matomo installation respects all the individuals’ rights. To make it short, you will need to know the features in Matomo that you need to use to respect user rights (right of access, right of rectification, right of erasure…). These features are available starting in Matomo 3.5.0 released on May 8th : GDPR tools for Matomo (User guide).

  5 – Subject access requests

  Make sure that you are able to answer an access request from a data subject for Matomo. For example, when a person would like to access her or his personal data that you have collected about her or him, then you will need to be you able to provide her or him with this information. We recommend you design a process for this like “Who is dealing with it ?” and check that it is working. If you can answer to the nightmare letter, then you are ready. The needed features for this in Matomo will be available soon.

  6 – Lawful basis for processing personal data

  There are different lawful basis you can use under GDPR. It can be either “Legitimate interest” or “Explicit consent”. Do not forget to mention it within your privacy policy page. Read more in our article about lawful basis.

  7 – Consent

  Users should be able to remove their consent at any time. By chance, Matomo is providing a feature in order to do just that : add the opt-out feature to your privacy policy page.
  We are also offering a tool that allows you optionally to require consent before any data is tracked. This will be useful if a person should be only tracked after she or he has given explicit consent to be tracked.

  8 – Children

  If your website or app is targeted for children and you are using Matomo, extra measures will need to be taken. For example you will need to write your privacy policy even more clear and moreover getting parents consent if the child is below 13. As it is a very specific case, we strongly recommend you to follow this link for further information.

  9 – Data breaches

  As you may be collecting personal data with Matomo, you should also check your “data breach procedure” to define if a leak may have consequences on the privacy of the data subject. Please consult ICO’s website for further information.

  10 – Data Protection by Design and Data Protection Impact Assessments

  Ask yourself if you really need to process personal data within Matomo. If the data you are processing within Matomo is sensitive, we strongly recommend you to make a Data Protection Impact Assessment. A software is available from the The open source PIA software helps to carry out data protection impact assessment, by French Privacy Commissioner : CNIL.

  11 – Data Protection Officers

  If you are reading this article and you are the Data Protection Officer (DPO), you will not be concerned by this step. If that’s not the case, your duty is to provide to the DPO (if your business has a DPO) our blog post in order for her or him to ask you questions regarding your use of Matomo. Note that your DPO can also be interested in the different data that Matomo can process : “What data does Matomo track ?” (FAQ).

  12 – International

  Matomo data is hosted wherever you want. So according to the location of the data, you will need to show specific safeguard except for EU. For example regarding the USA, you will have to check if your web hosting platform is registered to the Privacy Shield : privacyshield.gov/list
  Note : our Matomo cloud infrastructure is based in France.

  That’s the end of this blog post. As GDPR is a huge topic, we will release many more blog posts in the upcoming weeks. If there are any Matomo GDPR topic related posts you would like us to write, please feel free to contact us.

  The post How to make Matomo GDPR compliant in 12 steps appeared first on Analytics Platform - Matomo.

• Capturing audio and video from different sources, how to sync ?

  16 février 2017, par aerodavo

  Here is my code :

  Lapaki:~ Lapaki$ /Users/Lapaki/Desktop/ffmpeg -f avfoundation -video_size 960x540 -pixel_format uyvy422 -framerate ntsc -thread_queue_size 8B -i "XI:none" -f avfoundation -thread_queue_size 8B -i "none:XI" -vf 'crop=iw-240:ih:120:0' -af 'asetpts=PTS+.58735/TB' -pix_fmt yuv420p -aspect 4:3 -s 720x480 -q:v 3 -maxrate 5000k -bufsize 2000k -acodec ac3 -ac 2 -ab 256k -ar 48000 -f dvd /Users/Lapaki/Desktop/FF\ Test/`date +%F`\ `date +%H_%M_%S`.mpg
  
  ffmpeg version 3.2.3-tessus Copyright (c) 2000-2017 the FFmpeg developers
  
    built with Apple LLVM version 8.0.0 (clang-800.0.42.1)
  
    configuration: --cc=/usr/bin/clang --prefix=/opt/ffmpeg --extra-version=tessus --enable-avisynth --enable-fontconfig --enable-gpl --enable-libass --enable-libbluray --enable-libfreetype --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopus --enable-libschroedinger --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzmq --enable-version3 --disable-ffplay --disable-indev=qtkit --disable-indev=x11grab_xcb
  
    libavutil      55. 34.101 / 55. 34.101
  
    libavcodec     57. 64.101 / 57. 64.101
  
    libavformat    57. 56.101 / 57. 56.101
  
    libavdevice    57.  1.100 / 57.  1.100
  
    libavfilter     6. 65.100 /  6. 65.100
  
    libswscale      4.  2.100 /  4.  2.100
  
    libswresample   2.  3.100 /  2.  3.100
  
    libpostproc    54.  1.100 / 54.  1.100
  
  Input #0, avfoundation, from 'XI:none':
  
    Duration: N/A, start: 648413.295900, bitrate: N/A
  
      Stream #0:0: Video: rawvideo (UYVY / 0x59565955), uyvy422, 960x540, 29.97 fps, 29.97 tbr, 1000k tbn, 1000k tbc
  
  Input #1, avfoundation, from 'none:XI':
  
    Duration: N/A, start: 648413.884042, bitrate: 3072 kb/s
  
      Stream #1:0: Audio: pcm_f32le, 48000 Hz, stereo, flt, 3072 kb/s
  
  Output #0, dvd, to '/Users/Lapaki/Desktop/FF Test/2017-02-16 04_16_33.mpg':
  
    Metadata:
  
      encoder         : Lavf57.56.101
  
      Stream #0:0: Video: mpeg2video (Main), yuv420p, 720x480 [SAR 8:9 DAR 4:3], q=2-31, 200 kb/s, 29.97 fps, 90k tbn, 29.97 tbc
  
      Metadata:
  
        encoder         : Lavc57.64.101 mpeg2video
  
      Side data:
  
        cpb: bitrate max/min/avg: 5000000/0/200000 buffer size: 2000000 vbv_delay: -1
  
      Stream #0:1: Audio: ac3, 48000 Hz, stereo, fltp, 256 kb/s
  
      Metadata:
  
        encoder         : Lavc57.64.101 ac3
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (rawvideo (native) -> mpeg2video (native))
  
    Stream #1:0 -> #0:1 (pcm_f32le (native) -> ac3 (native))
  
  Press [q] to stop, [?] for help
  
  [swscaler @ 0x7f8e0c8ab400] Warning: data is not aligned! This can lead to a speedloss
  
  frame=   33 fps=0.0 q=3.0 size=     266kB time=00:00:01.06 bitrate=2051.9kbits/sframe=   49 fps= 48 q=3.0 size=     444kB time=00:00:01.54 bitrate=2358.8kbits/sframe=   64 fps= 42 q=3.0 size=     652kB time=00:00:02.08 bitrate=2560.5kbits/sframe=   79 fps= 39 q=3.0 size=     838kB time=00:00:02.59 bitrate=2642.4kbits/sframe=   94 fps= 37 q=3.0 size=    1022kB time=00:00:03.07 bitrate=2720.0kbits/sframe=  109 fps= 36 q=3.0 size=    1208kB time=00:00:03.59 bitrate=2756.5kbits/sframe=  124 fps= 35 q=3.0 size=    1406kB time=00:00:04.07 bitrate=2830.0kbits/sframe=  127 fps= 35 q=3.0 Lsize=    1474kB time=00:00:04.19 bitrate=2876.4kbits/s dup=12 drop=0 speed=1.15x    
  
  video:1310kB audio:113kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 3.604597%

  The start of Input #0 is 648413.295900, and the start of Input #1 is 648413.884042.

  I’ve been able to keep the audio and video in very close sync by subtracting the two values (which I assume are wallclock values), and using the asetpts audio filter to delay the audio stream of the recorded mpeg-2 file by that amount.

  I’d like to be able to do this exactly though, and that value changes slightly every time I start a new capture. Not to mention, I’d like to be able to do this reliably on different machines, where I assume the value will most likely be different, thus using a calculation as opposed to a fixed number is obviously the best option, if it’s possible.

  Is there a way to subtract the wallclock start time of input #0 from the wallclock start time of input #1 ? I’d like to do this inside the asetpts filter, instead of manually finding the difference from a previous run, which again is slightly different every time...

  I was thinking something like -af asetpts=PTS-([1:0]RTCSTART-[0:0]RTCSTART)/TB might work, but I have no idea how to format it.

  Thanks in advance !

• ffmpeg livestream alway stop after 160hours streamming

  2 avril 2018, par JerryJumper88

  I use ffmpeg with this code to run stream youtube 24/7 from Windows VPS. But stream alway stop after 160-167 hours and I don’t know why.

     dir/b/s "C:\Users\NASA\Desktop\ffmpeg\bin\1\*.mp4" > list.txt
  
  :encode video
  
  :loop
  
  for /F "delims=;" %%F in (list.txt)  DO ffmpeg -re -i "%%F" -vcodec libx264 -preset veryfast -maxrate 2500k -bufsize 3368k -vf "format=yuv420p" -g 60 -acodec libmp3lame -b:a 198k -ar 44100 -metadata title="" -metadata artist="" -metadata album_artist="" -metadata album="" -metadata date="" -metadata track="" -metadata genre="" -metadata publisher="" -metadata encoded_by="" -metadata copyright="" -metadata composer="" -metadata performer="" -metadata TIT1="" -metadata TIT3="" -metadata disc="" -metadata TKEY="" -metadata TBPM="" -metadata language="eng" -metadata encoder="" -f flv -s 1280x720 rtmp://a.rtmp.youtube.com/live2/xxxx-xxxx-xxxx-xxxx
  
  goto loop

  And this is stream log. I google " Larger timestamp than 24-bit : 0xffffff9f" but nothing about this error. I contacted to admin server system, he comfirmed that has no issue connection. Then I tried again in Windows 7 and Windows server 2012, same result, still drop after 160h on youtube.

      Larger timestamp than 24-bit: 0xffffff9f
  
  [flv @ 000000000275c820] Failed to update header with correct duration.
  
  [flv @ 000000000275c820] Failed to update header with correct filesize.
  
  frame=10575 fps= 30 q=-1.0 Lsize=   88449kB time=00:05:52.52 bitrate=2055.4kbits
  
  /s speed=0.998x
  
  video:79769kB audio:8263kB subtitle:0kB other streams:0kB global headers:0kB mux
  
  ing overhead: 0.474711%
  
  [libx264 @ 0000000002760560] frame I:182   Avg QP:20.08  size: 41314
  
  [libx264 @ 0000000002760560] frame P:4955  Avg QP:22.97  size: 11557
  
  [libx264 @ 0000000002760560] frame B:5438  Avg QP:23.75  size:  3108
  
  [libx264 @ 0000000002760560] consecutive B-frames: 29.6%  3.9%  5.0% 61.5%
  
  [libx264 @ 0000000002760560] mb I  I16..4: 23.0% 49.4% 27.5%
  
  [libx264 @ 0000000002760560] mb P  I16..4: 10.8% 15.7%  3.3%  P16..4: 17.4%  6.3
  
  %  2.4%  0.0%  0.0%    skip:44.1%
  
  [libx264 @ 0000000002760560] mb B  I16..4:  1.7%  1.6%  0.2%  B16..8: 12.4%  3.4
  
  %  0.3%  direct: 4.9%  skip:75.4%  L0:46.3% L1:46.0% BI: 7.6%
  
  [libx264 @ 0000000002760560] 8x8 transform intra:51.7% inter:36.6%
  
  [libx264 @ 0000000002760560] coded y,uvDC,uvAC intra: 38.7% 59.1% 14.8% inter: 4
  
  .5% 13.5% 0.3%
  
  [libx264 @ 0000000002760560] i16 v,h,dc,p: 43% 36% 17%  4%
  
  [libx264 @ 0000000002760560] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 31% 31% 21%  2%  2%
  
   3%  3%  3%  4%
  
  [libx264 @ 0000000002760560] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 29% 29% 15%  4%  5%
  
   5%  5%  5%  4%
  
  [libx264 @ 0000000002760560] i8c dc,h,v,p: 41% 27% 27%  4%
  
  [libx264 @ 0000000002760560] Weighted P-Frames: Y:0.1% UV:0.0%
  
  [libx264 @ 0000000002760560] kb/s:1853.78
  
  
  
  C:\Users\NASA\Desktop\ffmpeg\bin>ffmpeg -re -i "C:\Users\NASA\Desktop\ffmpeg\bin
  
  \1\6 x24.mp4" -vcodec libx264 -preset veryfast -maxrate 2500k -bufsize
  
  3368k -vf "format=yuv420p" -g 60 -acodec libmp3lame -b:a 198k -ar 44100 -metadat
  
  a title="" -metadata artist="" -metadata album_artist="" -metadata album="" -met
  
  adata date="" -metadata track="" -metadata genre="" -metadata publisher="" -meta
  
  data encoded_by="" -metadata copyright="" -metadata composer="" -metadata perfor
  
  mer="" -metadata TIT1="" -metadata TIT3="" -metadata disc="" -metadata TKEY="" -
  
  metadata TBPM="" -metadata language="eng" -metadata encoder="" -f flv -s 1280x72
  
  0 rtmp://a.rtmp.youtube.com/live2/xxxx-xxxx-xxxx-xxxx
  
  ffmpeg version N-87353-g183fd30 Copyright (c) 2000-2017 the FFmpeg developers
  
    built with gcc 7.2.0 (GCC)
  
    configuration: --enable-gpl --enable-version3 --enable-cuda --enable-cuvid --e
  
  nable-d3d11va --enable-dxva2 --enable-libmfx --enable-nvenc --enable-avisynth --
  
  enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv
  
  --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-li
  
  bfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug -
  
  -enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enabl
  
  e-libopenh264 --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-li
  
  bsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolam
  
  e --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx
  
   --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable
  
  -libxavs --enable-libxvid --enable-libxml2 --enable-libzimg --enable-lzma --enab
  
  le-zlib
  
    libavutil      55. 76.100 / 55. 76.100
  
    libavcodec     57.106.101 / 57.106.101
  
    libavformat    57. 82.101 / 57. 82.101
  
    libavdevice    57.  8.101 / 57.  8.101
  
    libavfilter     6.105.100 /  6.105.100
  
    libswscale      4.  7.103 /  4.  7.103
  
    libswresample   2.  8.100 /  2.  8.100
  
    libpostproc    54.  6.100 / 54.  6.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'C:\Users\NASA\Desktop\ffmpeg\bin\1\6 x.mp4':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: isommp42
  
      creation_time   : 2017-10-16T20:51:09.000000Z
  
    Duration: 00:03:22.04, start: 0.000000, bitrate: 1300 kb/s
  
      Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709)
  
  , 1280x720 [SAR 1:1 DAR 16:9], 1105 kb/s, 30 fps, 30 tbr, 15360 tbn, 60 tbc (def
  
  ault)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, flt
  
  p, 191 kb/s (default)
  
      Metadata:
  
        creation_time   : 2017-10-16T20:51:09.000000Z
  
        handler_name    : IsoMedia File Produced by Google, 5-11-2011
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
  
    Stream #0:1 -> #0:1 (aac (native) -> mp3 (libmp3lame))
  
  Press [q] to stop, [?] for help
  
  [libx264 @ 00000000029d0020] using SAR=1/1
  
  [libx264 @ 00000000029d0020] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
  
  AVX FMA3 BMI2 AVX2
  
  [libx264 @ 00000000029d0020] profile High, level 3.1
  
  [libx264 @ 00000000029d0020] 264 - core 152 r2851 ba24899 - H.264/MPEG-4 AVC cod
  
  ec - Copyleft 2003-2017 - http://www.videolan.org/x264.html - options: cabac=1 r
  
  ef=1 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=2 psy=1 psy_rd=1.00:0.00 mixed
  
  _ref=0 me_range=16 chroma_me=1 trellis=0 8x8dct=1 cqm=0 deadzone=21,11 fast_pski
  
  p=1 chroma_qp_offset=0 threads=3 lookahead_threads=1 sliced_threads=0 nr=0 decim
  
  ate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_a
  
  dapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=1 keyint=60 keyint_min=6 s
  
  cenecut=40 intra_refresh=0 rc_lookahead=10 rc=crf mbtree=1 crf=23.0 qcomp=0.60 q
  
  pmin=0 qpmax=69 qpstep=4 vbv_maxrate=2500 vbv_bufsize=3368 crf_max=0.0 nal_hrd=n
  
  one filler=0 ip_ratio=1.40 aq=1:1.00
  
  frame=   14 fps=0.0 q=0.0 size=       0kB time=-577014:32:22.77 bitrate=  -0.0kb
  
  Output #0, flv, to 'rtmp://a.rtmp.youtube.com/live2/xxxx-xxxx-xxxx-xxxx':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: isommp42
  
      encoder         : Lavf57.82.101
  
      Stream #0:0(und): Video: h264 (libx264) ([7][0][0][0] / 0x0007), yuv420p(pro
  
  gressive), 1280x720 [SAR 1:1 DAR 16:9], q=-1--1, 30 fps, 1k tbn, 30 tbc (default
  
  )
  
      Metadata:
  
        handler_name    : VideoHandler
  
        encoder         : Lavc57.106.101 libx264
  
      Side data:
  
        cpb: bitrate max/min/avg: 2500000/0/0 buffer size: 3368000 vbv_delay: -1
  
      Stream #0:1(eng): Audio: mp3 (libmp3lame) ([2][0][0][0] / 0x0002), 44100 Hz,
  
   stereo, fltp, 198 kb/s (default)
  
      Metadata:
  
        creation_time   : 2017-10-16T20:51:09.000000Z
  
        handler_name    : IsoMedia File Produced by Google, 5-11-2011
  
        encoder         : Lavc57.106.101 libmp3lame
  
  frame=   29 fps= 28 q=29.0 size=      77kB time=00:00:00.41 bitrate=1498.7kbits/
  
  frame=   44 fps= 28 q=29.0 size=     129kB time=00:00:00.94 bitrate=1118.8kbits/
  
  frame=   60 fps= 29 q=29.0 size=     180kB time=00:00:01.88 bitrate= 781.8kbits/
  
  frame=   76 fps= 30 q=26.0 size=     220kB time=00:00:02.37 bitrate= 758.1kbits/
  
  frame=   91 fps= 29 q=29.0 size=     311kB time=00:00:02.84 bitrate= 895.3kbits/
  
  frame=  107 fps= 30 q=29.0 size=     356kB time=00:00:03.34 bitrate= 870.9kbits/
  
  frame=  122 fps= 30 q=29.0 size=     395kB time=00:00:03.84 bitrate= 843.3kbits/
  
  frame=  137 fps= 30 q=29.0 size=     428kB time=00:00:04.31 bitrate= 813.2kbits/
  
  frame=  153 fps= 30 q=29.0 size=     535kB time=00:00:04.80 bitrate= 911.9kbits/
  
  frame=  168 fps= 30 q=29.0 size=     598kB time=00:00:05.30 bitrate= 923.0kbits/
  
  frame=  184 fps= 30 q=29.0 size=     661kB time=00:00:05.77 bitrate= 938.2kbits/
  
  frame=  199 fps= 30 q=29.0 size=     757kB time=00:00:06.27 bitrate= 989.2kbits/
  
  frame=  215 fps= 30 q=29.0 size=     833kB time=00:00:06.76 bitrate=1008.2kbits/
  
  frame=  230 fps= 30 q=29.0 size=     893kB time=00:00:07.23 bitrate=1011.1kbits/
  
  frame=  246 fps= 30 q=29.0 size=     963kB time=00:00:07.73 bitrate=1019.8kbits/
  
  frame=  261 fps= 30 q=29.0 size=    1049kB time=00:00:08.23 bitrate=1043.7kbits/
  
  frame=  276 fps= 30 q=29.0 size=    1117kB time=00:00:08.70 bitrate=1052.2kbits/
  
  frame=  292 fps= 30 q=29.0 size=    1166kB time=00:00:09.19 bitrate=1038.3kbits/
  
  frame=  307 fps= 30 q=29.0 size=    1216kB time=00:00:09.69 bitrate=1027.8kbits/
  
  frame=  322 fps= 30 q=29.0 size=    1304kB time=00:00:10.18 bitrate=1048.4kbits/
  
  frame=  338 fps= 30 q=29.0 size=    1363kB time=00:00:11.15 bitrate=1000.8kbits/
  
  s speed=0.985x