Sur d’autres sites (7462)

• 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

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

• Quick stream from file which exists

  4 mai 2017, par parsa

  I implement live streaming from mp4 video file which exists on the path with ffmpeg under hls format.
  When my video file have the quality greater than hd720 , in encoding there are so many delays for creating .ts fragments.
  I mean the .ts fragments slowly produced on my path,and because of it I have so many delays in showing the stream.
  Here is my ffmpeg code for streaming :

  ffmpeg -re -i 123.mp4 -s cga -f hls -hls_list_size 0 -c:v libx264 -c:a aac 200p/out.m3u8 
  
                -s nhd -f hls -hls_list_size 0 -c:v libx264 -c:a aac 360p/out.m3u8 
  
                -s hd480 -f hls -hls_list_size 0 -c:v libx264 -c:a aac 480p/out.m3u8 
  
                -s hd720 -f hls -hls_list_size 0 -c:v libx264 -c:a aac 720p/out.m3u8
  
                -s hd1080 -f hls -hls_list_size 0 -c:v libx264 -c:a aac 1080p/out.m3u8

  And here is the console output :

      ffmpeg -re -i ../files/412-887123464/video/412-887123464.mp4 -s cga -f hls -hls_list_size 0 -c:v libx264 -c:a aac ../fil
  
          es/412-887123464/video/200p/out.m3u8  -s nhd -f hls -hls_list_size 0 -c:v libx264 -c:a aac ../files/412-887123464/video/360p/out.m3u8 -s hd480 -f hls -
  
          hls_list_size 0 -c:v libx264 -c:a aac ../files/412-887123464/video/480p/out.m3u8 -s hd720 -f hls -hls_list_size 0 -c:v libx264 -c:a aac ../files/412-88
  
          7123464/video/720p/out.m3u8 -s hd1080 -f hls -hls_list_size 0 -c:v libx264 -c:a aac ../files/412-887123464/video/1080p/out.m3u8
  
          ffmpeg version N-82225-gb4e9252 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 --e
  
          nable-libebur128 --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcac
  
          a --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-lib
  
          opencore-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-libwa
  
          vpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-decklink --enable-zl
  
          ib
  
            libavutil      55. 35.100 / 55. 35.100
  
            libavcodec     57. 66.101 / 57. 66.101
  
            libavformat    57. 57.100 / 57. 57.100
  
            libavdevice    57.  2.100 / 57.  2.100
  
            libavfilter     6. 66.100 /  6. 66.100
  
            libswscale      4.  3.100 /  4.  3.100
  
            libswresample   2.  4.100 /  2.  4.100
  
            libpostproc    54.  2.100 / 54.  2.100
  
          Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '../files/412-887123464/video/412-887123464.mp4':
  
            Metadata:
  
              major_brand     : isom
  
              minor_version   : 512
  
              compatible_brands: isomiso2avc1mp41
  
              encoder         : Lavf57.31.100
  
            Duration: 00:05:04.07, start: 0.000000, bitrate: 3108 kb/s
  
              Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 1920x1080 [SAR 1:1 DAR 16:9], 2976 kb/s, 25 fps, 25 tbr, 90k tbn, 50
  
          tbc (default)
  
              Metadata:
  
                handler_name    : VideoHandler
  
              Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 125 kb/s (default)
  
              Metadata:
  
                handler_name    : SoundHandler
  
          [libx264 @ 0000000001c53f00] using SAR=10/9
  
          [libx264 @ 0000000001c53f00] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
  
          [libx264 @ 0000000001c53f00] profile High, level 1.3
  
          Output #0, hls, to '../files/412-887123464/video/200p/out.m3u8':
  
            Metadata:
  
              major_brand     : isom
  
              minor_version   : 512
  
              compatible_brands: isomiso2avc1mp41
  
              encoder         : Lavf57.57.100
  
              Stream #0:0(und): Video: h264 (libx264), yuv420p, 320x200 [SAR 10:9 DAR 16:9], q=-1--1, 25 fps, 90k tbn, 25 tbc (default)
  
              Metadata:
  
                handler_name    : VideoHandler
  
                encoder         : Lavc57.66.101 libx264
  
              Side data:
  
                cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
  
              Stream #0:1(und): Audio: aac (LC), 44100 Hz, stereo, fltp, 128 kb/s (default)
  
              Metadata:
  
                handler_name    : SoundHandler
  
                encoder         : Lavc57.66.101 aac
  
          [libx264 @ 0000000001f87180] using SAR=1/1
  
          [libx264 @ 0000000001f87180] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
  
          [libx264 @ 0000000001f87180] profile High, level 3.0
  
          Output #1, hls, to '../files/412-887123464/video/360p/out.m3u8':
  
            Metadata:
  
              major_brand     : isom
  
              minor_version   : 512
  
              compatible_brands: isomiso2avc1mp41
  
              encoder         : Lavf57.57.100
  
              Stream #1:0(und): Video: h264 (libx264), yuv420p, 640x360 [SAR 1:1 DAR 16:9], q=-1--1, 25 fps, 90k tbn, 25 tbc (default)
  
              Metadata:
  
                handler_name    : VideoHandler
  
                encoder         : Lavc57.66.101 libx264
  
              Side data:
  
                cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
  
              Stream #1:1(und): Audio: aac (LC), 44100 Hz, stereo, fltp, 128 kb/s (default)
  
              Metadata:
  
                handler_name    : SoundHandler
  
                encoder         : Lavc57.66.101 aac
  
          [libx264 @ 0000000001c55ba0] using SAR=640/639
  
          [libx264 @ 0000000001c55ba0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
  
          [libx264 @ 0000000001c55ba0] profile High, level 3.0
  
          Output #2, hls, to '../files/412-887123464/video/480p/out.m3u8':
  
            Metadata:
  
              major_brand     : isom
  
              minor_version   : 512
  
              compatible_brands: isomiso2avc1mp41
  
              encoder         : Lavf57.57.100
  
              Stream #2:0(und): Video: h264 (libx264), yuv420p, 852x480 [SAR 640:639 DAR 16:9], q=-1--1, 25 fps, 90k tbn, 25 tbc (default)
  
              Metadata:
  
                handler_name    : VideoHandler
  
                encoder         : Lavc57.66.101 libx264
  
              Side data:
  
                cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
  
              Stream #2:1(und): Audio: aac (LC), 44100 Hz, stereo, fltp, 128 kb/s (default)
  
              Metadata:
  
                handler_name    : SoundHandler
  
                encoder         : Lavc57.66.101 aac
  
          [libx264 @ 0000000001ca0220] using SAR=1/1
  
          [libx264 @ 0000000001ca0220] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
  
          [libx264 @ 0000000001ca0220] profile High, level 3.1
  
          Output #3, hls, to '../files/412-887123464/video/720p/out.m3u8':
  
            Metadata:
  
              major_brand     : isom
  
              minor_version   : 512
  
              compatible_brands: isomiso2avc1mp41
  
              encoder         : Lavf57.57.100
  
              Stream #3:0(und): Video: h264 (libx264), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], q=-1--1, 25 fps, 90k tbn, 25 tbc (default)
  
              Metadata:
  
                handler_name    : VideoHandler
  
                encoder         : Lavc57.66.101 libx264
  
              Side data:
  
                cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
  
              Stream #3:1(und): Audio: aac (LC), 44100 Hz, stereo, fltp, 128 kb/s (default)
  
              Metadata:
  
                handler_name    : SoundHandler
  
                encoder         : Lavc57.66.101 aac
  
          [libx264 @ 0000000001ca23e0] using SAR=1/1
  
          [libx264 @ 0000000001ca23e0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
  
          [libx264 @ 0000000001ca23e0] profile High, level 4.0
  
          Output #4, hls, to '../files/412-887123464/video/1080p/out.m3u8':
  
            Metadata:
  
              major_brand     : isom
  
              minor_version   : 512
  
              compatible_brands: isomiso2avc1mp41
  
              encoder         : Lavf57.57.100
  
              Stream #4:0(und): Video: h264 (libx264), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], q=-1--1, 25 fps, 90k tbn, 25 tbc (default)
  
              Metadata:
  
                handler_name    : VideoHandler
  
                encoder         : Lavc57.66.101 libx264
  
              Side data:
  
                cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
  
              Stream #4:1(und): Audio: aac (LC), 44100 Hz, stereo, fltp, 128 kb/s (default)
  
              Metadata:
  
                handler_name    : SoundHandler
  
                encoder         : Lavc57.66.101 aac
  
          Stream mapping:
  
            Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
  
            Stream #0:1 -> #0:1 (aac (native) -> aac (native))
  
            Stream #0:0 -> #1:0 (h264 (native) -> h264 (libx264))
  
            Stream #0:1 -> #1:1 (aac (native) -> aac (native))
  
            Stream #0:0 -> #2:0 (h264 (native) -> h264 (libx264))
  
            Stream #0:1 -> #2:1 (aac (native) -> aac (native))
  
            Stream #0:0 -> #3:0 (h264 (native) -> h264 (libx264))
  
            Stream #0:1 -> #3:1 (aac (native) -> aac (native))
  
            Stream #0:0 -> #4:0 (h264 (native) -> h264 (libx264))
  
            Stream #0:1 -> #4:1 (aac (native) -> aac (native))
  
          Press [q] to stop, [?] for help
  
  frame= 7600 fps= 21 q=-1.0 Lq=-1.0 q=-1.0 q=-1.0 q=-1.0 size=N/A time=00:05:04.06 bitrate=N/A speed=0.835x
  
  video:294980kB audio:23995kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
  
  [libx264 @ 0000000001d33f00] frame I:33    Avg QP:19.93  size: 11412
  
  [libx264 @ 0000000001d33f00] frame P:2281  Avg QP:23.72  size:  3112
  
  [libx264 @ 0000000001d33f00] frame B:5286  Avg QP:28.59  size:   446
  
  [libx264 @ 0000000001d33f00] consecutive B-frames:  4.3%  6.9%  5.9% 82.8%
  
  [libx264 @ 0000000001d33f00] mb I  I16..4: 12.9% 42.9% 44.2%
  
  [libx264 @ 0000000001d33f00] mb P  I16..4:  1.3%  4.4%  2.3%  P16..4: 41.4% 22.0% 15.5%  0.0%  0.0%    skip:13.1%
  
  [libx264 @ 0000000001d33f00] mb B  I16..4:  0.0%  0.1%  0.0%  B16..8: 35.2%  5.9%  2.1%  direct: 3.0%  skip:53.6%  L0:35.3% L1:48.0% BI:16.8%
  
  [libx264 @ 0000000001d33f00] 8x8 transform intra:53.4% inter:57.9%
  
  [libx264 @ 0000000001d33f00] coded y,uvDC,uvAC intra: 70.6% 89.7% 67.6% inter: 18.1% 20.3% 7.2%
  
  [libx264 @ 0000000001d33f00] i16 v,h,dc,p: 24% 24%  6% 45%
  
  [libx264 @ 0000000001d33f00] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 27% 14% 19%  5%  5%  7%  5% 10%  7%
  
  [libx264 @ 0000000001d33f00] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 31% 15% 15%  6%  6%  7%  6%  8%  6%
  
  [libx264 @ 0000000001d33f00] i8c dc,h,v,p: 42% 17% 28% 14%
  
  [libx264 @ 0000000001d33f00] Weighted P-Frames: Y:26.3% UV:12.9%
  
  [libx264 @ 0000000001d33f00] ref P L0: 58.7% 24.7% 10.9%  4.8%  1.0%
  
  [libx264 @ 0000000001d33f00] ref B L0: 92.6%  5.8%  1.6%
  
  [libx264 @ 0000000001d33f00] ref B L1: 96.3%  3.7%
  
  [libx264 @ 0000000001d33f00] kb/s:258.68
  
  [aac @ 00000000005fc9e0] Qavg: 686.637
  
  [libx264 @ 0000000002017180] frame I:31    Avg QP:19.77  size: 29228
  
  [libx264 @ 0000000002017180] frame P:2040  Avg QP:23.08  size:  8765
  
  [libx264 @ 0000000002017180] frame B:5529  Avg QP:27.28  size:  1471
  
  [libx264 @ 0000000002017180] consecutive B-frames:  1.3%  4.2%  2.4% 92.1%
  
  [libx264 @ 0000000002017180] mb I  I16..4:  8.3% 58.8% 32.9%
  
  [libx264 @ 0000000002017180] mb P  I16..4:  3.2%  9.5%  2.6%  P16..4: 41.5% 19.5% 11.4%  0.0%  0.0%    skip:12.2%
  
  [libx264 @ 0000000002017180] mb B  I16..4:  0.2%  0.3%  0.1%  B16..8: 34.5%  5.8%  1.7%  direct: 2.7%  skip:54.7%  L0:35.9% L1:49.5% BI:14.6%
  
  [libx264 @ 0000000002017180] 8x8 transform intra:61.2% inter:67.3%
  
  [libx264 @ 0000000002017180] coded y,uvDC,uvAC intra: 55.8% 84.8% 51.3% inter: 15.6% 19.3% 3.9%
  
  [libx264 @ 0000000002017180] i16 v,h,dc,p: 24% 29%  8% 39%
  
  [libx264 @ 0000000002017180] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 27% 17% 21%  5%  5%  7%  5%  8%  6%
  
  [libx264 @ 0000000002017180] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 29% 18% 15%  6%  7%  7%  6%  7%  5%
  
  [libx264 @ 0000000002017180] i8c dc,h,v,p: 42% 18% 27% 13%
  
  [libx264 @ 0000000002017180] Weighted P-Frames: Y:22.3% UV:12.2%
  
  [libx264 @ 0000000002017180] ref P L0: 58.5% 23.4% 12.2%  5.2%  0.8%
  
  [libx264 @ 0000000002017180] ref B L0: 93.1%  5.3%  1.6%
  
  [libx264 @ 0000000002017180] ref B L1: 96.6%  3.4%
  
  [libx264 @ 0000000002017180] kb/s:708.47
  
  [aac @ 0000000001d35200] Qavg: 686.637
  
  [libx264 @ 0000000001d35ba0] frame I:31    Avg QP:19.63  size: 41522
  
  [libx264 @ 0000000001d35ba0] frame P:2025  Avg QP:22.86  size: 13415
  
  [libx264 @ 0000000001d35ba0] frame B:5544  Avg QP:26.52  size:  2471
  
  [libx264 @ 0000000001d35ba0] consecutive B-frames:  1.1%  3.9%  2.8% 92.2%
  
  [libx264 @ 0000000001d35ba0] mb I  I16..4: 10.6% 62.4% 26.9%
  
  [libx264 @ 0000000001d35ba0] mb P  I16..4:  4.7% 12.4%  2.6%  P16..4: 41.1% 17.8%  9.4%  0.0%  0.0%    skip:11.9%
  
  [libx264 @ 0000000001d35ba0] mb B  I16..4:  0.3%  0.5%  0.1%  B16..8: 34.0%  5.5%  1.4%  direct: 2.9%  skip:55.3%  L0:36.7% L1:50.2% BI:13.1%
  
  [libx264 @ 0000000001d35ba0] 8x8 transform intra:61.7% inter:71.6%
  
  [libx264 @ 0000000001d35ba0] coded y,uvDC,uvAC intra: 48.0% 81.9% 43.3% inter: 14.7% 19.7% 2.6%
  
  [libx264 @ 0000000001d35ba0] i16 v,h,dc,p: 27% 29%  9% 35%
  
  [libx264 @ 0000000001d35ba0] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 27% 19% 22%  5%  5%  6%  5%  7%  5%
  
  [libx264 @ 0000000001d35ba0] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 26% 25% 16%  5%  6%  7%  6%  6%  4%
  
  [libx264 @ 0000000001d35ba0] i8c dc,h,v,p: 42% 20% 26% 12%
  
  [libx264 @ 0000000001d35ba0] Weighted P-Frames: Y:18.1% UV:10.8%
  
  [libx264 @ 0000000001d35ba0] ref P L0: 59.5% 22.6% 12.6%  4.8%  0.5%
  
  [libx264 @ 0000000001d35ba0] ref B L0: 93.6%  5.0%  1.4%
  
  [libx264 @ 0000000001d35ba0] ref B L1: 97.1%  2.9%
  
  [libx264 @ 0000000001d35ba0] kb/s:1109.23
  
  [aac @ 0000000001d828a0] Qavg: 686.637
  
  [libx264 @ 0000000001d7f880] frame I:32    Avg QP:19.45  size: 64737
  
  [libx264 @ 0000000001d7f880] frame P:2104  Avg QP:22.44  size: 23985
  
  [libx264 @ 0000000001d7f880] frame B:5464  Avg QP:25.65  size:  4999
  
  [libx264 @ 0000000001d7f880] consecutive B-frames:  1.2%  7.7%  3.2% 87.8%
  
  [libx264 @ 0000000001d7f880] mb I  I16..4: 12.5% 70.0% 17.5%
  
  [libx264 @ 0000000001d7f880] mb P  I16..4:  6.7% 17.1%  1.8%  P16..4: 40.7% 14.9%  6.6%  0.0%  0.0%    skip:12.2%
  
  [libx264 @ 0000000001d7f880] mb B  I16..4:  0.6%  0.9%  0.1%  B16..8: 32.5%  4.7%  1.0%  direct: 2.9%  skip:57.4%  L0:37.6% L1:51.6% BI:10.8%
  
  [libx264 @ 0000000001d7f880] 8x8 transform intra:65.7% inter:77.5%
  
  [libx264 @ 0000000001d7f880] coded y,uvDC,uvAC intra: 39.5% 76.4% 32.4% inter: 13.2% 19.8% 1.5%
  
  [libx264 @ 0000000001d7f880] i16 v,h,dc,p: 32% 27% 10% 31%
  
  [libx264 @ 0000000001d7f880] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 30% 18% 23%  4%  5%  5%  4%  5%  4%
  
  [libx264 @ 0000000001d7f880] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 29% 20% 15%  5%  7%  7%  6%  6%  4%
  
  [libx264 @ 0000000001d7f880] i8c dc,h,v,p: 42% 19% 27% 12%
  
  [libx264 @ 0000000001d7f880] Weighted P-Frames: Y:10.5% UV:6.7%
  
  [libx264 @ 0000000001d7f880] ref P L0: 62.3% 20.4% 12.7%  4.3%  0.3%
  
  [libx264 @ 0000000001d7f880] ref B L0: 93.4%  5.2%  1.4%
  
  [libx264 @ 0000000001d7f880] ref B L1: 97.7%  2.3%
  
  [libx264 @ 0000000001d7f880] kb/s:2101.26
  
  [aac @ 0000000001d81560] Qavg: 686.637
  
  [libx264 @ 0000000001d7fd60] frame I:33    Avg QP:18.36  size: 98904
  
  [libx264 @ 0000000001d7fd60] frame P:3180  Avg QP:21.67  size: 33377
  
  [libx264 @ 0000000001d7fd60] frame B:4387  Avg QP:24.61  size:  7729
  
  [libx264 @ 0000000001d7fd60] consecutive B-frames:  2.7% 55.9% 15.6% 25.9%
  
  [libx264 @ 0000000001d7fd60] mb I  I16..4: 22.4% 66.9% 10.7%
  
  [libx264 @ 0000000001d7fd60] mb P  I16..4:  9.9% 17.8%  0.7%  P16..4: 40.4%  9.2%  3.0%  0.0%  0.0%    skip:19.0%
  
  [libx264 @ 0000000001d7fd60] mb B  I16..4:  0.8%  1.3%  0.1%  B16..8: 30.2%  2.6%  0.4%  direct: 1.7%  skip:63.0%  L0:38.1% L1:54.9% BI: 7.0%
  
  [libx264 @ 0000000001d7fd60] 8x8 transform intra:62.5% inter:82.9%
  
  [libx264 @ 0000000001d7fd60] coded y,uvDC,uvAC intra: 25.4% 59.5% 11.6% inter: 9.6% 16.3% 0.7%
  
  [libx264 @ 0000000001d7fd60] i16 v,h,dc,p: 33% 28% 15% 24%
  
  [libx264 @ 0000000001d7fd60] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 34% 20% 29%  3%  3%  4%  3%  3%  3%
  
  [libx264 @ 0000000001d7fd60] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 30% 25% 16%  4%  6%  6%  5%  5%  4%
  
  [libx264 @ 0000000001d7fd60] i8c dc,h,v,p: 39% 21% 28% 12%
  
  [libx264 @ 0000000001d7fd60] Weighted P-Frames: Y:5.7% UV:3.6%
  
  [libx264 @ 0000000001d7fd60] ref P L0: 70.0% 18.6%  8.3%  3.1%  0.1%
  
  [libx264 @ 0000000001d7fd60] ref B L0: 91.4%  7.6%  1.0%
  
  [libx264 @ 0000000001d7fd60] ref B L1: 99.0%  1.0%
  
  [libx264 @ 0000000001d7fd60] kb/s:3771.31
  
  [aac @ 0000000001d823e0] Qavg: 686.637

  But I don’t have any problem for streaming files with creating resolutions from a file which have lower orginal quality than hd1080
  What I can to do ?