Recherche avancée

Sur d’autres sites (6596)

• 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

• How to complete your privacy policy with Matomo analytics under GDPR

  25 avril 2018, par InnoCraft

  Important note : this blog post has been written by digital analysts, not lawyers. The purpose of this article is to show you how to complete your existing privacy policy by adding the parts related to Matomo in order to comply with GDPR. 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. This blog post contains public sector information licensed under the Open Government Licence v3.0.

  Neither the GDPR official text or ICO are mentioning the words ‘privacy policy’. They use the words ‘privacy notice’ instead. As explained within our previous blog post about “How to write a privacy notice for Matomo”, the key concepts of privacy information are transparency and accessibility which are making the privacy notice very long.

  As a result, we prefer splitting the privacy notice into two parts :

  • Privacy notice : straight to the point information about how personal data is processed at the time of the data collection. This is the subject of the our previous blog post.
  • Privacy policy : a web page explaining in detail all the personal data you are processing and how visitors/users can exercise their rights. This is the blog post you are reading.

  Writing/updating your privacy policy page can be one of the most challenging task under GDPR.

  In order to make this mission less complicated, we have designed a template which you can use to complete the privacy policy part that concerns Matomo.

  Which information should your privacy policy include ?

  ICO is giving a clear checklist about what a privacy policy has to contain when the data is obtained from the data subject :

  1. Identity and contact details of the controller and where applicable, the controller’s representative and the data protection officer.
  2. Purpose of the processing and the legal basis for the processing.
  3. The legitimate interests of the controller or third party, where applicable.
  4. Any recipient or categories of recipients of the personal data.
  5. Details of transfers to third country and safeguards.
  6. Retention period or criteria used to determine the retention period.
  7. The existence of each of data subject’s rights.
  8. The right to withdraw consent at any time, where relevant.
  9. The right to lodge a complaint with a supervisory authority.
  10. Whether the provision of personal data part of a statutory or contractual requirement or obligation and possible consequences of failing to provide the personal data.
  11. The existence of automated decision-making, including profiling and information about how decisions are made, the significance and the consequences.

  So in order to use Matomo with due respect to GDPR you need to answer each of those points within your privacy policy.

  Matomo’s privacy policy template

  You will find below some examples to each point requested by GDPR. Those answers are just guidelines, they are not perfect, feel free to copy/paste them according to your needs.

  Note that this template needs to be tweaked according to the lawful basis you choose.

  1 – About Matomo

  Note : this part should describe the data controller instead, which is your company. But as you may already have included this part within your existing privacy policy, we prefer here to introduce what is Matomo.

  Matomo is an open source web analytics platform. A web analytics platform is used by a website owner in order to measure, collect, analyse and report visitors data for purposes of understanding and optimizing their website. If you would like to see what Matomo looks like, you can access a demo version at : https://demo.matomo.org.

  2 – Purpose of the processing

  Matomo is used to analyse the behaviour of the website visitors to identify potential pitfalls ; not found pages, search engine indexing issues, which contents are the most appreciated… Once the data is processed (number of visitors reaching a not found pages, viewing only one page…), Matomo is generating reports for website owners to take action, for example changing the layout of the pages, publishing some fresh content… etc.

  Matomo is processing the following personal data :

  Pick up the one you are using :

  • Cookies
  • IP address
  • User ID
  • Custom Dimensions
  • Custom Variables
  • Order ID
  • Location of the user

  And also :

  • Date and time
  • Title of the page being viewed
  • URL of the page being viewed
  • URL of the page that was viewed prior to the current page
  • Screen resolution
  • Time in local timezone
  • Files that were clicked and downloaded
  • Link clicks to an outside domain
  • Pages generation time
  • Country, region, city
  • Main Language of the browser
  • User Agent of the browser

  This list can be completed with additional features such as :

  • Session recording, mouse events (movements, content forms and clicks)
  • Form interactions
  • Media interactions
  • A/B Tests

  Pick up one of the two :

  1. The processing of personal data with Matomo is based on legitimate interests, or :
  2. The processing of personal data with Matomo is based on explicit consent. Your privacy is our highest concern. That’s why we will not process any personal data with Matomo unless you give us clear explicit consent.

  3 – The legitimate interests

  This content applies only if you are processing personal data based on legitimate interests. You need here to justify your legitimate interests to process personal data. It is a set of questions described here.

  Processing your personal data such as cookies is helping us identify what is working and what is not on our website. For example, it helps us identify if the way we are communicating is engaging or not and how we can organize the structure of the website better. Our team is benefiting from the processing of your personal data, and they are directly acting on the website. By processing your personal data, you can profit from a website which is getting better and better.

  Without the data, we would not be able to provide you the service we are currently offering to you. Your data will be used only to improve the user experience on our website and help you find the information you are looking for.

  4 – Recipient of the personal data

  The personal data received through Matomo are sent to :

  • Our company.
  • Our web hosting provider : name and contact details of the web hosting provider.

  Note : If you are using the Matomo Analytics Cloud by InnoCraft the web hosting provider is “InnoCraft, 150 Willis St, 6011 Wellington, New Zealand“.

  5 – Details of transfers to third country and safeguards

  Matomo data is hosted in Name of the country.

  If the country mentioned is not within the EU, you need to mention here the appropriate safeguards, for example : our data is hosted in the United States within company XYZ, registered to the Privacy Shield program.

  Note : The Matomo Analytics Cloud by InnoCraft is currently hosted in France. If you are using the cloud-hosted solution of Matomo, use “France” as name of the country.

  6 – Retention period or criteria used to determine the retention period

  We are keeping the personal data captured within Matomo for a period of indicate here the period.

  Justify your choice, for example : as our data is hosted in France, we are applying the French law which defines a retention period of no more than 13 months. You can set the retention period in Matomo by using the following feature.

  7 – The existence of each of the data subject’s rights

  If you are processing personal data with Matomo based on legitimate interest :

  As Matomo is processing personal data on legitimate interests, you can exercise the following rights :

  • Right of access : you can ask us at any time to access your personal data.
  • Right to erasure : you can ask us at any time to delete all the personal data we are processing about you.
  • Right to object : you can object to the tracking of your personal data by using the following opt-out feature :

  Insert here the opt-out feature.

  If you are processing personal data with Matomo based on explicit consent :

  As Matomo is processing personal data on explicit consent, you can exercise the following rights :

  • Right of access : you can ask us at any time to access your personal data.
  • Right to erasure : you can ask us at any time to delete all the personal data we are processing about you.
  • Right to portability : you can ask us at any time for a copy of all the personal data we are processing about you in Matomo.
  • Right to withdraw consent : you can withdraw your consent at any time by clicking on the following button.

  8 – The right to withdraw consent at any time

  If you are processing personal data under the consent lawful basis, you need to include the following section :

  You can withdraw at any time your consent by clicking here (insert here the Matomo tracking code to remove consent).

  9 – The right to lodge a complaint with a supervisory authority

  If you think that the way we process your personal data with Matomo analytics is infringing the law, you have the right to lodge a complaint with a supervisory authority.

  10 – Whether the provision of personal data is part of a statutory or contractual requirement ; or obligation and possible consequences of failing to provide the personal data

  If you wish us to not process any personal data with Matomo, you can opt-out from it at any time. There will be no consequences at all regarding the use of our website.

  11 – The existence of automated decision-making, including profiling and information about how decisions are made, the significance and the consequences

  Matomo is not doing any profiling.

   

  That’s the end of our blog post. We hope you enjoyed reading it and that it will help you get through the GDPR compliance process. If you have any questions dealing with this privacy policy in particular, do not hesitate to contact us.

  The post How to complete your privacy policy with Matomo analytics under GDPR appeared first on Analytics Platform - Matomo.

• Can't render or join Hindi ligatures in FFmpeg drawtext

  28 février 2024, par praveenK

  I have been trying to drawtext over a video in Hindi language but some characters are not rendering properly :

  


  

  


  The proper way is :

  


  

  


  I have enabled libfridi, libfontconfig and libfreetype.

  


  Even tried on Ubuntu.

  


  ANS : please see comment to Pops answer.