Recherche avancée

Sur d’autres sites (10110)

• Web Analytics : The Quick Start Guide

  25 janvier 2024, par Erin

  You’ve spent ages carefully designing your website, crafting copy to encourage as many users as possible to purchase your product. 

  But they aren’t. And you don’t know why. 

  The good news is you don’t have to remain in the dark. Collecting and analysing web analytics lets you understand how your users behave on your site and why they aren’t converting. 

  But before you can do that, you need to know what those metrics and KPIs mean. That’s why this article is taking things back to basics. Below, we’ll show you which metrics to track, what they mean and how to choose the best web analytics platform. 

  What is web analytics ?

  Web analytics is the process of collecting, analysing and reporting website data to understand how users behave on your website. Web analytics platforms like Matomo collect this data by adding a code line to every site page. 

  Why is it important to track web analytics ?

  There are plenty of reasons you should start tracking web analytics, including the following :

  

  Analyse user behaviour

  Being able to analyse user behaviour is the most important reason to track website analytics. After all, you can’t improve your website’s conversion rate if you don’t know what users do on your site.

  A web analytics platform can show you how users move around your site, the links they click on and the forms they fill in. 

  Improve site experience

  Web analytics is a fantastic way to identify issues and find areas where your site could improve. You could look at your site’s exit pages, for example, and see why so many users leave your site when viewing one of these pages and what you can do to fix it.

  It can also teach you about your user’s preferences so you can improve the user experience in the future. Maybe they always click a certain type of button or prefer one page’s design over another. Whatever the case, you can use the data to make your site more user-friendly and increase conversions.

  Boost marketing efforts

  Web analytics is one of the best ways to understand your marketing efforts and learn how to improve them.

  A good platform can collect valuable data about your marketing campaigns, including :

  • Where users came from
  • What actions these users take on your site
  • Which traffic sources create the most conversions

  This information can help you decide which marketing campaigns send the best users to your site and generate the highest ROI. 

  Make informed decisions

  Ultimately, web analytics simplifies decision-making for your website and marketing efforts by relying on concrete data instead of guesswork.

  Rather than wonder why users aren’t adding products to their shopping cart or signing up for your newsletter, you can analyse how they behave and use that information to hypothesise how you can improve conversions. Web analytics will even give you the data to confirm whether you were right or wrong. 

  What are the key metrics you should track ?

  Getting your head around web analytics means knowing the most important metrics to track. Below are seven key metrics and how to track them using Matomo. 

  Traffic

  Traffic is the number of people visiting your website over a period of time. It is the lifeblood of your website since the more visits your site receives, the more revenue it stands to generate.

  However, simply having a high volume of visitors does not guarantee substantial revenue. To maximise your success, focus on attracting your ideal customers and generating quality traffic from those who are most likely to engage with your offerings.

  Ideally, you should be seeing an upward trend in traffic over time though. The longer your website has been published and the more quality and targeted content you create, the more traffic you should receive. 

  Matomo offers multiple ways to check your website’s traffic :

  • Visits log report
  • Real-time visitor map
  • Visits in real-time report

  The visits log report in Matomo is perfect if you want a granular view of your visitors.

  

  It shows you each user session and get a detailed picture of each user, including :

  • Their geographic location
  • The number of actions they took
  • How they found your site
  • The length of time they stayed
  • Their device type
  • What browser they are using
  • The keyword they used to find your site

  Traffic sources

  Traffic sources show how users access your website. They can enter via a range of traffic sources, including search engines, email and direct visits, for instance.

  Matomo has five default traffic source types :

  • Search engine – visitors from search platforms (like Google, Bing, etc.)
  • Direct traffic – individuals who directly type your website’s URL into their browser or have it bookmarked, bypassing search engines or external links
  • Websites – visits from other external sites
  • Campaigns – traffic resulting from specific marketing initiatives (like a newsletter or ad campaign, for instance)
  • Social networks  – visitors who access your website through various social media platforms (such as Facebook, LinkedIn, Instagram. etc.)

  But each of these can be broken into more granular sources. Take organic traffic from search engines, for example :

  

  Matomo tracks visits from each search engine, showing you how many visits you had in total, how many actions those visitors took, and the average amount of time those visitors spent on your site. 

  You can even integrate Google, Bing and Yahoo search consoles to monitor keyword performance and enhance your search engine optimisation efforts.

  Pageviews

  Whenever a browser loads a page, your web analytics tool records a pageview. This term, pageview, represents the count of unique times a page on your website is loaded.

  You can track pageviews in Matomo by opening the Pages tab in the Behaviour section of the main navigation. 

  

  You can quickly see your site’s most visited pages in this report in Matomo. 

  Be careful of deriving too much meaning from pageviews. Just because a page has lots of views, doesn’t necessarily mean it’s quality or valuable. There are a couple of reasons for this. First, the page might be confusing, so users have to keep revisiting it to understand the content. Second, it could be the default page most visitors land on when they enter your site, like the homepage. 

  While pageviews offer insights, it’s important to dig deeper into user behaviour and other metrics to truly gauge a page’s importance and impact.

  Average time on page

  Time on page is the amount of time users spend on the page on average. You can see average time on page in Matomo’s page analytics report.

  A low time on page score isn’t necessarily a bad thing. Users will naturally spend less time on gateway pages and checkout pages. A short time spent on checkout pages, especially if users are successfully completing their transactions, indicates that the checkout process is easy and seamless.

  Conversely, a longer time on blog posts is a positive indicator. It suggests that readers are genuinely engaged with the content.

  Try Matomo for Free

  Get the web insights you need, without compromising data accuracy.

  Start for free

  No credit card required

  Returning visitors

  Returning visitors measures the number of people who visit your site more than once. It can be expressed as a number or a percentage. 

  While some analytics tools only show returning visitors as a percentage, Matomo lets you learn more about each of them in the Visitor profile report. 

  

  This report offers a full summary of a user’s previous actions, including :

  • How many times they’ve visited your site
  • The pages they viewed on each visit
  • Where they visited from
  • The devices they used
  • How quickly pages loaded

  When people keep coming back to a website, it’s usually a positive sign and means they like the service, content or products. But, it depends on the type of website. If it’s the kind of site where people make one-off purchases, the focus might not be on getting visitors to return. For a site like this, a high number of returning visitors could indicate that the website is confusing or difficult to use. 

  It’s all about the context – different websites have different goals, and it’s important to keep this in mind when analysing your site.

  Conversions

  A conversion is when a user takes a desired action on your website. This could be :

  • Making a purchase
  • Subscribing to your newsletter
  • Signing up for a webinar

  You can track virtually any action as a conversion in Matomo by setting goals and analysing the goals report.

  

  As you can see in the screenshot above, Matomo shows your conversions plotted over time. You can also see your conversion rate to get a complete picture and assign a value to each conversion to calculate how much revenue each conversion generates. 

  Bounce rate

  A visitor bounces when they leave your website without taking an action or visiting another page. 

  Typically, you want bounce rate to be low because it means people are engaged with your site and more likely to convert. However, in some cases, a high bounce rate isn’t necessarily bad. It might mean that visitors found what they needed on the first page and didn’t feel the need to look further. 

  The impact of bounce rate depends on your website’s purpose and goals.

  You can view your website’s bounce rate using Matomo’s page analytics report — the same report that shows pageviews.

  Try Matomo for Free

  Get the web insights you need, without compromising data accuracy.

  Start for free

  No credit card required

  Web analytics best practices

  You should follow several best practices to get the most from website analytics data. 

  Choose metrics that align with your goals

  Only some metrics your analytics platform tracks will be relevant to your business. So don’t waste time analysing all of them.

  Instead, focus on the ones that matter most to your business. A marketer for an e-commerce store, for example, might focus on conversion-related metrics like conversion rate and total number of transactions. They might also want to look at campaign-related metrics, like traffic sources and bounce rates, so they can optimise paid ad campaigns accordingly. 

  A marketer looking to improve their site’s SEO, on the other hand, will want to track SEO web analytics like bounce rate and broken links.

  Add context to your data

  Don’t take your data at face value. There could be dozens of factors that impact how visitors access and use your site — many of which are outside your control. 

  For example, you may think an update to your site has sent your conversions crashing when, in reality, a Google algorithm update has negatively impacted your search traffic.

  Adding annotations within Matomo can provide invaluable context to your data. These annotations can be used to highlight specific events, changes or external factors that might influence your website metrics.

  

  By documenting significant occurrences, such as website updates, marketing campaigns or algorithm changes, you create a timeline that helps explain fluctuations in your data.

  Go further with advanced web analytics features

  It’s clear that a web analytics platform is a necessary tool to understand your website’s performance.

  However, if you want greater confidence in decision-making, quicker insights and better use of budget and resources, you need an advanced solution with behavioural analytics features like heatmaps, A/B testing and session recordings. 

  Most web analytics solutions don’t offer these advanced features, but Matomo does, so we’ll be showcasing Matomo’s behavioural analytics features.

  Now, if you don’t have a Matomo account, you can try it free for 21-days to see if it’s the right tool for you.

  

  A heatmap, like the example above, makes it easy to discover where your users pay attention, which part of your site they have problems with, and how they convert. It adds a layer of qualitative data to the facts offered by your web analytics tool.

  Similarly, session recordings will offer you real-time playbacks of user interactions, helping you understand their navigation patterns, identify pain points and gain insights into the user experience.

  Then you can run experiments bu using A/B testing to compare different versions of your website or specific elements, allowing you to make informed decisions based on actual user preferences and behaviour. For instance, you can compare different headlines, images, page layouts or call-to-action buttons to see which resonates better with your audience. 

  Together, these advanced features will give you the confidence to optimise your website, improve user satisfaction and make data-driven decisions that positively impact your business.

  Try Matomo for Free

  Get the web insights you need, without compromising data accuracy.

  Start for free

  No credit card required

  How to choose a web analytics tool

  A web analytics tool is the best way to track the above metrics. Choose the best one for your company by following the steps below. 

  Look for the right features

  Most popular web analytics platforms, like Google Analytics, will offer the same core features like tracking website traffic, monitoring conversions and generating reports. 

  But it’s the added features that set great tools apart. Do you need specific tools to measure the performance of your e-commerce store, for example ? What about paid ad performance, A/B testing or form analytics ?

  By understanding exactly what you need from an analytics platform, you can make an informed choice. 

  Think about data accuracy

  Data accuracy is one of the biggest issues with analytics tools. Many users block cookies or opt out of tracking, making it difficult to get a clear picture of user behaviour — and meaning that you have to think about how your user data will be collected with your chosen platform.

  Google Analytics, for instance, uses data sampling to make assumptions about traffic levels rather than relying on accurate data. This can lead to inaccurate reports and false conclusions. 

  It’s why Matomo doesn’t use data sampling and provides 100% accurate data. 

  Understand how you’ll deal with data privacy

  Data privacy is another big concern for analytics users. Several major analytics platforms aren’t compatible with regional data privacy laws like GDPR, which can impact your ability to collect data in these regions. 

  It’s why many companies trust privacy-focused analytics tools that abide by regulations without impacting your ability to collect data. Matomo is a market leader in this respect and is one of the few web analytics tools that the Centre for Data Privacy Protection in France has said is exempt from tracking consent requirements.

  Many government agencies across Europe, Asia, Africa and North America, including organisations like the United Nations and European Commission, rely on Matomo for web analytics.

  Conclusion

  Web analytics is a powerful tool that helps you better understand your users, improve your site’s performance and boost your marketing efforts. 

  If you want a platform that offers advanced features, 100% accurate data and protects your users’ privacy, then look no further than Matomo. 

  Try Matomo free for 21 days, no credit card required. 

  Try Matomo for Free

  21 day free trial. No credit card required.

  
  

  Your email address
  

  Your website address
  

  Your Analytics subdomain will be .matomo.cloud (change)

