Recherche avancée

Sur d’autres sites (5459)

• Clickstream Data : Definition, Use Cases, and More

  15 avril 2024, par Erin

  Gaining a deeper understanding of user behaviour — customers’ different paths, digital footprints, and engagement patterns — is crucial for providing a personalised experience and making informed marketing decisions. 

  In that sense, clickstream data, or a comprehensive record of a user’s online activities, is one of the most valuable sources of actionable insights into users’ behavioural patterns. 

  This article will cover everything marketing teams need to know about clickstream data, from the basic definition and examples to benefits, use cases, and best practices. 

  What is clickstream data ? 

  As a form of web analytics, clickstream data focuses on tracking and analysing a user’s online activity. These digital breadcrumbs offer insights into the websites the user has visited, the pages they viewed, how much time they spent on a page, and where they went next.

  

  Your clickstream pipeline can be viewed as a “roadmap” that can help you recognise consistent patterns in how users navigate your website. 

  With that said, you won’t be able to learn much by analysing clickstream data collected from one user’s session. However, a proper analysis of large clickstream datasets can provide a wealth of information about consumers’ online behaviours and trends — which marketing teams can use to make informed decisions and optimise their digital marketing strategy. 

  Clickstream data collection can serve numerous purposes, but the main goal remains the same — gaining valuable insights into visitors’ behaviours and online activities to deliver a better user experience and improve conversion likelihood. 

  Depending on the specific events you’re tracking, clickstream data can reveal the following : 

  • How visitors reach your website 
  • The terms they type into the search engine
  • The first page they land on
  • The most popular pages and sections of your website
  • The amount of time they spend on a page 
  • Which elements of the page they interact with, and in what sequence
  • The click path they take 
  • When they convert, cancel, or abandon their cart
  • Where the user goes once they leave your website

  As you can tell, once you start collecting this type of data, you’ll learn quite a bit about the user’s online journey and the different ways they engage with your website — all without including any personal details about your visitors.

  Types of clickstream data 

  While all clickstream data keeps a record of the interactions that occur while the user is navigating a website or a mobile application — or any other digital platform — it can be divided into two types : 

  • Aggregated (web traffic) data provides comprehensive insights into the total number of visits and user interactions on a digital platform — such as your website — within a given timeframe 
  • Unaggregated data is broken up into smaller segments, focusing on an individual user’s online behaviour and website interactions 

  One thing to remember is that to gain valuable insights into user behaviour and uncover sequential patterns, you need a powerful tool and access to full clickstream datasets. Matomo’s Event Tracking can provide a comprehensive view of user interactions on your website or mobile app — everything from clicking a button and completing a form to adding (or removing) products from their cart. 

  On that note, based on the specific events you’re tracking when a user visits your website, clickstream data can include : 

  • Web navigation data : referring URL, visited pages, click path, and exit page
  • User interaction data : mouse movements, click rate, scroll depth, and button clicks
  • Conversion data : form submissions, sign-ups, and transactions 
  • Temporal data : page load time, timestamps, and the date and time of day of the user’s last login 
  • Session data : duration, start, and end times and number of pages viewed per session
  • Error data : 404 errors and network or server response issues 

  Try Matomo for Free

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

  Start for free

  No credit card required

  Clickstream data benefits and use cases 

  Given the actionable insights that clickstream data collection provides, it can serve a wide range of use cases — from identifying behavioural patterns and trends and examining competitors’ performance to helping marketing teams map out customer journeys and improve ROI.

  

  According to the global Clickstream Analytics Market Report 2024, some key applications of clickstream analytics include click-path optimisation, website and app optimisation, customer analysis, basket analysis, personalisation, and traffic analysis. 

  

  The behavioural patterns and user preferences revealed by clickstream analytics data can have many applications — we’ve outlined the prominent use cases below. 

  Customer journey mapping 

  Clickstream data allows you to analyse the e-commerce customer’s online journey and provides insights into how they navigate your website. With such a comprehensive view of their click path, it becomes easier to understand user behaviour at each stage — from initial awareness to conversion — identify the most effective touchpoints and fine-tune that journey to improve their conversion likelihood. 

  Identifying customer trends 

  Clickstream data analytics can also help you identify trends and behavioural patterns — the most common sequences and similarities in how users reached your website and interacted with it — especially when you can access data from many website visitors. 

  Think about it — there are many ways in which you can use these insights into the sequence of clicks and interactions and recurring patterns to your team’s advantage. 

  Here’s an example : 

  It can reveal that some pieces of content and CTAs are performing well in encouraging visitors to take action — which shows how you should optimise other pages and what you should strive to create in the future, too. 

  Preventing site abandonment 

  Cart abandonment remains a serious issue for online retailers : 

  According to a recent report, the global cart abandonment rate in the fourth quarter of 2023 was at 83%. 

  That means that roughly eight out of ten e-commerce customers will abandon their shopping carts — most commonly due to additional costs, slow website loading times and the requirement to create an account before purchasing. 

  In addition to cart abandonment predictions, clickstream data analytics can reveal the pages where most visitors tend to leave your website. These drop-off points are clear indicators that something’s not working as it should — and once you can pinpoint them, you’ll be able to address the issue and increase conversion likelihood.

  Improving marketing campaign ROI 

  As previously mentioned, clickstream data analysis provides insights into the customer journey. Still, you may not realise that you can also use this data to keep track of your marketing effectiveness. 

  Global digital ad spending continues to grow — and is expected to reach $836 billion by 2026. It’s easy to see why relying on accurate data is crucial when deciding which marketing channels to invest in. 

  You want to ensure you’re allocating your digital marketing and advertising budget to the channels — be it SEO, pay-per-click (PPC) ads, or social media campaigns — that impact driving conversions. 

  When you combine clickstream e-commerce data with conversion rates, you’ll find the latter in Matomo’s goal reports and have a solid, data-driven foundation for making better marketing decisions.

  Try Matomo for Free

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

  Start for free

  No credit card required

  Delivering a better user experience (UX) 

  Clickstream data analysis allows you to identify specific “pain points” — areas of the website that are difficult to use and may cause customer frustration. 

  It’s clear how this would be beneficial to your business : 

  Once you’ve identified these pain points, you can make the necessary changes to your website’s layout and address any technical issues that users might face, improving usability and delivering a smoother experience to potential customers. 

  Collecting clickstream data : Tools and legal implications 

  Your team will need a powerful tool capable of handling clickstream analytics to reap the benefits we’ve discussed previously. But at the same time, you need to respect users’ online privacy throughout clickstream data collection.

  

  Generally speaking, there are two ways to collect data about users’ online activity — web analytics tools and server log files.

  Web analytics tools are the more commonly used solution. Specifically designed to collect and analyse website data, these tools rely on JavaScript tags that run in the browser, providing actionable insights about user behaviour. Server log files can be a gold mine of data, too — but that data is raw and unfiltered, making it much more challenging to interpret and analyse. 

  That brings us to one of the major clickstream challenges to keep in mind as you move forward — compliance.

  While Google remains a dominant player in the web analytics market, there’s one area where Matomo has a significant advantage — user privacy. 

  Matomo operates according to privacy laws — including the General Data Protection Regulation (GDPR) and California Consumer Privacy Act (CCPA), making it an ethical alternative to Google Analytics. 

  It should go without saying, but compliance with data privacy laws — the most talked-about one being the GDPR framework introduced by the EU — isn’t something you can afford to overlook. 

  The GDPR was first implemented in the EU in 2018. Since then, several fines have been issued for non-compliance — including the record fine of €1.2 billion that Meta Platforms, Inc. received in 2023 for transferring personal data of EU-based users to the US.

  Clickstream analytics data best practices 

  

  As valuable as it might be, processing large amounts of clickstream analytics data can be a complex — and, at times, overwhelming — process. 

  Here are some best practices to keep in mind when it comes to clickstream analysis : 

  Define your goals 

  It’s essential to take the time to define your goals and objectives. 

  Once you have a clear idea of what you want to learn from a given clickstream dataset and the outcomes you hope to see, it’ll be easier to narrow down your scope — rather than trying to tackle everything at once — before moving further down the clickstream pipeline. 

  Here are a few examples of goals and objectives you can set for clickstream analysis : 

  • Understanding and predicting users’ behavioural patterns 
  • Optimising marketing campaigns and ROI 
  • Attributing conversions to specific marketing touchpoints and channels

  Analyse your data 

  Collecting clickstream analytics data is only part of the equation ; what you do with raw data and how you analyse it matters. You can have the most comprehensive dataset at your disposal — but it’ll be practically worthless if you don’t have the skill set to analyse and interpret it. 

  In short, this is the stage of your clickstream pipeline where you uncover common sequences and consistent patterns in user behaviour. 

  Clickstream data analytics can extract actionable insights from large datasets using various approaches, models, and techniques. 

  Here are a few examples : 

  • If you’re working with clickstream e-commerce data, you should perform funnel or conversion analyses to track conversion rates as users move through your sales funnel. 
  • If you want to group and analyse users based on shared characteristics, you can use Matomo for cohort analysis. 
  • If your goal is to predict future trends and outcomes — conversion and cart abandonment prediction, for example — based on available data, prioritise predictive analytics.

  Try Matomo for Free

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

  Start for free

  No credit card required

  Organise and visualise your data

  As you reach the end of your clickstream pipeline, you need to start thinking about how you will present and communicate your data. And what better way to do that than to transform that data into easy-to-understand visualisations ? 

  Here are a few examples of easily digestible formats that facilitate quick decision-making : 

  • User journey maps, which illustrate the exact sequence of interactions and user flow through your website 
  • Heatmaps, which serve as graphical — and typically colour-coded — representations of a website visitor’s activity 
  • Funnel analysis, which are broader at the top but get increasingly narrower towards the bottom as users flow through and drop off at different stages of the pipeline 

  Collect clickstream data with Matomo 

  Clickstream data is hard to beat when tracking the website visitor’s journey — from first to last interaction — and understanding user behaviour. By providing real-time insights, your clickstream pipeline can help you see the big picture, stay ahead of the curve and make informed decisions about your marketing efforts. 

  Matomo accurate data and compliance with GDPR and other data privacy regulations — it’s an all-in-one, ethical platform that can meet all your web analytics needs. That’s why over 1 million websites use Matomo for their web analytics.

  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)

  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

  

