Recherche avancée

Sur d’autres sites (9725)

• 9 Ways to Customise Your Matomo Like a Pro

  5 octobre 2022, par Erin

  Matomo is a feature-rich web analytics platform. As such, it has many layers of depth — core features, extra plug-ins, custom dimensions, reports, extensions and integrations. 

  Most of the product elements you see can be personalised and customised to your needs with minimal restrictions. However, this breadth of choice can be overlooked by new users. 

  In this post, we explain how to get the most out of Matomo with custom reports, dashboards, dimensions and even app design. 

  How to customise your Matomo web analytics

  To make major changes to Matomo (e.g., create custom dashboards or install new plugins), you’ll have to be a Matomo Super User (a.k.a. The Admin). Super Users can also grant administrator permissions to others so that more people could customise your Matomo deployment. 

  Most feature-related customisations (e.g. configuring a custom report, adding custom goal tracking, etc.) can be done by all users. 

  With the above in mind, here’s how you can tweak Matomo to better serve your website analytics needs : 

  1. Custom dashboards

  

  Dashboards provide a panorama view of all the collected website statistics. We display different categories of stats and KPIs as separate widgets — a standalone module you can also customise. 

  On your dashboard, you can change the type, position and number of widgets on display. This is an easy way to create separate dashboard views for different projects, clients or team members. Rather than a one-size-fits-all dashboard, a custom dashboard designed for a specific role or business unit will increase data-driven decision-making and efficiency across the business.

  You can create a new dashboard view in a few clicks. Then select a preferred layout — a split-page view or multi columns. Next, populate the new dashboard area with preferred widgets showing :

  • SEO website rankings 
  • Visits, conversions and revenue 
  • Custom reports 

  Or code a custom widget area to pull specific website stats or other reporting data you need. Once you are done, arrange everything with our drag-and-drop functionality. 

  

  Popular feature use cases

  • Personalised website statistics layout for convenient viewing 
  • Simplified analytics dashboards for the line of business leaders/stakeholders 
  • Project- or client-specific dashboards for easy report sharing 

  Read more about customising Matomo dashboards and widget areas. 

  2. Custom reports

  

  As the name implies, Custom Reports widget allows you to mesh any of the dimensions and metrics collected by Matomo into a custom website traffic analysis. Custom reports save users time by providing specific data needed in one view so there is no need to jump back and forth between multiple reports or toggle through a report to find data.

  For each custom report, you can select up to three dimensions and then apply additional quantitative measurements (metrics) to drill down into the data.

  For example, if you want to closely observe mobile conversion rates in one market, you can create the following custom report :

  • Dimensions : User Type (registered), Device type (mobile), Location (France)
  • Metrics : Visits, Conversion Rate, Revenue, Avg. Generation Time.

  Custom Report widget is available within Matomo Cloud and as a plugin for Matomo On-Premise.

  &lt;script type=&quot;text/javascript&quot;&gt;<br />
       if ('function' === typeof window.playMatomoVideo){<br />
       window.playMatomoVideo(&quot;custom_reports&quot;, &quot;#custom_reports&quot;)<br />
       } else {<br />
       document.addEventListener(&quot;DOMContentLoaded&quot;, function() { window.playMatomoVideo(&quot;custom_reports&quot;, &quot;#custom_reports&quot;); });<br />
       }<br />
  &lt;/script&gt;

  Popular feature use cases

  • Campaign-specific reporting to better understand the impact of different promo strategies 
  • Advanced event tracking for conversion optimization 
  • Market segmentation reports to analyse different audience cohorts 

  Read more about creating and analysing Custom Reports.

  3. Custom widgets

  

  We realise that our users have different degrees of analytics knowledge. Some love in-depth reporting dimensions and multi-row reporting tables. Others just want to see essential stats. 

  To delight both the pros and the novice users, we’ve created widgets — reporting sub-modules you can add, delete or rearrange in a few clicks. Essentially, a widget is a slice of a dashboard area you can populate with extra information. 

  You can add pre-made custom widgets to Matomo or develop your own widget to display custom reports or even external data (e.g., offline sales volume). At the same time, you can also embed Matomo widgets into other applications (e.g., a website CMS or corporate portal).

  Popular feature use cases

  • Display main goals (e.g., new trial sign-ups) on the main dashboard for greater visibility 
  • Highlight cost-per-conversion reporting by combining goals and conversion data to keep your budgets in check 
  • Run omnichannel eCommerce analytics (with embedded offline sales data) to get a 360-degree view into your operations 

  Read more about creating widgets in Matomo (beginner’s guide). 

  4. Custom dimensions 

  

  Dimensions describe the characteristics of reported data. Think of them as “filters” — a means to organise website analytics data by a certain parameter such as “Browser”, “Country”, “Device Type”, “User Type” and many more. 

  Custom Dimensions come in handy for all sorts of segmentation reports. For example, comparing conversion rates between registered and guest users. Or tracking revenue by device type and location. 

  For convenience, we’ve grouped Custom Dimensions in two categories :

  Visit dimensions. These associate metadata about a user with Visitor profiles — a summary of different knowledge you have about your audience. Reports for Visit scoped custom dimensions are available in the Visitors section of your dashboard. 

  Action dimensions. These segment users by specific actions tracked by Matomo such as pageviews, events completion, downloads, form clicks, etc. When configuring Custom Dimensions, you can select among pre-defined action types or code extra action dimensions. Action scoped custom dimensions are available in the Behaviours section of Matomo. 

  Depending on your Matomo version, you can apply 5 – 15 custom dimensions to reports. 

  Important : Since you can’t delete dimensions (only deactivate them), think about your use case first. Custom Dimensions each have their own dedicated reports page on your Matomo dashboard. 

  Popular custom dimension use cases among users :

  • Segmenting reports by users’ screen resolution size to understand how your website performs on different devices
  • Monitor conversion rates for different page types to determine your best-performing assets 

  Read more about creating, tracking and managing Custom Dimensions. 

  5. Custom scheduled reports

  Manually sending reports can be time consuming, especially if you have multiple clients or provide reports to numerous stakeholders. Custom scheduled reports remove this manual process to improve efficiency and ensure timely distribution of data to relevant users.

  Any report in Matomo (default or custom) can be shared with others by email as a PDF file, HTML content or as an attached CSV document. 

  You can customise which data you want to send to different people — your colleagues, upper management, clients or other company divisions. Then set up the frequency of email dispatches and Matomo will do the rest. 

  Auto-scheduling an email report is easy. Name your report, select a Segment (aka custom or standard report), pick time, file format and sender. 

  

  You can also share links to Matomo reports as text messages, if you are using ASPSMS or Clockwork SMS. 

  Popular feature use cases

  • Convenient stakeholder reporting on key website KPIs 
  • Automated client updates to keep clients informed and reduce workload 
  • Easy data downloads for doing custom analysis with business intelligence tools 

  Read more about email reporting features in Matomo. 

  6. Custom alerts

  

  Custom Alerts is a Matomo plugin for keeping you updated on the most important analytics events. Unlike Custom Reports, which provide a complete or segmented analytics snapshot, alerts are better suited for tracking individual events. For example, significant traffic increases from a specific channel, new 404 pages or major goal achievement (e.g., hitting 1,000 sales in a week). 

  Custom Alerts are a convenient way to keep your finger on the pulse of your site so you can quickly remedy an issue or get updated on reaching a crucial KPI promptly. You can receive custom alerts via email or text message in a matter of minutes.

  To avoid flooding your inbox with alerts, we recommend reserving Custom Alerts for a select few use cases (3 to 5) and schedule custom Email Reports to receive general web page analytics. 

  Popular custom alerts use cases among users :

  • Monitor sudden drops in revenue to investigate the cause behind them and solve any issues promptly 
  • Get notified of traffic spikes or sudden dips to better manage your website’s technical performance 

  Read more about creating and managing Custom Alerts. 

  7. Goals

  

  Goals feature helps you better understand how your website performs on certain business objectives such as lead generation, online sales or content discovery. A goal is a quantifiable action you want to measure (e.g., a specific page visit, form submission or a file download). 

  When combined together, Goals make up your sales funnel — a series of specific actions you expect users to complete in order to convert. 

  Goals-setting and Funnel Analytics are a powerful, customisable combo for understanding how people navigate your website ; what makes them take action or, on the contrary, lose interest and bounce off. 

  On Matomo, you can simultaneously track multiple goals, monitor multiple conversions per one visit (e.g., when one user requests two content downloads) and assign revenue targets to specific goals.

  &lt;script type=&quot;text/javascript&quot;&gt;<br />
       if ('function' === typeof window.playMatomoVideo){<br />
       window.playMatomoVideo(&quot;goals&quot;, &quot;#goals&quot;)<br />
       } else {<br />
       document.addEventListener(&quot;DOMContentLoaded&quot;, function() { window.playMatomoVideo(&quot;goals&quot;, &quot;#goals&quot;); });<br />
       }<br />
  &lt;/script&gt;

  Separately, Matomo Cloud users also get access to a premium Funnels feature and Multi Channel Conversion Attribution. On-Premises Matomo users can get both as paid plugins via our Marketplace.

  Popular goal tracking use cases among users :

  • Tracking newsletter subscription to maximise subscriber growth 
  • Conversion tracking for gated content (e.g., eBooks) to understand how each asset performs 
  • Analysing the volume of job applications per post to better interpret your HR marketing performance 

  Read more about creating and managing Goals in Matomo.

  8. Themes

  

  Want to give your Matomo app a distinctive visual flair ? Pick a new free theme for your On-Premises installation. Minimalistic, dark or classic — our community created six different looks that other Matomo users can download and install in a few clicks. 

  If you have some HTML/CSS/JS knowledge, you can also design your own Matomo theme. Since Matomo is an open-source project, we don’t restrict interface customisation and always welcome creativity from our users.

  Read more about designing your own Matomo theme (developer documentation).

  9. White labelling

  

  Matomo is one of the few website analytics tools to support white labelling. White labelling means that you can distribute our product to others under your brand. 

  For example, as a web design agency, you can delight customers with pre-installed GDPR-friendly website analytics. Marketing services providers, in turn, can present their clients with embedded reporting widgets, robust funnel analytics and 100% unsampled data. 

  Apart from selecting a custom theme, you can also align Matomo with your brand by :

  • Customising product name
  • Using custom header/font colours 
  • Change your tracking endpoint
  • Remove links to Matomo.org

  To streamline Matomo customisation and set-up, we developed a White Label plug-in. It provides a convenient set of controls for changing your Matomo deployment and distributing access rights to other users or sharing embedded Matomo widgets). 

  Read more about white labelling Matomo. 

  Learning more about Matomo 

  Matomo has an ever-growing list of features, ranging from standard website tracking controls to unique conversion rate optimisation tools (heatmaps, media analytics, user cohorts and more).

  To learn more about Matomo features you can check our free video web analytics training series where we cover the basics. For feature-specific tips, tricks and configurations, browse our video content or written guides. 

  21 day free trial. No credit card required.

• FFMPEG crash while cropping video

  18 octobre 2022, par Khawar Raza

  I am using FFMPEG to crop a video. I am using ffmpeg-kit as a ffmpeg wrapper in my android app where the user can select any output size irrespective of the original video aspect ratio. Below is the problematic command :

  


  -i "/storage/emulated/0/Download/83a2f6_1080p~2.mp4" -filter_complex "[0:v]crop=304:236:2:2[cropped]" -map "[cropped]" "/storage/emulated/0/DCIM/appname/vid_d8ee328d-ec7a-468b-9313-4561dceea33e.mp4"


  


  When the execution starts, the application crashes.

  


  Logs :

  


  I/ffmpeg-kit: Loading ffmpeg-kit.
I/ffmpeg-kit: Loaded ffmpeg-kit-min-gpl-arm64-v8a-4.5.1-20220101.
D/ffmpeg-kit: Async callback block started.
D/VideoEditor:  ffmpeg version v4.5-dev-3393-g30322ebe3c
D/VideoEditor:   Copyright (c) 2000-2021 the FFmpeg developers
D/VideoEditor:  
D/VideoEditor:    built with Android (7155654, based on r399163b1) clang version 11.0.5 (https://android.googlesource.com/toolchain/llvm-project 87f1315dfbea7c137aa2e6d362dbb457e388158d)
D/VideoEditor:    configuration: --cross-prefix=aarch64-linux-android- --sysroot=/files/android-sdk/ndk/22.1.7171670/toolchains/llvm/prebuilt/linux-x86_64/sysroot --prefix=/storage/light/projects/ffmpeg-kit/prebuilt/android-arm64/ffmpeg --pkg-config=/usr/bin/pkg-config --enable-version3 --arch=aarch64 --cpu=armv8-a --target-os=android --enable-neon --enable-asm --enable-inline-asm --ar=aarch64-linux-android-ar --cc=aarch64-linux-android24-clang --cxx=aarch64-linux-android24-clang++ --ranlib=aarch64-linux-android-ranlib --strip=aarch64-linux-android-strip --nm=aarch64-linux-android-nm --extra-libs='-L/storage/light/projects/ffmpeg-kit/prebuilt/android-arm64/cpu-features/lib -lndk_compat' --disable-autodetect --enable-cross-compile --enable-pic --enable-jni --enable-optimizations --enable-swscale --disable-static --enable-shared --enable-pthreads --enable-v4l2-m2m --disable-outdev=fbdev --disable-indev=fbdev --enable-small --disable-xmm-clobber-test --disable-debug --enable-lto --disable-neon-clobber-test --disable-programs --disable-postproc --disable-doc --disable-htmlpages --disable-manpages --disable-podpages --disable-txtpages --disable-sndio --disable-schannel --disable-securetransport --disable-xlib --disable-cuda --disable-cuvid --disable-nvenc --disable-vaapi --disable-vdpau --disable-videotoolbox --disable-audiotoolbox --disable-appkit --disable-alsa --disable-cuda --disable-cuvid --disable-nvenc --disable-vaapi --disable-vdpau --enable-libx264 --enable-libxvid --enable-libx265 --enable-libvidstab --disable-sdl2 --disable-openssl --enable-zlib --enable-mediacodec --enable-gpl
D/VideoEditor:    libavutil      57. 13.100 / 57. 13.100
D/VideoEditor:    libavcodec     59. 15.102 / 59. 15.102
D/VideoEditor:    libavformat    59. 10.100 / 59. 10.100
D/VideoEditor:    libavdevice    59.  1.100 / 59.  1.100
D/VideoEditor:    libavfilter     8. 21.100 /  8. 21.100
D/VideoEditor:    libswscale      6.  1.102 /  6.  1.102
D/VideoEditor:    libswresample   4.  0.100 /  4.  0.100
D/VideoEditor:  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/storage/emulated/0/Download/83a2f6_1080p~2.mp4':
D/VideoEditor:    Metadata:
D/VideoEditor:      major_brand     : 
D/VideoEditor:  mp42
D/VideoEditor:  
D/VideoEditor:      minor_version   : 
D/VideoEditor:  0
D/VideoEditor:  
D/VideoEditor:      compatible_brands: 
D/VideoEditor:  isommp42
D/VideoEditor:  
D/VideoEditor:      com.android.version: 
D/VideoEditor:  12
D/VideoEditor:  
D/VideoEditor:    Duration: 
D/VideoEditor:  00:02:18.11
D/VideoEditor:  , start: 
D/VideoEditor:  0.000000
D/VideoEditor:  , bitrate: 
D/VideoEditor:  1929 kb/s
D/VideoEditor:  
D/VideoEditor:    Stream #0:0
D/VideoEditor:  [0x1]
D/VideoEditor:  (eng)
D/VideoEditor:  : Video: h264 (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 1080x808, 1864 kb/s
D/VideoEditor:  , 
D/VideoEditor:  18 fps, 
D/VideoEditor:  18 tbr, 
D/VideoEditor:  90k tbn
D/VideoEditor:   (default)
D/VideoEditor:  
D/VideoEditor:      Metadata:
D/VideoEditor:        creation_time   : 
D/VideoEditor:  2022-10-06T11:47:07.000000Z
D/VideoEditor:  
D/VideoEditor:        handler_name    : 
D/VideoEditor:  VideoHandle
D/VideoEditor:  
D/VideoEditor:        vendor_id       : 
D/VideoEditor:  [0][0][0][0]
D/VideoEditor:  
D/VideoEditor:    Stream #0:1
D/VideoEditor:  [0x2]
D/VideoEditor:  (und)
D/VideoEditor:  : Audio: aac (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 64 kb/s
D/VideoEditor:   (default)
D/VideoEditor:  
D/VideoEditor:      Metadata:
D/VideoEditor:        creation_time   : 
D/VideoEditor:  2022-10-06T11:47:07.000000Z
D/VideoEditor:  
D/VideoEditor:        handler_name    : 
D/VideoEditor:  SoundHandle
D/VideoEditor:  
D/VideoEditor:        vendor_id       : 
D/VideoEditor:  [0][0][0][0]
D/VideoEditor:  


D/VideoEditor:  [h264 @ 0x7654fe8500] The "sub_text_format" option is deprecated: Deprecated, does nothing
D/VideoEditor:  Stream mapping:
D/VideoEditor:    Stream #0:0 (h264) -> crop
D/VideoEditor:  
D/VideoEditor:    crop
D/VideoEditor:   -> Stream #0:0 (libx264)
D/VideoEditor:  Press [q] to stop, [?] for help


D/VideoEditor:  [libx264 @ 0x7654fb9af0] using cpu capabilities: ARMv8 NEON
D/VideoEditor:  [libx264 @ 0x7654fb9af0] profile High, level 1.2, 4:2:0, 8-bit
D/VideoEditor:  [libx264 @ 0x7654fb9af0] 264 - core 163 - H.264/MPEG-4 AVC codec - Copyleft 2003-2021 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=7 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=18 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
D/VideoEditor:  Output #0, mp4, to '/storage/emulated/0/DCIM/appname/vid_d8ee328d-ec7a-468b-9313-4561dceea33e.mp4':
D/VideoEditor:    Metadata:
D/VideoEditor:      major_brand     : 
D/VideoEditor:  mp42
D/VideoEditor:  
D/VideoEditor:      minor_version   : 
D/VideoEditor:  0
D/VideoEditor:  
D/VideoEditor:      compatible_brands: 
D/VideoEditor:  isommp42
D/VideoEditor:  
D/VideoEditor:      com.android.version: 
D/VideoEditor:  12
D/VideoEditor:  
D/VideoEditor:      encoder         : 
D/VideoEditor:  Lavf59.10.100
D/VideoEditor:  
D/VideoEditor:    Stream #0:0
D/VideoEditor:  : Video: h264 (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 304x236, q=2-31
D/VideoEditor:  , 
D/VideoEditor:  18 fps, 
D/VideoEditor:  18432 tbn
D/VideoEditor:   (default)
D/VideoEditor:  
D/VideoEditor:      Metadata:
D/VideoEditor:        encoder         : 
D/VideoEditor:  Lavc59.15.102 libx264
D/VideoEditor:  
D/VideoEditor:      Side data:
D/VideoEditor:        
D/VideoEditor:  cpb: 
D/VideoEditor:  bitrate max/min/avg: 0/0/0 buffer size: 0 
D/VideoEditor:  vbv_delay: N/A
D/VideoEditor:  
D/VideoEditor:  frame=    1 fps=0.0 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x    

A/libc: Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x745d9ff000 in tid 16893 (pool-15-thread-), pid 16696 (videocompressor)


A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/x1sxx/x1s:12/SP1A.210812.016/G980FXXSFFVH7:user/release-keys'
Revision: '22'
ABI: 'arm64'
Processor: '5'
A/DEBUG: Timestamp: 2022-10-09 18:57:38.882598912+0500
A/DEBUG: Process uptime: 1086s
A/DEBUG: Cmdline: com.app.packagename
A/DEBUG: pid: 16939, tid: 20568, name: pool-15-thread-  >>> com.app.packagename <<<
A/DEBUG: uid: 11091
A/DEBUG: signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x74640ce000
A/DEBUG:     x0  0000007594f30960  x1  00000074640c9a60  x2  00000074640c9eb4  x3  00000074640cac34
A/DEBUG:     x4  00000074640cdff4  x5  00000074671bb2dc  x6  00000000fffffffb  x7  0000000000000013
A/DEBUG:     x8  000000000000000e  x9  00000074640cddc0  x10 0000000000000013  x11 0000007488459ffc
A/DEBUG:     x12 00000074640c9c70  x13 000000000000000e  x14 0000000000007fff  x15 0000000000000013
A/DEBUG:     x16 00000074640cac04  x17 00000074640c7a58  x18 000000746626e000  x19 0000000000000027
A/DEBUG:     x20 000000776541c3b0  x21 00000074671bc4f8  x22 00000074640ca9f0  x23 0000007765422300
A/DEBUG:     x24 0000000000000027  x25 00000074640cac04  x26 0000000000000028  x27 00000074640c9a30
A/DEBUG:     x28 0000007594f30940  x29 000000000000010a
A/DEBUG:     lr  000000748841a960  sp  00000074671bb290  pc  000000748845a010  pst 0000000080000000
A/DEBUG: backtrace:
A/DEBUG:       #00 pc 0000000000359010  /data/app/~~IBCbjRbZBpQ00ORNDFZdxg==/com.app.packagename-5sdOCmN82SjJJTibcsYMpQ==/base.apk!libavcodec.so


  


  I don't know what is wrong with the output width and height parameters. If I change [0:v]crop=304:236:2:2[cropped] to [0:v]crop=304:304:2:2[cropped] with change in height, the process completes successfully. The original video (1080x808) is not smaller than the output size. It does not seem to be a problem in the video as I have tried different videos. Any tips on what is missing from my command ?

  


• Download M3U8 That Is Playable

  15 octobre 2022, par Devin Dixon

  I am trying to download a livestream from this traffic camera source : https://vss1live.dot.ga.gov/lo/alph-cam-002.stream/playlist.m3u8

  


  The ffmpeg I am using is :

  


  ffmpeg -i https://vss1live.dot.ga.gov/lo/alph-cam-002.stream/playlist.m3u8 -preset slow -codec:a libfdk_aac -b:a 128k -codec:v libx264 -pix_fmt yuv420p -b:v 4500k -minrate 4500k -maxrate 9000k -bufsize 9000k -vf scale=-1:720 test.mp4


  


  And here are the logs when I quit the recording :

  


  ffmpeg version 5.0.1 Copyright (c) 2000-2022 the FFmpeg developers
  built with Apple clang version 13.1.6 (clang-1316.0.21.2)
  configuration: --prefix=/opt/homebrew/Cellar/ffmpeg/5.0.1 --enable-shared --enable-pthreads --enable-version3 --cc=clang --host-cflags= --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom --enable-libbluray --enable-libdav1d --enable-libmp3lame --enable-libopus --enable-librav1e --enable-librist --enable-librubberband --enable-libsnappy --enable-libsrt --enable-libtesseract --enable-libtheora --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libspeex --enable-libsoxr --enable-libzmq --enable-libzimg --disable-libjack --disable-indev=jack --enable-videotoolbox --enable-neon
  libavutil      57. 17.100 / 57. 17.100
  libavcodec     59. 18.100 / 59. 18.100
  libavformat    59. 16.100 / 59. 16.100
  libavdevice    59.  4.100 / 59.  4.100
  libavfilter     8. 24.100 /  8. 24.100
  libswscale      6.  4.100 /  6.  4.100
  libswresample   4.  3.100 /  4.  3.100
  libpostproc    56.  3.100 / 56.  3.100
[hls @ 0x1417050e0] Skip ('#EXT-X-VERSION:3')
[hls @ 0x1417050e0] Opening 'https://vss1live.dot.ga.gov/lo/alph-cam-002.stream/chunklist_w259023283.m3u8' for reading
[hls @ 0x1417050e0] Skip ('#EXT-X-VERSION:3')
[hls @ 0x1417050e0] Skip ('#EXT-X-DISCONTINUITY-SEQUENCE:0')
[hls @ 0x1417050e0] Opening 'https://vss1live.dot.ga.gov/lo/alph-cam-002.stream/media_w259023283_61526.ts' for reading
[hls @ 0x1417050e0] Opening 'https://vss1live.dot.ga.gov/lo/alph-cam-002.stream/media_w259023283_61527.ts' for reading
Input #0, hls, from 'https://vss1live.dot.ga.gov/lo/alph-cam-002.stream/playlist.m3u8':
  Duration: N/A, start: 65276.905822, bitrate: N/A
  Program 0 
    Metadata:
      variant_bitrate : 142637
  Stream #0:0: Data: timed_id3 (ID3  / 0x20334449)
    Metadata:
      variant_bitrate : 142637
  Stream #0:1: Video: h264 (Baseline) ([27][0][0][0] / 0x001B), yuvj420p(pc, bt709), 480x270 [SAR 1:1 DAR 16:9], 15 fps, 15 tbr, 90k tbn
    Metadata:
      variant_bitrate : 142637
Stream mapping:
  Stream #0:1 -> #0:0 (h264 (native) -> h264 (libx264))
Press [q] to stop, [?] for help
[swscaler @ 0x120248000] [swscaler @ 0x120258000] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x120248000] [swscaler @ 0x120278000] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x120248000] [swscaler @ 0x120288000] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x120248000] [swscaler @ 0x120298000] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x120248000] [swscaler @ 0x1202a8000] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x120248000] [swscaler @ 0x1202b8000] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x120248000] [swscaler @ 0x1202c8000] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x120248000] [swscaler @ 0x1202d8000] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x120248000] [swscaler @ 0x1202e8000] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x120248000] [swscaler @ 0x1202f8000] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x120248000] [swscaler @ 0x120308000] deprecated pixel format used, make sure you did set range correctly
[libx264 @ 0x14169ff30] using SAR=1/1
[libx264 @ 0x14169ff30] using cpu capabilities: ARMv8 NEON
[libx264 @ 0x14169ff30] profile High, level 3.1, 4:2:0, 8-bit
[libx264 @ 0x14169ff30] 264 - core 163 r3060 5db6aa6 - H.264/MPEG-4 AVC codec - Copyleft 2003-2021 - http://www.videolan.org/x264.html - options: cabac=1 ref=5 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=8 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=2 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=15 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=3 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=15 scenecut=40 intra_refresh=0 rc_lookahead=50 rc=abr mbtree=1 bitrate=4500 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 vbv_maxrate=9000 vbv_bufsize=9000 nal_hrd=none filler=0 ip_ratio=1.40 aq=1:1.00
Output #0, mp4, to 'test.mp4':
  Metadata:
    encoder         : Lavf59.16.100
  Stream #0:0: Video: h264 (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 1280x720 [SAR 1:1 DAR 16:9], q=2-31, 4500 kb/s, 15 fps, 15360 tbn
    Metadata:
      variant_bitrate : 142637
      encoder         : Lavc59.18.100 libx264
    Side data:
      cpb: bitrate max/min/avg: 9000000/0/4500000 buffer size: 9000000 vbv_delay: N/A
[https @ 0x13201ce00] Opening 'https://vss1live.dot.ga.gov/lo/alph-cam-002.stream/media_w259023283_61528.ts' for reading
[https @ 0x131814200] Opening 'https://vss1live.dot.ga.gov/lo/alph-cam-002.stream/chunklist_w259023283.m3u8' for reading
[hls @ 0x1417050e0] Skip ('#EXT-X-VERSION:3')
[hls @ 0x1417050e0] Skip ('#EXT-X-DISCONTINUITY-SEQUENCE:0')
[https @ 0x131814200] Opening 'https://vss1live.dot.ga.gov/lo/alph-cam-002.stream/chunklist_w259023283.m3u8' for reading
[hls @ 0x1417050e0] Skip ('#EXT-X-VERSION:3')
[hls @ 0x1417050e0] Skip ('#EXT-X-DISCONTINUITY-SEQUENCE:0')
[https @ 0x13201ce00] Opening 'https://vss1live.dot.ga.gov/lo/alph-cam-002.stream/media_w259023283_61529.ts' for reading
[tls @ 0x131606060] Error in the pull function.
[tls @ 0x131606060] IO error: End of file
[hls @ 0x1417050e0] Opening 'https://vss1live.dot.ga.gov/lo/alph-cam-002.stream/media_w259023283_61529.ts' for reading
^Cav_interleaved_write_frame(): Immediate exit requested93 bitrate=4697.0kbits/s speed=1.77x    
Error writing trailer of test.mp4: Immediate exit requested
frame=  610 fps= 23 q=4.0 Lsize=   20224kB time=00:00:36.13 bitrate=4585.1kbits/s speed=1.35x    
video:20500kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
Error closing file test.mp4: Immediate exit requested
[libx264 @ 0x14169ff30] frame I:3     Avg QP: 2.13  size:192240
[libx264 @ 0x14169ff30] frame P:156   Avg QP: 0.44  size: 66488
[libx264 @ 0x14169ff30] frame B:451   Avg QP: 1.32  size: 28629
[libx264 @ 0x14169ff30] consecutive B-frames:  1.1%  0.3%  1.5% 97.0%
[libx264 @ 0x14169ff30] mb I  I16..4: 21.7% 26.6% 51.7%
[libx264 @ 0x14169ff30] mb P  I16..4:  2.9%  3.1% 11.0%  P16..4:  9.3%  4.1%  3.4%  0.0%  0.0%    skip:66.1%
[libx264 @ 0x14169ff30] mb B  I16..4:  0.1%  0.4%  1.6%  B16..8: 14.6%  4.0%  2.1%  direct: 3.2%  skip:73.9%  L0:53.1% L1:41.6% BI: 5.3%
[libx264 @ 0x14169ff30] final ratefactor: -0.00
[libx264 @ 0x14169ff30] 8x8 transform intra:19.0% inter:11.1%
[libx264 @ 0x14169ff30] direct mvs  spatial:98.2% temporal:1.8%
[libx264 @ 0x14169ff30] coded y,uvDC,uvAC intra: 91.5% 77.2% 76.6% inter: 11.8% 12.2% 11.9%
[libx264 @ 0x14169ff30] i16 v,h,dc,p: 17% 54% 10% 19%
[libx264 @ 0x14169ff30] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 16% 42% 15%  3%  5%  3%  7%  3%  6%
[libx264 @ 0x14169ff30] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 16% 32% 13%  5%  9%  5%  9%  4%  7%
[libx264 @ 0x14169ff30] i8c dc,h,v,p: 38% 44% 13%  5%
[libx264 @ 0x14169ff30] Weighted P-Frames: Y:0.0% UV:0.0%
[libx264 @ 0x14169ff30] ref P L0: 83.7%  3.3%  8.8%  2.4%  1.8%  0.0%
[libx264 @ 0x14169ff30] ref B L0: 79.9% 19.0%  0.8%  0.3%
[libx264 @ 0x14169ff30] ref B L1: 99.0%  1.0%
[libx264 @ 0x14169ff30] kb/s:4693.84
Exiting normally, received signal 2.


  


  Except the video doesn't seem to be playable by VLC or Quicktime. Given that the stream can end at any moment thus ending the file, how do I make the file actually playable ?