Recherche avancée

Sur d’autres sites (5456)

• SEO for Financial Services : The Ultimate Guide

  26 juin 2024, par Erin

  You know that having a digital marketing strategy is crucial for helping your financial services business capture the attention and trust of potential customers and thrive in an increasingly competitive digital landscape.

  The question is — what’s the best way to go about improving your ranking in SERPs and driving organic traffic to your website ? 

  That’s where SEO strategies for financial services come into play. 

  This article will cover everything your company needs to know about SEO for financial services — from the unique challenges you’ll face to the proven tips and strategies you can implement to boost your ranking in SERPs. 

  What is SEO for financial services ? 

  SEO — short for search engine optimisation — refers to optimising your content and website for search engines, particularly Google. 

  The main goal of an SEO strategy is to make your site search-engine-friendly, show that you’re a trusted source and increase the likelihood of appearing in SERPs when potential customers look up relevant keywords — ultimately driving organic visibility and traffic. 

  Now, when it comes to evaluating the success of your financial services SEO strategy, there are certain key performance indicators (KPIs) you should keep track of — including : 

  • SEO ranking, or the position your web pages show up in SERPs for specific search terms (the terms and phrases identified during keyword research) 
  • SEO Score, which shows a website’s overall SEO health and indicates how well it will rank in SERPs
  • Impressions, or the number of times users saw your pages when they looked up relevant search terms 
  • Organic traffic, or the number of people that visit your website via search engines
  • Engagement metrics, such as time on page, pages per session, and bounce rate 
  • Conversion rates from website traffic, including both “hard” conversions (lead generation and purchases) and “soft” conversions (such as newsletter subscriptions) 

  It’s important to note that the financial services industry is incredibly competitive — especially given the large-scale digital transformations in the financial sector and the rise of fintech companies. 

  According to a 2022 report, the global market for financial services was valued at $25.51 trillion. Moreover, it’s expected to grow at a compound annual growth rate of 9.7%, reaching $58.69 trillion by 2031.

  Importance and challenges of financial services SEO 

  The financial services industry is changing rapidly, mainly driven by globalisation, innovation, shifting economies, and compliance risks. It’s crucial for financial service companies to develop effective SEO strategies that align with the opportunities and challenges unique to this sector. 

  Certain benefits of a well-executed SEO strategy, namely, better search engine rankings, driving more search traffic, delivering a better user experience, and maximising ROI and promoting business growth, are “universal.” 

  

  Financial services SEO efforts can provide a number of benefits. It can help you : 

  • Improve lead generation and customer acquisition ; the more search traffic you get, the higher the chances of converting visitors into potential clients 
  • Build a strong online presence and brand awareness, which comes as a result of increased visibility in organic search results and reaching a wider audience 
  • Increase your credibility and authority within the industry, primarily through high-quality content that shows your expertise and backlinks from authoritative websites 
  • Gain a competitive edge by analysing and outranking your main competitors 

  That said, financial services companies face some unique challenges :

  High competition : The digital arena for financial services is highly competitive, with numerous companies vying for the same business.

  YMYL (Your Money or Your Life) content : Google’s YMYL framework places higher scrutiny on financial content, demanding higher standards for experience, expertise, authoritativeness, and trustworthiness. We’ll cover this topic in greater detail shortly.

  Regulatory changes and compliance : The financial services sector is characterised by constant regulatory changes and new compliance requirements that businesses must navigate. Sometimes this makes it difficult to gather insights and market to your audience. 

  As a privacy-fist, compliant web analytics solution Matomo can provide valuable insights to support your SEO efforts. Matomo ensures compliance with privacy laws — including GDPR, CCPA and more — and provides 20-40% more comprehensive data than Google Analytics.

  Try Matomo for Free

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

  Start for free

  No credit card required

  8 proven strategies for implementing SEO for financial services 

  SEO for financial services involves a wide range of strategies — including keyword optimisation, technical SEO, content marketing, link building and other off-page SEO activities — that can help your website rank higher in SERPs. 

  Of course, it’s not just about better search rankings. It’s about attracting the right search traffic to your website — potential clients interested in your financial services.

  Here are some proven financial services SEO strategies you should implement : 

  1. Build trust and topical authority 

  Financial services content typically covers more complex topics that could impact the reader’s financial stability and well-being — or, as Google calls them, “Your Money or Your Life” topics (YMYL). As such, it’s subject to much stricter quality standards. 

  To improve your YMYL content, you’ll need to apply the E-E-A-T framework — short for “Experience, Expertise, Authority, and Trust”. 

  This is a key part of Google’s search rater guidelines for evaluating a website’s quality and credibility. 

  The E-E-A-T standards become even more relevant to financial topics such as investment strategies, financial advice, taxes, and retirement planning. 

  In that sense, the overarching goal of your content strategy should be to build customer trust by demonstrating real expertise and topical authority through in-depth educational content. 

  2. Earn reputable external links through link-building 

  You also need to monitor your off-page SEO—factors outside your website that can’t be directly controlled but can still build trust and contribute to better ranking in SERPs. 

  These include everything from social media engagement and unlinked brand mentions in blog posts, news articles, user reviews and social media discussions — to inbound links from other reputable websites in the finance industry.

  That brings us to high-quality backlinks as a significant factor for YMYL content that can improve your financial services website’s SEO performance : 

  Earning external links can improve your domain authority and reinforce your brand’s position as a reliable source in the financial services niche — which, in turn, can contribute to better search engine rankings and drive more website traffic. 

  Here are a few link-building strategies you can try : 

  • Use tools like Ahrefs and Semrush to look for reputable websites and then request for them to link to your site
  • Demonstrate your expertise and get backlinks from reputable media outlets through Help a Reporter Out (HARO) 
  • Reach out to authoritative websites that mention your company without linking to you directly and ask them to include a link to your websit

  3. Conduct an SEO audit 

  An SEO audit is a key step in developing and implementing a successful financial SEO strategy. It sets the foundation for all your future efforts — and allows you to measure progress further down the line. 

  You’ll need to perform a comprehensive SEO audit, covering both the existing content and technical aspects of your website — including : 

  • Indexing issues
  • Internal linking and site architecture 
  • Duplicate content 
  • Backlink profile 
  • Broken links 
  • Page titles and metadata 

  It’s possible to do this manually, third-party tools will allow you to dig deeper and speed up the process. Ahrefs and Screaming Frog — to name a few — can help you evaluate your website’s overall health and structure. And, with a web analytics platform like Matomo you can easily measure the success of your SEO efforts.

  But this shouldn’t be a one-time thing ; be sure to perform audits regularly — ideally every six months. 

  4. Understand your target audience

  You can’t create helpful content without learning about your customers’ needs, pain points and preferences. 

  For example, a financial service provider focusing on individuals nearing retirement would prioritise content that educates on retirement planning strategies, investment options for seniors, and tax-efficient withdrawal strategies, aiming to guide clients through the transition from saving to managing retirement funds effectively.

  In contrast, a provider targeting small business owners would emphasise content related to small business loans, funding options, and financial management advice tailored to entrepreneurs seeking to expand their businesses and navigate financial challenges effectively.

  So, before you dive into keyword research and content creation, ensure you have a deep understanding of your target audience. 

  Identifying different audience categories and developing detailed customer personas for each segment is crucial for creating content that resonates with them and aligns with their search intent. 

  Matomo’s Segmentation tool can be of huge help here. It allows you to divide your audience into smaller groups based on factors like demographics and website interactions : 

  

  In addition to that, you can : 

  • Engage with your frontline teams that interact directly with clients to gain deeper insights into prospects’ needs and concerns
  • Track social media channels and other online discussions related to the financial world and your audience
  • Gather qualitative insights from your site visitors through the Matomo Surveys plugin (questions like “What financial services are you most interested in ?” or “Are there any specific financial topics you would like us to cover in more detail ?” will help you understand your visitors better)
  • Watch out for financial trends and developments that could directly impact your audience’s needs and preferences 

  5. Identify new opportunities through keyword research 

  Comprehensive keyword research can help you identify key search terms — specific phrases that potential customers may use when looking up things related to their finances. 

  It’s best to start with a brainstorming session and assemble a list of relevant topics and core keywords. Once you have an initial list, use tools like Ahrefs and Semrush to get more keyword ideas based on your seed keywords, including : 

  • More specific long-tail keywords — and often less competitive — indicate a clearer intent to convert. For example :

  • • “low-risk investment options for retirees”
    • “financial planning for freelancers”
    • “small business loan requirements”

  • Keywords that your competitors already rank for. For instance :

  • • If a competing investment firm ranks for “best investment strategies for beginners,” targeting similar keywords can attract novice investors.
    • A competitor’s high ranking for “life insurance quotes online” suggests potential to optimise your own content around similar terms.
  • Location-specific keywords (if you have physical store locations)

  Google Search Console can provide information about the search terms you’re already ranking for — including underperforming content that may benefit from further optimisation. If you want deeper SEO insights, you can import your search keywords into Matomo. 

  While you’re at it, try Matomo’s Site Search feature, too. It will show you the exact terms and phrases visitors enter when using your website’s search bar — and you can use that information to find more content opportunities.

  Try Matomo for Free

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

  Start for free

  No credit card required

  Of course, not all keywords are equal — and it would be impossible to target them all. Instead, prioritise keywords based on two factors : 

  • Search volume, which indicates the “popularity” of a particular query
  • Keyword difficulty, which indicates how hard it’ll be to rank for a specific term, depending on domain authority, search volume and competition 

  

  6. Find your main organic competitors 

  Besides performing an SEO audit, finding your core keywords, and researching your target market, competitor analysis is another crucial aspect of SEO for finance companies. 

  Before you start, it’s important to differentiate between your main organic search competitors and your direct industry competitors : 

  You’ll always have direct competitors — other financial services brands offering similar products and services and targeting the same audience as you.

  However, regarding search results, your financial services business won’t be in a “bubble” specifically reserved for the financial industry. Depending on the specific search queries — and the search intent behind them — SERPs could feature a wider range of online content, from niche finance blogs to news websites, and huge financial publications.

  Even if another company doesn’t offer the same services, they’re an organic competitor if you’re both ranking for the same keywords. 

  Once you determine who your main organic competitors are, you can analyse their websites to : 

  • Check how they’re getting search traffic 
  • See which types of content they’re publishing 
  • Find and fill in any potential content gaps 
  • Assess the quality of their backlink profile 
  • See if they currently have any featured snippets

  7. Consider local SEO

  According to a 2023 survey, 21% of US-based consumers report using the internet to look up local businesses daily, while another 32% do so multiple times a week. 

  Local SEO is worth investing in as a financial service provider, especially with physical locations. Prospective clients will typically look up nearby financial services when they need additional information or are ready to engage in financial planning, investment, or other financial activities.

  Here are a few suggestions on how to optimise your site for local searches : 

  • Create listings on online business directories, like Google Business Profile (previously known as Google My Business)
  • If your financial service company operates in more than one physical location, be sure to create a separate Google Business Profile for each one 
  • Identify location-specific keywords that will help you rank in local SERPs
  • Make sure that your name, address, and phone number (NAP) citations are correct and consistent 
  • Leverage positive customer reviews and testimonials as social proof

  8. Optimise technical aspects of your website 

  Technical SEO — which primarily deals with the website’s underlying structure — is another crucial factor that financial services brands must monitor. 

  It’s an umbrella term that covers a wide range of elements, including : 

  • Site speed 
  • Indexing issues 
  • Broken links, orphaned pages, improper redirects 
  • On-page optimisation 
  • Mobile responsiveness

  In 2020, Google introduced Core Web Vitals, a set of metrics that measure web page performance in three key areas — loading speed, responsiveness and visual stability. 

  Given that they’re now a part of Google’s core ranking systems, you should consider using Matomo’s SEO Web Vitals feature to monitor these crucial metrics. Here’s why :

  When technical aspects of your website — namely, site speed and mobile responsiveness — are properly optimised, you can deliver a better user experience. That’s what Google seeks to reward. 

  Plus, it can be a critical brand differentiator for your business. 

  Conclusion 

  Investing in SEO for financial services is crucial for boosting online visibility and driving organic traffic and business growth. However, one thing to keep in mind is that SEO efforts shouldn’t be a one-time thing : 

  SEO is an ongoing process, and it will take time to establish your company as a trustworthy source and see real results. 

  You can start building that trust by using a web analytics platform that offers crucial insights for improving your website’s ranking in SERPs and maintains full compliance with GDPR and other privacy regulations. 

  That’s why Matomo is trusted by more than 1 million websites around the globe. As an ethical alternative to Google Analytics that doesn’t rely on data sampling, Matomo is not only easy to use but more accurate, too — providing 20-40% more data compared to GA4. 

  Sign up for a 21-day free trial and see how Matomo can support your financial services SEO strategy. No credit card required.

  Try Matomo for Free

  21 day free trial. No credit card required.

  
  

  Your email address
  

  Your website address
  

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

  Choose your analytics subdomain
  

  .matomo.cloud

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

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

  Start improving your websites now

  

