Recherche avancée

Sur d’autres sites (7728)

• A Quick Start Guide to the Payment Services Directive (PSD2)

  22 novembre 2024, par Daniel Crough — Banking and Financial Services, Privacy

  In 2023, there were 266.2 billion real-time payments indicating that the demand for secure transactions has never been higher. As we move towards a more open banking system, there are a host of new payment solutions that offer convenience and efficiency, but they also present new risks.

  The Payment Services Directive 2 (PSD2) is one of many regulations established to address these concerns. PSD2 is a European Union (EU) business initiative to offer smooth payment experiences while helping customers feel safe from online threats. 

  In this post, learn what PSD2 includes, how it improves security for online payments, and how Matomo supports banks and financial institutions with PSD2 compliance.

  What is PSD2 ? 

  PSD2 is an EU directive that aims to improve the security of electronic payments across the EU. It enforces strong customer authentication and allows third-party access to consumer accounts with explicit consent. 

  Its main objectives are :

  • Strengthening security and data privacy measures around digital payments.
  • Encouraging innovation by allowing third-party providers access to banking data.
  • Improving transparency with clear communication regarding fees, terms and conditions associated with payment services.
  • Establishing a framework for sharing customer data securely through APIs for PSD2 open banking.

  Rationale behind PSD2 

  PSD2’s primary purpose is to engineer a more integrated and efficient European payment market without compromising the security of online transactions. 

  The original directive aimed to standardise payment services across EU member states, but as technology evolved, an updated version was needed.

  PSD2 is mandatory for various entities within the European Economic Area (EEA), like :

  • Banks and credit institutions
  • Electronic money institutions or digital banks like Revolut
  • Card issuing and acquiring institutions
  • Fintech companies
  • Multi-national organisations operating in the EU

  PSD2 implementation timeline

  With several important milestones, PSD2 has reshaped how payment services work in Europe. Here’s a closer look at the pivotal events that paved the way for its launch.

  • 2002 : The banking industry creates the European Payments Council (EC), which drives the Single Euro Payments Area (SEPA) initiative to include non-cash payment instruments across European regions. 
  • 2007 : PSD1 goes into effect.
  • 2013 : EC proposes PSD2 to include protocols for upcoming payment services.
  • 2015 : The Council of European Union passes PSD2 and gives member states two years to incorporate it.
  • 2018 : PSD2 goes into effect. 
  • 2019 : The final deadline for all companies within the EU to comply with PSD2’s regulations and rules for strong customer authentication. 

  PSD2 : Key components 

  PSD2 introduces several key components. Let’s take a look at each one.

  Strong Customer Authentication (SCA)

  The Regulatory Technical Standards (RTS) under PSD2 outline specific requirements for SCA. 

  SCA requires multi-factor authentication for online transactions. When customers make a payment online, they need to verify their identity using at least two of the three following elements :

  • Knowledge : Something they know (like a password, a code or a secret answer)
  • Possession : Something they have (like their phone or card)
  • Inherence : Something they are (like biometrics — fingerprints or facial features)

  

  Before SCA, banks verified an individual’s identity only using a password. This dual verification allows only authorised users to complete transactions. SCA implementation reduces fraud and increases the security of electronic payments.

  SCA implementation varies for different payment methods. Debit and credit cards use the 3D Secure (3DS) protocol. E-wallets and other local payment measures often have their own SCA-compliant steps. 

  3DS is an extra step to authenticate a customer’s identity. Most European debit and credit card companies implement it. Also, in case of fraudulent chargebacks, the issuing bank becomes liable due to 3DS, not the business. 

  However, in SCA, certain transactions are exempt : 

  • Low-risk transactions : A transaction by an issuer or an acquirer whose fraud level is below a specific threshold. If the acquirer feels that a transaction is low risk, they can request to skip SCA. 
  • Low-value transactions : Transactions under €30.
  • Trusted beneficiaries : Trusted merchants customers choose to safelist.
  • Recurring payments : Recurring transactions for a fixed amount are exempt from SCA after the first transaction.

  Third-party payment service providers (TPPs) framework

  TPPs are entities authorised to access customer banking data and initiate payments. There are three types of TPPs :

  Account Information Service Providers (AISPs)

  AISPs are services that can view customers’ account details, but only with their permission. For example, a budgeting app might use AISP services to gather transaction data from a user’s bank account, helping them monitor expenses and oversee finances. 

  Payment Initiation Service Providers (PISPs)

  PISPs enable clients to initiate payments directly from their bank accounts, bypassing the need for conventional payment options such as debit or credit cards. After the customer makes a payment, PISPs immediately contact the merchant to ensure the user can access the online services or products they bought. 

  Card-Based Payment Instruments (CBPII)

  CBPIIs refer to services that issue payment cards linked to customer accounts. 

  Requirements for TPPs

  To operate effectively under PSD2, TPPs must meet several requirements :

  Consumer consent : Customers must explicitly authorise TPPs to retrieve their financial data. This way, users can control who can view their information and for what purpose.

  Security compliance : TPPs must follow SCA and secure communication guidelines to protect users from fraud and unauthorised access.

  API availability : Banks must make their Application Programming Interfaces (APIs) accessible and allow TPPs to connect securely with the bank’s systems. This availability helps in easy integration and lets TPPs access essential data. 

  Consumer protection methods

  PSD2 implements various consumer protection measures to increase trust and transparency between consumers and financial institutions. Here’s a closer look at some of these key methods :

  • Prohibition of unjustified fees : PSD2 requires banks to clearly communicate any additional charges or fees for international transfers or account maintenance. This ensures consumers are fully aware of the actual costs and charges.
  • Timely complaint resolution : PSD2 mandates that payment service providers (PSPs) have a straightforward complaint procedure. If a customer faces any problems, the provider must respond within 15 business days. This requirement encourages consumers to engage more confidently with financial services.
  • Refund in case of unauthorised payment : Customers are entitled to a full refund for payments made without their consent.
  • Surcharge ban : Additional charges on credit and debit card payments aren’t allowed. Businesses can’t impose extra fees on these payment methods, which increases customers’ purchasing power.

  Benefits of PSD2 

  Businesses — particularly those in banking, fintech, finserv, etc. — stand to benefit from PSD2 in several ways.

  Access to customer data

  With customer consent, banks can analyse spending patterns to develop tailored financial products that match customer needs, from personalised savings accounts to more relevant loan offerings.

  Innovation and cost benefits 

  PSD2 opened payment processing up to more market competition. New payment companies bring fresh approaches to banking services, making daily transactions more efficient while driving down processing fees across the sector.

  Also, banks now work alongside payment technology providers, combining their strengths to create better services. This collaboration brings faster payment options to businesses, helping them stay competitive while reducing operational costs.

  Improved customer trust and experience

  Due to PSD2 guidelines, modern systems handle transactions quickly without compromising the safety of payment data, creating a balanced approach to digital banking.

  

  Banking customers now have more control over their financial information. Clear processes allow consumers to view and adjust their financial preferences as needed.

  Strong security standards form the foundation of these new payment systems. Payment provider platforms must adhere to strict regulations and implement additional protection measures.

  Challenges in PSD2 compliance 

  What challenges can banks and financial institutions face regarding PSD2 compliance ? Let’s examine them. 

  Resource requirements

  For many businesses, the new requirements come with a high price tag. PSD2 requires banks and fintechs to build and update their systems so that other providers can access customer data safely. For example, they must develop APIs to allow TPPs to acquire customer data. 

  Many banks still use older systems that can’t meet PSD2’s added requirements. In addition to the cost of upgrades, complying with PSD2 requires banks to devote resources to training staff and monitoring compliance.

  The significant costs required to update legacy systems and IT infrastructure while keeping services running remain challenging.

  Risks and penalties

  Organisations that fail to comply with PSD2 regulations can face significant penalties.

  Additionally, the overlapping requirements of PSD2 and other regulations, such as the General Data Protection Regulation (GDPR), can create confusion. 

  Banks need clear agreements with TPPs about who’s responsible when things go wrong. This includes handling data breaches, preventing data misuse and protecting customer information. 

  Increased competition 

  Introducing new players in the financial ecosystem, such as AISPs and PISPs, creates competition. Banks must adapt their services to stay competitive while managing compliance costs.

  PSD2 aims to protect customers but the stronger authentication requirements can make banking less convenient. Banks must balance security with user experience. Focused time, effort and continuous monitoring are needed for businesses to stay compliant and competitive.

  How Matomo can help 

  Matomo gives banks and financial institutions complete control over their data through privacy-focused web analytics, keeping collected information internal rather than being used for marketing or other purposes. 

  Its advanced security setup includes access controls, audit logs, SSL encryption, single sign-on and two-factor authentication. This creates a secure environment where sensitive data remains accessible only to authorised staff.

  While prioritizing privacy, Matomo provides tools to understand user flow and customer segments, such as session recordings, heatmaps and A/B testing.

  Financial institutions particularly benefit from several key features : 

  • Tools for obtaining explicit consent before processing personal data like this Do Not Track preference
  • Insights into how financial institutions integrate TPPs (including API usage, user engagement and potential authentication drop-off points)
  • Tracking of failed login attempts or unusual access patterns
  • IP anonymization to analyse traffic patterns and detect potential fraud

  

  PSD3 : The next step 

  In recent years, we have seen the rise of innovative payment companies and increasingly clever fraud schemes. This has prompted regulators to propose updates to payment rules.

  PSD3’s scope is to adapt to the evolving digital transformation and to better handle these fraud risks. The proposed measures : 

  • Encourage PSPs to share fraud-related information.
  • Make customers aware of the different types of fraud.
  • Strengthen customer authentication standards.
  • Provide non-bank PSPs restricted access to EU payment systems. 
  • Enact payment rules in a directly applicable regulation and harmonise and enforce the directive.

  Web analytics that respect user privacy 

  Achieving compliance with PSD2 may be a long road for some businesses. With Matomo, organisations can enjoy peace of mind knowing their data practices align with legal requirements.

  Ready to stop worrying over compliance with regulations like PSD2 and take control of your data ? Start your 21-day free trial with Matomo.