• Sporadic "Error parsing Cues... Operation not permitted" errors when trying to generate a DASH manifest

  22 novembre 2023, par kshetline

  I have already-generated .webm audio and video files (1 audio, 3 video resolutions for each video I want to stream). The video has been generated not (directly) by ffmpeg, but HandbrakeCLI 1.7.0, with V9 encoding. The audio (which has never caused an error) is generated by ffmpeg using libvorbis.

  


  Most of the time ffmpeg (version 6.1) creates a manifest without any problem. Sporadically, however, "Error parsing Cues" comes up (frequently with the latest videos I've been trying to process) and I can't create a manifest. Since this is happening during an automated process to process many videos for streaming, the audio and video sources are being created exactly the same way whether ffmpeg succeeds or fails in generating a manifest, making this all the more confusing.

  


  The video files ffmpeg chokes on play perfectly well using VLC, and mediainfo doesn't show any problems with these files.

  


  Here's the way I've been (sometimes successfully, sometimes not) generating a manifest, with extra logging added :

  


  ffmpeg -v 9 -loglevel 99 \
  -f webm_dash_manifest -i '.\Sample Video.v480.webm' \
  -f webm_dash_manifest -i '.\Sample Video.v720.webm' \
  -f webm_dash_manifest -i '.\Sample Video.v1080.webm' \
  -f webm_dash_manifest -i '.\Sample Video.audio.webm' \
  -c copy -map 0 -map 1 -map 2 -map 3 \
  -f webm_dash_manifest -adaptation_sets "id=0,streams=0,1,2 id=1,streams=3" \
  '.\Sample Video.mpd'


  


  Here's the result when it fails :

  


  ffmpeg version 6.1-full_build-www.gyan.dev Copyright (c) 2000-2023 the FFmpeg developers
  built with gcc 12.2.0 (Rev10, Built by MSYS2 project)
  configuration: --enable-gpl --enable-version3 --enable-static --pkg-config=pkgconf --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-bzlib --enable-lzma --enable-libsnappy --enable-zlib --enable-librist --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libaribb24 --enable-libaribcaption --enable-libdav1d --enable-libdavs2 --enable-libuavs3d --enable-libzvbi --enable-librav1e --enable-libsvtav1 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxvid --enable-libaom --enable-libjxl --enable-libopenjpeg --enable-libvpx --enable-mediafoundation --enable-libass --enable-frei0r --enable-libfreetype --enable-libfribidi --enable-libharfbuzz --enable-liblensfun --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec --enable-nvenc --enable-dxva2 --enable-d3d11va --enable-libvpl --enable-libshaderc --enable-vulkan --enable-libplacebo --enable-opencl --enable-libcdio --enable-libgme --enable-libmodplug --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libshine --enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libcodec2 --enable-libilbc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-ladspa --enable-libbs2b --enable-libflite --enable-libmysofa --enable-librubberband --enable-libsoxr --enable-chromaprint
  libavutil      58. 29.100 / 58. 29.100
  libavcodec     60. 31.102 / 60. 31.102
  libavformat    60. 16.100 / 60. 16.100
  libavdevice    60.  3.100 / 60.  3.100
  libavfilter     9. 12.100 /  9. 12.100
  libswscale      7.  5.100 /  7.  5.100
  libswresample   4. 12.100 /  4. 12.100
  libpostproc    57.  3.100 / 57.  3.100
Splitting the commandline.
Reading option '-v' ... matched as option 'v' (set logging level) with argument '9'.
Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument '99'.
Reading option '-f' ... matched as option 'f' (force format) with argument 'webm_dash_manifest'.
Reading option '-i' ... matched as output url with argument '.\Sample Video.v480.webm'.
Reading option '-f' ... matched as option 'f' (force format) with argument 'webm_dash_manifest'.
Reading option '-i' ... matched as output url with argument '.\Sample Video.v720.webm'.
Reading option '-f' ... matched as option 'f' (force format) with argument 'webm_dash_manifest'.
Reading option '-i' ... matched as output url with argument '.\Sample Video.v1080.webm'.
Reading option '-f' ... matched as option 'f' (force format) with argument 'webm_dash_manifest'.
Reading option '-i' ... matched as output url with argument '.\Sample Video.audio.webm'.
Reading option '-c' ... matched as option 'c' (codec name) with argument 'copy'.
Reading option '-map' ... matched as option 'map' (set input stream mapping) with argument '0'.
Reading option '-map' ... matched as option 'map' (set input stream mapping) with argument '1'.
Reading option '-map' ... matched as option 'map' (set input stream mapping) with argument '2'.
Reading option '-map' ... matched as option 'map' (set input stream mapping) with argument '3'.
Reading option '-f' ... matched as option 'f' (force format) with argument 'webm_dash_manifest'.
Reading option '-adaptation_sets' ... matched as AVOption 'adaptation_sets' with argument 'id=0,streams=0,1,2 id=1,streams=3'.
Reading option '.\Sample Video.mpd' ... matched as output url.
Finished splitting the commandline.
Parsing a group of options: global .
Applying option v (set logging level) with argument 9.
Successfully parsed a group of options.
Parsing a group of options: input url .\Sample Video.v480.webm.
Applying option f (force format) with argument webm_dash_manifest.
Successfully parsed a group of options.
Opening an input file: .\Sample Video.v480.webm.
[webm_dash_manifest @ 000002bbcb41dc80] Opening '.\Sample Video.v480.webm' for reading
[file @ 000002bbcb41e300] Setting default whitelist 'file,crypto,data'
st:0 removing common factor 1000000 from timebase
[webm_dash_manifest @ 000002bbcb41dc80] Error parsing Cues
[AVIOContext @ 000002bbcb41e5c0] Statistics: 102283 bytes read, 4 seeks
[in#0 @ 000002bbcb41dac0] Error opening input: Operation not permitted
Error opening input file .\Sample Video.v480.webm.
Error opening input files: Operation not permitted


  


  This is mediainfo for the offending input file, Sample Video.v480.webm :

  


  General
Complete name                            : .\Sample Video.v480.webm
Format                                   : WebM
Format version                           : Version 2
File size                                : 628 MiB
Duration                                 : 1 h 34 min
Overall bit rate                         : 926 kb/s
Frame rate                               : 23.976 FPS
Encoded date                             : 2023-11-21 16:48:35 UTC
Writing application                      : HandBrake 1.7.0 2023111500
Writing library                          : Lavf60.16.100

Video
ID                                       : 1
Format                                   : VP9
Format profile                           : 0
Codec ID                                 : V_VP9
Duration                                 : 1 h 34 min
Bit rate                                 : 882 kb/s
Width                                    : 720 pixels
Height                                   : 480 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 23.976 (24000/1001) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Bits/(Pixel*Frame)                       : 0.106
Stream size                              : 598 MiB (95%)
Default                                  : Yes
Forced                                   : No
Color range                              : Limited
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709


  


  I don't know if I need different command line options, or whether this might be an ffmpeg or Handbrake bug. It has taken many, many hours to generate these video files (VP9 is painfully slow to encode), so I hate to do a lot of this over again, especially doing it again encoding the video with ffmpeg instead of Handbrake, as Handbrake is (oddly enough, considering it uses ffmpeg under the hood) noticeably faster.

  


  I have no idea what these "Cues" are that ffmpeg wants and can't parse, or how I would change them.

  


• Why does the frame count change when scaling with FFmpeg ?

  22 octobre 2016, par ajmicek

  I use this to scale 1920x1080 H.264 videos :

  ffmpeg -i IMG_1438.MOV -threads 2 -vf scale=-2:600 IMG_1438_scaledTo600.MOV

  And it works great ! But here is my question : most of the time, the frame rate stays exactly the same between the original file and the scaled file. For example :

  $ mediainfo -F IMG_1426.MOV | grep Frame\ rate
  
  Frame rate                               : 29.970
  
  Frame rate                               : 29.970 FPS
  
  Frame rate mode                          : VFR
  
  Frame rate mode                          : Variable
  
  Frame rate                               : 29.970
  
  Frame rate                               : 29.970 (29970/1000) FPS
  
  
  
  $ mediainfo -F IMG_1426_scaledTo600.MOV | grep Frame\ rate
  
  Frame rate                               : 29.970
  
  Frame rate                               : 29.970 FPS
  
  Frame rate mode                          : CFR
  
  Frame rate mode                          : Constant
  
  Frame rate                               : 29.970
  
  Frame rate                               : 29.970 (30000/1001) FPS

  But sometimes, the frame rate increases dramatically :

  $ mediainfo -F IMG_1438.MOV | grep Frame\ rate
  
  Frame rate                               : 25.044
  
  Frame rate                               : 25.044 FPS
  
  Frame rate mode                          : VFR
  
  Frame rate mode                          : Variable
  
  Frame rate                               : 25.044
  
  Frame rate                               : 25.044 FPS
  
  
  
  $ mediainfo -F IMG_1438_scaledTo600.MOV | grep Frame\ rate
  
  Frame rate                               : 120.000
  
  Frame rate                               : 120.000 FPS
  
  Frame rate mode                          : CFR
  
  Frame rate mode                          : Constant
  
  Frame rate                               : 120.000
  
  Frame rate                               : 120.000 FPS

  What should I know about FFmpeg or libx264 or libswscale that will help me understand why this happens ? (Hoping to hear from LordNeckbeard, in particular).

  mediainfo IMG_1438.MOV --Full outputs :

  General
  
  Count                                    : 327
  
  Count of stream of this kind             : 1
  
  Kind of stream                           : General
  
  Kind of stream                           : General
  
  Stream identifier                        : 0
  
  Count of video streams                   : 1
  
  Count of audio streams                   : 1
  
  OtherCount                               : 2
  
  Video_Format_List                        : AVC
  
  Video_Format_WithHint_List               : AVC
  
  Codecs Video                             : AVC
  
  Audio_Format_List                        : AAC
  
  Audio_Format_WithHint_List               : AAC
  
  Audio codecs                             : AAC LC
  
  Complete name                            : IMG_1438.MOV
  
  File name                                : IMG_1438
  
  File extension                           : MOV
  
  Format                                   : MPEG-4
  
  Format                                   : MPEG-4
  
  Format/Extensions usually used           : mp4 m4v m4a m4b m4p 3gpp 3gp 3gpp2 3g2 k3g jpm jpx mqv ismv isma f4v
  
  Commercial name                          : MPEG-4
  
  Format profile                           : QuickTime
  
  Internet media type                      : video/mp4
  
  Codec ID                                 : qt  
  
  Codec ID                                 : qt   0000.00 (qt  )
  
  Codec ID/Url                             : http://www.apple.com/quicktime/download/standalone.html
  
  CodecID_Version                          : 0000.00
  
  CodecID_Compatible                       : qt  
  
  Codec                                    : MPEG-4
  
  Codec                                    : MPEG-4
  
  Codec/Extensions usually used            : mp4 m4v m4a m4b m4p 3gpp 3gp 3gpp2 3g2 k3g jpm jpx mqv ismv isma f4v
  
  File size                                : 113990140
  
  File size                                : 109 MiB
  
  File size                                : 109 MiB
  
  File size                                : 109 MiB
  
  File size                                : 109 MiB
  
  File size                                : 108.7 MiB
  
  Duration                                 : 52268
  
  Duration                                 : 52 s 268 ms
  
  Duration                                 : 52 s 268 ms
  
  Duration                                 : 52 s 268 ms
  
  Duration                                 : 00:00:52.268
  
  Duration                                 : 00:00:52:09
  
  Duration                                 : 00:00:52.268 (00:00:52:09)
  
  Overall bit rate                         : 17447026
  
  Overall bit rate                         : 17.4 Mb/s
  
  Frame rate                               : 25.044
  
  Frame rate                               : 25.044 FPS
  
  Frame count                              : 1309
  
  Stream size                              : 56670
  
  Stream size                              : 55.3 KiB (0%)
  
  Stream size                              : 55 KiB
  
  Stream size                              : 55 KiB
  
  Stream size                              : 55.3 KiB
  
  Stream size                              : 55.34 KiB
  
  Stream size                              : 55.3 KiB (0%)
  
  Proportion of this stream                : 0.00050
  
  HeaderSize                               : 28
  
  DataSize                                 : 113966271
  
  FooterSize                               : 23841
  
  IsStreamable                             : No
  
  Encoded date                             : UTC 2016-10-08 22:51:19
  
  Tagged date                              : UTC 2016-10-08 22:52:12
  
  File last modification date              : UTC 2016-10-08 22:51:19
  
  File last modification date (local)      : 2016-10-08 17:51:19
  
  Writing library                          : Apple QuickTime
  
  Writing library                          : Apple QuickTime
  
  Encoded_Library_Name                     : Apple QuickTime
  
  com.apple.quicktime.make                 : Apple
  
  com.apple.quicktime.model                : iPhone 5
  
  com.apple.quicktime.software             : 10.0.2
  
  com.apple.quicktime.creationdate         : 2016-10-08T17:51:19-0500
  
  
  
  Video
  
  Count                                    : 334
  
  Count of stream of this kind             : 1
  
  Kind of stream                           : Video
  
  Kind of stream                           : Video
  
  Stream identifier                        : 0
  
  StreamOrder                              : 0
  
  ID                                       : 1
  
  ID                                       : 1
  
  Format                                   : AVC
  
  Format/Info                              : Advanced Video Codec
  
  Format/Url                               : http://developers.videolan.org/x264.html
  
  Commercial name                          : AVC
  
  Format profile                           : High@L4.1
  
  Format settings                          : CABAC / 1 Ref Frames
  
  Format settings, CABAC                   : Yes
  
  Format settings, CABAC                   : Yes
  
  Format settings, ReFrames                : 1
  
  Format settings, ReFrames                : 1 frame
  
  Internet media type                      : video/H264
  
  Codec ID                                 : avc1
  
  Codec ID/Info                            : Advanced Video Coding
  
  Codec ID/Url                             : http://www.apple.com/quicktime/download/standalone.html
  
  Codec                                    : AVC
  
  Codec                                    : AVC
  
  Codec/Family                             : AVC
  
  Codec/Info                               : Advanced Video Codec
  
  Codec/Url                                : http://developers.videolan.org/x264.html
  
  Codec/CC                                 : avc1
  
  Codec profile                            : High@L4.1
  
  Codec settings                           : CABAC / 1 Ref Frames
  
  Codec settings, CABAC                    : Yes
  
  Codec_Settings_RefFrames                 : 1
  
  Duration                                 : 52268
  
  Duration                                 : 52 s 268 ms
  
  Duration                                 : 52 s 268 ms
  
  Duration                                 : 52 s 268 ms
  
  Duration                                 : 00:00:52.268
  
  Duration                                 : 00:00:52:09
  
  Duration                                 : 00:00:52.268 (00:00:52:09)
  
  Bit rate                                 : 17375530
  
  Bit rate                                 : 17.4 Mb/s
  
  Width                                    : 1920
  
  Width                                    : 1 920 pixels
  
  Height                                   : 1080
  
  Height                                   : 1 080 pixels
  
  Stored_Height                            : 1088
  
  Sampled_Width                            : 1920
  
  Sampled_Height                           : 1080
  
  Pixel aspect ratio                       : 1.000
  
  Display aspect ratio                     : 1.778
  
  Display aspect ratio                     : 16:9
  
  Rotation                                 : 90.000
  
  Rotation                                 : 90°
  
  Frame rate mode                          : VFR
  
  Frame rate mode                          : Variable
  
  Frame rate                               : 25.044
  
  Frame rate                               : 25.044 FPS
  
  Minimum frame rate                       : 23.077
  
  Minimum frame rate                       : 23.077 FPS
  
  Maximum frame rate                       : 30.000
  
  Maximum frame rate                       : 30.000 FPS
  
  Frame count                              : 1309
  
  Resolution                               : 8
  
  Resolution                               : 8 bits
  
  Colorimetry                              : 4:2:0
  
  Color space                              : YUV
  
  Chroma subsampling                       : 4:2:0
  
  Chroma subsampling                       : 4:2:0
  
  Bit depth                                : 8
  
  Bit depth                                : 8 bits
  
  Scan type                                : Progressive
  
  Scan type                                : Progressive
  
  Interlacement                            : PPF
  
  Interlacement                            : Progressive
  
  Bits/(Pixel*Frame)                       : 0.335
  
  Stream size                              : 113523046
  
  Stream size                              : 108 MiB (100%)
  
  Stream size                              : 108 MiB
  
  Stream size                              : 108 MiB
  
  Stream size                              : 108 MiB
  
  Stream size                              : 108.3 MiB
  
  Stream size                              : 108 MiB (100%)
  
  Proportion of this stream                : 0.99590
  
  Title                                    : Core Media Video
  
  Encoded date                             : UTC 2016-10-08 22:51:19
  
  Tagged date                              : UTC 2016-10-08 22:52:12
  
  Color range                              : Limited
  
  colour_description_present               : Yes
  
  Color primaries                          : BT.709
  
  Transfer characteristics                 : BT.709
  
  Matrix coefficients                      : BT.709
  
  
  
  Audio
  
  Count                                    : 272
  
  Count of stream of this kind             : 1
  
  Kind of stream                           : Audio
  
  Kind of stream                           : Audio
  
  Stream identifier                        : 0
  
  StreamOrder                              : 1
  
  ID                                       : 2
  
  ID                                       : 2
  
  Format                                   : AAC
  
  Format/Info                              : Advanced Audio Codec
  
  Commercial name                          : AAC
  
  Format profile                           : LC
  
  Codec ID                                 : 40
  
  Codec                                    : AAC LC
  
  Codec                                    : AAC LC
  
  Codec/Family                             : AAC
  
  Codec/CC                                 : 40
  
  Duration                                 : 52268
  
  Duration                                 : 52 s 268 ms
  
  Duration                                 : 52 s 268 ms
  
  Duration                                 : 52 s 268 ms
  
  Duration                                 : 00:00:52.268
  
  Duration                                 : 00:00:52:15
  
  Duration                                 : 00:00:52.268 (00:00:52:15)
  
  Source duration                          : 52338
  
  Source duration                          : 52 s 338 ms
  
  Source duration                          : 52 s 338 ms
  
  Source duration                          : 52 s 338 ms
  
  Source duration                          : 00:00:52.338
  
  Bit rate mode                            : CBR
  
  Bit rate mode                            : Constant
  
  Bit rate                                 : 64000
  
  Bit rate                                 : 64.0 kb/s
  
  Channel(s)                               : 1
  
  Channel(s)                               : 1 channel
  
  Channel positions                        : Front: C
  
  Channel positions                        : 1/0/0
  
  ChannelLayout                            : C
  
  Samples per frame                        : 1024
  
  Sampling rate                            : 44100
  
  Sampling rate                            : 44.1 kHz
  
  Samples count                            : 2305019
  
  Frame rate                               : 43.066
  
  Frame rate                               : 43.066 FPS (1024 spf)
  
  Frame count                              : 2251
  
  Source frame count                       : 2254
  
  Compression mode                         : Lossy
  
  Compression mode                         : Lossy
  
  Stream size                              : 410424
  
  Stream size                              : 401 KiB (0%)
  
  Stream size                              : 401 KiB
  
  Stream size                              : 401 KiB
  
  Stream size                              : 401 KiB
  
  Stream size                              : 400.8 KiB
  
  Stream size                              : 401 KiB (0%)
  
  Proportion of this stream                : 0.00360
  
  Source stream size                       : 410894
  
  Source stream size                       : 401 KiB (0%)
  
  Source stream size                       : 401 KiB
  
  Source stream size                       : 401 KiB
  
  Source stream size                       : 401 KiB
  
  Source stream size                       : 401.3 KiB
  
  Source stream size                       : 401 KiB (0%)
  
  Source_StreamSize_Proportion             : 0.00360
  
  Title                                    : Core Media Audio
  
  Encoded date                             : UTC 2016-10-08 22:51:19
  
  Tagged date                              : UTC 2016-10-08 22:52:12
  
  
  
  Other #1
  
  Count                                    : 112
  
  Count of stream of this kind             : 2
  
  Kind of stream                           : Other
  
  Kind of stream                           : Other
  
  Stream identifier                        : 0
  
  Stream identifier                        : 1
  
  Type                                     : meta
  
  Duration                                 : 52268
  
  Duration                                 : 52 s 268 ms
  
  Duration                                 : 52 s 268 ms
  
  Duration                                 : 52 s 268 ms
  
  Duration                                 : 00:00:52.268
  
  Duration                                 : 00:00:52.268
  
  Frame count                              : 6
  
  Bit rate mode                            : VBR
  
  
  
  Other #2
  
  Count                                    : 112
  
  Count of stream of this kind             : 2
  
  Kind of stream                           : Other
  
  Kind of stream                           : Other
  
  Stream identifier                        : 1
  
  Stream identifier                        : 2
  
  Type                                     : meta
  
  Duration                                 : 52268
  
  Duration                                 : 52 s 268 ms
  
  Duration                                 : 52 s 268 ms
  
  Duration                                 : 52 s 268 ms
  
  Duration                                 : 00:00:52.268
  
  Duration                                 : 00:00:52.268
  
  Frame count                              : 1
  
  Bit rate mode                            : CBR

  and ffprobe IMG_1438.MOV outputs :

  ffprobe version 3.1.3 Copyright (c) 2007-2016 the FFmpeg developers
  
    built with Apple LLVM version 7.3.0 (clang-703.0.31)
  
    configuration: --prefix=/usr/local/Cellar/ffmpeg/3.1.3 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-opencl --enable-libx264 --enable-libmp3lame --enable-libxvid --disable-lzma --enable-vda
  
    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
  
    libavresample   3.  0.  0 /  3.  0.  0
  
    libswscale      4.  1.100 /  4.  1.100
  
    libswresample   2.  1.100 /  2.  1.100
  
    libpostproc    54.  0.100 / 54.  0.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'IMG_1438.MOV':
  
    Metadata:
  
      major_brand     : qt  
  
      minor_version   : 0
  
      compatible_brands: qt  
  
      creation_time   : 2016-10-08 22:51:19
  
      com.apple.quicktime.make: Apple
  
      com.apple.quicktime.model: iPhone 5
  
      com.apple.quicktime.software: 10.0.2
  
      com.apple.quicktime.creationdate: 2016-10-08T17:51:19-0500
  
    Duration: 00:00:52.27, start: 0.000000, bitrate: 17446 kb/s
  
      Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 1920x1080, 17375 kb/s, 25.04 fps, 120 tbr, 600 tbn, 1200 tbc (default)
  
      Metadata:
  
        rotate          : 90
  
        creation_time   : 2016-10-08 22:51:19
  
        handler_name    : Core Media Data Handler
  
        encoder         : H.264
  
      Side data:
  
        displaymatrix: rotation of -90.00 degrees
  
      Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, mono, fltp, 62 kb/s (default)
  
      Metadata:
  
        creation_time   : 2016-10-08 22:51:19
  
        handler_name    : Core Media Data Handler
  
      Stream #0:2(und): Data: none (mebx / 0x7862656D), 0 kb/s (default)
  
      Metadata:
  
        creation_time   : 2016-10-08 22:51:19
  
        handler_name    : Core Media Data Handler
  
      Stream #0:3(und): Data: none (mebx / 0x7862656D), 0 kb/s (default)
  
      Metadata:
  
        creation_time   : 2016-10-08 22:51:19
  
        handler_name    : Core Media Data Handler
  
  Unsupported codec with id 0 for input stream 2
  
  Unsupported codec with id 0 for input stream 3

  UPDATE
  To clarify : my video above, the one with the high framerate (120 FPS) output after scaling, plays perfectly before and after scaling with FFmpeg (no sync issues, and 120 FPS is only about 14% larger in file size), I am simply trying to understand why this increase in framerate happens (just a little beyond Mulvya’s note that the framerate stored in the container is wrong).

  From a programming perspective, the initial issue I ran into was that I was using frame= from FFmpeg’s sterr console output to determine progress, which reports erroneous results when the frame count increases dramatically on output ("I’m 372% done encoding ?!") ; I have since read another stackoverflow answer and changed my code to use time=, which appears to be a more robust way for me to display FFmpeg progress. (Also, there is FFmpeg’s -progress option, of course).

  Improving on the original command

  My new command to scale, preserve a useful framerate, and optimize threads :

  ffmpeg -i IMG_1438.MOV -vf scale=-2:600 -r 30 -vsync 0 IMG_1438_scaledTo600.MOV

  Where 30 is the "Maximum frame rate" from mediainfo.

  Thanks to help in the comments, I now know I do not fully understand FFmpeg’s use of three different time bases for timestamps : tbn, tbc, and tbr.
  They were explained by Robert Swain in 2009 and his explanation was also used to answer a Stackoverflow question about tbn, tbc, tbr.

  It sounds to me, as I’m pulling together comments from Mulvya below and Michael Rampe at another forum, that tbr is guessed ; it is frequently but not always the best value to use when changing from a variable to a constant frame rate video.

  Which leaves these 2 questions...

  (1) tbr is incorrect when "field rate and frame rate" differ ? Does this happen a lot ?
  (2) Is -r 30 where 30 is the maximum frame rate reported by mediainfo the best way to do it for most codec/container combinations ? (Or should I only use this method when I am scaling a H.264/MPEG-4 AVC video ?)