Sur d’autres sites (2669)

• Using ffmpeg to overlay dvdsub subtitles

  7 mai 2019, par ib11

  I am trying to overlay a dvdsub file pair (*.idx + *.sub) to a video file.

  Here is the sub pair.

  This is the batch script with the command line I am trying to use :

  @echo off
  
  set srcVidFile1="myvideo.mov"
  
  set srcSubFile=mysub.sub
  
  set srcIdxFile=mysub.idx
  
  set destFile=D:\testsub.mp4
  
  
  
  ffmpeg.exe -i %srcVidFile1% -i %srcSubFile% -i %srcIdxFile% 
  
      -filter_complex "[0:v][1:s]overlay" -c:s dvdsub -c:v 
  
      libx264 -crf 24 -c:a aac -b:a 160K -ar 48K -strict -2 -y 
  
      %destFile%

  This however only accepts 720x576 VOBsub files. And also the color gets inverted.

  My video however is 1080p and do have a 1920x1080 VOBsub file pair, but when I trying use them, I get an error sub2video : rectange (xxx xxx xxx xxx) overflowing 720 576

  Looks like adding -canvas_size 1920x1080 before -i %srcSubFile% handles the error on the canvas size. But I can’t figure out the color.

  The full output :

      ffmpeg version N-81516-gbe07c25 Copyright (c) 2000-2016 the FFmpeg developers
  
        built with gcc 5.4.0 (GCC)
  
        configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-dxva2 --enable-libmfx --enable-nvenc --enable-avisynth --enable-bzlib --enable-libebur128 --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-decklink --enable-zlib
  
        libavutil      55. 29.100 / 55. 29.100
  
        libavcodec     57. 54.101 / 57. 54.101
  
        libavformat    57. 48.101 / 57. 48.101
  
        libavdevice    57.  0.102 / 57.  0.102
  
        libavfilter     6. 58.100 /  6. 58.100
  
        libswscale      4.  1.100 /  4.  1.100
  
        libswresample   2.  1.100 /  2.  1.100
  
        libpostproc    54.  0.100 / 54.  0.100
  
      Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'myvideo.mov':
  
        Metadata:
  
          major_brand     : qt  
  
          minor_version   : 537199360
  
          compatible_brands: qt  
  
          creation_time   : 2017-07-18T19:00:46.000000Z
  
          timecode        : 00:59:58;00
  
        Duration: 00:01:19.01, start: 0.000000, bitrate: 146880 kb/s
  
          Stream #0:0(eng): Video: dnxhd (DNXHD) (AVdn / 0x6E645641), yuv422p(tv, bt709/unknown/unknown), 1920x1080, 145344 kb/s, 29.97 fps,
  
  29.97 tbr, 29970 tbn, 29970 tbc (default)
  
          Metadata:
  
            creation_time   : 2017-07-18T19:00:46.000000Z
  
            handler_name    : Apple Alias Data Handler
  
            encoder         : Avid DNxHD Codec
  
          Stream #0:1(eng): Audio: pcm_s16le (sowt / 0x74776F73), 48000 Hz, stereo, s16, 1536 kb/s (default)
  
          Metadata:
  
            creation_time   : 2017-07-18T19:00:46.000000Z
  
            handler_name    : Apple Alias Data Handler
  
          Stream #0:2(eng): Data: none (tmcd / 0x64636D74) (default)
  
          Metadata:
  
            creation_time   : 2017-07-18T19:01:18.000000Z
  
            handler_name    : Apple Alias Data Handler
  
            timecode        : 00:59:58;00
  
      Input #1, mpeg, from 'mysub.sub':
  
        Duration: 00:00:52.88, start: 3600.042000, bitrate: 10 kb/s
  
          Stream #1:0[0x20]: Subtitle: dvd_subtitle
  
      Input #2, vobsub, from 'mysub.idx':
  
        Duration: N/A, bitrate: N/A
  
          Stream #2:0[0x0](en): Subtitle: dvd_subtitle, 1920x1080 (default)
  
      [mpeg @ 0000000002de4580] sub2video: using 720x576 canvas
  
      [libx264 @ 00000000005234c0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2
  
      [libx264 @ 00000000005234c0] profile High, level 4.0
  
      [libx264 @ 00000000005234c0] 264 - core 148 r2705 3f5ed56 - H.264/MPEG-4 AVC codec - Copyleft 2003-2016 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=6 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=24.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
  
      [mp4 @ 00000000005218a0] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead.
  
          Last message repeated 2 times
  
      Output #0, mp4, to 'D:\testsub.mp4':
  
        Metadata:
  
          major_brand     : qt  
  
          minor_version   : 537199360
  
          compatible_brands: qt  
  
          timecode        : 00:59:58;00
  
          encoder         : Lavf57.48.101
  
          Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv420p, 1920x1080, q=-1--1, 0.03 fps, 11988 tbn, 29.97 tbc (default)
  
          Metadata:
  
            encoder         : Lavc57.54.101 libx264
  
          Side data:
  
            cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
  
          Stream #0:1(eng): Audio: aac (LC) ([64][0][0][0] / 0x0040), 48000 Hz, stereo, fltp, delay 1024, padding 0, 160 kb/s (default)
  
          Metadata:
  
            creation_time   : 2017-07-18T19:00:46.000000Z
  
            handler_name    : Apple Alias Data Handler
  
            encoder         : Lavc57.54.101 aac
  
          Stream #0:2: Subtitle: dvd_subtitle (dvdsub) ([224][0][0][0] / 0x00E0), 720x480
  
          Metadata:
  
            encoder         : Lavc57.54.101 dvdsub
  
      Stream mapping:
  
        Stream #0:0 (dnxhd) -> overlay:main (graph 0)
  
        Stream #1:0 (dvdsub) -> overlay:overlay (graph 0)
  
        overlay (graph 0) -> Stream #0:0 (libx264)
  
        Stream #0:1 -> #0:1 (pcm_s16le (native) -> aac (native))
  
        Stream #1:0 -> #0:2 (dvd_subtitle (dvdsub) -> dvd_subtitle (dvdsub))
  
      Press [q] to stop, [?] for help
  
      sub2video: rectangle (942 858 163 60) overflowing 720 576
  
          Last message repeated 1 times
  
      frame=   33 fps=0.0 q=0.0 size=       0kB time=00:00:07.08 bitrate=   0.1kbits/s speed=14.1x    
  
      frame=   63 fps= 62 q=30.0 size=      10kB time=00:00:07.08 bitrate=  11.1kbits/s speed=7.01x    
  
      frame=   91 fps= 59 q=30.0 size=      30kB time=00:00:07.08 bitrate=  34.7kbits/s speed= 4.6x    
  
      frame=  112 fps= 55 q=30.0 size=     197kB time=00:00:07.08 bitrate= 227.9kbits/s speed=3.45x    
  
      frame=  124 fps= 47 q=30.0 size=     407kB time=00:00:07.08 bitrate= 470.6kbits/s speed=2.69x    
  
      frame=  137 fps= 44 q=30.0 size=     639kB time=00:00:07.08 bitrate= 738.6kbits/s speed=2.26x    
  
      frame=  152 fps= 41 q=30.0 size=     861kB time=00:00:07.08 bitrate= 995.4kbits/s speed=1.89x    
  
      frame=  163 fps= 37 q=30.0 size=    1002kB time=00:00:07.08 bitrate=1158.6kbits/s speed=1.63x    
  
      frame=  175 fps= 36 q=30.0 size=    1412kB time=00:00:07.08 bitrate=1633.3kbits/s speed=1.46x    
  
      frame=  187 fps= 35 q=30.0 size=    1642kB time=00:00:07.31 bitrate=1838.4kbits/s speed=1.36x    
  
      frame=  202 fps= 34 q=30.0 size=    1892kB time=00:00:07.82 bitrate=1979.7kbits/s speed=1.31x    
  
      frame=  213 fps= 33 q=30.0 size=    2071kB time=00:00:08.19 bitrate=2071.2kbits/s speed=1.26x    
  
      sub2video: rectangle (419 785 1209 133) overflowing 720 576
  
      frame=  225 fps= 32 q=30.0 size=    2363kB time=00:00:09.54 bitrate=2028.5kbits/s speed=1.36x    
  
      frame=  236 fps= 31 q=30.0 size=    2554kB time=00:00:09.54 bitrate=2192.6kbits/s speed=1.26x    
  
      frame=  249 fps= 31 q=30.0 size=    2760kB time=00:00:09.54 bitrate=2369.7kbits/s speed=1.18x    
  
      frame=  262 fps= 30 q=30.0 size=    2957kB time=00:00:09.83 bitrate=2463.4kbits/s speed=1.14x    
  
      frame=  272 fps= 29 q=30.0 size=    3111kB time=00:00:10.15 bitrate=2509.4kbits/s speed=1.09x    
  
      frame=  283 fps= 29 q=30.0 size=    3796kB time=00:00:10.51 bitrate=2957.1kbits/s speed=1.07x    
  
      sub2video: rectangle (942 858 163 60) overflowing 720 576
  
      frame=  289 fps= 28 q=30.0 size=    4144kB time=00:00:13.62 bitrate=2491.4kbits/s speed=1.32x    
  
      frame=  297 fps= 27 q=30.0 size=    4613kB time=00:00:13.62 bitrate=2773.6kbits/s speed=1.26x    
  
      frame=  304 fps= 27 q=30.0 size=    5036kB time=00:00:13.62 
  
  
  
      [---TRUNCATED REST OF FRAMES---]
  
  
  
      video:94601kB audio:1616kB subtitle:52kB other streams:0kB global headers:0kB muxing overhead: 0.085206%
  
      [libx264 @ 00000000005234c0] frame I:35    Avg QP:23.92  size:153135
  
      [libx264 @ 00000000005234c0] frame P:958   Avg QP:26.88  size: 69163
  
      [libx264 @ 00000000005234c0] frame B:1375  Avg QP:26.60  size: 18365
  
      [libx264 @ 00000000005234c0] consecutive B-frames: 22.2%  0.7%  1.3% 75.8%
  
      [libx264 @ 00000000005234c0] mb I  I16..4: 11.8% 84.0%  4.2%
  
      [libx264 @ 00000000005234c0] mb P  I16..4:  3.2% 22.6%  0.4%  P16..4: 40.9% 10.7%  6.7%  0.0%  0.0%    skip:15.4%
  
      [libx264 @ 00000000005234c0] mb B  I16..4:  0.3%  2.2%  0.0%  B16..8: 44.9%  2.2%  0.4%  direct: 2.8%  skip:47.2%  L0:45.9% L1:51.3% BI: 2.8%
  
      [libx264 @ 00000000005234c0] 8x8 transform intra:86.2% inter:89.3%
  
      [libx264 @ 00000000005234c0] coded y,uvDC,uvAC intra: 76.4% 65.9% 37.2% inter: 23.4% 29.3% 3.5%
  
      [libx264 @ 00000000005234c0] i16 v,h,dc,p: 18% 42%  5% 34%
  
      [libx264 @ 00000000005234c0] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 10%  9% 47%  5%  6%  5%  6%  5%  6%
  
      [libx264 @ 00000000005234c0] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 15% 18% 17%  7% 11%  9% 10%  6%  7%
  
      [libx264 @ 00000000005234c0] i8c dc,h,v,p: 63% 16% 16%  5%
  
      [libx264 @ 00000000005234c0] Weighted P-Frames: Y:5.2% UV:2.9%
  
      [libx264 @ 00000000005234c0] ref P L0: 50.5% 14.8% 22.5% 11.6%  0.6%
  
      [libx264 @ 00000000005234c0] ref B L0: 87.9%  9.7%  2.4%
  
      [libx264 @ 00000000005234c0] ref B L1: 95.2%  4.8%
  
      [libx264 @ 00000000005234c0] kb/s:9808.13
  
      [aac @ 0000000000524340] Qavg: 574.088

  Original subtitle :
  

  Rendered frame :
  

  I would like to input the 1920x1080 VOBsub file pair and overlay it on the 1080p video with 24bit original colors.

  Can somebody give me the correct command line for this ?

  And as it seems that the VOBsub are low res, is there any means that allow overlaying 1920x1080 24 bit pngs using ffmpeg ?

• Révision 115671 : Début de modification du plugin pour intégrer la nouvelle gestion des catégories...

  14 juin 2019, par eric@smellup.net

  - configuration de l’utilisation des catégories et tags : par défaut c’est non
  - si on l’utilise, la mise à jour ne se fait plus via le XML mais via le plugin SVP Typologie qui transmet les associations plugin-type via l’API REST fournie par le module SVP API.
  - mise à jour du schéma pour lancer le vidage du champ categorie sur la table spip_plugins.

• Exceeded GA’s 10M hits data limit, now what ?

  21 juin 2019, par Joselyn Khor
  Exceeded GA’s 10M hits data limit, now what ? Matomo has the answers

  “Your data volume (1XXM hits) exceeds the limit of 10M hits per month as outlined in our Terms of Service. If you continue to exceed the limit, we will stop processing new data on XXX 21, 2019. Learn more about possible solutions.”

  Yikes. Alarm bells were ringing when a Google Analytics free user came to us faced with this notice. Let’s call him ‘Mark’. Mark had reached the limits on the data he could collect through Google Analytics and was shocked by the limited options available to fix the problem, without blowing the budget. The thoughts racing through his head were :

  • “What happens to all my data ?”
  • “What if Google starts charging USD150K now ?”

  Then he came across Matomo and decided to get in touch with our support team …

  “Can you fix this issue ?” he asked us.

  “Absolutely !” we said.

  We’ll get back to helping Mark in a minute. For now let’s go over why this was such a dilemma for him.

  In order to resolve this data limits issue, one of the solutions was for him to upgrade to Google Analytics 360, which meant shelling out USD150,000 per year for their 1 billion hits per month option. Going from free to USD150,000 was too much of a stretch for a growing company.

  “Your data volume (1XXM hits) exceeds the limit of 10M hits per month …”, what did this message mean ?

  With the free version, Mark could collect up to 10 million “hits” per month, per account. Going over meant Google Analytics could stop collecting any more data for free as outlined in their Terms.

  Google Analytics’ Terms of Service (2018, sec. 2) states, “Subject to Section 15, the Service is provided without charge to You for up to 10 million Hits per month per account.”[1]

  In general, what’s a "hit" ?

  Data being sent to Google Analytics. It can be a transaction, event, social interaction or pageview - these all produce what Google calls a “hit”.

  

  And their Analytics Help Data Limits (n.d.) support page makes clear that : “If a property sends more hits per month to Analytics than allowed by the Analytics Terms of Service, there is no assurance that the excess hits will be processed. If the property’s hit volume exceeds this limit, a warning may be displayed in the user interface and you may be prevented from accessing reports.”[2]

  

  Possible solutions

  So the possible solutions given by Google Analytics’ Data Limits support page were (also shown in image below) :

  • To pay USD150K to upgrade to Google Analytics 360
  • To send fewer hits by setting up sampling
  • Or choose the slightly less relevant option to upgrade mobile app tracking to Google Analytics for Firebase.

  Without the means to pay, the free version was fast becoming inaccessible for Mark as he was facing a future where he risked no longer having access to up-to-date data used in his business’ reporting.

  Mark was facing a problem that potentially didn’t have a cost-effective solution.

  

  So what can you really do about it ?

  This is where we can help provide some assistance. If you’re reading this article, we’ll assume you can relate to Mark and share with you the advice on options we gave him.

  Options :

  One option posed by Google is for you to send fewer hits by auditing your data collection processes

  If you really don’t have the budget, you’ll need to reassess your data collection priorities and go over your strategies to see what is necessary to track, and what isn’t.

  • Make sure you know what you’re tracking and why. Look at what websites are being tracked by Google and into what properties.
  • Go through what data you’re tracking and decide what is or isn’t of value.
  • Set up data sampling, this however, will lead to inaccurate data.

  From here you can start to course correct. If you’ve found data you’re not using for analysis, get rid of these events/pageviews in your Google Analytics.

  But the limitations here are that eventually, you’re going to run out of irrelevant metrics and everything you’re tracking will be essential. So you’ll hit another brick wall and return to the same situation.

  Option 2 – Ignore and continue using the free version of Google Analytics

  With this option, you’ll have to bear the business risks involved by basing decisions off of analytics reports that may or may not be updated. In this case, you may still get contacted about exceeding the limits. As the free service is provided for only up to 10 million hits, once you’ve gone over them, you’re violating what’s stipulated in the Terms of Service. 

  There’s also the warning that “… you may be prevented from accessing reports” (Data limits, n.d.). So while we may not know for certain what Google Analytics will do, in this case it may be better to be safe rather than sorry by acting quickly to resolve it. 

  Option 3 –The Matomo solution. Upgrade to a web analytics platform that can handle your demanding data requirements

  Save money while continuing to gain valuable insights by moving over to Matomo Analytics (recommended)

  This is where you can save up to USD130,000 a year. As well as that, the transition from Google Analytics to the Matomo Cloud is a seamless experience as setup and maintenance is taken care of by our experts.

  For example, you can get up to 15M pageviews for USD1,612.50/month (or USD19,350/year) on the Essentials plan.

  Or even 25M pageviews for USD2400/month (or USD24000/year) on the Business plan – which offers additional web analytics and conversion optimization resources.

  Matomo Cloud is a great option if you’re looking for a secure, cost-effective and powerful analytics solution. You also get what Google Analytics could never offer you : full control and ownership of your own data and privacy. 

  No need to worry about losing your Google Analytics data because …

  Now you can import your historic Google Analytics data directly into your Matomo with the Google Analytics Importer tool. Simply follow the step-by-step guide to get started for free.

  Along with savings you can get :

  • A solution for the data limits issue forever. You choose the right plan to suit your data needs and adapt as you continue growing
  • 100% accurate data (no data sampling)
  • 100% data ownership of all your information without signing away your data to a third party
  • Powerful web analytics and conversion optimization features
  • Matomo Tag Manager
  • Easy setup
  • Support from Matomo’s specialists

  Learn more about Matomo Cloud pricing.

  

  Or go for Matomo On-Premise

  If you have the in-house infrastructure to support self-hosting Matomo on your own servers then there’s also the option of Matomo On-Premise. Here you’ll get full security knowing the data is on your own servers. 

  Setup will also require technical knowledge. There will also be costs associated with acquiring your own servers, and keeping up with regular maintenance and updates. With On-Premise you get maximum flexibility, with no data limits whatsoever. But if you’re coming over from Google Analytics and don’t have the infrastructure and team to host On-Premise, the Matomo Cloud could be right for you.

  Learn more about Matomo On-Premise.

  Where do you go from here ?

  Getting 10 millions hits per month is no small feat, it’s actually pretty fantastic. But if it means having to shell out USD150,000 just to be able to continue with Google Analytics, we feel your problem could be fixed with Matomo Cloud. You could then put the rest of the money you save to better use.

  If you choose Matomo, you now have the option to : 

  • Raise your data limits for a fraction of Google Analytics 360’s price
  • Get a comprehensive range of analytics features for the most impactful insights to ensure your website continues excelling
  • Get data that’s not sampled – meaning 100% accuracy in your reports
  • Migrate your data easily with the help of Matomo’s support team

  We’ll have you covered. 

  By sharing with you the options and advice we gave to Mark, we hope you’ll be able to find a solution that makes your life easier and solves the issue of data restrictions forever.

  The team at Matomo is here to help you every step of the way to ensure a stress-free transition from Google Analytics if that is what works best for you.

  For next steps, why not check out our pricing page to see what could suit your needs !

  References :

  [1] Terms of Service. (2018, July 24). In Google Analytics Terms of Service. Retrieved June 12, 2019, from https://www.google.com/analytics/terms/us.html

  [2] Data limits. (n.d.). In Analytics Help Data limits. Retrieved June 12, 2019, from https://support.google.com/analytics/answer/1070983?hl=en