• B2B Marketing Attribution Guide : How to Master It in 2024

  21 mai 2024, par Erin

  The last thing you want is to invest your advertising dollars in channels, campaigns and ads that don’t work. But B2B marketing attribution — figuring out which marketing efforts drive revenue — is far from easy.

  With longer sales funnels and multiple people from the same company involved in the same sales process, B2B (business-to-business) is a different ballgame from B2C (business-to-consumer) marketing.

  In this guide, we break down what B2B marketing attribution is, how it’s different, which tools you can use to set it up and the best practices.

  What is B2B marketing attribution ?

  Marketing attribution in B2B companies is about figuring out where your high-value leads come from — nailing down long customer journeys across many different touchpoints.

  

  The goal is to determine which campaigns and content contributed to various parts of the customer journey. It’s a complex process that needs a reliable, privacy-focused web analytics tool and a CRM that integrates with it.

  This process significantly differs from traditional marketing attribution, where you focus more on short sales cycles from individual customers. With multiple contributing decision makers, B2B attribution requires more robust systems.

  What makes marketing attribution different for B2B ?

  The key differences between B2B and B2C marketing attribution are a longer sales funnel and more people involved in the sales process.

  The B2B sales funnel is significantly longer and more complex

  The typical B2C sales funnel is often broken down into four simple stages :

  1. Awareness : when a prospect first finds out about your product or brand
  2. Interest : where a prospect starts to learn about the benefits of your product
  3. Desire : when a prospect understands that they need your product
  4. Action : the actual process of closing the sale

  Even the most simplified B2B sales funnel includes several key stages.

  

  Here’s a brief overview of each :

  1. Awareness : Buyers recognise they have a problem and start looking for solutions. Stand out with blog posts, social media updates, ebooks and whitepapers.
  2. Consideration : Buyers are aware of your company and are comparing options. Provide product demos, webinars and case studies to address their concerns and build trust.
  3. Conversion : Buyers have chosen your product or company. Offer live demos, customer service, case studies and testimonials to finalise the purchase.
  4. Loyalty : Buyers have made a purchase and are now customers. Nurture relationships with thank you emails, follow-ups, how-tos, reward programs and surveys to encourage repeat business.
  5. Advocacy : Loyal customers become advocates, promoting your brand to others. Encourage this with surveys, testimonial requests and a referral program.

  A longer sales cycle typically involves not only more touchpoints but also extended decision-making processes.

  More teams are involved in the marketing and sales process

  The last differentiation in B2B attribution is the number of people involved. Instead of clear-cut sales and marketing teams, revenue teams are becoming more common.

  They include all go-to-market teams like sales, marketing, customer success and customer support. In B2B sales, long-term customer relationships can be incredibly valuable. As such, the focus shifts away from new customer acquisition alone.

  For example, you can also track and optimise your onboarding process. Marketing gets involved in post-sale efforts to boost loyalty. Sales reps follow up with customer success to get new sales angles and insights. Customer support insights drive future product development.

  Everyone works together to meet high-level company goals.

  The next section will explore how to set up an attribution system.

  How to find the right mix of B2B marketing attribution tools

  For most B2B marketing teams, the main struggle with attribution is not with the strategy but with creating a reliable system that gives them the data points they need to implement that strategy.

  We’ll outline one approach you can take to achieve this without a million-dollar budget or internal data science team.

  Use website analytics to track touchpoints

  The first thing you want to do is install a reliable website analytics solution on your website. 

  Once you’ve got your analytics in place, use campaign tracking parameters to track touchpoints from external campaigns like email newsletters, social media ads, review sites (like Capterra) and third-party partner campaigns.

  This way, you get a clear picture of which sources are driving traffic and conversions, helping you improve your marketing strategies.

  With analytics installed, you can track the referring sources of visits, engagement and conversion events. A robust solution like Matomo tracks everything from traffic sources, marketing attribution and visitor counts to behavioural analytics, like clicks, scrolling patterns and form interactions on your site.

  Marketing attribution will give you a cohesive view of which traffic sources and campaigns drive conversions and revenue over long periods. With Matomo’s marketing attribution feature, you can even use different marketing attribution models to compare results :

  

  For example, in a single report, you can compare the last interaction, first interaction and linear (three common marketing attribution models). 

  In total, Matomo has 6 available attribution models to choose from :

  1. First interaction
  2. Last interaction
  3. Last non-direct 
  4. Linear
  5. Position based
  6. Time decay 

  These additional attribution models are crucial for B2B sites. While other web analytics solutions often limit to last-click attribution, this model isn’t optimal for B2B with extended sales cycles.

  Try Matomo for Free

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

  Start for free

  No credit card required

  Use a CRM to integrate customer data from multiple sources

  Use your CRM software to integrate customer data from multiple sources. This will give you the ability to get meaningful B2B marketing insights. For example, you can get company-level insights so you can view conversion information by company, not just by person.

  Done effectively, you can close the loop back to analytics data by integrating data from multiple teams and platforms. 

  Implement self-reported attribution

  To further enhance the data, add qualifying questions in the lead signup process to create a hybrid attribution model. This is also known as self-reported attribution.

  

  Your web analytics platform won’t always be able to track the source of certain visits — for instance, “dark social” or peer-to-peer sharing, where links are shared privately and are not easily traceable by analytics tools.

  Doing self-reported attribution is crucial for getting a holistic image of your customer journey. 

  However, self-reported attribution isn’t foolproof ; users may click randomly or inaccurately recall where they first heard about you. So it’s essential to blend this data with your analytics to gain a more accurate understanding.

  Best practices for handling B2B prospect data in a privacy-sensitive world 

  Lastly, it’s important to respect your prospects’ privacy and comply with privacy regulations when conducting B2B marketing attribution.

  Privacy regulations and their enforcement are rapidly gaining momentum around the globe. Meta recently received a record GDPR fine of €1.2 billion for insufficient privacy measures when handling user data by the Irish Data Protection Agency.

  If you don’t want to risk major fines (or customers feeling betrayed), you shouldn’t follow in the same footsteps.

  Switch to a privacy-friendly web analytics

  Instead of using a controversial solution like Google Analytics, use a privacy-friendly web analytics solution like Matomo, Fathom or Plausible. 

  These alternatives not only ensure compliance with regulations like GDPR but also provide peace of mind amid the uncertain relationship between Google and GDPR. Google Analytics has faced bans in recent years, raising concerns about the future of the solution.

  While organisations governed by GDPR can currently use Google Analytics, there’s no guarantee of its continued availability.

  Make the switch to privacy-friendly web analytics to avoid potential fines and disruptive rulings that could force you to change platforms urgently. Such disruptions can be catastrophic for marketing teams heavily reliant on web analytics for tracking campaigns, business goals and marketing efforts.

  Improve your B2B marketing attribution with Matomo

  Matomo’s privacy-by-design architecture makes it the perfect analytics platform for the modern B2B marketer. Matomo enables you to meet even the strictest privacy regulations.

  At the same time, through campaign tracking URLs, marketing attribution, integrations and our API, you can track the results of various marketing channels and campaigns effectively. We help you understand the impact of each dollar of your marketing budget. 

  If you want a competitive edge over other B2B companies, try Matomo for free for 21 days. No credit card required.

  Try Matomo for Free

  21 day free trial. No credit card required.

  
  

  Your email address
  

  Your website address
  

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

  Choose your analytics subdomain
  

  .matomo.cloud

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

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

  Start improving your websites now

  