• Top 5 Customer Segmentation Software in 2024

  12 mars 2024, par Erin

  In marketing, we all know the importance of reaching the right customer with the right message at the right time. That’s how you cut through the noise.

  For that, you need data on your customers — even though gathering the data is not enough. You can have all the data worldwide, but that raises an ethical responsibility and the need to make sense of it.

  Enter customer segmentation software — the answer to delivering personalised customer experiences at scale. 

  This article lists some of the best customer segmentation tools currently in the market. 

  We’ll also go over the benefits of using such tools and how you can choose the best one for your business.

  Let’s get started !

  What is customer segmentation software ?

  Customer segmentation software is a tool that helps businesses analyse customer data and group them based on common characteristics like age, income, and buying habits.

  The main goal of customer segmentation is to gain deeper insights into customer behaviours and preferences. This helps create targeted marketing and product strategies that fit each group and makes it easier to predict how customers will behave in the future.

  

  Benefits of a customer segmentation software

  Understanding your customers is the cornerstone of effective marketing, and customer segmentation software plays a pivotal role in this endeavour. 

  You can deliver more targeted and relevant marketing campaigns by dividing your audience into distinct groups based on shared characteristics. 

  Specifically, here are the main benefits of using customer segmentation tools :

  • Understand your audience better : The software helps businesses group customers with common traits to better understand their preferences and behaviour.
  • Make data-driven decisions : Base your business and marketing decisions on data analytics.
  • Aid product development : Insights from segmentation analytics can guide the creation of products that meet specific customer group needs.
  • Allocate your resources efficiently : Focusing on the customer segments that generate the most revenue leads to more effective and strategic use of your marketing resources.

  Best customer segmentation software in 2024 

  In this section, we go over the top customer segmentation tools in 2024. 

  We’ll look at these tools’ key features and pros and cons.

  1. Matomo

  

  Matomo is a comprehensive web analytics tool that merges traditional web analytics, such as tracking pageviews and visitor bounce rates, with more advanced web analytics features for tracking user behaviour. 

  With robust segmentation features, users can filter website traffic based on criteria such as location and device type, enabling them to analyse specific visitor groups and their behaviour. Users can create custom segments to analyse specific groups of visitors and their behaviour.

  Presenting as the ethical alternative to Google Analytics, Matomo emphasises transparency, 100% accurate data, and compliance with privacy laws.

  Key features

  • Heatmaps and Session Recordings : Matomo provides tools that allow businesses to understand website user interactions visually. This insight is crucial for optimising user experience and increasing conversions.
  • Form Analytics : This feature in Matomo tracks how users interact with website forms, helping businesses understand user behaviour in detail and improve form design and functionality.
  • User Flow Analysis : The tool tracks the journey of a website’s visitors, highlighting the paths taken and where users drop off. This is key for optimising website structure for better user experience and more conversions.
  • A/B Testing : Businesses can use Matomo to test different versions of web pages, determining which is more effective in driving conversions.
  • Conversion Funnels : This feature allows businesses to visualise and optimise the steps customers take toward conversion, identifying areas for improvement.

  Pros 

  • Affordability : With plans starting at $19 per month, Matomo is a cost-effective solution for CRO.
  • Free support : Matomo provides free email support to all Matomo Cloud users.
  • Open-source benefits : Being open-source, Matomo offers enhanced security, privacy, customisation options, and a supportive community.
  • Hosting options : Matomo is available either as a self-hosted solution or cloud-hosted.

  Cons

  • Cost for advanced features : Access to advanced features may incur additional costs for Matomo On-Premise users, although the On-Premise solution itself is free.
  • Technical knowledge required : The self-hosted version of Matomo requires technical knowledge for effective management.

  Try Matomo for Free

  Get the web insights you need, without compromising data accuracy.

  Start for free

  No credit card required

  2. Google Analytics 

  

  Google Analytics 4 (GA4) comprehensively understands website and app performance. It focuses on event-based data collection, allowing businesses to understand user interactions across platforms. 

  Similarly to Matomo, GA4 provides features that allow businesses to segment their audience based on various criteria such as demographics, behaviours, events, and more.

  Key features

  • Event-based tracking : GA4’s shift to an event-based model allows for a flexible and predictive analysis of user behaviour. This includes a detailed view of user interactions on websites and apps.
  • Machine Learning and Smarter Insights : GA4 uses machine learning to automatically detect trends, estimate purchase probabilities and provide marketing insights.
  • Google Ads integration : The integration with Google Ads in GA4 enables tracking customer interactions from first ad engagement, providing a holistic view of the customer experience across various platforms.
  • Customer-centric measurements : GA4 collects data as events, covering a wide range of user interactions and offering a comprehensive view of customer behaviour.
  • Pathing reports : GA4 introduces new pathing reports, allowing detailed user flow analysis through websites and apps.
  • Audiences and filters : GA4 allows the creation of audiences based on specific criteria and the application of filters to segment and refine data analysis.

  Pros 

  • Integration with various platforms, including Google Ads, enhances cross-platform user journey analysis.
  • GA4 has a clean reporting interface, making it easier for marketers to identify key trends and data irregularities.
  • Google Analytics has an active community with an abundance of educational resources available for users.

  Cons

  • Complexity for beginners : The wide range of features and new event-based model might overwhelm users new to analytics tools.
  • Dependence on machine learning : Reliance on machine learning for insights and predictions may require trust in the tool’s data processing and large volumes of traffic for accuracy.
  • Transition from UA to GA4 : Users familiar with Universal Analytics (UA) might find the transition to GA4 challenging due to differences in features and data models.

  3. HubSpot

  

  HubSpot is a marketing and sales software that helps businesses attract visitors and turn them into paying customers. 

  It supports various business processes, from social media posts to email marketing, sales, and customer service. HubSpot organises and tracks user interactions across different channels, providing a unified and efficient approach to customer relationship management (CRM) and customer segmentation.

  Businesses can leverage HubSpot’s customer segmentation through lists, workflows, and smart content.

  Key features

  • Integration capabilities : HubSpot offers over 1,000 integrations in its ecosystem, ensuring seamless connectivity across various marketing, sales, and service tools, which helps maintain data consistency and reduces manual efforts.
  • Segmentation and personalisation : HubSpot allows businesses to deliver personalised content and interactions based on customer behaviour and preferences, using its robust CRM features and advanced automation capabilities.

  Pros 

  • Comprehensive support : HubSpot offers a range of support options, including a knowledge base, real-time chat, and more.
  • User-friendly interface : The platform is designed for ease of use, ensuring a smooth experience even for less tech-savvy users.
  • Personalisation capabilities : HubSpot provides personalised marketing, sales and service experiences, leveraging customer data effectively.

  Cons

  • High price point : HubSpot can be expensive, especially as you scale up and require more advanced features.
  • Steep learning curve : For businesses new to such comprehensive platforms, there might be an initial learning curve to utilise its features effectively.

  4. Klaviyo

  

  Klaviyo is a marketing automation software primarily focused on email and SMS messaging for e-commerce businesses. It’s designed to personalise and optimise customer communication. 

  Klaviyo integrates with e-commerce platforms like Shopify, making it a go-to solution for online stores. Its strength lies in its ability to use customer data to deliver targeted and effective marketing campaigns.

  Key features

  • Email marketing automation : Klaviyo allows users to send automated and personalised emails based on customer behaviour and preferences. This feature is crucial for e-commerce businesses in nurturing leads and maintaining customer engagement.
  • SMS marketing : It includes SMS messaging capabilities, enabling businesses to engage customers directly through text messages.
  • Segmentation and personalisation : Klaviyo offers advanced segmentation tools that enable businesses to categorise customers based on their behaviour, preferences and purchase history, facilitating highly targeted marketing efforts.
  • Integration with e-commerce platforms : Klaviyo integrates with popular e-commerce platforms like Shopify, Magento, and WooCommerce, allowing easy data synchronisation and campaign management.

  Pros 

  • Enhanced e-commerce integration : Klaviyo’s deep integration with e-commerce platforms greatly benefits online retailers regarding ease of use and campaign effectiveness.
  • Advanced segmentation and personalisation : The platform’s strong segmentation capabilities enable businesses to tailor their marketing messages more effectively.
  • Robust automation features : Klaviyo’s automation tools are powerful and user-friendly, saving time and improving marketing efficiency.

  Cons

  • Cost : Klaviyo can be more expensive than other options in this list, particularly as you scale up and add more contacts.
  • Complexity for beginners : The platform’s wide range of features and advanced capabilities might overwhelm beginners or small businesses with simpler needs.

  5. UserGuiding

  

  UserGuiding is a no-code product adoption tool that lets businesses create in-app user walkthroughs, guides, and checklists to onboard, engage, and retain users.

  UserGuiding facilitates customer segmentation by enabling businesses to create segmented onboarding flows, analyse behavioural insights, deliver personalised guidance, and collect feedback tailored to different user segments.

  Key features

  • In-app walkthroughs, guides and checklists : UserGuiding has multiple features that can promote product adoption early in the user journey.
  • In-app messaging : UserGuiding offers in-app messaging to help users learn more about the product and various ways to get value.
  • User feedback : UserGuiding allows businesses to gather qualitative feedback to streamline the adoption journey for users.

  Pros 

  • User-friendly interface
  • Customisable onboarding checklists
  • Retention analytics

  Cons

  • Need for technical expertise to maximise all features
  • Limited customisation options for less tech-savvy users

  What to look for in a customer segmentation software 

  When choosing a customer segmentation software, choosing the right one for your specific business needs is important. 

  Here are a few factors to consider when choosing your customer segmentation tool :

  1. Ease of use : Select a tool with an intuitive interface that simplifies navigation. This enhances the user experience, making complex tasks more manageable. Additionally, responsive customer support is crucial. It ensures that issues are promptly resolved, contributing to a smoother operation.
  2. Scalability and flexibility : Your chosen tool should adjust to your needs. A flexible tool like Matomo can adjust to your growing requirements, offering capabilities that evolve as your business expands.
  3. Integration capabilities : The software should seamlessly integrate with your existing systems, such as CRM, marketing, and automation platforms. 
  4. Advanced analytics and reporting : Assess the software’s capability to analyse and interpret complex data sets, without relying on machine learning to fill data gaps. A robust tool should provide accurate insights and detailed reports, enabling you to make informed decisions based on real data.
  5. Privacy and security considerations : Data security is paramount in today’s digital landscape. Look for features like data encryption, security storage, and adherence to privacy standards like GDPR and CCPA compliance. 
  6. Reviews and recommendations : Before making a decision, consider the reputation of the software providers. Look for reviews and recommendations from other users, especially those in similar industries. This can provide real-world insights into the software’s performance and reliability.

  

  Leverage Matomo’s segmentation capabilities to deliver personalised experiences

  Segmentation is the best place to start if you want to deliver personalised customer experiences. There are several customer segmentation software in the market. But they’re not all the same.

  In this article, we reviewed the top segmentation tools — based on factors like their user base, features, and ethical data privacy considerations.

  Ideally, you want a tool to support your evolving business and segmentation needs. Not to mention one that cares about your customers’ privacy and ensures you stay compliant. 

  Enter Matomo at the top of the list. You can leverage Matomo’s accurate insights and comprehensive segmentation capabilities without compromising on privacy. Try it free for 21-days. No credit card required.

  Try Matomo for Free

  21 day free trial. No credit card required.

  
  

  Your email address
  

  Your website address
  

  Your Analytics subdomain will be .matomo.cloud (change)

  Choose your analytics subdomain
  

  .matomo.cloud

  I accept the terms and conditions and data processing agreement (DPA)

  
  Your information will be used to create an account on our cloud service. For more information please consult our privacy policy.
  
  
  

  Start improving your websites now

  

