Recherche avancée

Sur d’autres sites (6475)

• Fintech Content Marketing : 10 Best Practices & Growth Strategies

  24 juillet 2024, par Erin

  Content marketing is an effective strategy for growth and building trust. This is especially true in the fintech industry, where competition is intense and trust is crucial. Content marketing helps you strengthen customer relationships, engage your audience, and differentiate yourself from competitors.

  To get the most out of your fintech content marketing, you need to develop the right strategy.

  In this guide, we’ll cover everything you need to know about content marketing for fintech companies so you can expand your reach and grow your business.

  What is fintech content marketing ?

  Fintech content marketing is creating content around financial topics on the internet to attract, engage, and convert audiences.

  Fintech companies can use a content strategy to drive leads by creating educational content.

  

  While financial content is important, it’s easy for it to feel boring, unrelatable, or confusing. But, when done right, fintech companies can educate their audiences with great content marketing that helps their audience understand financial topics in-depth.

  Fintech companies can create written, audio, or video content to inform their audiences about financial topics they’re interested in.

  From there, each piece of content can then be distributed to different mediums :

  • Blogs
  • Website
  • Facebook
  • YouTube
  • Instagram
  • Other websites
  • Apps
  • And more

  Once content is distributed, fintech companies can then analyse how effective the content is by tracking web analytics data like search engine traffic, social media engagement, and new customers.

  7 reasons fintech companies need content marketing

  Before we dive into fintech content marketing best practices, let’s recap why fintech companies need to lean into content to grow their business.

  Here are seven reasons your financial company needs to deploy a robust content strategy :

  

  1. Reach new audiences

  If you want to grow your fintech company, you need to find new customers. Creating content is a proven path to marketing yourself online and attracting a larger audience.

  By using search engine optimisation (SEO), social media marketing, and YouTube, you can expand your audience and grow your customer base.

  With content marketing, you can find new audiences without needing a massive budget, making scaling easier.

  2. Engage current audience

  While content can be a powerful method to reach new customers, it isn’t the only thing it’s good for.

  If you want to grow your business, another way to leverage your content is to keep your current audience engaged.

  You can create financial content to educate, inform, and add value to your current audience who already knows you. Repurposing content between the different platforms your audience is on keeps them engaged with you and your brand.

  It’s a simple way to capture and keep the attention of your audience, build trust, and convert more prospects into customers.

  3. Build relationships with customers

  You should leverage content marketing in various spaces, such as social media, your website, a blog, or even YouTube. Creating content on different channels allows you to build relationships with your customers on autopilot.

  The general rule in marketing is that the more touch points you have with your customers, the more you’ll sell. Creating more content means you always have new opportunities to increase those touchpoints, build deeper relationships, and sell more.

  4. Grow authority in a space

  If you want people to trust you and your financial tech, you need to be seen as an authority. How can someone trust that your app or web platform will help them with their finances if they don’t trust you’re a financial expert ?

  You should use informative content to become a thought leader in your space. You can post content on social media or your own platforms.

  You can also spread your authority by leveraging other brands’ or influencers’ audiences through guest blog posting and guest podcasting.

  5. Drive new leads

  Content marketing isn’t just a fun hobby for businesses. It’s one of the smartest ways to drive new leads.

  You should be crafting content for your top-of-funnel marketing strategy to attract potential customers.

  Creating content consistently is a great way to bring in new audience members into your funnel.

  Once you grow your top-of-funnel audience, you can convert them into leads by getting them to join your email list or trial your financial software.

  One tip to get more out of your content strategy is creating evergreen content to continually drive leads. For example, create “set-it-and-forget it” blog posts or YouTube videos that will continue working for you daily to attract new audience members searching for helpful financial information. Then, provide a call to action on that content to join your email list (by leveraging a lead magnet).

  6. Convert prospects to customers

  When you have a continual flow of new top-of-funnel prospects, you always have a fresh cycle of prospects you can convert into customers.

  Content is primarily used to attract new audience members and engage your current audience at the top of your funnel. But it can also be used to convert your audience into customers.

  Try mixing up your content types to drive conversions :

  • Educational
  • Entertaining
  • Promotional

  Don’t just show off educational content.

  You should also mix in “authority” content by displaying case studies of user success stories and calling to action to sign up for a free trial or request a demo.

  7. Lower Customer Acquisition Cost (CAC)

  On the business side, if you want a marketing strategy that will keep expenses low long term, you’ll want to invest more in content.

  Content marketing has a great return on investment (ROI) for your time and effort.

  Why ?

  Because the customer acquisition costs (CAC) are so low.

  You can create content that can bring in leads for months if not years.

  If you only use Google or Facebook ads to drive new leads, you always have to “pay-to-play.” When you turn the advertising tap off, your leads dry up.

  But, with blogs and videos, you can create content that can bring in organic customers on repeat. It’s like a snowball effect that keeps going long after you’ve completed the initial work.

  10 fintech content marketing best practices

  Here are ten best practices to establish a strong content marketing strategy as a fintech company :

  

  1. Set SMART goals

  A good content strategy starts with goal-setting. You’ll never get there if you don’t know where you’re going.

  To make sure your fintech content marketing strategy is a success, you need to set SMART goals :

  • Specific
  • Measurable
  • Achievable
  • Relevant
  • Time-bound

  For example, you might set a goal to reach 20,000 blog visits in one year and convert blog visits at a rate of 3%.

  Setting clear content goals will streamline operations, so you stay consistent and get the most out of your efforts.

  3. Be transparent

  Transparency is crucial for fintech companies, as they handle sensitive financial data and, in many cases, monetary transactions.

  It’s essential for you to be open and clear about your products, services, and data practices. By being honest about privacy and security measures, fintechs can build and maintain trust with their customers.

  This transparency not only helps in establishing credibility but also ensures customers feel confident about how their financial information is managed and protected.

  

  4. Take an education-first approach

  Content isn’t just about “hooking” or entertaining your audience. That’s just one aspect of a content strategy.

  The best approach to building authority and converting leads from your content is to take an education-first approach.

  Remember above, when we touched on understanding your ICP ? You need to know your ICP’s interests and pain points inside and out and then map your product’s strengths to those that are relevant.

  Always start with your ICP, then build the content strategy around them based on your product.

  Find connections and identify how your product can address the ICP’s interests and pain points.

  For example, let’s say your ICPs are Gen Z consumers. They’re interested in independence and saving for future goals. Their pain points might include lack of investment knowledge and managing student debts and other loans.

  Let’s say your product is a personal finance app. Some of your benefits might be budget tracking and beginner-friendly investment options. You could create a content strategy around budgeting in your 20s and investing for beginners.

  Content strategies will vary widely based on your ICP. For instance, content for a fintech company targeting those approaching retirement will need a different focus compared to that aimed at younger consumers.

  Remember : practical, step-by-step, value-driven content performs best regarding conversions.

  5. Leverage the right tools

  If you’re going to succeed with content, you need to lean on the right tools.

  Here are a few types of tools you should consider (and recommendations) :

  • Project management (i.e., Asana)
  • Content management system (i.e., WordPress)
  • Content scheduling (i.e., Hootsuite)
  • Design (i.e., Canva)
  • SEO (i.e., Ahrefs)
  • Web analytics (i.e., Matomo)

  Try Matomo for Free

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

  Start for free

  No credit card required

  6. Promote your content on different platforms

  You’ll want to promote your fintech content marketing strategy on different channels and platforms to get the most out of your fintech content marketing strategy.

  Start with one core platform before you pick a few platforms to promote your content. You should leverage at least one social media platform.

  Then, create a blog and an email newsletter to ensure you create multiple touchpoints.

  Here are some tips on how to pick the right platform :

  • Consider age range (i.e. TikTok for a younger audience, Facebook for an older audience)
  • Consider your preferred content type (YouTube for long-form video, X for short-form written content
  • Consider your competition (i.e. go where competitive fintech companies already are)

  7. Track results 

  How do you know if you’re on pace to reach the SMART goals you set earlier ?

  By tracking your results. 

  You should dive into your data regularly to ensure your content is working. Make sure to track social media, email marketing, and web results.

  Keep a close eye on your website KPIs and track your conversions to ensure a return on investment (ROI). For more detailed guidance on monitoring your website’s performance, check out our blog on how to check website traffic as accurately as possible.

  Remember, a data-driven approach is the best way to stay on track with your content goals.

  8. Establish a content leader

  Your content marketing needs a leader. You should establish someone on your marketing team to oversee your content plan. 

  They should ensure they collaborate well with different teams, understand social media and SEO, and know how to manage projects.

  Most of all, don’t forget that they’re in charge of tracking your data and reporting to higher-ups, so they should be comfortable with web analytics and know how to track performance well.

  9. Optimise for SEO

  It’s not enough to create a weekly blog post. You could craft the most valuable content on your website, but nobody will find it online if it isn’t optimised for SEO.

  Your content leader should analyse SEO data using a tool like Ahrefs or SEMrush to analyse different keywords to target in your content. 

  A web analytics tool like Matomo can then be used to track results. Matomo offers traditional web analytics, including pageviews, bounce rate, and sources of traffic, alongside features like heatmaps, session recordings, and A/B testing.

  These advanced features provide deeper insights into how users interact with your site and content, helping you pinpoint areas for improvement. Improving the user experience based on these insights can then positively impact your Google rankings.

  Try Matomo for Free

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

  Start for free

  No credit card required

  10. Stay compliant

  Fintech is a highly regulated industry. Keeping this in mind, you need to ensure you take the necessary steps to ensure you remain compliant with all applicable laws and regulations.

  Non-compliance can result in severe penalties.

  Given these high standards, it’s crucial to ensure that user data remains private and secure. Matomo helps with this by providing a compliant web analytics solution that respects user privacy. With Matomo, you can confidently manage compliance and build trust with your customers while also reliably tracking the performance of your content marketing.

  

  Drive your content marketing strategy with Matomo

  Leaning into content marketing can be one of the best ways your fintech company can attract, engage, convert, and retain your audience.

  By creating high-quality content for your audience on social media, YouTube, and your website, you can establish your brand as an authority to grow your business for years to come.

  But remember, you need to make sure you’re only using privacy-friendly, compliant tools to protect your audience’s data.

  Thankfully, Matomo has you covered.

  As a privacy-friendly web analytics tool, Matomo ensures that your website data is tracked and stored in compliance with privacy laws.

  Trusted by over 1 million websites, it offers reliable data without sampling, guaranteeing accuracy. Matomo is designed to be fully compliant with privacy regulations such as GDPR and CCPA, while also providing advanced features like heatmaps, session recordings, and A/B testing to help you track and enhance your website’s performance.

  Request a demo to see how Matomo can benefit your fintech business now.

  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

  

• OCPA, FDBR and TDPSA – What you need to know about the US’s new privacy laws

  22 juillet 2024, par Daniel Crough

  On July 1, 2024, new privacy laws took effect in Florida, Oregon, and Texas. People in these states now have more control over their personal data, signaling a shift in privacy policy in the United States. Here’s what you need to know about these laws and how privacy-focused analytics can help your business stay compliant.

  Consumer rights are front and centre across all three laws

  The Florida Digital Bill of Rights (FDBR), Oregon Consumer Privacy Act (OCPA), and Texas Data Privacy and Security Act (TDPSA) grant consumers similar rights.

  Access : Consumers can access their personal data held by businesses.

  Correction : Consumers can correct inaccurate data.

  Deletion : Consumers may request data deletion.

  Opt-Out : Consumers can opt-out of the sale of their personal data and targeted advertising.

  Oregon Consumer Privacy Act (OCPA)

  The Oregon Consumer Privacy Act (OCPA), signed into law on June 23, 2023, and effective as of July 1, 2024, grants Oregonians new rights regarding their personal data and imposes obligations on businesses. Starting July 1, 2025, authorities will enforce provisions that require data protection assessments, and businesses must recognize universal opt-out mechanisms by January 1, 2026. In Oregon, the OCPA applies to business that :

  • Either conduct business in Oregon or offer products and services to Oregon residents

  • Control or process the personal data of 100,000 consumers or more, or

  • Control or process the data of 25,000 or more consumers while receiving over 25% of their gross revenues from selling personal data.

  Exemptions include public bodies like state and local governments, financial institutions, and insurers that operate under specific financial regulations. The law also excludes protected health information covered by HIPAA and other specific federal regulations.

  Business obligations

  Data Protection Assessments : Businesses must conduct data protection assessments for high-risk processing activities, such as those involving sensitive data or targeting children.

  Consent for Sensitive Data : Businesses must secure explicit consent before collecting, processing, or selling sensitive personal data, such as racial or ethnic origin, religious beliefs, health information, biometric data, and geolocation.

  Universal Opt-out : Starting January 1, 2025, businesses must acknowledge universal opt-out mechanisms, like the Global Privacy Control, that allow consumers to opt out of data collection and processing activities.

  Enforcement

  The Oregon Attorney General can issue fines up to $7,500 per violation. There is no private right of action.

  Unique characteristics of the OCPA

  The OCPA differs from other state privacy laws by requiring affirmative opt-in consent for processing sensitive and children’s data, and by including nonprofit organisations under its scope. It also requires global browser opt-out mechanisms starting in 2026.

  Florida Digital Bill of Rights (FDBR)

  The Florida Digital Bill of Rights (FDBR) became law on June 6, 2023, and it came into effect on July 1, 2024. This law targets businesses with substantial operations or revenues tied to digital activities and seeks to protect the personal data of Florida residents by granting them greater control over their information and imposing stricter obligations on businesses. It applies to entities that :

  • Conduct business in Florida or provide products or services targeting Florida residents,

  • Have annual global gross revenues exceeding $1 billion,

  • Receive 50% or more of their revenues from digital advertising or operate significant digital platforms such as app stores or smart speakers with virtual assistants.

  Exemptions include governmental entities, nonprofits, financial institutions covered by the Gramm-Leach-Bliley Act, and entities covered by HIPAA.

  Business obligations

  Data Security Measures : Companies are required to implement reasonable data security measures to protect personal data from unauthorised access and breaches.

  Handling Sensitive Data : Explicit consent is required for processing sensitive data, which includes information like racial or ethnic origin, religious beliefs, and biometric data.

  Non-Discrimination : Entities must ensure they do not discriminate against consumers who exercise their privacy rights.

  Data Minimisation : Businesses must collect only necessary data.

  Vendor Management : Businesses must ensure that their processors and vendors also comply with the FDBR, regarding the secure handling and processing of personal data.

  Enforcement

  The Florida Attorney General can impose fines of up to $50,000 per violation, with higher penalties for intentional breaches.

  Unique characteristics of the FDBR

  Unlike broader privacy laws such as the California Consumer Privacy Act (CCPA), which apply to a wider range of businesses based on lower revenue thresholds and the volume of data processed, the FDBR distinguishes itself by targeting large-scale businesses with substantial revenues from digital advertising. The FDBR also emphasises specific consumer rights related to modern digital interactions, reflecting the evolving landscape of online privacy concerns.

  Texas Data Privacy and Security Act (TDPSA)

  The Texas Data Privacy and Security Act (TDPSA), signed into law on June 16, 2023, and effective as of July 1, 2024, enhances data protection for Texas residents. The TDPSA applies to entities that :

  • Conduct business in Texas or offer products or services to Texas residents.

  • Engage in processing or selling personal data.

  • Do not fall under the classification of small businesses according to the U.S. Small Business Administration’s criteria, which usually involve employee numbers or average annual receipts. 

  The law excludes state agencies, political subdivisions, financial institutions compliant with the Gramm-Leach-Bliley Act, and entities compliant with HIPAA.

  Business obligations

  Data Protection Assessments : Businesses must conduct data protection assessments for processing activities that pose a heightened risk of harm to consumers, such as processing for targeted advertising, selling personal data, or profiling.

  Consent for Sensitive Data : Businesses must get explicit consent before collecting, processing, or selling sensitive personal data, such as racial or ethnic origin, religious beliefs, health information, biometric data, and geolocation.

  Companies must have adequate data security practices based on the personal information they handle.

  Data Subject Access Requests (DSARs) : Businesses must respond to consumer requests regarding their personal data (e.g., access, correction, deletion) without undue delay, but no later than 45 days after receipt of the request.

  Sale of Data : If businesses sell personal data, they must disclose these practices to consumers and provide them with an option to opt out.

  Universal Opt-Out Compliance : Starting January 1, 2025, businesses must recognise universal opt-out mechanisms like the Global Privacy Control, enabling consumers to opt out of data collection and processing activities.

  Enforcement

  The Texas Attorney General can impose fines up to $25,000 per violation. There is no private right of action.

  Unique characteristics of the TDPSA

  The TDPSA stands out for its small business carve-out, lack of specific thresholds based on revenue or data volume, and requirements for recognising universal opt-out mechanisms starting in 2025. It also mandates consent for processing sensitive data and includes specific measures for data protection assessments and privacy notices.

  Try Matomo for Free

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

  Start for free

  No credit card required

  Privacy notices across Florida, Oregon, and Texas

  All three laws include a mandate for privacy notices, though there are subtle variations in their specific requirements. Here’s a breakdown of these differences :

  FDBR privacy notice requirements

  Clarity : Privacy notices must clearly explain the collection and use of personal data.

  Disclosure : Notices must inform consumers about their rights, including the right to access, correct, delete their data, and opt-out of data sales and targeted advertising.

  Specificity : Businesses must disclose if they sell personal data or use it for targeted advertising.

  Security Practices : The notice should describe the data security measures in place.

  OCPA privacy notice requirements

  Comprehensive Information : Notices must provide information about the personal data collected, the purposes for processing, and any third parties that can access it.

  Consumer Rights : Must plainly outline consumers’ rights to access, correct, delete their data, and opt-out of data sales, targeted advertising, and profiling.

  Sensitive Data : To process sensitive data, businesses or entities must get explicit consent and communicate it.

  Universal Opt-Out : Starting January 1, 2026, businesses must recognise and honour universal opt-out mechanisms.

  TDPSA privacy notice requirements

  Detailed Notices : Must provide clear and detailed information about data collection practices, including the data collected and the purposes for its use.

  Consumer Rights : Must inform consumers of their rights to access, correct, delete their data, and opt-out of data sales and targeted advertising.

  High-Risk Processing : Notices should include information about any high-risk processing activities and the safeguards in place.

  Sensitive Data : To process sensitive data, entities and businesses must get explicit consent.

  What these laws mean for your businesses

  Businesses operating in Florida, Oregon, and Texas must now comply with these new data privacy laws. Here’s what you can do to avoid fines :

  1. Understand the Laws : Familiarise yourself with the specific requirements of the FDBR, OCPA, and TDPSA, including consumer rights and business obligations.

  2. Implement Data Protection Measures : Ensure you have robust data security measures in place. This includes conducting regular data protection assessments, especially for high-risk processing activities.

  3. Update Privacy Policies : Provide clear and comprehensive privacy notices that inform consumers about their rights and how their data is processed.

  4. Obtain Explicit Consent : For sensitive data, make sure you get explicit consent from consumers. This includes information like health, race, sexual orientation, and more.

  5. Manage Requests Efficiently : Be prepared to handle requests from consumers to access, correct, delete their data, and opt-out of data sales and targeted advertising within the stipulated timeframes.

  6. Recognise Opt-Out Mechanisms : For Oregon, businesses must be ready to implement and recognise universal opt-out mechanisms by January 1, 2026. In Texas, opt-out enforcement begins in 2026. In Florida, the specific opt-out provisions began on July 1, 2024.

  7. Stay Updated : Keep abreast of any changes or updates to these laws to ensure ongoing compliance. Keep an eye on the Matomo blog or sign up for our newsletter to stay in the know.

  Are we headed towards a more privacy-focused future in the United States ?

  Florida, Oregon, and Texas are joining states like California, Virginia, Colorado, Connecticut, Utah, Iowa, Indiana, Tennessee, and Montana in strengthening consumer privacy protections. This trend could signify a shift in US policy towards a more privacy-focused internet, underlining the importance of consumer data rights and transparent business practices. Even if these laws do not apply to your business, considering updates to your data and privacy policies is wise. Fortunately, there are tools and solutions designed for privacy and compliance to help you navigate these changes.

  Avoid fines and get better data with Matomo

  Most analytics tools don’t prioritize safeguarding user data. At Matomo, we believe everyone has the right to data sovereignty, privacy and amazing analytics. Matomo offers a solution that meets privacy regulations while delivering incredible insights. With Matomo, you get :

  100% Data Ownership : Keep full control over your data, ensuring it is used according to your privacy policies.

  Privacy Protection : Built with privacy in mind, Matomo helps businesses comply with privacy laws.

  Powerful Features : Gain insights with tools like heatmaps, session recordings, and A/B testing.

  Open Source : Matomo’s is open-source and committed to transparency and customisation.

  Flexibility : Choose to host Matomo on your servers or in the cloud for added security.

  No Data Sampling : Ensure accurate and complete insights without data sampling.

  Privacy Compliance : Easily meet GDPR and other requirements, with data stored securely and never sold or shared.

  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

  

  Disclaimer : This content is provided for informational purposes only and is not intended as legal advice. While we strive to ensure the accuracy and timeliness of the information provided, the laws and regulations surrounding privacy are complex and subject to change. We recommend consulting with a qualified legal professional to address specific legal issues related to your circumstances. 

• Flutter streaming with FFmpeg_flutter_kit not reaching server

  22 juillet 2024, par Julio Cesar Reis

  I'm trying to stream my flutter screen to youtube using FFmpeg flutter kit. Everything seems fine but the output never reaches youtube server.

  


  


  1. log in using Yt flutter package.

     


  


  2. create a broadcast

     


  


  3. create the livestream and bind it to the broadcast

     


  


  4. get the ingestion address through LiveStreamItem.cdn.ingestionInfo.ingestionAddress

     


  


  5. stream the frames saved through FFmpeg :

     


     final String rtmpUrl = "ls.cdn.ingestionInfo.ingestionAddress"

     


     final String command = '-re -i $framePath -c:v libx264 -f flv $rtmpUrl';

     


     await FFmpegKit.execute(command);

     


  


  


  But at the end I get errors like SESSION_NOT_FOUND, or the stream never reaches the server which keeps my broadcast as ready and not active so I can't go live.

  


  I've tried using the ingestionAddress plus the streamName separated by a slash, I've tried the direct stream using rtmp ://x.rtmp.youtube.com/live2/MY_API_KEY but none of that worked.

  


  ERROR LOG :

  


  


  I/flutter (19889) : ffmpeg version n6.0 I/flutter (19889) : Copyright
(c) 2000-2023 the FFmpeg developers I/flutter (19889) : I/flutter
(19889) : built with Android (7155654, based on r399163b1) clang
version 11.0.5
(https://android.googlesource.com/toolchain/llvm-project
87f1315dfbea7c137aa2e6d362dbb457e388158d) I/flutter (19889) :
  
configuration : —cross-prefix=aarch64-linux-android-
—sysroot=/Users/sue/Library/Android/sdk/ndk/22.1.7171670/toolchains/llvm/prebuilt/darwin-x86_64/sysroot
—prefix=/Users/sue/Projects/arthenica/ffmpeg-kit/prebuilt/android-arm64/ffmpeg
—pkg-config=/opt/homebrew/bin/pkg-config —enable-version3 —arch=aarch64 —cpu=armv8-a —target-os=android —enable-neon —enable-asm —enable-inline-asm —ar=aarch64-linux-android-ar —cc=aarch64-linux-android24-clang —cxx=aarch64-linux-android24-clang++ —ranlib=aarch64-linux-android-ranlib —strip=aarch64-linux-android-strip —nm=aarch64-linux-android-nm —extra-libs='-L/Users/sue/Projects/arthenica/ffmpeg-kit/prebuilt/android-arm64/cpu-features/lib
-lndk_compat' —disable-autodetect —enable-cross-compile —enable-pic —enable-jni —enable-optimizations —enable-swscale —disable-static —enable-shared —enable-pthreads —enable-v4l2-m2m —disable-outdev=fbdev —disable-indev=fbdev —enable-small —disable-xmm-clobber-test —disable-debug —enable-lto —disable-neon I/flutter (19889) : libavutil 58. 2.100 / 58. 2.100 I/flutter
(19889) : libavcodec 60. 3.100 / 60. 3.100 I/flutter (19889) :
  
libavformat 60. 3.100 / 60. 3.100 I/flutter (19889) :
  
libavdevice 60. 1.100 / 60. 1.100 I/flutter (19889) :
  
libavfilter 9. 3.100 / 9. 3.100 I/flutter (19889) : libswscale
7. 1.100 / 7. 1.100 I/flutter (19889) : libswresample 4. 10.100 / 4. 10.100 I/flutter (19889) : Input #0, png_pipe, from
'/data/user/0/com.example.poc_stream/cache/frame.png' : I/flutter
(19889) : Duration : I/flutter (19889) : N/A I/flutter (19889) : ,
bitrate : I/flutter (19889) : N/A I/flutter (19889) : I/flutter
(19889) : Stream #0:0 I/flutter (19889) : : Video : png, rgba(pc),
412x771 I/flutter (19889) : , I/flutter (19889) : 25 fps, I/flutter
(19889) : 25 tbr, I/flutter (19889) : 25 tbn I/flutter (19889) :
E/flutter (19889) : [ERROR:flutter/runtime/dart_vm_initializer.cc(41)]
Unhandled Exception : PlatformException(SESSION_NOT_FOUND, Session not
found., null, null) E/flutter (19889) : #0
  
StandardMethodCodec.decodeEnvelope
(package:flutter/src/services/message_codecs.dart:648:7) E/flutter
(19889) : #1 MethodChannel._invokeMethod
(package:flutter/src/services/platform_channel.dart:334:18) E/flutter
(19889) : E/flutter (19889) : #2
  
FFmpegKitFactory.mapToNullableSession
(package:ffmpeg_kit_flutter_min_gpl/src/ffmpeg_kit_factory.dart:76:3)
E/flutter (19889) : E/flutter (19889) : #3
  
FFmpegKitInitializer._processCompleteCallbackEvent.
(package:ffmpeg_kit_flutter_min_gpl/src/ffmpeg_kit_flutter_initializer.dart:213:48)
E/flutter (19889) : E/flutter (19889) :
I/flutter (19889) : Stream mapping : I/flutter (19889) : Stream #0:0 ->
#0:0 I/flutter (19889) : (png (native) -> h264 (libx264)) I/flutter (19889) : I/flutter (19889) : Press [q] to stop, [?] for help I/flutter
(19889) : [libx264 @ 0xb40000736398c190] using cpu capabilities : ARMv8
NEON I/flutter (19889) : [libx264 @ 0xb400007363a92e40] using cpu
capabilities : ARMv8 NEON I/flutter (19889) : [libx264 @
0xb40000736398c190] profile High 4:4:4 Predictive, level 3.0, 4:4:4,
8-bit I/flutter (19889) : [libx264 @ 0xb40000736398c190] 264 - core 164

  


  

  • 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=4 threads=6
lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0
bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1
b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250
keyint_min=25 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 I/flutter (19889) : Output #0, flv, to
'rtmp ://x.rtmp.youtube.com/live2/x7k6-grm1-z15w-tqb7-akrt' : I/flutter
(19889) : Metadata : I/flutter (19889) : encoder :
I/flutter (19889) : Lavf60.3.100 I/flutter (19889) : I/flutter (19889) :
Stream #0:0 I/flutter (19889) : : Video : h264 ([7][0][0][0] / 0x0007),
yuv444p(tv, unknown/bt709/iec61966-2-1, progressive), 412x771, q=2-31
I/flutter (19889) : , I/flutter (19889) : 25 fps, I/flutter (19889) :
1k tbn I/flutter (19889) : I/flutter (19889) : Metadata : I/flutter
(19889) : encoder : I/flutter (19889) : Lavc60.3.100
libx264 I/flutter (19889) : I/flutter (19889) : Side data :
I/flutter (19889) : I/flutter (19889) : cpb : I/flutter (19889) :
bitrate max/min/avg : 0/0/0 buffer size : 0 I/flutter (19889) :
vbv_delay : N/A I/flutter (19889) : I/flutter (19889) : Instance of
'Statistics' I/flutter (19889) : frame= 0 fps=0.0 q=0.0 size=
    
0kB time=N/A bitrate=N/A speed=N/A I/flutter (19889) : [libx264 @
0xb400007363a92e40] profile High 4:4:4 Predictive, level 3.0, 4:4:4,
8-bit I/flutter (19889) : [libx264 @ 0xb400007363a92e40] 264 - core 164

  


  • 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=4 threads=6
lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0
bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1
b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250
keyint_min=25 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 I/flutter (19889) : Output #0, flv, to
'rtmp ://x.rtmp.youtube.com/live2/x7k6-grm1-z15w-tqb7-akrt' : I/flutter
(19889) : Metadata : I/flutter (19889) : encoder :
I/flutter (19889) : Lavf60.3.100 I/flutter (19889) : I/flutter (19889) :
Stream #0:0 I/flutter (19889) : : Video : h264 ([7][0][0][0] / 0x0007),
yuv444p(tv, unknown/bt709/iec61966-2-1, progressive), 412x771, q=2-31
I/flutter (19889) : , I/flutter (19889) : 25 fps, I/flutter (19889) :
1k tbn I/flutter (19889) : I/flutter (19889) : Metadata : I/flutter
(19889) : encoder : I/flutter (19889) : Lavc60.3.100
libx264 I/flutter (19889) : I/flutter (19889) : Side data :
I/flutter (19889) : I/flutter (19889) : cpb : I/flutter (19889) :
bitrate max/min/avg : 0/0/0 buffer size : 0 I/flutter (19889) :
vbv_delay : N/A I/flutter (19889) : I/flutter (19889) : Instance of
'Statistics' I/flutter (19889) : frame= 0 fps=0.0 q=0.0 size=
    
0kB time=N/A bitrate=N/A speed=N/A I/flutter (19889) : [flv @
0xb4000074238c1c30] Failed to update header with correct duration.
I/flutter (19889) : [flv @ 0xb4000074238c1c30] Failed to update header
with correct filesize. I/flutter (19889) : Instance of 'Statistics'
I/flutter (19889) : frame= 1 fps=0.0 q=28.0 Lsize= 4kB
time=00:00:00.00 bitrate=N/A speed= 0x I/flutter (19889) :
video:4kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB
muxing overhead : I/flutter (19889) : 8.895621% I/flutter (19889) :
I/flutter (19889) : [libx264 @ 0xb40000736398c190] frame I:1 Avg
QP:14.17 size : 2957 I/flutter (19889) : [libx264 @
0xb40000736398c190] mb I I16..4 : 1.4% 93.3% 5.3% I/flutter (19889) :
[libx264 @ 0xb40000736398c190] 8x8 transform intra:93.3% I/flutter
(19889) : [libx264 @ 0xb40000736398c190] coded y,u,v intra : 3.4% 1.4%
1.7% I/flutter (19889) : [libx264 @ 0xb40000736398c190] i16 v,h,dc,p : 78% 17% 6% 0% I/flutter (19889) : [libx264 @ 0xb40000736398c190] i8
v,h,dc,ddl,ddr,vr,hd,vl,hu : 36% 0% 64% 0% 0% 0% 0% 0% 0%
I/flutter (19889) : [libx264 @ 0xb40000736398c190] i4
v,h,dc,ddl,ddr,vr,hd,vl,hu : 49% 21% 14% 1% 3% 4% 3% 2% 3%
I/flutter (19889) : [libx264 @ 0xb40000736398c190] kb/s:591.40
I/flutter (19889) : ffmpeg version n6.0 I/flutter (19889) : Copyright
(c) 2000-2023 the FFmpeg developers I/flutter (19889) : I/flutter
(19889) : built with Android (7155654, based on r399163b1) clang
version 11.0.5
(https://android.googlesource.com/toolchain/llvm-project 87f1315dfbea7c137aa2e6d362dbb457e388158d) I/flutter (19889) :
    
configuration : —cross-prefix=aarch64-linux-android-
—sysroot=/Users/sue/Library/Android/sdk/ndk/22.1.7171670/toolchains/llvm/prebuilt/darwin-x86_64/sysroot
—prefix=/Users/sue/Projects/arthenica/ffmpeg-kit/prebuilt/android-arm64/ffmpeg
—pkg-config=/opt/homebrew/bin/pkg-config —enable-version3 —arch=aarch64 —cpu=armv8-a —target-os=android —enable-neon —enable-asm —enable-inline-asm —ar=aarch64-linux-android-ar —cc=aarch64-linux-android24-clang —cxx=aarch64-linux-android24-clang++ —ranlib=aarch64-linux-android-ranlib —strip=aarch64-linux-android-strip —nm=aarch64-linux-android-nm —extra-libs='-L/Users/sue/Projects/arthenica/ffmpeg-kit/prebuilt/android-arm64/cpu-features/lib
-lndk_compat' —disable-autodetect —enable-cross-compile —enable-pic —enable-jni —enable-optimizations —enable-swscale —disable-static —enable-shared —enable-pthreads —enable-v4l2-m2m —disable-outdev=fbdev —disable-indev=fbdev —enable-small —disable-xmm-clobber-test —disable-debug —enable-lto —disable-neon I/flutter (19889) : libavutil 58. 2.100 / 58. 2.100 I/flutter
(19889) : libavcodec 60. 3.100 / 60. 3.100 I/flutter (19889) :
    
libavformat 60. 3.100 / 60. 3.100 I/flutter (19889) :
    
libavdevice 60. 1.100 / 60. 1.100 I/flutter (19889) :
    
libavfilter 9. 3.100 / 9. 3.100 I/flutter (19889) : libswscale

  


  


  

  7. 1.100 / 7. 1.100 I/flutter (19889) : libswresample 4. 10.100 / 4. 10.100 I/flutter (19889) : [flv @ 0xb4000074238dac30] Failed to
update header with correct duration. I/flutter (19889) : [flv @
0xb4000074238dac30] Failed to update header with correct filesize.
I/flutter (19889) : Instance of 'Statistics' I/flutter (19889) : frame=
1 fps=0.0 q=28.0 Lsize= 4kB time=00:00:00.00 bitrate=N/A speed=
0x I/flutter (19889) : video:4kB audio:0kB subtitle:0kB other
streams:0kB global headers:0kB muxing overhead : I/flutter (19889) :
8.895621% I/flutter (19889) : I/flutter (19889) : Input #0, png_pipe, from '/data/user/0/com.example.poc_stream/cache/frame.png' : I/flutter
(19889) : Duration : I/flutter (19889) : N/A I/flutter (19889) : ,
bitrate : I/flutter (19889) : N/A I/flutter (19889) : I/flutter
(19889) : Stream #0:0 I/flutter (19889) : : Video : png, rgba(pc),
412x771 I/flutter (19889) : , I/flutter (19889) : 25 fps, I/flutter
(19889) : 25 tbr, I/flutter (19889) : 25 tbn I/flutter (19889) :
I/flutter (19889) : [libx264 @ 0xb400007363a92e40] frame I:1 Avg
QP:14.17 size : 2957 I/flutter (19889) : [libx264 @
0xb400007363a92e40] mb I I16..4 : 1.4% 93.3% 5.3% I/flutter (19889) :
[libx264 @ 0xb400007363a92e40] 8x8 transform intra:93.3% I/flutter
(19889) : [libx264 @ 0xb400007363a92e40] coded y,u,v intra : 3.4% 1.4%
1.7% I/flutter (19889) : [libx264 @ 0xb400007363a92e40] i16 v,h,dc,p : 78% 17% 6% 0% I/flutter (19889) : [libx264 @ 0xb400007363a92e40] i8
v,h,dc,ddl,ddr,vr,hd,vl,hu : 36% 0% 64% 0% 0% 0% 0% 0% 0%
I/flutter (19889) : [libx264 @ 0xb400007363a92e40] i4
v,h,dc,ddl,ddr,vr,hd,vl,hu : 49% 21% 14% 1% 3% 4% 3% 2% 3%
I/flutter (19889) : [libx264 @ 0xb400007363a92e40] kb/s:591.40
I/flutter (19889) : ffmpeg version n6.0 I/flutter (19889) : Copyright
(c) 2000-2023 the FFmpeg developers I/flutter (19889) : I/flutter
(19889) : built with Android (7155654, based on r399163b1) clang
version 11.0.5
(https://android.googlesource.com/toolchain/llvm-project
87f1315dfbea7c137aa2e6d362dbb457e388158d) I/flutter (19889) :
     
configuration : —cross-prefix=aarch64-linux-android-
—sysroot=/Users/sue/Library/Android/sdk/ndk/22.1.7171670/toolchains/llvm/prebuilt/darwin-x86_64/sysroot
—prefix=/Users/sue/Projects/arthenica/ffmpeg-kit/prebuilt/android-arm64/ffmpeg
—pkg-config=/opt/homebrew/bin/pkg-config —enable-version3 —arch=aarch64 —cpu=armv8-a —target-os=android —enable-neon —enable-asm —enable-inline-asm —ar=aarch64-linux-android-ar —cc=aarch64-linux-android24-clang —cxx=aarch64-linux-android24-clang++ —ranlib=aarch64-linux-android-ranlib —strip=aarch64-linux-android-strip —nm=aarch64-linux-android-nm —extra-libs='-L/Users/sue/Projects/arthenica/ffmpeg-kit/prebuilt/android-arm64/cpu-features/lib
-lndk_compat' —disable-autodetect —enable-cross-compile —enable-pic —enable-jni —enable-optimizations —enable-swscale —disable-static —enable-shared —enable-pthreads —enable-v4l2-m2m —disable-outdev=fbdev —disable-indev=fbdev —enable-small —disable-xmm-clobber-test —disable-debug —enable-lto —disable-neon I/flutter (19889) : libavutil 58. 2.100 / 58. 2.100 I/flutter
(19889) : libavcodec 60. 3.100 / 60. 3.100 I/flutter (19889) :
     
libavformat 60. 3.100 / 60. 3.100 I/flutter (19889) :
     
libavdevice 60. 1.100 / 60. 1.100 I/flutter (19889) :
     
libavfilter 9. 3.100 / 9. 3.100 I/flutter (19889) : libswscale

  


  8. 1.100 / 7. 1.100 I/flutter (19889) : libswresample 4. 10.100 / 4. 10.100 I/flutter (19889) : Input #0, png_pipe, from
'/data/user/0/com.example.poc_stream/cache/frame.png' : E/flutter
(19889) : [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled
Exception : PlatformException(SESSION_NOT_FOUND, Session not found.,
null, null) E/flutter (19889) : #0
     
StandardMethodCodec.decodeEnvelope
(package:flutter/src/services/message_codecs.dart:648:7) E/flutter
(19889) : #1 MethodChannel._invokeMethod
(package:flutter/src/services/platform_channel.dart:334:18) E/flutter
(19889) : E/flutter (19889) : #2
     
FFmpegKitFactory.mapToNullableSession
(package:ffmpeg_kit_flutter_min_gpl/src/ffmpeg_kit_factory.dart:76:3)
E/flutter (19889) : E/flutter (19889) : #3
     
FFmpegKitInitializer._processCompleteCallbackEvent.
(package:ffmpeg_kit_flutter_min_gpl/src/ffmpeg_kit_flutter_initializer.dart:213:48)
E/flutter (19889) : E/flutter (19889) :
I/flutter (19889) : Duration : I/flutter (19889) : N/A I/flutter
(19889) : , bitrate : I/flutter (19889) : N/A I/flutter (19889) :
I/flutter (19889) : Stream #0:0 I/flutter (19889) : : Video : png,
rgba(pc), 412x771 I/flutter (19889) : , I/flutter (19889) : 25 fps,
I/flutter (19889) : 25 tbr, I/flutter (19889) : 25 tbn I/flutter
(19889) : E/flutter (19889) :
[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled
Exception : PlatformException(SESSION_NOT_FOUND, Session not found.,
null, null) E/flutter (19889) : #0
     
StandardMethodCodec.decodeEnvelope
(package:flutter/src/services/message_codecs.dart:648:7) E/flutter
(19889) : #1 MethodChannel._invokeMethod
(package:flutter/src/services/platform_channel.dart:334:18) E/flutter
(19889) : E/flutter (19889) : #2
     
FFmpegKitFactory.mapToNullableSession
(package:ffmpeg_kit_flutter_min_gpl/src/ffmpeg_kit_factory.dart:76:3)
E/flutter (19889) : E/flutter (19889) : #3
     
FFmpegKitInitializer._processCompleteCallbackEvent.
(package:ffmpeg_kit_flutter_min_gpl/src/ffmpeg_kit_flutter_initializer.dart:213:48)
E/flutter (19889) : E/flutter (19889) :
I/flutter (19889) : yzsFZWrI_Iw I/flutter (19889) : currentBc :
yzsFZWrI_Iw I/flutter (19889) : Stream mapping : I/flutter (19889) :
     
Stream #0:0 -> #0:0 I/flutter (19889) : (png (native) -> h264
(libx264)) I/flutter (19889) : I/flutter (19889) : Press [q] to stop,
[?] for help I/flutter (19889) : Stream mapping : I/flutter (19889) :
     
Stream #0:0 -> #0:0 I/flutter (19889) : (png (native) -> h264
(libx264)) I/flutter (19889) : I/flutter (19889) : Press [q] to stop,
[?] for help I/flutter (19889) : [libx264 @ 0xb4000073639665d0] using
cpu capabilities : ARMv8 NEON I/flutter (19889) : [libx264 @
0xb4000073639665d0] profile High 4:4:4 Predictive, level 3.0, 4:4:4,
8-bit I/flutter (19889) : [libx264 @ 0xb4000073639665d0] 264 - core 164

  


  


  

  • 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=4 threads=6
lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0
bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1
b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250
keyint_min=25 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 I/flutter (19889) : Output #0, flv, to
'rtmp ://x.rtmp.youtube.com/live2/x7k6-grm1-z15w-tqb7-akrt' : I/flutter
(19889) : Metadata : I/flutter (19889) : encoder :
I/flutter (19889) : Lavf60.3.100 I/flutter (19889) : I/flutter (19889) :
Stream #0:0 I/flutter (19889) : : Video : h264 ([7][0][0][0] / 0x0007),
yuv444p(tv, unknown/bt709/iec61966-2-1, progressive), 412x771, q=2-31
I/flutter (19889) : , I/flutter (19889) : 25 fps, I/flutter (19889) :
1k tbn I/flutter (19889) : I/flutter (19889) : Metadata : I/flutter
(19889) : encoder : I/flutter (19889) : Lavc60.3.100
libx264 I/flutter (19889) :