• FFMPEG error submitting a packet to the muxer

  27 juillet 2024, par Badgio10177

  I am attempting to stream video frames to a RTSP server using FFMPEG. I instantiate an ffmpeg pipeline in c++. There are times when the process works perfectly and other times I get the error Error submitting a packet to the muxer : Broken pipe. Error muxing a packet. What uis strange is that there are times when the stream works and times when it does not which leads me to believe that the FFMPEG parameters that I set are not necessarily incorrect.

  


  I am using a mex function within MATLAB to take in a frame and stream it.

  


  // Global variables&#xA;FILE* openPipeLine = NULL;&#xA;&#xA;void mexFunction(int nlhs, mxArray *plhs[], int nrhs, const mxArray *prhs[], int frameWidth, int frameHeight)&#xA;{&#xA;&#xA;    Ptr<mat> inputFrame = ocvMxArrayToImage_uint8(prhs[0], true);&#xA;    Mat processedFrame = *inputFrame;&#xA;&#xA;    // Check if FFMPEG process has been started&#xA;    if (!openPipeLine)&#xA;    {&#xA;        openPipeLine = _popen("ffmpeg -report -f rawvideo -r 10 -video_size 1280x720 -pixel_format bgr24 -i pipe: -vcodec libx264 -pix_fmt yuv420p -f rtsp rtsp://localhost:8554/mystream 2> log.txt", "wb");&#xA;&#xA;    }&#xA;&#xA;    // Write the frame data to the pipeline&#xA;    fwrite(processedFrame.data, 1, frameWidth * frameHeight * 3, openPipeLine);&#xA;    mexAtExit(exitFcn);&#xA;}&#xA;</mat>

  


  Below is the full report from the ffmpeg process. Do my operating system variables change from time to time which cause the stream to work at times and break at others ? I am using Windows 10.

  


  Log level: 48