• FFmpeg smearing rtp missed packet

  3 janvier 2018, par Akim Benchiha

  I’m using ffmpeg to combine streams. But during the combinaison I have some errors/Warnings. I don’t know why. I can see the frames are dropping. And the output video is poor quality

  Here the situation :
  First : Try to combine local video and a rtsp stream from data center.

  ffmpeg -i rtsp://cloudzensg.loginto.me:554/livecast -i Xmen2trailer.mov -filter_complex "[0]scale=-1:-1[b];[1]scale=128:128[w];[b][w] overlay=10:10" -vcodec libx264 -preset ultrafast -f flv out.mp4
  
  ffmpeg version N-89672-g41e51fbcd9 Copyright (c) 2000-2018 the FFmpeg developers
  
    built with gcc 7.2.0 (GCC)
  
  [udp @ 000001e07f58ccc0] 'circular_buffer_size' option was set but it is not supported on this build (pthread support is required)
  
  [udp @ 000001e07f5a2b80] 'circular_buffer_size' option was set but it is not supported on this build (pthread support is required)
  
  [udp @ 000001e07f5b4040] 'circular_buffer_size' option was set but it is not supported on this build (pthread support is required)
  
  [udp @ 000001e07f5c4300] 'circular_buffer_size' option was set but it is not supported on this build (pthread support is required)
  
  Input #0, rtsp, from 'rtsp://cloudzensg.loginto.me:554/livecast':
  
    Metadata:
  
      title           : session
  
    Duration: N/A, start: 0.086367, bitrate: N/A
  
      Stream #0:0: Audio: aac, 44100 Hz, stereo, fltp
  
      Stream #0:1: Video: h264 (Constrained Baseline), yuv420p(progressive), 1280x720, 30 fps, 30 tbr, 90k tbn, 60 tbc
  
  Input #1, mov,mp4,m4a,3gp,3g2,mj2, from 'Xmen2trailer.mov':
  
    Metadata:
  
      creation_time   : 2003-02-17T16:23:00.000000Z
  
      title           : X2
  
      title-eng       : X2
  
      copyright-eng   : ┬⌐2003 20th Century Fox
  
      comment         : QuickTime 5 version encoded and delivered by www.apple.com/trailers/
  
      copyright       : ┬⌐2003 20th Century Fox
  
      comment-eng     : QuickTime 5 version encoded and delivered by www.apple.com/trailers/
  
    Duration: 00:02:29.08, start: 0.000000, bitrate: 1283 kb/s
  
      Stream #1:0(eng): Video: svq3 (SVQ3 / 0x33515653), yuvj420p(pc), 480x272, 1153 kb/s, 24 fps, 24 tbr, 600 tbn, 600 tbc (default)
  
      Metadata:
  
        creation_time   : 2003-02-17T16:23:00.000000Z
  
        handler_name    : Apple Alias Data Handler
  
        encoder         : Sorenson Video 3
  
      Stream #1:1(eng): Audio: qdm2 (QDM2 / 0x324D4451), 44100 Hz, stereo, s16, 128 kb/s (default)
  
      Metadata:
  
        creation_time   : 2003-02-17T16:23:00.000000Z
  
        handler_name    : Apple Alias Data Handler
  
  File 'out.mp4' already exists. Overwrite ? [y/N] y
  
  Stream mapping:
  
    Stream #0:1 (h264) -> scale (graph 0)
  
    Stream #1:0 (svq3) -> scale (graph 0)
  
    overlay (graph 0) -> Stream #0:0 (libx264)
  
    Stream #1:1 -> #0:1 (qdm2 (native) -> mp3 (libmp3lame))
  
  Press [q] to stop, [?] for help
  
  [swscaler @ 000001e002b3d980] deprecated pixel format used, make sure you did set range correctly
  
  [libx264 @ 000001e07f5edd00] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
  
  [libx264 @ 000001e07f5edd00] profile Constrained Baseline, level 3.1
  
  [libx264 @ 000001e07f5edd00] 264 - core 152 r2851 ba24899 - H.264/MPEG-4 AVC codec - Copyleft 2003-2017 - http://www.videolan.org/x264.html - options: cabac=0 ref=1 deblock=0:0:0 analyse=0:0 me=dia subme=0 psy=1 psy_rd=1.00:0.00 mixed_ref=0 me_range=16 chroma_me=1 trellis=0 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=0 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=250 keyint_min=25 scenecut=0 intra_refresh=0 rc=crf mbtree=0 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=0
  
  Output #0, flv, to 'out.mp4':
  
    Metadata:
  
      title           : session
  
      encoder         : Lavf58.3.100
  
      Stream #0:0: Video: h264 (libx264) ([7][0][0][0] / 0x0007), yuv420p, 1280x720, q=-1--1, 30 fps, 1k tbn, 30 tbc (default)
  
      Metadata:
  
        encoder         : Lavc58.9.100 libx264
  
      Side data:
  
        cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
  
      Stream #0:1(eng): Audio: mp3 (libmp3lame) ([2][0][0][0] / 0x0002), 44100 Hz, stereo, s16p (default)
  
      Metadata:
  
        creation_time   : 2003-02-17T16:23:00.000000Z
  
        handler_name    : Apple Alias Data Handler
  
        encoder         : Lavc58.9.100 libmp3lame
  
  Past duration 0.889320 too large
  
  Past duration 0.629326 too large
  
  Past duration 0.979652 too large
  
  Past duration 0.909660 too large
  
  Past duration 0.646996 too large
  
  Past duration 0.881325 too large
  
  Past duration 0.728661 too large
  
  Past duration 0.970665 too large
  
  Past duration 0.610664 too large
  
  Past duration 0.851997 too large
  
  Past duration 0.779991 too large
  
  Past duration 0.870995 too large
  
  Past duration 0.752327 too large
  
  Past duration 0.970665 too large
  
  Past duration 0.679665 too large
  
  Past duration 0.951988 too large
  
  Past duration 0.913994 too large
  
  Past duration 0.641655 too large
  
  [rtsp @ 000001e07f58a700] max delay reached. need to consume packet
  
  [rtsp @ 000001e07f58a700] RTP: missed 747 packets
  
  [h264 @ 000001e07f63a140] corrupted macroblock 30 15 (total_coeff=-1)063.3kbits/s dup=0 drop=66 speed=6.52x
  
  [h264 @ 000001e07f63a140] error while decoding MB 30 15
  
  [h264 @ 000001e07f63a140] concealing 2380 DC, 2380 AC, 2380 MV errors in P frame
  
  Past duration 0.971657 too large
  
  Past duration 0.867989 too large    1280kB time=00:00:04.44 bitrate=2360.6kbits/s dup=0 drop=70 speed=1.44x
  
  [rtsp @ 000001e07f58a700] max delay reached. need to consume packet
  
  [rtsp @ 000001e07f58a700] RTP: missed 43 packets
  
  [h264 @ 000001e07f639380] corrupted macroblock 11 18 (total_coeff=-1)
  
  [h264 @ 000001e07f639380] error while decoding MB 11 18
  
  [h264 @ 000001e07f639380] concealing 2156 DC, 2156 AC, 2156 MV errors in P frame
  
  Past duration 0.895988 too large
  
  Past duration 0.708656 too large
  
  frame=  105 fps= 29 q=-1.0 Lsize=    2169kB time=00:00:08.98 bitrate=1977.1kbits/s dup=0 drop=76 speed=2.52x
  
  video:2020kB audio:141kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.363079%
  
  [libx264 @ 000001e07f5edd00] frame I:1     Avg QP:20.00  size: 84510
  
  [libx264 @ 000001e07f5edd00] frame P:104   Avg QP:18.44  size: 19074
  
  [libx264 @ 000001e07f5edd00] mb I  I16..4: 100.0%  0.0%  0.0%
  
  [libx264 @ 000001e07f5edd00] mb P  I16..4: 15.4%  0.0%  0.0%  P16..4: 23.1%  0.0%  0.0%  0.0%  0.0%    skip:61.5%
  
  [libx264 @ 000001e07f5edd00] coded y,uvDC,uvAC intra: 7.4% 7.3% 4.5% inter: 14.3% 12.2% 3.4%
  
  [libx264 @ 000001e07f5edd00] i16 v,h,dc,p: 71% 27%  1%  0%
  
  [libx264 @ 000001e07f5edd00] i8c dc,h,v,p: 58% 37%  4%  0%
  
  [libx264 @ 000001e07f5edd00] kb/s:1969.74
  
  Exiting normally, received signal 2

  second :
  Try to combine local rtsp and local video

  ffmpeg -i rtsp://192.168.1.203:554/livecast -i Xmen2trailer.mov -filter_complex "[0]scale=-1:-1[b];[1]scale=128:128[w];[b][w] overlay=10:10" -vcodec libx264 -preset ultrafast -f flv out.mp4
  
  ffmpeg version N-89672-g41e51fbcd9 Copyright (c) 2000-2018 the FFmpeg developers
  
    built with gcc 7.2.0 (GCC)
  
  [udp @ 000002aa1fe4ca00] 'circular_buffer_size' option was set but it is not supported on this build (pthread support is required)
  
  [udp @ 000002aa1fe62900] 'circular_buffer_size' option was set but it is not supported on this build (pthread support is required)
  
  [udp @ 000002aa1fe73d80] 'circular_buffer_size' option was set but it is not supported on this build (pthread support is required)
  
  [udp @ 000002aa1fe84040] 'circular_buffer_size' option was set but it is not supported on this build (pthread support is required)
  
  Input #0, rtsp, from 'rtsp://192.168.1.203:554/livecast':
  
    Metadata:
  
      title           : session
  
    Duration: N/A, start: 0.000000, bitrate: N/A
  
      Stream #0:0: Audio: aac (LC), 48000 Hz, stereo, fltp
  
      Stream #0:1: Video: h264 (Constrained Baseline), yuv420p(progressive), 1920x1080, 30 fps, 30 tbr, 90k tbn, 60 tbc
  
  Input #1, mov,mp4,m4a,3gp,3g2,mj2, from 'Xmen2trailer.mov':
  
    Metadata:
  
      creation_time   : 2003-02-17T16:23:00.000000Z
  
      title           : X2
  
      title-eng       : X2
  
      copyright-eng   : ┬⌐2003 20th Century Fox
  
      comment         : QuickTime 5 version encoded and delivered by www.apple.com/trailers/
  
      copyright       : ┬⌐2003 20th Century Fox
  
      comment-eng     : QuickTime 5 version encoded and delivered by www.apple.com/trailers/
  
    Duration: 00:02:29.08, start: 0.000000, bitrate: 1283 kb/s
  
      Stream #1:0(eng): Video: svq3 (SVQ3 / 0x33515653), yuvj420p(pc), 480x272, 1153 kb/s, 24 fps, 24 tbr, 600 tbn, 600 tbc (default)
  
      Metadata:
  
        creation_time   : 2003-02-17T16:23:00.000000Z
  
        handler_name    : Apple Alias Data Handler
  
        encoder         : Sorenson Video 3
  
      Stream #1:1(eng): Audio: qdm2 (QDM2 / 0x324D4451), 44100 Hz, stereo, s16, 128 kb/s (default)
  
      Metadata:
  
        creation_time   : 2003-02-17T16:23:00.000000Z
  
        handler_name    : Apple Alias Data Handler
  
  File 'out.mp4' already exists. Overwrite ? [y/N] y
  
  Stream mapping:
  
    Stream #0:1 (h264) -> scale (graph 0)
  
    Stream #1:0 (svq3) -> scale (graph 0)
  
    overlay (graph 0) -> Stream #0:0 (libx264)
  
    Stream #0:0 -> #0:1 (aac (native) -> mp3 (libmp3lame))
  
  Press [q] to stop, [?] for help
  
  [swscaler @ 000002aa2355ba40] deprecated pixel format used, make sure you did set range correctly
  
  [libx264 @ 000002aa202d9600] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
  
  [libx264 @ 000002aa202d9600] profile Constrained Baseline, level 4.0
  
  [libx264 @ 000002aa202d9600] 264 - core 152 r2851 ba24899 - H.264/MPEG-4 AVC codec - Copyleft 2003-2017 - http://www.videolan.org/x264.html - options: cabac=0 ref=1 deblock=0:0:0 analyse=0:0 me=dia subme=0 psy=1 psy_rd=1.00:0.00 mixed_ref=0 me_range=16 chroma_me=1 trellis=0 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=0 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=250 keyint_min=25 scenecut=0 intra_refresh=0 rc=crf mbtree=0 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=0
  
  Output #0, flv, to 'out.mp4':
  
    Metadata:
  
      title           : session
  
      encoder         : Lavf58.3.100
  
      Stream #0:0: Video: h264 (libx264) ([7][0][0][0] / 0x0007), yuv420p, 1920x1080, q=-1--1, 30 fps, 1k tbn, 30 tbc (default)
  
      Metadata:
  
        encoder         : Lavc58.9.100 libx264
  
      Side data:
  
        cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
  
      Stream #0:1: Audio: mp3 (libmp3lame) ([2][0][0][0] / 0x0002), 48000 Hz, stereo, fltp
  
      Metadata:
  
        encoder         : Lavc58.9.100 libmp3lame
  
  Past duration 0.711662 too large
  
  Past duration 0.822990 too large
  
  Past duration 0.854332 too large
  
  [rtsp @ 000002aa1fe4a680] max delay reached. need to consume packet
  
  [rtsp @ 000002aa1fe4a680] RTP: missed 1315 packets
  
  [h264 @ 000002aa20262580] Invalid level prefix
  
  [h264 @ 000002aa20262580] error while decoding MB 12 37
  
  [h264 @ 000002aa20262580] concealing 3757 DC, 3757 AC, 3757 MV errors in I frame
  
  Past duration 0.732323 too large     256kB time=00:00:02.88 bitrate= 727.2kbits/s dup=0 drop=13 speed=5.76x
  
  Past duration 0.824333 too large
  
  Past duration 0.988991 too large
  
  Past duration 0.862328 too large    1024kB time=00:00:03.38 bitrate=2477.4kbits/s dup=0 drop=21 speed=3.34x
  
  Past duration 0.861320 too large
  
  Past duration 0.883324 too large
  
  Past duration 0.910652 too large    1280kB time=00:00:03.94 bitrate=2659.3kbits/s dup=0 drop=30 speed=2.59x
  
  Past duration 0.954659 too large
  
  Past duration 0.790657 too large    1792kB time=00:00:04.40 bitrate=3335.6kbits/s dup=0 drop=37 speed=2.17x
  
  Past duration 0.861320 too large
  
  Past duration 0.943657 too large
  
  Past duration 0.988655 too large    2304kB time=00:00:04.90 bitrate=3849.6kbits/s dup=0 drop=45 speed=1.94x
  
  Past duration 0.810326 too large
  
  Past duration 0.893654 too large
  
  Past duration 0.822319 too large    3072kB time=00:00:05.40 bitrate=4655.2kbits/s dup=0 drop=53 speed=1.78x
  
  Past duration 0.902657 too large
  
  Past duration 0.909660 too large
  
  Past duration 0.779655 too large    3328kB time=00:00:05.93 bitrate=4596.7kbits/s dup=0 drop=61 speed=1.67x
  
  Past duration 0.957664 too large
  
  Past duration 0.778328 too large    3840kB time=00:00:06.43 bitrate=4890.0kbits/s dup=0 drop=68 speed=1.59x
  
  Past duration 0.861992 too large
  
  Past duration 0.992653 too large
  
  Past duration 0.729652 too large    4352kB time=00:00:06.94 bitrate=5133.4kbits/s dup=0 drop=76 speed=1.53x
  
  [rtsp @ 000002aa1fe4a680] max delay reached. need to consume packet
  
  [rtsp @ 000002aa1fe4a680] RTP: missed 2 packets
  
  Past duration 0.857994 too large
  
  [h264 @ 000002aa20260580] Invalid level prefix
  
  [h264 @ 000002aa20260580] error while decoding MB 43 62
  
  [h264 @ 000002aa20260580] concealing 726 DC, 726 AC, 726 MV errors in P frame
  
  Past duration 0.889000 too large
  
  Past duration 0.800987 too large    4864kB time=00:00:07.42 bitrate=5365.7kbits/s dup=0 drop=83 speed=1.47x
  
  Past duration 0.909660 too large
  
  Past duration 0.946327 too large
  
  Past duration 0.795998 too large
  
  Past duration 0.902321 too large    5376kB time=00:00:07.95 bitrate=5539.0kbits/s dup=0 drop=91 speed=1.43x
  
  Past duration 0.841652 too large
  
  Past duration 0.859657 too large
  
  Past duration 0.992332 too large    5632kB time=00:00:08.43 bitrate=5472.3kbits/s dup=0 drop=99 speed=1.39x
  
  Past duration 0.893990 too large
  
  Past duration 0.947990 too large    6400kB time=00:00:08.95 bitrate=5853.4kbits/s dup=0 drop=106 speed=1.36x
  
  Past duration 0.678322 too large
  
  Past duration 0.994987 too large
  
  Past duration 0.942329 too large
  
  Past duration 0.975319 too large
  
  Past duration 0.702660 too large    6912kB time=00:00:09.45 bitrate=5986.8kbits/s dup=0 drop=114 speed=1.34x
  
  Past duration 0.821663 too large
  
  Past duration 0.937325 too large
  
  Past duration 0.992989 too large
  
  Past duration 0.684990 too large    7168kB time=00:00:09.96 bitrate=5895.0kbits/s dup=0 drop=122 speed=1.31x
  
  Past duration 0.763664 too large
  
  Past duration 0.990318 too large
  
  Past duration 0.921333 too large
  
  Past duration 0.945320 too large
  
  Past duration 0.711327 too large    7680kB time=00:00:10.49 bitrate=5994.1kbits/s dup=0 drop=130 speed=1.29x
  
  Past duration 0.841652 too large
  
  Past duration 0.948997 too large
  
  Past duration 0.994652 too large
  
  Past duration 0.759987 too large    8448kB time=00:00:11.04 bitrate=6267.0kbits/s dup=0 drop=138 speed=1.28x
  
  Past duration 0.860985 too large
  
  Past duration 0.984993 too large
  
  Past duration 0.796989 too large    8960kB time=00:00:11.50 bitrate=6382.1kbits/s dup=0 drop=145 speed=1.26x
  
  Past duration 0.914665 too large
  
  Past duration 0.804329 too large    9472kB time=00:00:12.02 bitrate=6452.2kbits/s dup=0 drop=152 speed=1.25x
  
  frame=  303 fps= 31 q=-1.0 Lsize=   10246kB time=00:00:12.33 bitrate=6803.2kbits/s dup=0 drop=156 speed=1.25x
  
  video:10039kB audio:193kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.140463%
  
  [libx264 @ 000002aa202d9600] frame I:2     Avg QP:18.00  size:199681
  
  [libx264 @ 000002aa202d9600] frame P:301   Avg QP:18.96  size: 32823
  
  [libx264 @ 000002aa202d9600] mb I  I16..4: 100.0%  0.0%  0.0%
  
  [libx264 @ 000002aa202d9600] mb P  I16..4:  9.3%  0.0%  0.0%  P16..4: 32.1%  0.0%  0.0%  0.0%  0.0%    skip:58.6%
  
  [libx264 @ 000002aa202d9600] coded y,uvDC,uvAC intra: 12.9% 34.0% 11.0% inter: 12.0% 22.7% 6.2%
  
  [libx264 @ 000002aa202d9600] i16 v,h,dc,p: 38% 49%  9%  4%
  
  [libx264 @ 000002aa202d9600] i8c dc,h,v,p: 38% 42% 14%  6%
  
  [libx264 @ 000002aa202d9600] kb/s:6833.78
  
  Exiting normally, received signal 2.

  third :
  Combine RTMP from phone and RTSP video from server

  ffmpeg -i rtsp://192.168.1.203:554/livecast -i rtmp://192.168.1.152:1935/ingest/test -filter_complex "[0]scale=-1:-1[b];[1]scale=200:200[w];[b][w] overlay=10:10" -c:v libx264 -preset ultrafast -f flv outputRTMP.mp4
  
  ffmpeg version N-89672-g41e51fbcd9 Copyright (c) 2000-2018 the FFmpeg developers
  
    built with gcc 7.2.0 (GCC)
  
    configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-bzlib --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-amf --enable-cuda --enable-cuvid --enable-d3d11va --enable-nvenc --enable-dxva2 --enable-avisynth --enable-libmfx
  
    libavutil      56.  7.100 / 56.  7.100
  
    libavcodec     58.  9.100 / 58.  9.100
  
    libavformat    58.  3.100 / 58.  3.100
  
    libavdevice    58.  0.100 / 58.  0.100
  
    libavfilter     7.  8.100 /  7.  8.100
  
    libswscale      5.  0.101 /  5.  0.101
  
    libswresample   3.  0.101 /  3.  0.101
  
    libpostproc    55.  0.100 / 55.  0.100
  
  [udp @ 0000018c0ccbca40] 'circular_buffer_size' option was set but it is not supported on this build (pthread support is required)
  
  [udp @ 0000018c0ccd2900] 'circular_buffer_size' option was set but it is not supported on this build (pthread support is required)
  
  [udp @ 0000018c0cce3dc0] 'circular_buffer_size' option was set but it is not supported on this build (pthread support is required)
  
  [udp @ 0000018c0ccf4080] 'circular_buffer_size' option was set but it is not supported on this build (pthread support is required)
  
  Input #0, rtsp, from 'rtsp://192.168.1.203:554/livecast':
  
    Metadata:
  
      title           : session
  
    Duration: N/A, start: 0.000000, bitrate: N/A
  
      Stream #0:0: Audio: aac (LC), 48000 Hz, stereo, fltp
  
      Stream #0:1: Video: h264 (Constrained Baseline), yuv420p(progressive), 1920x1080, 30 fps, 30 tbr, 90k tbn, 60 tbc
  
  Input #1, flv, from 'rtmp://192.168.1.152:1935/ingest/test':
  
    Metadata:
  
      Server          : NGINX RTMP (github.com/arut/nginx-rtmp-module)
  
      displayWidth    : 640
  
      displayHeight   : 480
  
      fps             : 0
  
      profile         :
  
      level           :
  
    Duration: 00:00:00.00, start: 173.197000, bitrate: N/A
  
      Stream #1:0: Audio: aac (LC), 44100 Hz, mono, fltp, 47 kb/s
  
      Stream #1:1: Video: h264 (Baseline), yuv420p(tv, smpte170m/bt470bg/smpte170m, progressive), 640x480, 1999 kb/s, 29.92 fps, 29.92 tbr, 1k tbn
  
  File 'outputRTMP.mp4' already exists. Overwrite ? [y/N] y
  
  Stream mapping:
  
    Stream #0:1 (h264) -> scale (graph 0)
  
    Stream #1:1 (h264) -> scale (graph 0)
  
    overlay (graph 0) -> Stream #0:0 (libx264)
  
    Stream #0:0 -> #0:1 (aac (native) -> mp3 (libmp3lame))
  
  Press [q] to stop, [?] for help
  
  [libx264 @ 0000018c0d1321c0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
  
  [libx264 @ 0000018c0d1321c0] profile Constrained Baseline, level 4.0
  
  [libx264 @ 0000018c0d1321c0] 264 - core 152 r2851 ba24899 - H.264/MPEG-4 AVC codec - Copyleft 2003-2017 - http://www.videolan.org/x264.html - options: cabac=0 ref=1 deblock=0:0:0 analyse=0:0 me=dia subme=0 psy=1 psy_rd=1.00:0.00 mixed_ref=0 me_range=16 chroma_me=1 trellis=0 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=0 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=250 keyint_min=25 scenecut=0 intra_refresh=0 rc=crf mbtree=0 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=0
  
  Output #0, flv, to 'outputRTMP.mp4':
  
    Metadata:
  
      title           : session
  
      encoder         : Lavf58.3.100
  
      Stream #0:0: Video: h264 (libx264) ([7][0][0][0] / 0x0007), yuv420p, 1920x1080, q=-1--1, 30 fps, 1k tbn, 30 tbc (default)
  
      Metadata:
  
        encoder         : Lavc58.9.100 libx264
  
      Side data:
  
        cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
  
      Stream #0:1: Audio: mp3 (libmp3lame) ([2][0][0][0] / 0x0002), 48000 Hz, stereo, fltp
  
      Metadata:
  
        encoder         : Lavc58.9.100 libmp3lame
  
  Past duration 0.931999 too large
  
  [rtsp @ 0000018c0ccba6c0] max delay reached. need to consume packet
  
  [rtsp @ 0000018c0ccba6c0] RTP: missed 92 packets
  
  [rtsp @ 0000018c0ccba6c0] max delay reached. need to consume packet
  
  [rtsp @ 0000018c0ccba6c0] RTP: missed 2904 packets
  
  Past duration 0.671654 too large
  
  [h264 @ 0000018c0d0da140] concealing 4160 DC, 4160 AC, 4160 MV errors in I frame
  
  Past duration 0.991997 too large
  
  Past duration 0.791328 too large     256kB time=00:00:05.12 bitrate= 409.3kbits/s dup=0 drop=12 speed=4.14x
  
  Past duration 0.969994 too large
  
  [rtsp @ 0000018c0ccba6c0] max delay reached. need to consume packet
  
  [rtsp @ 0000018c0ccba6c0] RTP: missed 573 packets
  
  [h264 @ 0000018c0d0d8a80] concealing 2468 DC, 2468 AC, 2468 MV errors in P frame
  
  Past duration 0.670326 too large
  
  [rtsp @ 0000018c0ccba6c0] max delay reached. need to consume packet
  
  [rtsp @ 0000018c0ccba6c0] RTP: missed 25 packets
  
  [h264 @ 0000018c0d0d8a80] concealing 6479 DC, 6479 AC, 6479 MV errors in P frame
  
  Past duration 0.961327 too large     512kB time=00:00:11.10 bitrate= 377.7kbits/s dup=0 drop=16 speed=1.57x
  
  Past duration 0.689323 too large
  
  [rtsp @ 0000018c0ccba6c0] max delay reached. need to consume packet
  
  [rtsp @ 0000018c0ccba6c0] RTP: missed 620 packets
  
  [h264 @ 0000018c0d0da140] negative number of zero coeffs at 33 32
  
  [h264 @ 0000018c0d0da140] error while decoding MB 33 32
  
  [h264 @ 0000018c0d0da140] concealing 4336 DC, 4336 AC, 4336 MV errors in P frame
  
  Past duration 0.790321 too large
  
  Past duration 0.910332 too large     768kB time=00:00:12.23 bitrate= 514.3kbits/s dup=0 drop=18 speed=1.62x
  
  [rtsp @ 0000018c0ccba6c0] max delay reached. need to consume packet
  
  [rtsp @ 0000018c0ccba6c0] RTP: missed 24 packets
  
  [h264 @ 0000018c0d0da140] corrupted macroblock 22 25 (total_coeff=-1)
  
  [h264 @ 0000018c0d0da140] error while decoding MB 22 25
  
  [h264 @ 0000018c0d0da140] concealing 5151 DC, 5151 AC, 5151 MV errors in P frame
  
  Past duration 0.924324 too large    1024kB time=00:00:17.03 bitrate= 492.5kbits/s dup=0 drop=19 speed= 1.3x
  
  Past duration 0.656654 too large
  
  [rtsp @ 0000018c0ccba6c0] max delay reached. need to consume packet
  
  [rtsp @ 0000018c0ccba6c0] RTP: missed 516 packets
  
  [h264 @ 0000018c0d0daf00] Invalid level prefix
  
  [h264 @ 0000018c0d0daf00] error while decoding MB 0 36
  
  [h264 @ 0000018c0d0daf00] concealing 3889 DC, 3889 AC, 3889 MV errors in P frame
  
  [rtsp @ 0000018c0ccba6c0] max delay reached. need to consume packet
  
  [rtsp @ 0000018c0ccba6c0] RTP: missed 132 packets
  
  [h264 @ 0000018c0d0d8a80] top block unavailable for requested intra mode -1
  
  [h264 @ 0000018c0d0d8a80] error while decoding MB 55 26
  
  [h264 @ 0000018c0d0d8a80] concealing 5034 DC, 5034 AC, 5034 MV errors in I frame
  
  [h264 @ 0000018c0d0d9cc0] concealing 2621 DC, 2621 AC, 2621 MV errors in P frame
  
  Past duration 0.935661 too large
  
  Past duration 0.878319 too large
  
  Past duration 0.929329 too large    1280kB time=00:00:18.32 bitrate= 572.1kbits/s dup=0 drop=22 speed=1.27x
  
  [rtsp @ 0000018c0ccba6c0] max delay reached. need to consume packet
  
  [rtsp @ 0000018c0ccba6c0] RTP: missed 560 packets
  
  [h264 @ 0000018c0d0d8140] Invalid level prefix
  
  Past duration 0.661659 too large
  
  [h264 @ 0000018c0d0d8140] error while decoding MB 91 24
  
  [h264 @ 0000018c0d0d8140] concealing 5214 DC, 5214 AC, 5214 MV errors in P frame
  
  Past duration 0.823662 too large
  
  Past duration 0.864662 too large
  
  [rtsp @ 0000018c0ccba6c0] max delay reached. need to consume packet
  
  [rtsp @ 0000018c0ccba6c0] RTP: missed 29 packets
  
  [h264 @ 0000018c0d0d8140] corrupted macroblock 42 3 (total_coeff=-1)
  
  [h264 @ 0000018c0d0d8140] error while decoding MB 42 3
  
  [h264 @ 0000018c0d0d8140] concealing 7760 DC, 7760 AC, 7760 MV errors in P frame
  
  Past duration 0.780663 too large    1792kB time=00:00:19.50 bitrate= 752.8kbits/s dup=0 drop=24 speed=1.27x
  
  Past duration 0.900322 too large
  
  Past duration 0.990990 too large
  
  [rtsp @ 0000018c0ccba6c0] max delay reached. need to consume packet
  
  [rtsp @ 0000018c0ccba6c0] RTP: missed 565 packets
  
  [h264 @ 0000018c0d0d8140] corrupted macroblock 83 27 (total_coeff=-1)
  
  [h264 @ 0000018c0d0d8140] Past duration 0.862999 too large
  
  error while decoding MB 83 27
  
  [h264 @ 0000018c0d0d8140] concealing 4866 DC, 4866 AC, 4866 MV errors in P frame
  
  [rtsp @ 0000018c0ccba6c0] max delay reached. need to consume packet
  
  [rtsp @ 0000018c0ccba6c0] RTP: missed 7 packets
  
  [h264 @ 0000018c0d0d8f00] top block unavailable for requested intra mode
  
  [h264 @ 0000018c0d0d8f00] error while decoding MB 79 16
  
  [h264 @ 0000018c0d0d8f00] concealing 2661 DC, 2661 AC, 2661 MV errors in P frame
  
  Past duration 0.907997 too large
  
  [rtsp @ 0000018c0ccba6c0] max delay reached. need to consume packet= 816.0kbits/s dup=0 drop=28 speed=1.29x
  
  [rtsp @ 0000018c0ccba6c0] RTP: missed 19 packets
  
  [h264 @ 0000018c0d0d9cc0] corrupted macroblock 88 59 (total_coeff=-1)
  
  [h264 @ 0000018c0d0d9cc0] error while decoding MB 88 59
  
  [h264 @ 0000018c0d0d9cc0] concealing 1041 DC, 1041 AC, 1041 MV errors in P frame
  
  [rtsp @ 0000018c0ccba6c0] max delay reached. need to consume packet
  
  [rtsp @ 0000018c0ccba6c0] RTP: missed 6 packets
  
  [h264 @ 0000018c0d0d8140] out of range intra chroma pred mode
  
  [h264 @ 0000018c0d0d8140] error while decoding MB 118 6
  
  [h264 @ 0000018c0d0d8140] concealing 3320 DC, 3320 AC, 3320 MV errors in P frame
  
  Past duration 0.845665 too large    2304kB time=00:00:20.72 bitrate= 910.6kbits/s dup=0 drop=29 speed=1.23x
  
  [rtsp @ 0000018c0ccba6c0] max delay reached. need to consume packet
  
  [rtsp @ 0000018c0ccba6c0] RTP: missed 574 packets
  
  [h264 @ 0000018c0d0d8140] negative number of zero coeffs at 39 26
  
  [h264 @ 0000018c0d0d8140] error while decoding MB 39 26
  
  [h264 @ 0000018c0d0d8140] concealing 5050 DC, 5050 AC, 5050 MV errors in P frame
  
  Past duration 0.950996 too large
  
  [rtsp @ 0000018c0ccba6c0] max delay reached. need to consume packet
  
  [rtsp @ 0000018c0ccba6c0] RTP: missed 37 packets
  
  [h264 @ 0000018c0d0d8140] corrupted macroblock 48 37 (total_coeff=-1)
  
  [h264 @ 0000018c0d0d8140] error while decoding MB 48 37
  
  [h264 @ 0000018c0d0d8140] concealing 3721 DC, 3721 AC, 3721 MV errors in P frame
  
  Past duration 0.789330 too large    2816kB time=00:00:22.02 bitrate=1047.5kbits/s dup=0 drop=33 speed=1.23x
  
  Past duration 0.848320 too large
  
  [rtsp @ 0000018c0ccba6c0] max delay reached. need to consume packet
  
  [rtsp @ 0000018c0ccba6c0] RTP: missed 581 packets
  
  [h264 @ 0000018c0d0d8f00] corrupted macroblock 13 10 (total_coeff=-1)
  
  [h264 @ 0000018c0d0d8f00] error while decoding MB 13 10
  
  Past duration 0.875664 too large
  
  [h264 @ 0000018c0d0d8f00] concealing 6952 DC, 6952 AC, 6952 MV errors in P frame
  
  [rtsp @ 0000018c0ccba6c0] max delay reached. need to consume packet=1181.0kbits/s dup=0 drop=35 speed=1.25x
  
  [rtsp @ 0000018c0ccba6c0] RTP: missed 6 packets
  
  [h264 @ 0000018c0d0d8f00] corrupted macroblock 72 37 (total_coeff=-1)
  
  [h264 @ 0000018c0d0d8f00] error while decoding MB 72 37
  
  [h264 @ 0000018c0d0d8f00] concealing 3675 DC, 3675 AC, 3675 MV errors in P frame
  
  frame=  101 fps=5.3 q=-1.0 Lsize=    4095kB time=00:00:23.67 bitrate=1417.0kbits/s dup=0 drop=37 speed=1.25x
  
  video:3739kB audio:340kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.405426%
  
  [libx264 @ 0000018c0d1321c0] frame I:1     Avg QP:20.00  size:178581
  
  [libx264 @ 0000018c0d1321c0] frame P:100   Avg QP:20.42  size: 36495
  
  [libx264 @ 0000018c0d1321c0] mb I  I16..4: 100.0%  0.0%  0.0%
  
  [libx264 @ 0000018c0d1321c0] mb P  I16..4: 11.8%  0.0%  0.0%  P16..4: 31.7%  0.0%  0.0%  0.0%  0.0%    skip:56.5%
  
  [libx264 @ 0000018c0d1321c0] coded y,uvDC,uvAC intra: 26.5% 36.0% 9.2% inter: 15.0% 18.5% 3.4%
  
  [libx264 @ 0000018c0d1321c0] i16 v,h,dc,p: 44% 39% 10%  7%
  
  [libx264 @ 0000018c0d1321c0] i8c dc,h,v,p: 36% 36% 21%  7%
  
  [libx264 @ 0000018c0d1321c0] kb/s:1383.65
  
  Exiting normally, received signal 2.

  So If you have some ideas for me it will help. Thank you