Recherche avancée

Sur d’autres sites (4543)

• Rotate video according to rotation metadata and strip off metadata using ffmpeg [on hold]

  12 décembre 2018, par this.lau_

  I’ve got a video with the following metadata :

  Metadata:
  
    rotate          : 90
  
    creation_time   : 2018-12-03T16:13:47.000000Z
  
    handler_name    : VideoHandle
  
  Side data:
  
    displaymatrix: rotation of -90.00 degrees

  And I would like to remove this metadata and rotate the video by whatever rotation value is found there (in this case -90 but it can be anything).

  The result will be a video with the correct orientation and that works with all video players (including those that don’t auto-rotate based on the metadata).

  I’ve tried various commands but couldn’t find anything that would work. Any idea how to do this ?

• Why Matomo is a serious alternative to Google Analytics 360

  12 décembre 2018, par Jake Thornton — Marketing
  There’s no doubt about it, the free version of Google Analytics offers great value when it comes to making data-driven decisions for your business. But as your business starts to grow, so does the need for a more powerful web analytics tool.

  Why would I need to use a different web analytics tool ? It’s because Google Analytics (free version) is very limited when it comes to meeting the needs of a fast growing business whose website plays a pivotal role in converting its customers.

  This is where the Google Analytics 360 suite comes in, which is designed to meet the needs of businesses looking to get more accurate and insightful metrics.

  So what’s holding a growing business back from using Google Analytics 360 ?

  While GA360 sounds like a great option when upgrading your web analytics platform, we have found there are three core reasons holding businesses back from taking the leap :

  • Businesses can’t bear to swallow the US$150,000+ price tag (per year !) that comes with upgrading
  • Businesses can’t rely on GA360 to give them all the insights they need
  • Businesses want more control and ownership of their data

  Thankfully there are (only a few) alternatives and as the leading open-source alternative to Google Analytics, we hope to share insights on why Matomo Analytics can be the perfect solution for anyone at this crossroads in their web analytics journey.

  First, what does Google Analytics 360 offer that Google Analytics (free) doesn’t ?

  There’s no doubt about it, the GA360 suite is designed for larger sized businesses with demanding data limits, big budgets to use across the Google Marketing Platform (Google Adwords, DoubleClick etc.) and to get more advanced reporting visualisations and options.
  

  Data Sampling

  Data sampling is the elephant in the room when it comes to comparing GA360 with the freemium version. This is an entire article in its own right but at a basic level, Google Analytics samples your data (makes assumptions based on patterns) once the number of traffic visiting your website reaches a certain limit.

  Google Analytics provides the following information :

  Ad-hoc queries of your data are subject to the following general thresholds for sampling :

  Analytics Standard : 500k sessions at the property level for the date range you are using

  Analytics 360 : 100M sessions at the view level for the date range you are using

  In short, sampled data means inaccurate data. This is why as businesses grow, GA360 becomes a more attractive prospect because there’s no point making data-driven business decisions based on inaccurate data. This is a key weapon Google uses when selling to large businesses, however, this may not seem as concerning if you’re a small business within the sampled data range. For small businesses though, make sure you know the full extent of how this can affect your metrics, for example, your ecommerce data could be sampled, hence your GA reporting not matching your CRM/Ecommerce store data.

  Benefit of using Matomo : There is no data sampling anywhere in Matomo Analytics, that’s why we say 100% Accurate Data reporting across all plans.

  

  Integration with the Google Marketing Platform

  Yes ok, we’ll admit it, GA does a great job at integrating seamlessly with its own products like Google Ads, Google Optimize etc. with a touch of Salesforce integration ; while GA360 takes this to another level compared to it’s freemium version (integration with Google Search 360, Google Display & Video 360 etc.)

  But… what about non-Google advertising platforms ? Well with Google being a dominant leader as a search engine, web browser, email provider, social media channel ; sometimes Google needs to keep its best interests at heart.

  Google is an online advertising giant and a bonus of Google Search 360 is that you can integrate your Bing Ads, Baidu and Yahoo Japan Search campaigns but that’s about it when it comes to integrations from its direct competitors. 

  Benefit of using Matomo : No biased treatment. You can integrate your Google, Yahoo and Bing search consoles for accurate search engine reporting, and in early 2019, Matomo will be releasing a Google Ads, Bing Ads and Facebook Ads Manager integration feature.

  Roll-Up Reporting
  

  Roll-up reporting lets you combine multiple accounts and properties into one view. This is a great benefit when upgrading from GA freemium to GA360. For example, if you’re a digital agency with multiple clients or you manage multiple websites under the one account, the roll-up reporting feature is wonderful when you need to combine data and reporting, instantly.

  Benefit of using Matomo : Matomo’s got this covered ! Roll-up reporting is available in the Matomo Business package (starting at $29 per month) for cloud hosting or you can purchase as a Premium Feature for On-Premise starting at $99 per year.

  Staying in full control of your data

  Who would have thought that one of biggest reasons people choose Matomo isn’t because of anything that leads to a higher ROI, but for the fact that users want more control of their data.
  

  Matomo’s philosophy around data ownership is simple, you own your data, no one else. If you choose to host Matomo Analytics On-Premise then you are in complete control because your data is stored on your own servers where no one can gain access to it in whichever country you choose.

  So what about when you cloud host Matomo ? For users who don’t have the technical knowledge to host Matomo On-Premise, you can still have 100% data ownership and fully respect your user’s privacy when choosing to host Matomo Analytics through our cloud service.

  The difference between cloud hosting Matomo Analytics vs Google Analytics is that when you choose Matomo, we acknowledge you own the data and we have no right to access it. This means we can’t on-sell it to third-parties, we can’t claim ownership of it, you can export your data at anytime (how awesome is that !) and you can migrate between cloud hosting and hosting on-premise for ultimate flexibility whenever you want.

  Matomo also prides itself in allowing its users to be GDPR compliant with ease with a powerful GDPR Manager.

  Businesses can’t rely on Google Analytics 360 to give them all the insights they need

  Unlike Google Analytics 360, Matomo blends its Premium Web Analytics platform with Conversion Optimization features to allow its users to fully evaluate the user-experience on your website.

  Matomo is designed to be a complete analytics platform, meaning you have everything you need all in the one place which gives you greater insights and better business outcomes.

  
  These features include :

  Premium Web Analytics – You can still (accurately) measure all the basic metrics you love and are familiar with in Google Analytics like Location, Referrer traffic, Multi Attribution, Campaign Tracking and Ecommerce etc.

  Conversion Optimization – Eliminate the need for multiple analytics tools to get what Google Analytics doesn’t offer. These features include Heatmaps, Session Recordings, Form Analytics and more – giving you the best chance possible to convert more traffic by evaluating the user-experience.

  By having one tool for all your features you can integrate metrics, have one single view for all your data and it’s easy to use.

  Enhanced SEO – Get more insights into the performance of your search campaigns with unbiased search engine reporting, keyword ranking positions, integration with multiple search consoles and crawling stats. Google Analytics offers limited features to help with your SEO campaigns and only integrates with Google products.

  Visitor Profiles – Get a detailed life-time evaluation of every user who visits your website.

  Tag Manager – A powerful open-source Tag Manager tool to embed your third-party marketing tags. By being open-source and with our commitment to giving you 100% data ownership, you can always ensure you are in full control.

  Full Matomo vs Google Analytics 360 Comparison Table

  Just putting it out there ...

  Google leads the market with its freemium tool which offers great insights for businesses (fyi – Matomo has a forever free analytics tool too !), but when it comes to upgrading to get accurate reporting (kind of a big deal), owning your own data (a huge deal !) and having a complete range of features to excel ROI for your business, Matomo Analytics is often a preferred option to the Google Analytics 360 suite.

  Matomo is designed to be easy to use, is fully flexible and gives users full peace of mind by respecting user privacy. Want to learn more about the benefits of Matomo ?

