Recherche avancée

Sur d’autres sites (6730)

• Is Google Analytics Accurate ? 6 Important Caveats

  8 novembre 2022, par Erin

  It’s no secret that accurate website analytics is crucial for growing your online business — and Google Analytics is often the go-to source for insights. 

  But is Google Analytics data accurate ? Can you fully trust the provided numbers ? Here’s a detailed explainer.

  How Accurate is Google Analytics ? A Data-Backed Answer 

  When properly configured, Google Analytics (Universal Analytics and Google Analytics 4) is moderately accurate for global traffic collection. That said : Google Analytics doesn’t accurately report European traffic. 

  According to GDPR provisions, sites using GA products must display a cookie consent banner. This consent is required to collect third-party cookies — a tracking mechanism for identifying users across web properties.

  Google Analytics (GA) cannot process data about the user’s visit if they rejected cookies. In such cases, your analytics reports will be incomplete.

  Cookie rejection refers to visitors declining or blocking cookies from ever being collected by a specific website (or within their browser). It immediately affects the accuracy of all metrics in Google Analytics.

  Google Analytics is not accurate in locations where cookie consent to tracking is legally required. Most consumers don’t like disruptive cookie banners or harbour concerns about their privacy — and chose to reject tracking. 

  This leaves businesses with incomplete data, which, in turn, results in : 

  • Lower traffic counts as you’re not collecting 100% of the visitor data. 
  • Loss of website optimisation capabilities. You can’t make data-backed decisions due to inconsistent reporting

  For the above reasons, many companies now consider cookieless website tracking apps that don’t require consent screen displays. 

  Why is Google Analytics Not Accurate ? 6 Causes and Solutions 

  A high rejection rate of cookie banners is the main reason for inaccurate Google Analytics reporting. In addition, your account settings can also hinder Google Analytics’ accuracy.

  If your analytics data looks wonky, check for these six Google Analytics accuracy problems. 

  You Need to Secure Consent to Cookies Collection 

  To be GDPR-compliant, you must display a cookie consent screen to all European users. Likewise, other jurisdictions and industries require similar measures for user data collection. 

  This is a nuisance for many businesses since cookie rejection undermines their remarketing capabilities. Hence, some try to maximise cookie acceptance rates with dark patterns. For example : hide the option to decline tracking or make the texts too small. 

  

  Sadly, not everyone’s treating users with respect. A joint study by German and American researchers found that only 11% of US websites (from a sample of 5,000+) use GDPR-compliant cookie banners.

  As a result, many users aren’t aware of the background data collection to which they have (or have not) given consent. Another analysis of 200,000 cookies discovered that 70% of third-party marketing cookies transfer user data outside of the EU — a practice in breach of GDPR.

  Naturally, data regulators and activities are after this issue. In April 2022, Google was pressured to introduce a ‘reject all’ cookies button to all of its products (a €150 million compliance fine likely helped with that). Whereas, noyb has lodged over 220 complaints against individual websites with deceptive cookie consent banners.

  The takeaway ? Messing up with the cookie consent mechanism can get you in legal trouble. Don’t use sneaky banners as there are better ways to collect website traffic statistics. 

  Solution : Try Matomo GDPR-Friendly Analytics 

  Fill in the gaps in your traffic analytics with Matomo – a fully GDPR-compliant product that doesn’t rely on third-party cookies for tracking web visitors. Because of how it is designed, the French data protection authority (CNIL) confirmed that Matomo can be used to collect data without tracking consent.

  With Matomo, you can track website users without asking for cookie consent. And when you do, we supply you with a compact, compliant, non-disruptive cookie banner design. 

  Your Google Tag Isn’t Embedded Correctly 

  Google Tag (gtag.js) is a web tracking script that sends data to your Google Analytics, Google Ads and Google Marketing Platform.

  A corrupted gtag.js installation can create two accuracy issues : 

  • Duplicate page tracking 
  • Missing script installation 

  Is there a way to tell if you’re affected ?

  Yes. You may have duplicate scripts installed if you have a very low bounce rate on most website pages (below 15% – 20%). The above can happen if you’re using a WordPress GA plugin and additionally embed gtag.js straight in your website code. 

  A tell-tale sign of a missing script on some pages is low/no traffic stats. Google alerts you about this with a banner : 

  

  Solution : Use Available Troubleshooting Tools 

  Use Google Analytics Debugger extension to analyse pages with low bounce rates. Use the search bar to locate duplicate code-tracking elements. 

  Alternatively, you can use Google Tag Assistant for diagnosing snippet install and troubleshooting issues on individual pages. 

  If the above didn’t work, re-install your analytics script. 

  Machine Learning and Blended Data Are Applied

  Google Analytics 4 (GA4) relies a lot on machine learning and algorithmic predictions.

  By applying Google’s advanced machine learning models, the new Analytics can automatically alert you to significant trends in your data. [...] For example, it calculates churn probability so you can more efficiently invest in retaining customers.

  Vidhya Srinivasan, VP of Measurement, Analytics and Buying Platforms at Google

  On the surface, the above sounds exciting. In practice, Google’s application of predictive algorithms means you’re not seeing actual data. 

  To offer a variation of cookieless tracking, Google algorithms close the gaps in reporting by creating models (i.e., data-backed predictions) instead of reporting on actual user behaviours. Therefore, your GA4 numbers may not be accurate.

  For bigger web properties (think websites with 1+ million users), Google also relies on data sampling — a practice of extrapolating data analytics, based on a data subset, rather than the entire dataset. Once again, this can lead to inconsistencies in reporting with some numbers (e.g., average conversion rates) being inflated or downplayed. 

  Solution : Try an Alternative Website Analytics App 

  Unlike GA4, Matomo reports consist of 100% unsampled data. All the aggregated reporting you see is based on real user data (not guesstimation). 

  Moreover, you can migrate from Universal Analytics (UA) to Matomo without losing access to your historical records. GA4 doesn’t yet have any backward compatibility.

  Spam and Bot Traffic Isn’t Filtered Out 

  Surprise ! 42% of all Internet traffic is generated by bots, of which 27.7% are bad ones.

  Good bots (aka crawlers) do essential web “housekeeping” tasks like indexing web pages. Bad bots distribute malware, spam contact forms, hack user accounts and do other nasty stuff. 

  A lot of such spam bots are designed specifically for web analytics apps. The goal ? Flood your dashboard with bogus data in hopes of getting some return action from your side. 

  Types of Google Analytics Spam :

  • Referral spam. Spambots hijack the referrer, displayed in your GA referral traffic report to indicate a page visit from some random website (which didn’t actually occur). 
  • Event spam. Bots generate fake events with free language entries enticing you to visit their website. 
  • Ghost traffic spam. Malicious parties can also inject fake pageviews, containing URLs that they want you to click. 

  Obviously, such spammy entities distort the real website analytics numbers. 

  Solution : Set Up Bot/Spam Filters 

  Google Analytics 4 has automatic filtering of bot traffic enabled for all tracked Web and App properties. 

  But if you’re using Universal Analytics, you’ll have to manually configure spam filtering. First, create a new view and then set up a custom filter. Program it to exclude :

  • Filter Field : Request URI
  • Filter Pattern : Bot traffic URL

  Once you’ve configured everything, validate the results using Verify this filter feature. Then repeat the process for other fishy URLs, hostnames and IP addresses. 

  You Don’t Filter Internal Traffic 

  Your team(s) spend a lot of time on your website — and their sporadic behaviours can impair your traffic counts and other website metrics.

  To keep your data “employee-free”, exclude traffic from : 

  • Your corporate IPs addresses 
  • Known personal IPs of employees (for remote workers) 

  If you also have a separate stage version of your website, you should also filter out all traffic coming from it. Your developers, contractors and marketing people spend a lot of time fiddling with your website. This can cause a big discrepancy in average time on page and engagement rates. 

  Solution : Set Internal Traffic Filters 

  Google provides instructions for excluding internal traffic from your reports using IPv4/IPv6 address filters. 

  

  Session Timeouts After 30 Minutes 

  After 30 minutes of inactivity, Google Analytics tracking sessions start over. Inactivity means no recorded interaction hits during this time. 

  Session timeouts can be a problem for some websites as users often pin a tab to check it back later. Because of this, you can count the same user twice or more — and this leads to skewed reporting. 

  Solution : Programme Custom Timeout Sessions

  You can codify custom cookie timeout sessions with the following code snippets : 

  • _setSessionCookieTimeout. Set a custom new session cookie timeout in milliseconds.
  • _setVisitorCookieTimeout. Sets a custom Google Analytics visitor cookie expiration time frame in milliseconds.

  Final Thoughts 

  Thanks to its scale and longevity, Google Analytics has some strong sides, but its data accuracy isn’t 100% perfect.

  The inability to capture analytics data from users who don’t consent to cookie tracking and data sampling applied to bigger web properties may be a deal-breaker for your business. 

  If that’s the case, try Matomo — a GDPR-compliant, accurate web analytics solution. Start your 21-day free trial now. No credit card required.

  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 hereby accept the terms and conditions and the 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

  

