Recherche avancée

Médias (0)

Mot : - Tags -/xmlrpc

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (16)

  • Installation en mode ferme

    4 février 2011, par

    Le mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
    C’est la méthode que nous utilisons sur cette même plateforme.
    L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
    Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...)

  • Les formats acceptés

    28 janvier 2010, par

    Les commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
    ffmpeg -codecs ffmpeg -formats
    Les format videos acceptés en entrée
    Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
    Les formats vidéos de sortie possibles
    Dans un premier temps on (...)

  • La sauvegarde automatique de canaux SPIP

    1er avril 2010, par

    Dans le cadre de la mise en place d’une plateforme ouverte, il est important pour les hébergeurs de pouvoir disposer de sauvegardes assez régulières pour parer à tout problème éventuel.
    Pour réaliser cette tâche on se base sur deux plugins SPIP : Saveauto qui permet une sauvegarde régulière de la base de donnée sous la forme d’un dump mysql (utilisable dans phpmyadmin) mes_fichiers_2 qui permet de réaliser une archive au format zip des données importantes du site (les documents, les éléments (...)

Sur d’autres sites (3973)

  • 9 Form Optimisation Tips to Convert More Visitors

    15 février 2024, par Erin

    Forms might seem boring — that is, until you realise how powerful they are.

    No forms mean no leads.

    No leads mean no sales.

    No sales means you’ll run out of business.

    So, what do you do ?

    Optimise forms to land more leads.

    They’re a critical part of the sales funnel.

    Forms have many different purposes and can be used to :

    • Contact a company
    • Sign up for a newsletter
    • Request a demo
    • Start a free trial
    • And more

    If you want to get more leads (and ultimately more sales), then you need to optimise your forms.

    This guide will show you exactly how to do that (so you can start getting more conversions today). 

    What is form optimisation ?

    Before we dive into form optimisation, let’s back up a bit.

    Form conversion is our primary focus.

    Your form conversion rate is the percentage of visitors who submit a form divided by the total number of visitors who started the form times one hundred.

    For example, if 5,000 people started filling out your form this month and 350 submitted the form, the conversion rate would be : 

    350 / 5,000 x 100 = 7%

    So, what’s form optimisation ?

    What is form optimisation?

    It’s simply improving your forms to increase conversion rates.

    For most people, form conversion is all about increasing leads.

    Before you begin optimising your forms, it’s important you understand what’s good (and what’s not good) when it comes to form conversions.

    The average form conversion rate across all industries is 2.9%.

    This means you should expect about 3 out of every 100 visitors who start your form to submit it.

    If your form conversion is lower — or hovering around this number — then it’s important to start optimising now.

    With Matomo, you can track your form conversions with Matomo Form Analytics. Gain powerful insights into how your visitors interact with your forms with our intuitive dashboard.

    Why it’s important to optimise your forms

    Most people hear the word “forms” and think it’s boring.

    But forms are the doorway to leads.

    If you want to generate more sales, then you need to generate great forms.

    Here are five reasons you need to optimise your forms today :

    1. Improve conversions

    Form optimisation is really just conversion optimisation.

    But, instead of optimising and improving your site to directly improve sales conversions, you’re increasing lead conversions.

    Every smart website owner uses forms to draw people in further.

    The reality is that most of your website visitors will never return to your site.

    This means you need to do everything you can to grab their contact information so you can continue marketing to them day in and day out.

    Otherwise, you’ll lose them forever.

    When you know how to optimise your forms, you’ll be able to get a higher percentage of form viewers to fill it out.

    Higher conversions mean you get more leads, more customers, and ultimately more revenue.

    2. Capture more leads

    When you can increase your form conversion rate from 1% to 2%, it may seem insignificant.

    What’s a measly percentage point in conversions ?

    It’s a lot.

    When you’re dealing with traffic in the tens or hundreds of thousands each month, an increase in conversion rate by a whole percentile is massive.

    Let’s say you take your conversion rate from 2% to 3% on your form, and you have 70,000 visitors view the form each month.

    Well, if 1,400 people used to sign up to your email list each month at a 2% conversion rate, then at a 3% conversion rate, you’d get 2,100 new email signups every month.

    That’s a major difference.

    When you can improve your signup forms, you improve your lead generation (which is conversion rate optimisation). And the more leads you have, the more sales you’ll make in the long run.

    3. Get the most out of your traffic

    If your forms don’t perform well, then you’re wasting your time (and your traffic).

    By analysing your form data, you can quickly see what’s working and what’s not so you can optimise and improve the user experience (and your forms).

    For most people, this means getting more form viewers to fill out the form with their email and name.

    If 50,000 people visit your site each month, but only 1% of them fill out your form, you’re only getting 500 email signups per month.

    Rather than paying money to generate more traffic, why not just work on improving your website by implementing a better form ?

    If you can increase your form conversion rate to 2%, you will immediately go from 500 new subscribers per month to 1,000 per month.

    4. Spend less on acquisition

    If you’re able to get more form signups without having to generate more traffic, you just solved a pricey problem : acquisition costs.

    If you can now get 1,000 of your 50,000 visitors to sign up to your email list through a better form, then you doubled your signups.

    But that’s not all. You just cut your acquisition costs in half.

    If you spend $2,000 per month on acquisition but you’re able to get twice as many leads, then your acquisition costs are at 50% of what they used to be.

    This means you can pay the same amount but get twice as many leads.

    Or, you can pour even more money into acquisition since it’s now twice as effective so you can fuel growth even more.

    5. Grow revenue

    Forms generate revenue. It may not be direct (although, in some cases, it is). 

    But, forms will lead to sales.

    By placing optimised forms throughout your website at the right places, you will be able to capture a percentage of your visitors as leads, which means you’ll eventually make more sales.

    13 tips to optimise your forms for more conversions

    Now that you know what forms can do and why they’re important to grow your business, it’s time to dive into the best practices.

    Follow these 13 tips to ensure you’re getting the most out of your forms :

    1. Set form goals

    Your forms are hopeless without a goal.

    Before you set up a form on your website, ask yourself, “What am I trying to accomplish with this form ?”

    It could be :

    • Encouraging customers to reach out through a contact form
    • To get visitors to leave feedback on your product/service
    • Convert visitors into leads by giving you their email

    No matter what your goal is, make sure you’re clear on it ; otherwise, you won’t be as targeted and specific with your forms.

    Matomo Goals helps you set specific objectives for your marketing campaigns so you’re able to easily track conversions. Whether you’re looking to capture feedback or generate leads, you can leverage Matomo to see what’s working and what’s not in seconds.

    2. Remove or improve fields with high average time spent and high drop-off rates

    Delving into your Form Analytics provides invaluable insights into individual field performance. A crucial metric to focus on is the Average Time Spent. 

    If a field stands out with a significantly higher average time spent and experiences a high drop-off rate compared to others in the form, it’s a clear indicator that it’s causing frustration or confusion for your visitors.

    To address this, consider improving the field by converting it into a dropdown menu for easier completion or providing helpful text prompts. Alternatively, if the field isn’t essential, you might opt to remove it altogether.

    When you cut down on time spent and drop-offs, you’ll see your conversion rates go up.

    Matomo's Form Analytics dashboard displaying field timings

    Here’s a standout example from Matomo’s Form Analytics feature : the “Overview of your needs” field is taking on average 1 minute and 37 seconds to complete. 

    To streamline this, we might want to consider a simple fix like converting it into a dropdown menu. This change would offer visitors a clearer and quicker way to select from options.

    Screenshot of drop-off fields report in Matomo's Form Analytics feature

    Likewise, we observe that the “Overview of your needs” field experiences the highest drop-off rate, totaling 1,732 drop-offs. 

    With Form Analytics, it becomes clear what is needed to optimise forms and increase conversions.

    Try Matomo for Free

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

    No credit card required

    3. Start with the CTA

    When crafting and optimising your forms, you need to start with the end in mind. That’s why you need to start with your business goals.

    What are you trying to do with this form ? If you want to capture more emails, then make sure that’s very clear with the call to action (CTA).

    Start building your form by beginning with the CTA.

    For example : “Sign Up Now.”

    Once you have the action you want your potential customers to take, place it on the form. Then, you can work towards crafting the rest of the form.

    4. Put it above the fold

    If your visitors can’t find your form, they won’t fill it out. It’s plain and simple.

    You need to make sure your form is visible above the fold. This is the part of the screen that’s visible to your visitors once they land on your site (without needing to scroll down).

    Always remember to test this out on both desktop and mobile to ensure anyone (using laptops or a mobile device) will see your form upon landing on your site or page.

    Don’t forget about your mobile users. More people view mobile forms than desktop forms. 

    5. Put a CTA in the headline

    Your form needs to be clear.

    You have 1-3 seconds to communicate with your site visitors what your form is all about.

    For example, if you’re trying to get email signups with a lead magnet, then tell them the benefit quickly and concisely with a CTA in the headline, like this one :

    “Subscribe to Save 10% On Your Next Order”

    This is a great example of a headline-CTA combo that tells the visitor what to do and what they get out of it.

    Matomo’s behaviour analytics features like Session Recordings let you see where visitors are clicking and spending time. For example, if people are reading the headline, but not scrolling down to read the form, it’s probably a sign you need to test a different headline.

    6. Ensure you have the right fields

    Your form fields matter.

    What information are you trying to capture from your audience ?

    One beginner mistake people make is requiring too much information and including many fields in a form.

    You want to get as much data on your audience as possible, right ? Wrong.

    If you ask for too much information, people won’t fill it out, and it will harm the user experience. You need to make it super easy.

    If you want more emails to grow your list, then stick with someone’s email (and possibly their name as well). One line for a name. One line for an email address. Keep it simple.

    If you’re after SMS as well, don’t include it on the form. Instead, create a two-step form that pops up an SMS form after someone fills out the email form.

    Multi-step forms enable you to capture those emails easily (and still get a percentage to fill out the second form) without making it seem like too much work for your audience.

    Another path is to include optional fields (that users don’t have to fill out to click submit).

    Just keep in mind that shorter forms perform better than longer ones.

    If you make them too long, it feels like work for the user and will lead to lower completion rates.

    7. Always capture email address

    If you’re unsure of what information to capture (i.e. name, number, email, occupation, age, etc.), always stick to email.

    Email is used by over 4 billion people every single day, and it’s not going away anytime soon.

    When determining which fields to include, start with email.

    Capture more leads with quality forms.

    8. Test different buttons and copy

    You need to track your form performance if you want to get the best conversions.

    One of the best form elements to start testing is your button copy.

    In most cases, form completion buttons will have the word “submit” on them.

    But you don’t have to stick with this word.

    You can (and should) experiment with different submit button copy.

    Here are a few examples of replacement words for your action button :

    • Complete
    • Sign Up
    • Join now
    • Get started

    Remember to experiment with your action button. Try a different copy. Just keep it short.

    You can also try A/B testing your form by experimenting with different colours, copy, and more.

    Matomo's A/B testing dashboard displaying results of CTA experiment

    In the example above from Matomo’s A/B testing feature, we found that changing the wording of our call to action made a big difference. The new “Apply Now” button performed much better, with a 3.6% conversion rate compared to just 1.7% for the original one.

    Try Matomo for Free

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

    No credit card required

    9. Test static vs. popup

    There are various types of online forms.

    The most common is the static form that just sits in one place and is always there.

    Another popular form type is the popup.

    This is where a form will appear based on a certain trigger like :

    • A certain amount of time on page
    • A certain distance scrolling down the page
    • If someone is a new or returning visitor

    Depending on the form software you use, you may be able to add conditional logic.

    Start tracking your form conversions

    Form optimisation is all about conversion rate optimisation.

    If you want to increase your conversions and generate more revenue, then you need to test out different forms and know how to optimise them.

    With Matomo, you can easily track, manage, and A/B test your forms so you can improve your conversions. 

    Try Matomo free for 21 days. No credit card required.

  • RTMP server with OpenCV (python)

    12 février 2024, par Overnout

    I'm trying to process an RTMP stream in Python, using OpenCV2 but I'm not able to get OpenCV to capture it (i.e. act as RTMP server).

    


    I can run FFmpeg/FFplay from the command line and receive the stream successfully.
What could cause OpenCV to fail opening the stream in listening mode ?

    


    Here is my code :

    


    import cv2

cap = cv2.VideoCapture("rtmp://0.0.0.0:8000/live", cv2.CAP_FFMPEG)

if not cap.isOpened():
    print("Cannot open video source")
    exit()


    


    And the output :

    


    [tcp @ 00000192c490d640] Connection to tcp://0.0.0.0:8000 failed: Error number -138 occurred
[rtmp @ 00000192c490d580] Cannot open connection tcp://0.0.0.0:8000 
Cannot open video source


    


    edit2 : Output with debug logging turned on :

    


    output of the python script with debug logging on:
[DEBUG:0@0.017] global videoio_registry.cpp:218 cv::`anonymous-namespace'::VideoBackendRegistry::VideoBackendRegistry VIDEOIO: Builtin backends(9): FFMPEG(1000); GSTREAMER(990); INTEL_MFX(980); MSMF(970); DSHOW(960); CV_IMAGES(950); CV_MJPEG(940); UEYE(930); OBSENSOR(920)
[DEBUG:0@0.026] global videoio_registry.cpp:242 cv::`anonymous-namespace'::VideoBackendRegistry::VideoBackendRegistry VIDEOIO: Available backends(9): FFMPEG(1000); GSTREAMER(990); INTEL_MFX(980); MSMF(970); DSHOW(960); CV_IMAGES(950); CV_MJPEG(940); UEYE(930); OBSENSOR(920)
[ INFO:0@0.031] global videoio_registry.cpp:244 cv::`anonymous-namespace'::VideoBackendRegistry::VideoBackendRegistry VIDEOIO: Enabled backends(9, sorted by priority): FFMPEG(1000); GSTREAMER(990); INTEL_MFX(980); MSMF(970); DSHOW(960); CV_IMAGES(950); CV_MJPEG(940); UEYE(930); OBSENSOR(920)
[ WARN:0@0.037] global cap.cpp:132 cv::VideoCapture::open VIDEOIO(FFMPEG): trying capture filename='rtmp://192.168.254.101:8000/live' ...
[ INFO:0@0.040] global backend_plugin.cpp:383 cv::impl::getPluginCandidates Found 2 plugin(s) for FFMPEG
[ INFO:0@0.043] global plugin_loader.impl.hpp:67 cv::plugin::impl::DynamicLib::libraryLoad load C:\Users\me\src\opencv\.venv\Lib\site-packages\cv2\opencv_videoio_ffmpeg490_64.dll => OK
[ INFO:0@0.047] global backend_plugin.cpp:50 cv::impl::PluginBackend::initCaptureAPI Found entry: 'opencv_videoio_capture_plugin_init_v1'
[ INFO:0@0.049] global backend_plugin.cpp:169 cv::impl::PluginBackend::checkCompatibility Video I/O: initialized 'FFmpeg OpenCV Video I/O Capture plugin': built with OpenCV 4.9 (ABI/API = 1/1), current OpenCV version is '4.9.0' (ABI/API = 1/1)
[ INFO:0@0.055] global backend_plugin.cpp:69 cv::impl::PluginBackend::initCaptureAPI Video I/O: plugin is ready to use 'FFmpeg OpenCV Video I/O Capture plugin'
[ INFO:0@0.058] global backend_plugin.cpp:84 cv::impl::PluginBackend::initWriterAPI Found entry: 'opencv_videoio_writer_plugin_init_v1'
[ INFO:0@0.061] global backend_plugin.cpp:169 cv::impl::PluginBackend::checkCompatibility Video I/O: initialized 'FFmpeg OpenCV Video I/O Writer plugin': built with OpenCV 4.9 (ABI/API = 1/1), current OpenCV version is '4.9.0' (ABI/API = 1/1)
[ INFO:0@0.065] global backend_plugin.cpp:103 cv::impl::PluginBackend::initWriterAPI Video I/O: plugin is ready to use 'FFmpeg OpenCV Video I/O Writer plugin'
[tcp @ 00000266b2f0d0c0] Connection to tcp://192.168.254.101:8000 failed: Error number -138 occurred
[rtmp @ 00000266b2f0cfc0] Cannot open connection tcp://192.168.254.101:8000
[ WARN:0@5.630] global cap.cpp:155 cv::VideoCapture::open VIDEOIO(FFMPEG): can't create capture
[DEBUG:0@5.632] global cap.cpp:225 cv::VideoCapture::open VIDEOIO: choosen backend does not work or wrong. Please make sure that your computer support chosen backend and OpenCV built with right flags.
Cannot open video source
[ INFO:1@5.661] global plugin_loader.impl.hpp:74 cv::plugin::impl::DynamicLib::libraryRelease unload C:\Users\me\src\opencv\.venv\Lib\site-packages\cv2\opencv_videoio_ffmpeg490_64.dll


    


    Here is the output of cv2.getBuildInformation()

    


    General configuration for OpenCV 4.9.0 =====================================
  Version control:               4.9.0

  Platform:
    Timestamp:                   2023-12-31T11:21:12Z
    Host:                        Windows 10.0.17763 AMD64
    CMake:                       3.24.2
    CMake generator:             Visual Studio 14 2015
    CMake build tool:            MSBuild.exe
    MSVC:                        1900
    Configuration:               Debug Release

  CPU/HW features:
    Baseline:                    SSE SSE2 SSE3
      requested:                 SSE3
    Dispatched code generation:  SSE4_1 SSE4_2 FP16 AVX AVX2
      requested:                 SSE4_1 SSE4_2 AVX FP16 AVX2 AVX512_SKX
      SSE4_1 (16 files):         + SSSE3 SSE4_1
      SSE4_2 (1 files):          + SSSE3 SSE4_1 POPCNT SSE4_2
      FP16 (0 files):            + SSSE3 SSE4_1 POPCNT SSE4_2 FP16 AVX
      AVX (8 files):             + SSSE3 SSE4_1 POPCNT SSE4_2 AVX
      AVX2 (36 files):           + SSSE3 SSE4_1 POPCNT SSE4_2 FP16 FMA3 AVX AVX2

  C/C++:
    Built as dynamic libs?:      NO
    C++ standard:                11
    C++ Compiler:                C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/x86_amd64/cl.exe  (ver 19.0.24247.2)
    C++ flags (Release):         /DWIN32 /D_WINDOWS /W4 /GR  /D _CRT_SECURE_NO_DEPRECATE /D _CRT_NONSTDC_NO_DEPRECATE /D _SCL_SECURE_NO_WARNINGS /Gy /bigobj /Oi  /fp:precise     /EHa /wd4127 /wd4251 /wd4324 /wd4275 /wd4512 /wd4589 /wd4819 /MP  /O2 /Ob2 /DNDEBUG 
    C++ flags (Debug):           /DWIN32 /D_WINDOWS /W4 /GR  /D _CRT_SECURE_NO_DEPRECATE /D _CRT_NONSTDC_NO_DEPRECATE /D _SCL_SECURE_NO_WARNINGS /Gy /bigobj /Oi  /fp:precise     /EHa /wd4127 /wd4251 /wd4324 /wd4275 /wd4512 /wd4589 /wd4819 /MP  /Zi /Ob0 /Od /RTC1 
    C Compiler:                  C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/x86_amd64/cl.exe
    C flags (Release):           /DWIN32 /D_WINDOWS /W3  /D _CRT_SECURE_NO_DEPRECATE /D _CRT_NONSTDC_NO_DEPRECATE /D _SCL_SECURE_NO_WARNINGS /Gy /bigobj /Oi  /fp:precise     /MP   /O2 /Ob2 /DNDEBUG 
    C flags (Debug):             /DWIN32 /D_WINDOWS /W3  /D _CRT_SECURE_NO_DEPRECATE /D _CRT_NONSTDC_NO_DEPRECATE /D _SCL_SECURE_NO_WARNINGS /Gy /bigobj /Oi  /fp:precise     /MP /Zi /Ob0 /Od /RTC1 
    Linker flags (Release):      /machine:x64  /NODEFAULTLIB:atlthunk.lib /INCREMENTAL:NO  /NODEFAULTLIB:libcmtd.lib /NODEFAULTLIB:libcpmtd.lib /NODEFAULTLIB:msvcrtd.lib
    Linker flags (Debug):        /machine:x64  /NODEFAULTLIB:atlthunk.lib /debug /INCREMENTAL  /NODEFAULTLIB:libcmt.lib /NODEFAULTLIB:libcpmt.lib /NODEFAULTLIB:msvcrt.lib
    ccache:                      NO
    Precompiled headers:         YES
    Extra dependencies:          wsock32 comctl32 gdi32 ole32 setupapi ws2_32
    3rdparty dependencies:       libprotobuf ade ittnotify libjpeg-turbo libwebp libpng libtiff libopenjp2 IlmImf zlib ippiw ippicv

  OpenCV modules:
    To be built:                 calib3d core dnn features2d flann gapi highgui imgcodecs imgproc ml objdetect photo python3 stitching video videoio
    Disabled:                    java world
    Disabled by dependency:      -
    Unavailable:                 python2 ts
    Applications:                -
    Documentation:               NO
    Non-free algorithms:         NO

  Windows RT support:            NO

  GUI:                           WIN32UI
    Win32 UI:                    YES
    VTK support:                 NO

  Media I/O: 
    ZLib:                        build (ver 1.3)
    JPEG:                        build-libjpeg-turbo (ver 2.1.3-62)
      SIMD Support Request:      YES
      SIMD Support:              NO
    WEBP:                        build (ver encoder: 0x020f)
    PNG:                         build (ver 1.6.37)
    TIFF:                        build (ver 42 - 4.2.0)
    JPEG 2000:                   build (ver 2.5.0)
    OpenEXR:                     build (ver 2.3.0)
    HDR:                         YES
    SUNRASTER:                   YES
    PXM:                         YES
    PFM:                         YES

  Video I/O:
    DC1394:                      NO
    FFMPEG:                      YES (prebuilt binaries)
      avcodec:                   YES (58.134.100)
      avformat:                  YES (58.76.100)
      avutil:                    YES (56.70.100)
      swscale:                   YES (5.9.100)
      avresample:                YES (4.0.0)
    GStreamer:                   NO
    DirectShow:                  YES
    Media Foundation:            YES
      DXVA:                      YES

  Parallel framework:            Concurrency

  Trace:                         YES (with Intel ITT)

  Other third-party libraries:
    Intel IPP:                   2021.11.0 [2021.11.0]
           at:                   D:/a/opencv-python/opencv-python/_skbuild/win-amd64-3.7/cmake-build/3rdparty/ippicv/ippicv_win/icv
    Intel IPP IW:                sources (2021.11.0)
              at:                D:/a/opencv-python/opencv-python/_skbuild/win-amd64-3.7/cmake-build/3rdparty/ippicv/ippicv_win/iw
    Lapack:                      NO
    Eigen:                       NO
    Custom HAL:                  NO
    Protobuf:                    build (3.19.1)
    Flatbuffers:                 builtin/3rdparty (23.5.9)

  OpenCL:                        YES (NVD3D11)
    Include path:                D:/a/opencv-python/opencv-python/opencv/3rdparty/include/opencl/1.2
    Link libraries:              Dynamic load

  Python 3:
    Interpreter:                 C:/hostedtoolcache/windows/Python/3.7.9/x64/python.exe (ver 3.7.9)
    Libraries:                   C:/hostedtoolcache/windows/Python/3.7.9/x64/libs/python37.lib (ver 3.7.9)
    numpy:                       C:/hostedtoolcache/windows/Python/3.7.9/x64/lib/site-packages/numpy/core/include (ver 1.17.0)
    install path:                python/cv2/python-3

  Python (for build):            C:\hostedtoolcache\windows\Python\3.7.9\x64\python.exe

  Java:                          
    ant:                         NO
    Java:                        YES (ver 1.8.0.392)
    JNI:                         C:/hostedtoolcache/windows/Java_Temurin-Hotspot_jdk/8.0.392-8/x64/include C:/hostedtoolcache/windows/Java_Temurin-Hotspot_jdk/8.0.392-8/x64/include/win32 C:/hostedtoolcache/windows/Java_Temurin-Hotspot_jdk/8.0.392-8/x64/include
    Java wrappers:               NO
    Java tests:                  NO

  Install to:                    D:/a/opencv-python/opencv-python/_skbuild/win-amd64-3.7/cmake-install
-----------------------------------------------------------------


    


    edit : Receiving the stream with ffplay from command line :

    


    >ffplay.exe -i "rtmp://0.0.0.0:8000/live"  -listen 1 -f flv
ffplay version 2024-02-04-git-7375a6ca7b-full_build-www.gyan.dev Copyright (c) 2003-2024 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. 36.101 / 58. 36.101
  libavcodec     60. 38.100 / 60. 38.100
  libavformat    60. 20.100 / 60. 20.100
  libavdevice    60.  4.100 / 60.  4.100
  libavfilter     9. 17.100 /  9. 17.100
  libswscale      7.  6.100 /  7.  6.100
  libswresample   4. 13.100 /  4. 13.100
  libpostproc    57.  4.100 / 57.  4.100
[rtmp @ 0000018a564ed340] Unexpected stream , expecting livef=0/0
    Last message repeated 1 times
Input #0, flv, from 'rtmp://0.0.0.0:8000/live':KB sq=    0B f=0/0
  Metadata:
    fileSize        : 0
    audiochannels   : 2
    2.1             : false
    3.1             : false
    4.0             : false
    4.1             : false
    5.1             : false
    7.1             : false
    encoder         : obs-output module (libobs version 30.0.2)
  Duration: 00:00:00.00, start: 0.000000, bitrate: N/A
  Stream #0:0: Audio: aac (LC), 48000 Hz, stereo, fltp, 163 kb/s
  Stream #0:1: Video: h264 (Constrained Baseline), yuv420p(tv, bt709, progressive), 1280x720 [SAR 1:1 DAR 16:9], 2560 kb/s, 30 fps, 30 tbr, 1k tbn
   7.54 A-V: -0.024 fd=  18 aq=   24KB vq=  498KB sq=    0B f=0/0


    


  • What is White Label Analytics ? Everything You Need to Know

    6 février 2024, par Erin

    Reports are a core part of a marketing agency’s offering. It’s how you build trust with clients by highlighting your efforts and demonstrating your results. 

    But all too often, those reports deliver a jarring and incohesive experience. The culprit ? The logos, colours and names of third-party brands your agency uses to deliver work and create the reports. 

    Luckily, there’s a way to make sure your reports elevate your agency’s stature ; not undermine it. 

    By white labelling your tools, you can deliver a clear and cohesive brand experience — one that strengthens the client relationship rather than diminishing it. 

    In this article, we explain what white label analytics tools are, why it’s important to white label your analytics solution and how you can do it using Matomo. 

    What is white label analytics ?

    White labelling is the process of redesigning a product or service using your company’s brand. The term comes from the act of putting a white label on a product that covers the original branding and allows the reseller to personalise the product.

    White label analytics, then, is a way to customise your analytics software with your agency’s logo and colours. When you white label your analytics, you ensure your reports, dashboards and interface provide a consistent and familiar user experience.

    White label analytics example screenshot from Matomo

    The alternative is to provide your clients with an analytics report containing the logo and branding of your analytics software provider — whether that’s Google Analytics, Matomo, or another tool. 

    For some clients, it can create a confusing experience that takes attention away from your agency’s results.

    Why white label analytics is important

    There are plenty of reasons to white label your analytics tool, from improving your client’s experience to generating additional revenue. Here are four of the most important benefits to know :

    Improve the client experience

    You want your clients to have a seamless user experience with your agency’s brand, whether they visit your website, log into their client portal, or read one of your reports. 

    By white labelling your analytics platform, you can give your clients a visually appealing experience that stays in line with the rest of your branding and doesn’t leave them confused about who they are interacting with or which company is providing the service they pay for. 

    This is especially important if your agency uses other third-party tools like a client portal or productivity platform that also allows for custom branding. 

    Strengthen client relationships

    When you use white labelling to remove solution providers’ logos, you ensure your brand gets all of the credit for the hard work you’ve been doing. This can strengthen the agency-client relationship and reaffirm the importance of your agency. 

    But, white labelling allows you to tell a better story through your reports and increases the perceived value you offer. There are no other brands, logos, or names to confuse the narrative or detract from your key points — or to stop the client from understanding just how much value you provide. 

    Save time and increase productivity 

    White labelling your analytics platform can save your team a significant amount of time when creating client reports. 

    There’s no need to carefully screenshot graphs to add them to your own branded report. You can simply email clients a report using your white labelled analytics platform, assuring them of a seamlessly branded experience.

    The upshot is that your team can spend more time on billable work, improving the value they deliver to existing clients or opening up capacity to take on even more work. 

    Increase monetisation opportunities

    Whether you are an agency or consultant, white labelling an analytics solution gives you the opportunity to package and sell analytics as part of your own services. This can open up new revenue streams, help you to diversify your income, and reach a wider audience.

    The beauty of a white label offering is that there is no allusion to the company providing the underlying service.

    The most important elements of an analytics platform to white label 

    A white label analytics solution should offer a broad range of customisation options that range from surface-level branding to functional elements like tracking codes. 

    Below we take a look at the top components you should be able to customise with your chosen platform. 

    Logo and Favicon

    The logo is the first thing clients will see when they open up their analytics platform or look at your reports. It should make your services instantly recognisable, which is why it’s so jarring when clients read a report with another company’s brand slapped on every chart. 

    This should be the very first thing you change since it will be on almost every page and report your client views. Don’t stop there, however. If you send clients web-based reports, you’ll also want to change the platform’s favicon — the small logo you see next to your website in a browser. 

    Customising both your logo and favicon is easy with Matomo. 

    Just head to Administration, then General Settings and click Use a custom Logo under Brand settings.

    Matomo white label custom branding settings

    Upload your brand, click Save, and it will automatically populate your brand in place of the Matomo logo across the platform, just like in the image above.

    Brand name

    Most analytics platforms will mention their brand names repeatedly across the site, so it’s important to change these, too.

    Otherwise, you risk clients reading your analytics reports in detail or playing around with your platform’s settings and getting confused when another seemingly unrelated name keeps popping up. 

    Again, this is easily done with Matomo’s White Label plugin. 

    Head to Administration, then General Settings. Scroll to the bottom of the page to find WhiteLabel settings.

    Enter your brand or product name in the first box and click Save

    White label the Matomo platform with your brand name.

    Just like your logo, this will replace every instance of Matomo’s brand name with your own.

    Brand colours

    Changing your analytics platform’s colours to match your own is almost as important as swapping out the logo. 

    Failure to do so could mean the charts and graphs you add to your client reports could cause confusion. 

    You can also use Matomo’s WhiteLabel settings to change the platform’s background and font colours. 

    Just enter a new header background and font colour using hexadecimal values.

    Matomo white label brand colour settings.

    This change will also apply to automated email reports. 

    Custom tracking

    Tracking requests and links are an overlooked element of analytics when it comes to white labelling. Most people wouldn’t think twice about them, but they are an easy way for someone in the know to identify which platform you are using. 

    With Matomo’s White Label plugin, it’s possible to customise every request Matomo makes to your clients’ websites. 

    If left unbranded, tracking requests contain the following references : matomo.js and matomo.php. 

    By clicking the Whitelabel tracking endpoint box on the WhiteLabel settings page, those references will be replaced with js/tracker.js and js/tracker.php

    You’ll need to update your tracking code to reflect these changes, otherwise, requests will still contain Matomo branding. 

    Try Matomo for Free

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

    No credit card required

    Links

    Finally, you’ll want to remove any links to any additional content offered by the analytics company. These are usually included to improve the user experience, but they are best removed if you are letting clients access your platform. 

    With Matomo, you can remove all links by clicking the relevant box in WhiteLabel settings. 

    You can also use the Show Marketplace only to Super Users checkbox to limit the visibility of Matomo’s Marketplace to everyone bar Super Users.

    Can you white label Google Analytics ?

    In a word : no. 

    Google Analytics might be the most popular analytics platform, but it comes up short if you want to customise its appearance. 

    This can be a particular problem for agencies that need to stand out from competitors offering the same generic reports. You can add more context, detail and graphs to your analytics reports, of course. But you’ll never be able to create completely custom, brand-cohesive reports using Google Analytics. 

    3 analytics platforms you can white label

    While you can’t white label Google Analytics, there are several web analytics providers that do offer a white labelling service. Here are three of the best :

    Matomo

    As you’ve already seen, Matomo is the ideal web analytics platform if you want to let your own brand shine through. Matomo lets you personalise the entire dashboard and all of your reports. That includes :

    • Adding your brand logo and favicon
    • Changing the font and background colours 
    • Removing third-party links
    • Tracking using custom URLs 
    • Develop your own custom theme

    Matomo offers a 21-day free trial (no credit card required). If you want to get remove the Matomo branding, you need the White Label plugin, which starts at just $179 per year after a free trial.

    Try Matomo for Free

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

    No credit card required

    Clicky

    Clicky is a simple, privacy-focused web analytics platform with a white label offering. Like Matomo, you can add your logo and change the platform’s colours. 

    Clicky offers a seven-day free trial and charges a $99 setup fee, with prices starting from $49 and rising to $399. 

    Plausible 

    Plausible is another privacy-focused Google Analytics alternative that offers white labelling. The difference here is that it’s pretty complex to set up. 

    Rather than customising Plausible’s platform, for instance, you need to embed its dashboard into your own user interface. If you want to create your own custom dashboard, you’ll need to use an API. 

    Plausible offers a 30-day free trial.

    Leverage white label analytics today with Matomo

    Don’t put up with confusing unbranded clients a moment longer. White label your analytics platform so the next time you sit down to share insights with your clients, they’ll only see one brand : yours.

    Matomo makes it quick and easy to customise the look of your analytics platform and all of the reports you generate. If you already use Matomo, try the White Label plugin free for 30 days.

    If not, try Matomo with a free 21-day trial. No credit card required.