• FFMPEG Incorrect Stream Index Matching with -var_stream_map

  28 décembre 2018, par Hugo

  I am using a bash script to run an FFMPEG command to turn an input file called Awoo.mkv into three HLS playlists each with a different resolution, video and audio bitrate.

  This is the script :

  name=gw
  
  
  
  rm /tmp/hls/*
  
  
  
  ./ffmpeg -y \
  
      -stream_loop -1 -re \
  
      -i Awoo.mkv \
  
      -b:v:0 4000k -b:a:0 512k -s:0 1920x1080 -r:0 30 -g:0 90 -preset:0 superfast -tune:0 zerolatency -profile:v:0 high -level:v:0 4 \
  
      -b:v:1 2500k -b:a:1 256k -s:1 1280x720 -r:1 30 -g:1 90 -preset:1 superfast -tune:1 zerolatency -profile:v:1 high -level:v:1 4 \
  
      -b:v:2 800k -b:a:2 255k -s:2 960x540 -r:2 30 -g:2 90 -preset:2 superfast -tune:2 zerolatency -profile:v:2 high -level:v:2 4 \
  
      -hls_time 6 \
  
      -hls_list_size 2 \
  
      -hls_flags delete_segments \
  
      -map 0:v -map 0:a -map 0:v -map 0:a -map 0:v -map 0:a \
  
      -var_stream_map "v:0,a:0 v:1,a:1 v:2,a:2" \
  
      -f hls -master_pl_name "${name}.m3u8" \
  
      -hls_segment_filename "/tmp/hls/${name}_-%d-%v.ts" \
  
      "/tmp/hls/${name}_%v.m3u8"

  This almost works great, but the output is slightly off...

  If you look at these two lines :

  -b:v:1 2500k -b:a:1 256k -s:1 1280x720 -r:1 30 -g:1 90 -preset:1 superfast -tune:1 zerolatency -profile:v:1 high -level:v:1 4 \
  
  -b:v:2 800k -b:a:2 255k -s:2 960x540 -r:2 30 -g:2 90 -preset:2 superfast -tune:2 zerolatency -profile:v:2 high -level:v:2 4 \

  A resolution of 1280x720 should have a bitrate of 2500k, a resolution of 960x540 should have a bitrate of 800k.

  This is the relevant output from FFMPEG :

  Stream #0:2(und): Video: h264 (libx264), yuv420p(progressive), 960x540 [SAR 1:1 DAR 16:9], q=-1--1, 2500 kb/s, 30 fps, 90k tbn, 30 tbc (default)
  
  Metadata:
  
    CREATION_TIME   : 2017-01-27 05:02:53
  
    LANGUAGE        : und
  
    HANDLER_NAME    : VideoHandler
  
    DURATION        : 00:02:24.310000000
  
    encoder         : Lavc58.18.100 libx264
  
  Side data:
  
    cpb: bitrate max/min/avg: 0/0/2500000 buffer size: 0 vbv_delay: -1
  
  Stream #0:3(eng): Audio: aac (LC), 44100 Hz, stereo, fltp, 256 kb/s (default)
  
  Metadata:
  
    LANGUAGE        : eng
  
    DURATION        : 00:02:24.348000000
  
    encoder         : Lavc58.18.100 aac
  
  Stream #0:4(und): Video: h264 (libx264), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], q=-1--1, 800 kb/s, 29 fps, 90k tbn, 29 tbc (default)
  
  Metadata:
  
    CREATION_TIME   : 2017-01-27 05:02:53
  
    LANGUAGE        : und
  
    HANDLER_NAME    : VideoHandler
  
    DURATION        : 00:02:24.310000000
  
    encoder         : Lavc58.18.100 libx264
  
  Side data:
  
    cpb: bitrate max/min/avg: 0/0/800000 buffer size: 0 vbv_delay: -1
  
  Stream #0:5(eng): Audio: aac (LC), 44100 Hz, stereo, fltp, 255 kb/s (default)
  
  Metadata:
  
    LANGUAGE        : eng
  
    DURATION        : 00:02:24.348000000
  
    encoder         : Lavc58.18.100 aac

  Stream #0:2 is given the wrong resolution of 960x540, and therefore also the wrong bitrate of 2500. This should be the resolution of 1280x720, but this is below matched with the bitrate of 800.

  From what I know, the resolutions are showing in the wrong order, if 720 was first and 540 after then everything would match up fine. I’m not sure what’s causing this, I am new to the -var_stream_map.

  If it is relevant, the entire output from FFMPEG is below :

  ffmpeg version 4.0.3-static https://johnvansickle.com/ffmpeg/  Copyright (c) 2000-2018 the FFmpeg developers
  
    built with gcc 6.3.0 (Debian 6.3.0-18+deb9u1) 20170516
  
    configuration: --enable-gpl --enable-version3 --enable-static --disable-debug --disable-ffplay --disable-indev=sndio --disable-outdev=sndio --cc=gcc-6 --enable-fontconfig --enable-frei0r --enable-gnutls --enable-gray --enable-libaom --enable-libfribidi --enable-libass --enable-libvmaf --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librubberband --enable-libsoxr --enable-libspeex --enable-libvorbis --enable-libopus --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg
  
    libavutil      56. 14.100 / 56. 14.100
  
    libavcodec     58. 18.100 / 58. 18.100
  
    libavformat    58. 12.100 / 58. 12.100
  
    libavdevice    58.  3.100 / 58.  3.100
  
    libavfilter     7. 16.100 /  7. 16.100
  
    libswscale      5.  1.100 /  5.  1.100
  
    libswresample   3.  1.100 /  3.  1.100
  
    libpostproc    55.  1.100 / 55.  1.100
  
  Input #0, matroska,webm, from 'Awoo.mkv':
  
    Metadata:
  
      COMPATIBLE_BRANDS: iso6avc1mp41
  
      MAJOR_BRAND     : dash
  
      MINOR_VERSION   : 0
  
      ENCODER         : Lavf56.40.101
  
    Duration: 00:02:24.35, start: 0.000000, bitrate: 1114 kb/s
  
      Stream #0:0(und): Video: h264 (Main), yuv420p(tv, bt709, progressive), 1280x720 [SAR 1:1 DAR 16:9], 29 fps, 29 tbr, 1k tbn, 58 tbc (default)
  
      Metadata:
  
        CREATION_TIME   : 2017-01-27 05:02:53
  
        LANGUAGE        : und
  
        HANDLER_NAME    : VideoHandler
  
        DURATION        : 00:02:24.310000000
  
      Stream #0:1(eng): Audio: vorbis, 44100 Hz, stereo, fltp (default)
  
      Metadata:
  
        LANGUAGE        : eng
  
        DURATION        : 00:02:24.348000000
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
  
    Stream #0:1 -> #0:1 (vorbis (native) -> aac (native))
  
    Stream #0:0 -> #0:2 (h264 (native) -> h264 (libx264))
  
    Stream #0:1 -> #0:3 (vorbis (native) -> aac (native))
  
    Stream #0:0 -> #0:4 (h264 (native) -> h264 (libx264))
  
    Stream #0:1 -> #0:5 (vorbis (native) -> aac (native))
  
  Press [q] to stop, [?] for help
  
  [libx264 @ 0x664d1c0] using SAR=1/1
  
  [libx264 @ 0x664d1c0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
  
  [libx264 @ 0x664d1c0] profile High, level 4.0, 4:2:0, 8-bit
  
  [libx264 @ 0x664d1c0] 264 - core 157 r2935 545de2f - H.264/MPEG-4 AVC codec - Copyleft 2003-2018 - http://www.videolan.org/x264.html - options: cabac=1 ref=1 deblock=1:0:0 analyse=0x3:0x3 me=dia subme=1 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_pskip=1 chroma_qp_offset=0 threads=4 lookahead_threads=4 sliced_threads=1 slices=4 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=1 keyint=90 keyint_min=9 scenecut=40 intra_refresh=0 rc=abr mbtree=0 bitrate=4000 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
  
  [libx264 @ 0x664f080] using SAR=1/1
  
  [libx264 @ 0x664f080] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
  
  [libx264 @ 0x664f080] profile High, level 4.0, 4:2:0, 8-bit
  
  [libx264 @ 0x664f080] 264 - core 157 r2935 545de2f - H.264/MPEG-4 AVC codec - Copyleft 2003-2018 - http://www.videolan.org/x264.html - options: cabac=1 ref=1 deblock=1:0:0 analyse=0x3:0x3 me=dia subme=1 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_pskip=1 chroma_qp_offset=0 threads=4 lookahead_threads=4 sliced_threads=1 slices=4 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=1 keyint=90 keyint_min=9 scenecut=40 intra_refresh=0 rc=abr mbtree=0 bitrate=2500 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
  
  [libx264 @ 0x6680b80] using SAR=1/1
  
  [libx264 @ 0x6680b80] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
  
  [libx264 @ 0x6680b80] profile High, level 4.0, 4:2:0, 8-bit
  
  [libx264 @ 0x6680b80] 264 - core 157 r2935 545de2f - H.264/MPEG-4 AVC codec - Copyleft 2003-2018 - 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=abr mbtree=1 bitrate=800 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
  
  [hls @ 0x6650000] Opening '/tmp/hls/gw_-0-0.ts' for writing
  
  [hls @ 0x6650000] Opening '/tmp/hls/gw_-0-1.ts' for writing
  
  [hls @ 0x6650000] Opening '/tmp/hls/gw_-0-2.ts' for writing
  
  Output #0, hls, to '/tmp/hls/gw_%v.m3u8':
  
    Metadata:
  
      COMPATIBLE_BRANDS: iso6avc1mp41
  
      MAJOR_BRAND     : dash
  
      MINOR_VERSION   : 0
  
      encoder         : Lavf58.12.100
  
      Stream #0:0(und): Video: h264 (libx264), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=-1--1, 4000 kb/s, 30 fps, 90k tbn, 30 tbc (default)
  
      Metadata:
  
        CREATION_TIME   : 2017-01-27 05:02:53
  
        LANGUAGE        : und
  
        HANDLER_NAME    : VideoHandler
  
        DURATION        : 00:02:24.310000000
  
        encoder         : Lavc58.18.100 libx264
  
      Side data:
  
        cpb: bitrate max/min/avg: 0/0/4000000 buffer size: 0 vbv_delay: -1
  
      Stream #0:1(eng): Audio: aac (LC), 44100 Hz, stereo, fltp, 512 kb/s (default)
  
      Metadata:
  
        LANGUAGE        : eng
  
        DURATION        : 00:02:24.348000000
  
        encoder         : Lavc58.18.100 aac
  
      Stream #0:2(und): Video: h264 (libx264), yuv420p(progressive), 960x540 [SAR 1:1 DAR 16:9], q=-1--1, 2500 kb/s, 30 fps, 90k tbn, 30 tbc (default)
  
      Metadata:
  
        CREATION_TIME   : 2017-01-27 05:02:53
  
        LANGUAGE        : und
  
        HANDLER_NAME    : VideoHandler
  
        DURATION        : 00:02:24.310000000
  
        encoder         : Lavc58.18.100 libx264
  
      Side data:
  
        cpb: bitrate max/min/avg: 0/0/2500000 buffer size: 0 vbv_delay: -1
  
      Stream #0:3(eng): Audio: aac (LC), 44100 Hz, stereo, fltp, 256 kb/s (default)
  
      Metadata:
  
        LANGUAGE        : eng
  
        DURATION        : 00:02:24.348000000
  
        encoder         : Lavc58.18.100 aac
  
      Stream #0:4(und): Video: h264 (libx264), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], q=-1--1, 800 kb/s, 29 fps, 90k tbn, 29 tbc (default)
  
      Metadata:
  
        CREATION_TIME   : 2017-01-27 05:02:53
  
        LANGUAGE        : und
  
        HANDLER_NAME    : VideoHandler
  
        DURATION        : 00:02:24.310000000
  
        encoder         : Lavc58.18.100 libx264
  
      Side data:
  
        cpb: bitrate max/min/avg: 0/0/800000 buffer size: 0 vbv_delay: -1
  
      Stream #0:5(eng): Audio: aac (LC), 44100 Hz, stereo, fltp, 255 kb/s (default)
  
      Metadata:
  
        LANGUAGE        : eng
  
        DURATION        : 00:02:24.348000000
  
        encoder         : Lavc58.18.100 aac
  
  [hls @ 0x6650000] Opening '/tmp/hls/gw_0.m3u8.tmp' for writing6.50 bitrate=N/A dup=12 drop=0 speed=0.965x    
  
  [hls @ 0x6650000] Opening '/tmp/hls/gw_1.m3u8.tmp' for writing
  
  [hls @ 0x6650000] Opening '/tmp/hls/gw_2.m3u8.tmp' for writing
  
  [hls @ 0x6650000] Opening '/tmp/hls/gw.m3u8' for writing