• Organic Traffic : What It Is and How to Increase It

  19 septembre 2023, par Erin — Analytics Tips

  Organic traffic can be a website’s most valuable source of visitors. But it can also be the hardest form of traffic to acquire. While paid ads can generate traffic almost instantly, you need to invest time and energy into growing traffic from search engines.

  And it all starts with understanding exactly what organic traffic is. 

  If you want to understand what organic traffic is, how to measure it and how to generate more of it, then this article is for you.

  What is organic traffic ?

  Organic traffic is the visitors your website receives from the unpaid results on search engines like Google, Bing and DuckDuckGo. 

  The higher your website ranks in the search engine results pages and the more search terms your website ranks for, the more organic traffic your site will receive. 

  Organic traffic is highly valued by marketers, partly because it has a much higher clickthrough rate than PPC ads. Research shows the top organic result has a 39.8% CTR compared to just 2.1% for paid ads.

  

  So, while you can pay to appear at the top of search engines (using a platform like Google Ads, for instance), you probably won’t receive as much traffic as you would if you were to rank organically in the same search engine.

  What other types of traffic are there ? 

  Organic traffic isn’t the only type of traffic your website can get. You can also receive traffic from the following channels :

  Direct

  People familiar with your site may visit it directly, either by entering your URL into their browser or accessing it through a bookmarked link ; both scenarios are counted as direct traffic.

  Social

  Social traffic includes visits to your website from a social media platform. For example, if someone shares a link to your website on Facebook, any user who clicks on it will be counted as social traffic. 

  Websites

  Social media isn’t the only way for someone to share a link to your website. Any time a visitor finds your website by clicking on a link on another website, it will be counted as “websites”. This is also known as referral traffic on some analytics platforms. 

  Campaign

  Campaign traffic encompasses both paid and unpaid traffic sources. Paid sources include advertising on search engines and social media (also known as PPC or pay-per-click), as well as collaborations with influencers and sponsorships. Unpaid sources, such as your organisation’s email newsletters, cross-promotions with other businesses and other similar methods, are also part of this mix. 

  In simpler terms, it’s the traffic you deliberately direct to your site, and you utilise campaign tracking URLs to measure how these efforts impact your ROI.

  A word on multi-touch attribution

  If you are interested in learning more about types of traffic to track conversions, then it’s important to understand multi-touch attribution. The truth is most customers won’t just use a single traffic channel to find your website. In reality, the modern customer journey has multiple touchpoints, and customers may first find your site through an ad and then search for more about your brand on Google before going directly to your website. 

  

  You are at risk of under or overestimating the effectiveness of a marketing channel without using multi-touch attribution tracking. With this marketing analytics model, you can accurately weigh the impact of every channel and allocate budgets accordingly. 

  What are the benefits of organic traffic ?

  Getting more organic traffic is a common marketing goal for many companies. And it’s not surprising why. There’s a lot to love about organic traffic. 

  For starters, it’s arguably the most cost-effective traffic your site can receive. You will still need to pay to create and distribute organic content (whether it’s a blog post or product page). You don’t need to pay for it to show up in a search engine. You continue to get value from organic traffic long after you’ve created the page, too. A good piece of organic content can receive high volumes of monthly visitors for years. That’s a stark difference from paid ads, where traffic stops as soon as you turn off the ad. 

  It also puts your website in front of a massive audience, with Google alone processing over 3.5 billion searches every day. There’s a good chance that if your target audience is looking for a solution to their problems, they start with Google. 

  Organic traffic is fantastic at building brand awareness. Usually, users aren’t searching for a specific brand or company. They are searching for informational keywords (“how to brew the perfect cup of coffee”) or unbranded transactional keywords (“best home workout machine”). In both cases, customers can use search engines to become aware of your brand. 

  Finally, organic traffic brings in high-quality leads at every marketing funnel stage. Because users are searching for informational and transactional keywords, your site can receive visits from buyers at every stage of the marketing funnel, giving you multiple chances to convert them and helping to increase the number of touch points you have.

  How to check your website’s organic traffic

  You don’t need to complete complex calculations to determine your site’s organic traffic. A web analytics solution like Matomo will accurately measure your site’s organic traffic. 

  In Matomo, on the left-hand sidebar, you can access organic traffic data by clicking Acquisition and then selecting All Channels.

  

  You’ll find a detailed breakdown of all traffic sources, including organic traffic, within the specified timeframe. The report is set to the current day by default, but you can view organic traffic metrics over a day, week, month, year or a date range of your choice.

  If you want to take things further, you can get a detailed view of organic visitors by creating a custom report for “Visitors from Search Engines only.” By creating a custom report with the segment “Channel Type is search”, you’ll be able to combine other metrics like average actions per visit, bounce rate, goal conversions, etc., to create a comprehensive report on your organic traffic and the behavior of these visitors.

  Matomo also lets you integrate Google, Bing and Yahoo search consoles directly into your Matomo Analytics to monitor keyword performance.

  How to increase organic traffic

  Follow these six tips if you want to increase the web traffic you get organically from search engines. 

  Create more and better content

  Here’s the reality : Most websites don’t get much traffic from Google. Only 40% of sites rank on the first page, and just 23% sit in the top three results. 

  Let’s take quality first. The best content tends to rise to the top of search engines. That’s because it gets shared more, receives more backlinks and gets more user engagement. So, if you want to appear at the top of Google results, creating mediocre content probably won’t cut it. You need to go above and beyond what is already there. 

  But you can’t just create one fantastic piece of content and expect to receive thousands of visitors. You need multiple pages targeting as many search terms as possible. The more pages search engines index, the more opportunities you have to rank. Or, to put it another way, the more shots you take, the greater your chances of scoring. 

  Use keyword research tools

  While creating great content is essential, you want to ensure that content targets the right keywords. These keywords receive a suitable amount of traffic and are easy to rank for. 

  Keyword research tools like Ahrefs of Semrush are the easiest way to find high-traffic topics to write about. Specifically, you want to aim for long-tail keywords. These are search terms that contain three or more words. Think “Nike men’s basketball shoe” rather than “basketball shoe.”

  

  As you can see, long tail keywords have a lower monthly search volume (250 vs. 1,100 using the example above) than broad terms but are much easier to rank for (14 vs. 41 Keyword Difficulty).

  

  While the above tools can help you find new topics to write about, Matomo’s Search Engine Keywords Performance plugin can help highlight topics you have already covered that could be expanded.

  

  The plugin automatically connects to APIs from all significant search engines and imports all the keywords people search for when clicking on your websites into your Matomo report. 

  If you find a cluster of keywords on the same topic that generates a lot of visitors, it may be worth creating even more content on that topic. Similarly, if there’s a topic you think you have covered but isn’t generating much traffic, you can look at revising and refreshing your existing content to try to rank higher. 

  Build high-quality backlinks

  Backlinks are arguably the most important Google ranking factor and the primary way Google assesses the authoritativeness of your site and content. Backlinks strongly and positively correlate with traffic — at least according to 67.5% of respondents in a uSERP industry survey. 

  There are plenty of ways you can create high-quality backlinks that Google loves. Strategies include :

  • Creating and promoting the best content about a given topic
  • Guest posting on high-authority websites
  • Building relationships with other websites

  Ensure you avoid building low-quality spam links at all costs — such as private blog networks (PBNs), forum and comment spam links and directory links. These links won’t help your content to rank higher, and Google may even penalise your entire site if you build them. 

  Find and fix any technical Search Engine Optimisation (SEO) issues

  Search engines like Google need to be able to quickly and accurately crawl and index your website to rank your content. Unfortunately, many sites suffer from technical issues that impede search engine bots. 

  The good news is that certain tools make these issues easy to spot. Take the Matomo SEO Web Vitals feature, for instance. This lets you track a set of core web vital metrics, including :

  • Page Speed Score
  • First Contentful Paint (FCP)
  • Final Input Delay (FID)
  • Last Contentful Paint (LCP)
  • Cumulative Layout Shift (CLS)

  Take things even further by identifying major bugs and issues with your site. Crashes and other issues that impact user experience can also hurt your SEO and organic traffic efforts — so it’s best to eliminate them as soon as they occur. 

  

  Use Matomo’s Crash Analytics feature to get precise bug location information as well as the user’s interactions that triggered, the device they were using, etc. Scheduled reporting and alerts allow you to automate this task and instantly detect bugs as soon as they occur.

  Improve your on-page SEO

  As well as fixing technical issues, you should spend time optimising specific elements of your website to improve how it ranks in search engines. 

  There are several on-page elements you should optimise :

  • Image alt tags
  • URLs
  • Headings
  • Title tags
  • Internal links

  Your goal should be to include a target keyword in each element above. For example, your URL should be something like yoursite.com/keyword.

  It’s best to err on the side of caution here. Avoid adding too many keywords to each of these elements. This is called keyword stuffing, and Google may slap your site with a penalty. 

  Track your content’s performance

  One final way to increase organic traffic is to use an analytics platform to understand what content needs improving and which pages can be removed.

  

  Use an analytics platform like Matomo to see which pages generate the most organic traffic and which lag behind. This can help you prioritise your SEO efforts while highlighting pages that add no value. These pages can be completely revamped, redirected to another page or removed if appropriate. 

  Conclusion

  Organic traffic is arguably the most valuable traffic source your site can acquire. It is essential to monitor organic traffic levels and take steps to increase your organic traffic. 

  A good analytics platform can help you do both. Matomo’s powerful, open-source web analytics solution protects your data and your users’ privacy, while providing the SEO tools you need to send your organic traffic levels soaring. 

  Start a free 21-day trial now, no credit card required.