Command line:
ffmpeg -report -f rawvideo -r 10 -video_size 1280x720 -pixel_format bgr24 -i pipe: -vcodec libx264 -pix_fmt yuv420p -f rtsp rtsp://localhost:8554/mystream

  built with gcc 12.2.0 (Rev10, 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-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-d3d11va --enable-dxva2 --enable-lib  libavutil      58. 16.101 / 58. 16.101
  libavcodec     60. 23.100 / 60. 23.100
  libavformat    60. 10.100 / 60. 10.100
  libavdevice    60.  2.101 / 60.  2.101
  libavfilter     9. 11.100 /  9. 11.100
  libswscale      7.  3.100 /  7.  3.100
  libswresample   4. 11.100 /  4. 11.100
  libpostproc    57.  2.100 / 57.  2.100
Splitting the commandline.

Successfully parsed a group of options.
Opening an input file: pipe:.
[rawvideo @ 00000182dba5efc0] Opening 'pipe:' for reading
[pipe @ 00000182dba611c0] Setting default whitelist 'crypto,data'
[rawvideo @ 00000182dba5efc0] Before avformat_find_stream_info() pos: 0 bytes read:65536 seeks:0 nb_streams:1
[rawvideo @ 00000182dba5efc0] All info found
[rawvideo @ 00000182dba5efc0] After avformat_find_stream_info() pos: 2764800 bytes read:2764800 seeks:0 frames:1
Input #0, rawvideo, from 'pipe:':
  Duration: N/A, start: 0.000000, bitrate: 221184 kb/s
  Stream #0:0, 1, 1/10: Video: rawvideo (BGR[24] / 0x18524742), bgr24, 1280x720, 221184 kb/s, 10 tbr, 10 tbn
Successfully opened the file.
Parsing a group of options: output url rtsp://192.168.0.2:8554/mystream.
Applying option vcodec (force video codec ('copy' to copy stream)) with argument libx264.
Applying option pix_fmt (set pixel format) with argument yuv420p.
Applying option f (force format) with argument rtsp.
Successfully parsed a group of options.
Opening an output file: rtsp://192.168.0.2:8554/mystream.
[out#0/rtsp @ 00000182dba72c00] No explicit maps, mapping streams automatically...
[vost#0:0/libx264 @ 00000182dba75cc0] Created video stream from input stream 0:0
Successfully opened the file.
Stream mapping:
  Stream #0:0 -> #0:0 (rawvideo (native) -> h264 (libx264))
[rawvideo @ 00000182dba72700] PACKET SIZE: 2764800, STRIDE: 3840
detected 16 logical cores
[graph 0 input from stream 0:0 @ 00000182dba86180] Setting 'video_size' to value '1280x720'
[graph 0 input from stream 0:0 @ 00000182dba86180] Setting 'pix_fmt' to value '3'
[graph 0 input from stream 0:0 @ 00000182dba86180] Setting 'time_base' to value '1/10'
[graph 0 input from stream 0:0 @ 00000182dba86180] Setting 'pixel_aspect' to value '0/1'
[graph 0 input from stream 0:0 @ 00000182dba86180] Setting 'frame_rate' to value '10/1'
[graph 0 input from stream 0:0 @ 00000182dba86180] w:1280 h:720 pixfmt:bgr24 tb:1/10 fr:10/1 sar:0/1
[format @ 00000182dba86540] Setting 'pix_fmts' to value 'yuv420p'
[auto_scale_0 @ 00000182dba869c0] w:iw h:ih flags:'' interl:0
[format @ 00000182dba86540] auto-inserting filter 'auto_scale_0' between the filter 'Parsed_null_0' and the filter 'format'
[AVFilterGraph @ 00000182dba49040] query_formats: 4 queried, 2 merged, 1 already done, 0 delayed
[auto_scale_0 @ 00000182dba869c0] w:1280 h:720 fmt:bgr24 sar:0/1 -> w:1280 h:720 fmt:yuv420p sar:0/1 flags:0x00000004
[libx264 @ 00000182dba76080] using mv_range_thread = 24
[libx264 @ 00000182dba76080] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2 AVX512
[libx264 @ 00000182dba76080] profile High, level 3.1, 4:2:0, 8-bit
[libx264 @ 00000182dba76080] 264 - core 164 r3107 a8b68eb - H.264/MPEG-4 AVC codec - Copyleft 2003-2023 - 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=22 lookahead_threads=3 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=10 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
[tcp @ 00000182dc5ce480] No default whitelist set
[tcp @ 00000182dc5ce480] Original list of addresses:
[tcp @ 00000182dc5ce480] Address 192.168.0.2 port 8554
[tcp @ 00000182dc5ce480] Interleaved list of addresses:
[tcp @ 00000182dc5ce480] Address 192.168.0.2 port 8554
[tcp @ 00000182dc5ce480] Starting connection attempt to 192.168.0.2 port 8554
[tcp @ 00000182dc5ce480] Successfully connected to 192.168.0.2 port 8554
[rtsp @ 00000182dba72d00] SDP:
v=0

o=- 0 0 IN IP4 127.0.0.1

s=No Name

c=IN IP4 192.168.0.2

t=0 0

a=tool:libavformat 60.10.100

m=video 0 RTP/AVP 96

a=rtpmap:96 H264/90000

a=fmtp:96 packetization-mode=1; sprop-parameter-sets=Z2QAH6zZQFAFuhAAAAMAEAAAAwFA8YMZYA==,aOvjyyLA; profile-level-id=64001F

a=control:streamid=0


[rtp @ 00000182dc5cd040] No default whitelist set
[udp @ 00000182dba4b140] No default whitelist set
[udp @ 00000182dba4b140] end receive buffer size reported is 393216
[udp @ 00000182dc9bf040] No default whitelist set
[udp @ 00000182dc9bf040] end receive buffer size reported is 393216
Output #0, rtsp, to 'rtsp://192.168.0.2:8554/mystream':
  Metadata:
    encoder         : Lavf60.10.100
  Stream #0:0, 0, 1/90000: Video: h264, yuv420p(tv, progressive), 1280x720, q=2-31, 10 fps, 90k tbn
    Metadata:
      encoder         : Lavc60.23.100 libx264
    Side data:
      cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: N/A
frame=    0 fps=0.0 q=0.0 size=       0kB time=N/A bitrate=N/A speed=N/A    
[rawvideo @ 00000182dba72700] PACKET SIZE: 2764800, STRIDE: 3840
[rawvideo @ 00000182dba72700] PACKET SIZE: 2764800, STRIDE: 3840
frame=    0 fps=0.0 q=0.0 size=       0kB time=N/A bitrate=N/A speed=N/A    
[rawvideo @ 00000182dba72700] PACKET SIZE: 2764800, STRIDE: 3840
[rawvideo @ 00000182dba72700] PACKET SIZE: 2764800, STRIDE: 3840
frame=    0 fps=0.0 q=0.0 size=       0kB time=N/A bitrate=N/A speed=N/A    
[rawvideo @ 00000182dba72700] PACKET SIZE: 2764800, STRIDE: 3840   
[rawvideo @ 00000182dba72700] PACKET SIZE: 2764800, STRIDE: 3840
[libx264 @ 00000182dba76080] frame=   0 QP=21.34 NAL=3 Slice:I Poc:0   I:3600 P:0    SKIP:0    size=135901 bytes
frame=    0 fps=0.0 q=25.0 size=       0kB time=-00:00:00.20 bitrate=  -0.0kbits/s speed=N/A    
[vost#0:0/libx264 @ 00000182dba75cc0] Error submitting a packet to the muxer: Broken pipe
[out#0/rtsp @ 00000182dba72c00] Error muxing a packet
[out#0/rtsp @ 00000182dba72c00] Terminating muxer thread
[rawvideo @ 00000182dba72700] PACKET SIZE: 2764800, STRIDE: 3840
[libx264 @ 00000182dba76080] frame=   1 QP=18.29 NAL=2 Slice:P Poc:2   I:2662 P:866  SKIP:72   size=54835 bytes
frame=    1 fps=0.0 q=25.0 size=N/A time=-00:00:00.10 bitrate=N/A speed=N/A    
No more output streams to write to, finishing.

Conversion failed!