• FFmpeg Could not write header (incorrect codec parameters ?) : Invalid data found when processing input [closed]

  14 juillet 2024, par cookie

  The command

  


  ffmpeg -v verbose -i in.mkv -c copy -y out.mkv


  


  produces the following error :

  


  ffmpeg version 7.0.1-full_build-www.gyan.dev Copyright (c) 2000-2024 the FFmpeg developers
  built with gcc 13.2.0 (Rev5, Built by MSYS2 project)
  configuration: --enable-gpl --enable-version3 --enable-static --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-libxevd --enable-libzvbi --enable-librav1e --enable-libsvtav1 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxeve --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-dxva2 --enable-d3d11va --enable-d3d12va --enable-ffnvcodec --enable-libvpl --enable-nvdec --enable-nvenc --enable-vaapi --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      59.  8.100 / 59.  8.100
  libavcodec     61.  3.100 / 61.  3.100
  libavformat    61.  1.100 / 61.  1.100
  libavdevice    61.  1.100 / 61.  1.100
  libavfilter    10.  1.100 / 10.  1.100
  libswscale      8.  1.100 /  8.  1.100
  libswresample   5.  1.100 /  5.  1.100
  libpostproc    58.  1.100 / 58.  1.100
[hevc @ 00000133b5bb5040] Invalid default display window
Input #0, matroska,webm, from 'in.mkv':
  Metadata:
    encoder         : libebml v1.3.0 + libmatroska v1.4.1
    creation_time   : 2015-03-20T14:07:27.000000Z
  Duration: 00:24:11.75, start: 0.000000, bitrate: 5185 kb/s
  Chapters:
    Chapter #0:0: start 0.000000, end 48.047000
      Metadata:
        title           : Chapter 01
    Chapter #0:1: start 48.047000, end 137.846000
      Metadata:
        title           : Chapter 02
    Chapter #0:2: start 137.846000, end 535.868000
      Metadata:
        title           : Chapter 03
    Chapter #0:3: start 535.868000, end 1330.871000
      Metadata:
        title           : Chapter 04
    Chapter #0:4: start 1330.871000, end 1420.877000
      Metadata:
        title           : Chapter 05
    Chapter #0:5: start 1420.877000, end 1451.741000
      Metadata:
        title           : Chapter 06
    Chapter #0:6: start 1451.741000, end 1451.745000
      Metadata:
        title           : Chapter 07
  Stream #0:0: Video: hevc (Main 10), 1 reference frame, yuv420p10le(tv, left), 1920x1080, SAR 1:1 DAR 16:9, 23.98 fps, 23.98 tbr, 1k tbn (default)
      Metadata:
        _STATISTICS_WRITING_APP: mkvmerge v7.0.0 ('Where We Going') 32bit built on Jun  9 2014 15:08:34
        _STATISTICS_WRITING_APP-eng: mkvmerge v7.0.0 ('Where We Going') 32bit built on Jun  9 2014 15:08:34
        _STATISTICS_WRITING_DATE_UTC: 2015-03-20 14:07:27
        _STATISTICS_WRITING_DATE_UTC-eng: 2015-03-20 14:07:27
        _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
        _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
        BPS             : 3754023
        BPS-eng         : 3754023
        DURATION        : 00:24:11.742000000
        DURATION-eng    : 00:24:11.742000000
        NUMBER_OF_FRAMES: 34807
        NUMBER_OF_FRAMES-eng: 34807
        NUMBER_OF_BYTES : 681234123
        NUMBER_OF_BYTES-eng: 681234123
  Stream #0:1(jpn): Audio: flac, 48000 Hz, stereo, s32 (24 bit) (default)
      Metadata:
        _STATISTICS_WRITING_APP: mkvmerge v7.0.0 ('Where We Going') 32bit built on Jun  9 2014 15:08:34
        _STATISTICS_WRITING_APP-eng: mkvmerge v7.0.0 ('Where We Going') 32bit built on Jun  9 2014 15:08:34
        _STATISTICS_WRITING_DATE_UTC: 2015-03-20 14:07:27
        _STATISTICS_WRITING_DATE_UTC-eng: 2015-03-20 14:07:27
        _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
        _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
        BPS             : 1429414
        BPS-eng         : 1429414
        DURATION        : 00:24:11.745000000
        DURATION-eng    : 00:24:11.745000000
        NUMBER_OF_FRAMES: 17013
        NUMBER_OF_FRAMES-eng: 17013
        NUMBER_OF_BYTES : 259393130
        NUMBER_OF_BYTES-eng: 259393130