• Change AVI creation date with ffmpeg ?

  1er novembre 2016, par brock

  As far as I can tell the following ffmpeg command should copy all existing metadata in the input file to the output file and modify the specified field in the output file :

  ffmpeg -i VID_20130502_220104.avi -metadata creation_time="2013-05-02 22:01:04" -codec copy VID_20130502_220104-2.avi

  Instead, it seems to strip all metadata from the output file. Here is the output of a few commands. I am going nuts. I think this should work, but why is it not ?

  Command to edit the creation time :

  ffmpeg -i VID_20130502_220104.avi -metadata creation_time="2013-05-02 22:01:04" -codec copy VID_20130502_220104-2.avi
  
  
  
  ffmpeg version 3.1.5 Copyright (c) 2000-2016 the FFmpeg developers
  
    built with gcc 5.4.0 (GCC)
  
    configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-dxva2 --enable-libmfx --enable-nvenc --enable-avisynth --enable-bzlib --enable-libebur128 --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-decklink --enable-zlib
  
    libavutil      55. 28.100 / 55. 28.100
  
    libavcodec     57. 48.101 / 57. 48.101
  
    libavformat    57. 41.100 / 57. 41.100
  
    libavdevice    57.  0.101 / 57.  0.101
  
    libavfilter     6. 47.100 /  6. 47.100
  
    libswscale      4.  1.100 /  4.  1.100
  
    libswresample   2.  1.100 /  2.  1.100
  
    libpostproc    54.  0.100 / 54.  0.100
  
  Guessed Channel Layout for Input Stream #0.1 : mono
  
  Input #0, avi, from 'VID_20130502_220104.avi':
  
    Metadata:
  
      encoder         : 
  
      maker           : NIKON
  
      model           : COOLPIX S4300
  
      creation_time   : 2011-01-01 00:00:00
  
    Duration: 00:01:30.50, start: 0.000000, bitrate: 32135 kb/s
  
      Stream #0:0: Video: mjpeg (MJPG / 0x47504A4D), yuvj422p(pc, bt470bg/unknown/unknown), 1280x720, 31782 kb/s, 30 fps, 30 tbr, 30 tbn, 30 tbc
  
      Stream #0:1: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 22050 Hz, 1 channels, s16, 352 kb/s
  
  [avi @ 000000000032ad40] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead.
  
      Last message repeated 1 times
  
  Output #0, avi, to 'VID_20130502_220104-2.avi':
  
    Metadata:
  
      creation_time   : 2013-05-02 22:01:04
  
      maker           : NIKON
  
      model           : COOLPIX S4300
  
      ISFT            : Lavf57.41.100
  
      Stream #0:0: Video: mjpeg (MJPG / 0x47504A4D), yuvj422p(pc, bt470bg/unknown/unknown), 1280x720, q=2-31, 31782 kb/s, 30 fps, 30 tbr, 30 tbn, 30 tbc
  
      Stream #0:1: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 22050 Hz, mono, 352 kb/s
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (copy)
  
    Stream #0:1 -> #0:1 (copy)
  
  Press [q] to stop, [?] for help
  
  frame=  891 fps=0.0 q=-1.0 size=  116171kB time=00:00:29.69 bitrate=32043.1kbits/s speed=59.4x    
  
  frame= 1739 fps=1739 q=-1.0 size=  227191kB time=00:00:57.96 bitrate=32107.5kbits/s speed=  58x    
  
  frame= 2609 fps=1739 q=-1.0 size=  340940kB time=00:01:26.96 bitrate=32115.9kbits/s speed=  58x    
  
  frame= 2715 fps=1734 q=-1.0 Lsize=  355018kB time=00:01:30.49 bitrate=32136.3kbits/s speed=57.8x    
  
  video:350984kB audio:3897kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.038597%

  Command to inspect the output file metadata with ffmpeg :

  ffmpeg -i VID_20130502_220104-2.avi
  
  
  
  ffmpeg version 3.1.5 Copyright (c) 2000-2016 the FFmpeg developers
  
    built with gcc 5.4.0 (GCC)
  
    configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-dxva2 --enable-libmfx --enable-nvenc --enable-avisynth --enable-bzlib --enable-libebur128 --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-decklink --enable-zlib
  
    libavutil      55. 28.100 / 55. 28.100
  
    libavcodec     57. 48.101 / 57. 48.101
  
    libavformat    57. 41.100 / 57. 41.100
  
    libavdevice    57.  0.101 / 57.  0.101
  
    libavfilter     6. 47.100 /  6. 47.100
  
    libswscale      4.  1.100 /  4.  1.100
  
    libswresample   2.  1.100 /  2.  1.100
  
    libpostproc    54.  0.100 / 54.  0.100
  
  Guessed Channel Layout for Input Stream #0.1 : mono
  
  Input #0, avi, from 'VID_20130502_220104-2.avi':
  
    Metadata:
  
      encoder         : Lavf57.41.100
  
    Duration: 00:01:30.50, start: 0.000000, bitrate: 32136 kb/s
  
      Stream #0:0: Video: mjpeg (MJPG / 0x47504A4D), yuvj422p(pc, bt470bg/unknown/unknown), 1280x720, 31782 kb/s, 30 fps, 30 tbr, 30 tbn, 30 tbc
  
      Stream #0:1: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 22050 Hz, 1 channels, s16, 352 kb/s
  
  At least one output file must be specified

  Command to inspect the input file metadata with exiftool :

  exiftool.exe VID_20130502_220104.avi
  
  
  
  ExifTool Version Number         : 10.30
  
  File Name                       : VID_20130502_220104.avi
  
  Directory                       : .
  
  File Size                       : 347 MB
  
  File Modification Date/Time     : 2013:05:13 16:33:52-04:00
  
  File Access Date/Time           : 2015:11:10 23:08:25-05:00
  
  File Creation Date/Time         : 2015:11:10 23:08:25-05:00
  
  File Permissions                : rw-rw-rw-
  
  File Type                       : AVI
  
  File Type Extension             : avi
  
  MIME Type                       : video/x-msvideo
  
  Frame Rate                      : 30
  
  Max Data Rate                   : 488.3 kB/s
  
  Frame Count                     : 2715
  
  Stream Count                    : 2
  
  Stream Type                     : Video
  
  Video Codec                     : mjpg
  
  Video Frame Rate                : 30
  
  Video Frame Count               : 2715
  
  Quality                         : 10000
  
  Sample Size                     : Variable
  
  Image Width                     : 1280
  
  Image Height                    : 720
  
  Planes                          : 1
  
  Bit Depth                       : 24
  
  Compression                     : MJPG
  
  Image Length                    : 2764800
  
  Pixels Per Meter X              : 0
  
  Pixels Per Meter Y              : 0
  
  Num Colors                      : Use BitDepth
  
  Num Important Colors            : All
  
  Audio Codec                     : 
  
  Audio Sample Rate               : 22050
  
  Audio Sample Count              : 1995256
  
  Encoding                        : Microsoft PCM
  
  Num Channels                    : 1
  
  Sample Rate                     : 22050
  
  Avg Bytes Per Sec               : 44100
  
  Bits Per Sample                 : 16
  
  Maker Note Type                 : NIKON
  
  Maker Note Version              : 0.1.0.0
  
  Make                            : NIKON
  
  Model                           : COOLPIX S4300
  
  Software                        : V1.0
  
  Equipment                       : NIKON DIGITAL CAMERA
  
  Orientation                     : Horizontal (normal)
  
  Exposure Time                   : 1/15
  
  F Number                        : 3.5
  
  Exposure Compensation           : 0
  
  Max Aperture Value              : 3.2
  
  Metering Mode                   : Multi-segment
  
  Focal Length                    : 4.6 mm
  
  X Resolution                    : 72
  
  Y Resolution                    : 72
  
  Resolution Unit                 : inches
  
  Date/Time Original              : 2011:01:01 00:00:00
  
  Create Date                     : 2011:01:01 00:00:00
  
  Focus Mode                      : AF-S
  
  Digital Zoom                    : 1
  
  Color Mode                      : COLOR
  
  Sharpness                       : AUTO
  
  White Balance                   : NORMAL
  
  Noise Reduction                 : OFF
  
  Thumbnail Image                 : (Binary data 3082 bytes, use -b option to extract)
  
  Aperture                        : 3.5
  
  Duration                        : 0:01:30
  
  Image Size                      : 1280x720
  
  Megapixels                      : 0.922
  
  Shutter Speed                   : 1/15
  
  Focal Length                    : 4.6 mm

  Command to inspect the output file metadata with exiftool :

  exiftool.exe VID_20130502_220104-2.avi
  
  
  
  ExifTool Version Number         : 10.30
  
  File Name                       : VID_20130502_220104-2.avi
  
  Directory                       : .
  
  File Size                       : 347 MB
  
  File Modification Date/Time     : 2016:11:01 00:17:38-04:00
  
  File Access Date/Time           : 2016:11:01 00:17:36-04:00
  
  File Creation Date/Time         : 2016:11:01 00:15:18-04:00
  
  File Permissions                : rw-rw-rw-
  
  File Type                       : AVI
  
  File Type Extension             : avi
  
  MIME Type                       : video/x-msvideo
  
  Frame Rate                      : 30
  
  Max Data Rate                   : 3923 kB/s
  
  Frame Count                     : 2715
  
  Stream Count                    : 2
  
  Stream Type                     : Video
  
  Video Codec                     : MJPG
  
  Video Frame Rate                : 30
  
  Video Frame Count               : 2715
  
  Quality                         : Default
  
  Sample Size                     : Variable
  
  Image Width                     : 1280
  
  Image Height                    : 720
  
  Planes                          : 1
  
  Bit Depth                       : 24
  
  Compression                     : MJPG
  
  Image Length                    : 2764800
  
  Pixels Per Meter X              : 0
  
  Pixels Per Meter Y              : 0
  
  Num Colors                      : Use BitDepth
  
  Num Important Colors            : All
  
  Audio Codec                     : .
  
  Audio Sample Rate               : 22050
  
  Audio Sample Count              : 1995256
  
  Encoding                        : Microsoft PCM
  
  Num Channels                    : 1
  
  Sample Rate                     : 22050
  
  Avg Bytes Per Sec               : 44100
  
  Bits Per Sample                 : 16
  
  Software                        : Lavf57.41.100
  
  Duration                        : 0:01:30
  
  Image Size                      : 1280x720
  
  Megapixels                      : 0.922