[out#0/matroska @ 00000133b5bb5a40] No explicit maps, mapping streams automatically...
[vost#0:0/copy @ 00000133b5c2f580] Created video stream from input stream 0:0
[aost#0:1/copy @ 00000133b5bf1680] Created audio stream from input stream 0:1
Stream mapping:
  Stream #0:0 -> #0:0 (copy)
  Stream #0:1 -> #0:1 (copy)
[out#0/matroska @ 00000133b5bb5a40] Could not write header (incorrect codec parameters ?): Invalid data found when processing input
[AVIOContext @ 00000133b5c27940] Statistics: 291 bytes written, 0 seeks, 1 writeouts
[AVIOContext @ 00000133b5b97980] Statistics: 66432 bytes read, 2 seeks
Conversion failed!


  


  Originally, I was trying to add a subtitle to in.mkv, but I keep encountering this error. When I add the subtitle to another MKV file, it works fine, so I believe the problem lies with in.mkv.

  


  Troubleshooting

  


  Output only video stream produce the same error :

  


  ffmpeg -i in.mkv -map 0:v:0 -c copy out.mkv


  


  Output only audio stream works fine :

  


  ffmpeg -i in.mkv -map 0:a:0 -c copy out.mkv


  


  Output as mp4 got no error, but the output file is unplayable :

  


  ffmpeg -i in.mkv -c copy -strict -2 out.mp4


  


  Re-encoding works fine :

  


  ffmpeg -i in.mkv -c:v libx265 -c:a copy out.mkv


  


  How can I fix the video stream in in.mkv so that I can add a subtitle stream and remux the file without re-encoding the video ? Any insights or suggestions on handling this error would be greatly appreciated.

  


• 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