Recherche avancée

Sur d’autres sites (4493)

• Matomo Celebrates 15 Years of Building an Open-Source & Transparent Web Analytics Solution

  30 juin 2022, par Matthieu Aubry — About, Community
  &lt;script type=&quot;text/javascript&quot;&gt;<br />
       if ('function' === typeof window.playMatomoVideo){<br />
       window.playMatomoVideo(&quot;brand&quot;, &quot;#brand&quot;)<br />
       } else {<br />
       document.addEventListener(&quot;DOMContentLoaded&quot;, function() { window.playMatomoVideo(&quot;brand&quot;, &quot;#brand&quot;); });<br />
       }<br />
  &lt;/script&gt;

  Fifteen years ago, I realised that people (myself included) were increasingly integrating the internet into their everyday lives, and it was clear that it would only expand in the future. It was an exciting new world, but the amount of personal data shared online, level of tracking and lack of security was a growing concern. Google Analytics was just launched then and was already gaining huge traction – so data from millions of websites started flowing into Google’s database, creating what was then the biggest centralised database about people worldwide and their actions online.

  So as a young engineering student, I decided we needed to build an open source and transparent solution that could help make the internet more secure and private while still providing organisations with powerful insights. I aimed to create a win-win solution for businesses and their digital consumers.

  And in 2007, I started developing Matomo with the help from Scott Switzer and Jennifer Langdon (who offered me an internship and support).   

  All thanks to the Matomo Community

  We have reached significant milestones and made major changes over the last 15 years, but we wouldn’t be where we are today without the Matomo Community.

  So I would like to celebrate and thank the hundreds of volunteer developers who have donated their time to develop Matomo, the thousands of contributors who provided feedback to improve Matomo, the countless supportive forum members, our passionate team of 40 at Matomo, the numerous translators who have translated Matomo and the 1.5 million websites that choose Matomo as their analytics platform.

  

  Matomo has been a community effort built on the shoulders of many, and we will continue to work for you. 

  So let’s look at some milestones we have achieved over the last 15 years.

  Looking back on milestones in our timeline

  2007

  • Birth of Matomo
  • First alpha version released

  2008

  • Release first public 0.1.0 version

  2009

  • 50,000 websites use Matomo

  2010

  • Matomo first stable 1.0.0 released
  • Mobile app launched

  2011

  • Released Ecommerce Analytics, Custom Variables, First Party Cookies

  • Released Privacy control features (first of many privacy features to come !)

  2012

  • Released Log Analytics feature
  • 1 Million Downloads !
  • 300,000 websites worldwide use Matomo

  2013

  • Matomo is now available in 50 languages !
  • Matomo brand redesign

  2016

  • Released Roll-Up Reporting Premium Feature, Users Flow Premium Feature, White Label Premium Feature, A/B Testing Premium Feature, Media Analytics Premium Feature, Funnels Premium Feature and Activity Log Premium Feature 
  • On-Premise Premium Plugins now available on the Marketplace

  2017

  • Launched Matomo Cloud service 
  • Released Multi Channel Conversion Attribution Premium Feature, Custom Reports Premium Feature, Login Saml Premium Feature, WooCommerceAnalytics Premium Feature and Heatmap & Session Recording Premium Feature 

  2018

  • Piwik renamed to Matomo
  • New Matomo logo and Matomo.org website re-launch
  • Launch of Matomo Tag Manager
  • 10,000 stars on Github
  • GDPR comes into effect, and Matomo released new product features and published several new guides
  • 17 Matomo features videos published online
  • Reached thousands of paying customers, making the project sustainable and financially independent

  2019

  • 700,000 websites worldwide use Matomo
  • Google Analytics importer released

  2020

  • Matomo For WordPress goes live on the WP Marketplace !
  • Released Paid Advertising Performance Premium feature
  • 100 million On-Premise Plugins downloads on the marketplace (since the beginning)

  2021

  • 1,000,000 websites worldwide use Matomo
  • including 30,000 active Matomo for WordPress installations
  • Released SEO Web Vitals, Advertising Conversion Export and Tracking Spam Prevention feature

  2022

  • Released WP Statistics to Matomo importer

  Our efforts continue

  While we’ve seen incredible growth over the years, our work doesn’t stop there. In fact, we’re only just getting started.

  Today over 55% of the internet continues to use privacy-threatening web analytics solutions, while 1.5% uses Matomo. So there are still great strides to be made to create a more private internet, and joining the Matomo Community is one way to support this movement.

  There are many ways to get involved too, such as :

  • Submitting feature requests
  • Developing for Matomo 
  • Leaving Matomo a review on sites like Capterra, TrustRadius, G2 Crowd, alternativeTo, SaaSworthy, Siftery, Open Hub
  • Translating Matomo
  • Joining our Security Bug Bounty Programme
  • Sharing Matomo with your peers
  • Talking about Matomo on social platforms

  So what comes next for Matomo ?

  The future of Matomo is approachable, powerful and flexible. We’re strengthening the customers’ voice, expanding our resources internally (we’re continuously hiring !) and conducting rigorous customer research to craft a tool that balances usability and functionality.

  I look forward to the next 15 years and seeing what the future holds for Matomo and our community.

• Google Analytics Privacy Issues : Is It Really That Bad ?

  2 juin 2022, par Erin

  If you find yourself asking : “What’s the deal with Google Analytics privacy ?”, you probably have some second thoughts. 

  Your hunch is right. Google Analytics (GA) is a popular web analytics tool, but it’s far from being perfect when it comes to respecting users’ privacy. 

  This post helps you understand tremendous Google Analytics privacy concerns users, consumers and regulators expressed over the years.

  In this blog, we’ll cover :

  What Does Google Analytics Collect About Users ? 

  To understand Google Analytics privacy issues, you need to know how Google treats web users’ data. 

  By default, Google Analytics collects the following information : 

  • Session statistics — duration, page(s) viewed, etc. 
  • Referring website details — a link you came through or keyword used. 
  • Approximate geolocation — country, city. 
  • Browser and device information — mobile vs desktop, OS usage, etc. 

  Google obtains web analytics data about users via two means : an on-site Google Analytics tracking code and cookies.

  A cookie is a unique identifier (ID) assigned to each user visiting a web property. Each cookie stores two data items : unique user ID and website name. 

  With the help of cookies, web analytics solutions can recognise returning visitors and track their actions across the website(s).

  

  • First party cookies are generated by one website and collect user behaviour data from said website only. 
  • Third-party cookies are generated by a third-party website object (for example, an ad) and can track user behaviour data across multiple websites. 

  As it’s easy to imagine, third-party cookies are a goldmine for companies selling online ads. Essentially, they allow ad platforms to continue watching how the user navigates the web after clicking a certain link. 

  Yet, people have little clue as to which data they are sharing and how it is being used. Also, user consent to tracking across websites is only marginally guaranteed by existing Google Analytics controls. 

  Why Third-Party Cookie Data Collection By GA Is Problematic 

  Cookies can transmit personally identifiable information (PII) such as name, log in details, IP address, saved payment method and so on. Some of these details can end up with advertisers without consumers’ direct knowledge or consent.

  Regulatory frameworks such as General Data Protection Regulation (GDPR) in Europe and California Consumer Privacy Act (CCPA) emerged as a response to uncontrolled user behaviour tracking.

  Under regulatory pressure, Big Tech companies had to adapt their data collection process.

  Apple was the first to implement by-default third-party blocking in the Safari browser. Then added a tracking consent mechanism for iPhone users starting from iOS 15.2 and later. 

  Google, too, said it would drop third-party cookie usage after The European Commission and UK’s Competition and Markets Authority (CMA) launched antitrust investigations into its activity. 

  To shake off the data watchdogs, Google released a Privacy Sandbox — a set of progressive tech, operational and compliance changes for ensuring greater consumer privacy. 

  Google’s biggest promise : deprecate third-party cookies usage for all web and mobile products. 

  Originally, Google promised to drop third-party cookies by 2022, but that didn’t happen. Instead, Google delayed cookie tracking depreciation for Chrome until the second half of 2023. 

  Why did they push back on this despite hefty fines from regulators ?

  Because online ads make Google a lot of money.

  In 2021, Alphabet Inc (parent company of Google), made $256.7 billion in revenue, of which $209.49 billion came from selling advertising. 

  Lax Google Analytics privacy enforcement — and its wide usage by website owners — help Google make those billions from collecting and selling user data. 

  How Google Uses Collected Google Analytics Data for Advertising 

  Over 28 million websites (or roughly 85% of the Internet) have Google Analytics tracking codes installed. 

  Even if one day we get a Google Analytics version without cookies, it still won’t address all the privacy concerns regulators and consumers have. 

  Over the years, Google has accumulated an extensive collection of user data. The company’s engineers used it to build state-of-the-art deep learning models, now employed to build advanced user profiles. 

  Deep learning is the process of training a machine to recognise data patterns. Then this “knowledge” is used to produce highly-accurate predictive insights. The more data you have for model training — the better its future accuracy will be. 

  Google has amassed huge deposits of data from its collection of products — GA, YouTube, Gmail, Google Docs and Google Maps among others. Now they are using this data to build a third-party cookies-less alternative mechanism for modelling people’s preferences, habits, lifestyles, etc. 

  Their latest model is called Google Topics. 

  This comes only after Google’s failed attempt to replace cookie-based training with Federated Learning of Cohorts (FLoC) model. But the solution wasn’t offering enough user transparency and user controls among other issues.

  

  Google Topics promises to limit the granularity of data advertisers get about users. 

  But it’s still a web user surveillance method. With Google Topics, the company will continue collecting user data via Chrome (and likely other Google products) — and share it with advertisers. 

  Because as we said before : Google is in the business of profiting off consumers’ data. 

  Two Major Ways Google Takes Advantage of Customer Data

  Every bit of data Google collects across its ecosystem of products can be used in two ways :

  • For ad targeting and personalisation 
  • To improve Google’s products 

  The latter also helps the former. 

  Advanced Ad Personalisation and Targeting

  GA provides the company with ample data on users’ 

  • Recent and frequent searches 
  • Location history
  • Visited websites
  • Used apps 
  • Videos and ads viewed 
  • Personal data like age or gender 

  The company’s privacy policy explicitly states that :
  

  

  Google also admits to using collected data to “measure the effectiveness of advertising” and “personalise content and ads you see on Google.” 

  But there are no further elaborations on how exactly customers’ data is used — and what you can do to prevent it from being shared with third parties. 

  In some cases, Google also “forgets” to inform users about its in-product tracking.

  Journalists from CNBC and The New York Times independently concluded that Google monitors users’ Gmail activity. In particular, the company scans your inbox for recent purchases, trips, flights and bills notifications. 

  While Google says that this information isn’t sold to advertisers (directly), they still may use the “saved information about your orders in other Google services”. 

  Once again, this means you have little control or knowledge of subsequent data usage. 

  Improving Product Usability 

  Google has many “arms” to collect different data points — from user’s search history to frequently-travelled physical routes. 

  They also reserve the right to use these insights for improving existing products. 

  Here’s what it means : by combining different types of data points obtained from various products, Google can pierce a detailed picture of a person’s life. Even if such user profile data is anonymised, it is still alarmingly accurate. 

  Douglas Schmidt, a computer science researcher at Vanderbilt University, well summarised the matter : 

  “[Google’s] business model is to collect as much data about you as possible and cross-correlate it so they can try to link your online persona with your offline persona. This tracking is just absolutely essential to their business. ‘Surveillance capitalism’ is a perfect phrase for it.”

  Google Data Collection Obsession Is Backed Into Its Business Model 

  OK, but Google offers some privacy controls to users ? Yes. Google only sees and uses the information you voluntarily enter or permit them to access. 

  But as the Washington Post correspondent points out :

  “[Big Tech] companies get to set all the rules, as long as they run those rules by consumers in convoluted terms of service that even those capable of decoding the legalistic language rarely bother to read. Other mechanisms for notice and consent, such as opt-outs and opt-ins, create similar problems. Control for the consumer is mostly an illusion.”

  Google openly claims to be “one of many ad networks that personalise ads based on your activity online”. 

  The wrinkle is that they have more data than all other advertising networks (arguably combined). This helps Google sell high-precision targeting and contextually personalised ads for billions of dollars annually.

  Given that Google has stakes in so many products — it’s really hard to de-Google your business and minimise tracking and data collection from the company.
  

  They are also creating a monopoly on data collection and ownership. This fact makes regulators concerned. The 2021 antitrust lawsuit from the European Commission says : 

  “The formal investigation will notably examine whether Google is distorting competition by restricting access by third parties to user data for advertising purposes on websites and apps while reserving such data for its own use.”

  In other words : By using consumer data to its unfair advantage, Google allegedly shuts off competition.

  But that’s not the only matter worrying regulators and consumers alike. Over the years, Google also received numerous other lawsuits for breaching people’s privacy, over and over again. 

  Here’s a timeline : 

  • 2019 : UK citizens issued a class action suit against Google for imposing cookies to override users’ privacy settings in the Safari browser. 
  • 2020 : US citizens pushed for a $5 billion class-action suit for tracking their activity through browsers set in “private” mode.
  • 2022 : Another class-action lawsuit in the US for deceptive privacy controls and unconsented location data tracking by Google mobile apps. 
  • 2022 : Google reached a $100 million class-action settlement for breaching Illinois biometrics privacy laws in Google Photos. 

  Separately, Google has a very complex history with GDPR compliance. 

  How Google Analytics Contributes to the Web Privacy Problem 

  Google Analytics is the key puzzle piece that supports Google’s data-driven business model. 

  If Google was to release a privacy-focused Google Analytics alternative, it’d lose access to valuable web users’ data and a big portion of digital ad revenues. 

  Remember : Google collects more data than it shares with web analytics users and advertisers. But they keep a lot of it for personal usage — and keep looking for ways to share this intel with advertisers (in a way that keeps regulators off their tail).

  For Google Analytics to become truly ethical and privacy-focused, Google would need to change their entire revenue model — which is something they are unlikely to do.

  Where does this leave Google Analytics users ? 

  In a slippery territory. By proxy, companies using GA are complicit with Google’s shady data collection and usage practice. They become part of the problem.

  In fact, Google Analytics usage opens a business to two types of risks : 

  • Reputational. 77% of global consumers say that transparency around how data is collected and used is important to them when interacting with different brands. That’s why data breaches and data misuse by brands lead to major public outrages on social media and boycotts in some cases. 
  • Legal. EU regulators are on a continuous crusade against Google Analytics 4 (GA4) as it is in breach of GDPR. French and Austrian watchdogs ruled the “service” illegal. Since Google Analytics is not GDPR compliant, it opens any business using it to lawsuits (which is already happening).

  But there’s a way out.

  Choose a Privacy-Friendly Google Analytics Alternative 

  Google Analytics is a popular web analytics service, but not the only one available. You have alternatives such as Matomo. 

  Our guiding principle is : respecting privacy.

  Unlike Google Analytics, we leave data ownership 100% in users’ hands. Matomo lets you implement privacy-centred controls for user data collection.

  Plus, you can self-host Matomo On-Premise or choose Matomo Cloud with data securely stored in the EU and in compliance with GDPR.

  The best part ? You can try our ethical alternative to Google Analytics for free. No credit card required ! Start your free 21-day trial now. 

  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 hereby accept the terms and conditions and the data processing agreeement (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

  

• Android FFMPEG video editing operation failed

  30 mai 2022, par Bipin Vayalu

  I am using FFMPEG in my Android app for video cropping and trimming but when I execute the following command on a specific video. FFMPEG command execution failed and the app crashed.

  


  Command :

  


  ffmpeg -y -i "/storage/emulated/0/DCIM/Camera/Test-Video.mp4" -crf 19 -color_primaries 1 -color_trc 1 -colorspace 1 -vcodec h264 -acodec aac -ss 00:00:00 -t 00:00:15 -async 1 -vf "crop=540:539:0:0:exact=0 , scale='if(gt(iw,ih),min(640,iw),-2)':'if(gt(iw,ih),-2,min(640,ih))'" "/data/user/0/com.bipin.myapp/cache/Test-Video_16535454525974982000318197164476.mp4"


  


  Failure logs :

  


  2022-05-26 11:40:52.605 5308-9484/com.bipin.myapp D/[RxCachedThreadScheduler-11;FFmpegUtil#performVideoOperation:151]: Debug - performVideoOperation - Source File: Test-Video.mp4, size: 9.697972297668457 MBs
2022-05-26 11:40:52.605 5308-9484/com.bipin.myapp D/[RxCachedThreadScheduler-11;FFmpegUtil#performVideoOperation:159]: Debug - performVideoOperation - Command: -y -i "/storage/emulated/0/DCIM/Camera/Test-Video.mp4" -crf 19 -color_primaries 1 -color_trc 1 -colorspace 1 -vcodec h264 -acodec aac -ss 00:00:00 -t 00:00:15 -async 1 -vf "crop=540:539:0:0:exact=0 , scale='if(gt(iw,ih),min(640,iw),-2)':'if(gt(iw,ih),-2,min(640,ih))'" "/data/user/0/com.bipin.myapp/cache/Test-Video_16535454525974982000318197164476.mp4"
2022-05-26 11:40:52.607 5308-9484/com.bipin.myapp I/mobile-ffmpeg: Loading mobile-ffmpeg.
2022-05-26 11:40:52.617 5308-9484/com.bipin.myapp I/mobile-ffmpeg: Loaded mobile-ffmpeg-min-gpl-arm64-v8a-4.4-lts-20200724.
2022-05-26 11:40:52.619 5308-9485/com.bipin.myapp D/mobile-ffmpeg: Callback thread started.
2022-05-26 11:40:52.620 5308-9485/com.bipin.myapp I/mobile-ffmpeg: ffmpeg version v4.4-dev-416
2022-05-26 11:40:52.620 5308-9485/com.bipin.myapp I/mobile-ffmpeg:  Copyright (c) 2000-2020 the FFmpeg developers
2022-05-26 11:40:52.620 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.620 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   built with Android (6454773 based on r365631c2) clang version 9.0.8 (https://android.googlesource.com/toolchain/llvm-project 98c855489587874b2a325e7a516b99d838599c6f) (based on LLVM 9.0.8svn)
2022-05-26 11:40:52.620 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   configuration: --cross-prefix=aarch64-linux-android- --sysroot=/files/android-sdk/ndk/21.3.6528147/toolchains/llvm/prebuilt/linux-x86_64/sysroot --prefix=/home/taner/Projects/mobile-ffmpeg/prebuilt/android-arm64/ffmpeg --pkg-config=/usr/bin/pkg-config --enable-version3 --arch=aarch64 --cpu=armv8-a --cc=aarch64-linux-android21-clang --cxx=aarch64-linux-android21-clang++ --extra-libs='-L/home/taner/Projects/mobile-ffmpeg/prebuilt/android-arm64/cpu-features/lib -lndk_compat' --target-os=android --enable-neon --enable-asm --enable-inline-asm --enable-cross-compile --enable-pic --enable-jni --enable-optimizations --enable-swscale --enable-shared --enable-v4l2-m2m --disable-outdev=fbdev --disable-indev=fbdev --enable-small --disable-openssl --disable-xmm-clobber-test --disable-debug --enable-lto --disable-neon-clobber-test --disable-programs --disable-postproc --disable-doc --disable-htmlpages --disable-manpages --disable-podpages --disable-txtpages --disable-static --disable-sndio --disable-schannel --disable-securetransport --disable-xlib --disable-cuda --disable-cuvid --disable-nvenc --disable-vaapi --disable-vdpau --disable-videotoolbox --disable-audiotoolbox --disable-appkit --disable-alsa --disable-cuda --disable-cuvid --disable-nvenc --disable-vaapi --disable-vdpau --enable-libx264 --enable-gpl --enable-libxvid --enable-gpl --enable-libx265 --enable-gpl --enable-libvidstab --enable-gpl --disable-sdl2 --enable-zlib --enable-mediacodec
2022-05-26 11:40:52.621 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   libavutil      56. 55.100 / 56. 55.100
2022-05-26 11:40:52.621 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   libavcodec     58. 96.100 / 58. 96.100
2022-05-26 11:40:52.621 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   libavformat    58. 48.100 / 58. 48.100
2022-05-26 11:40:52.622 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   libavdevice    58. 11.101 / 58. 11.101
2022-05-26 11:40:52.622 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   libavfilter     7. 87.100 /  7. 87.100
2022-05-26 11:40:52.622 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   libswscale      5.  8.100 /  5.  8.100
2022-05-26 11:40:52.622 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   libswresample   3.  8.100 /  3.  8.100
2022-05-26 11:40:52.638 5308-5308/com.bipin.myapp D/InputMethodManager: startInputInner - Id : 0
2022-05-26 11:40:52.638 5308-5308/com.bipin.myapp I/InputMethodManager: startInputInner - mService.startInputOrWindowGainedFocus
2022-05-26 11:40:52.645 5308-9485/com.bipin.myapp I/mobile-ffmpeg: Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/storage/emulated/0/DCIM/Camera/Test-Video.mp4':
2022-05-26 11:40:52.645 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   Metadata:
2022-05-26 11:40:52.645 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     major_brand     : 
2022-05-26 11:40:52.646 5308-9485/com.bipin.myapp I/mobile-ffmpeg: mp42
2022-05-26 11:40:52.646 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.646 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     minor_version   : 
2022-05-26 11:40:52.646 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 1
2022-05-26 11:40:52.646 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.646 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     compatible_brands: 
2022-05-26 11:40:52.646 5308-9485/com.bipin.myapp I/mobile-ffmpeg: isommp41mp42
2022-05-26 11:40:52.646 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.646 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     creation_time   : 
2022-05-26 11:40:52.646 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 2022-04-05T14:20:18.000000Z
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   Duration: 
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 00:00:15.48
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: , start: 
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 0.000000
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: , bitrate: 
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 5255 kb/s
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     Stream #0:0
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: (und)
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: : Video: h264 (avc1 / 0x31637661), yuv420p(tv, bt709), 540x960, 5251 kb/s
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: , 
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 30.04 fps, 
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 30 tbr, 
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 600 tbn, 
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 1200 tbc
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg:  (default)
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     Metadata:
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg:       creation_time   : 
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 2022-04-05T14:20:18.000000Z
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg:       handler_name    : 
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg: Core Media Video
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg: Stream mapping:
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   Stream #0:0 -> #0:0
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg:  (h264 (native) -> h264 (libx264))
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg: Press [q] to stop, [?] for help
2022-05-26 11:40:52.673 5308-9485/com.bipin.myapp W/mobile-ffmpeg: [graph 0 input from stream 0:0 @ 0xb400007bf58e0ed0] sws_param option is deprecated and ignored
2022-05-26 11:40:52.674 5308-9485/com.bipin.myapp I/mobile-ffmpeg: [libx264 @ 0xb400007c65974720] using cpu capabilities: ARMv8 NEON
2022-05-26 11:40:52.678 5308-9485/com.bipin.myapp I/mobile-ffmpeg: [libx264 @ 0xb400007c65974720] profile High, level 3.0, 4:2:0, 8-bit
2022-05-26 11:40:52.678 5308-9485/com.bipin.myapp I/mobile-ffmpeg: [libx264 @ 0xb400007c65974720] 264 - core 160 - H.264/MPEG-4 AVC codec - Copyleft 2003-2020 - 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=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=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=19.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
2022-05-26 11:40:52.678 5308-9485/com.bipin.myapp I/mobile-ffmpeg: Output #0, mp4, to '/data/user/0/com.bipin.myapp/cache/Test-Video_16535454525974982000318197164476.mp4':
2022-05-26 11:40:52.678 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   Metadata:
2022-05-26 11:40:52.678 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     major_brand     : 
2022-05-26 11:40:52.678 5308-9485/com.bipin.myapp I/mobile-ffmpeg: mp42
2022-05-26 11:40:52.678 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.678 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     minor_version   : 
2022-05-26 11:40:52.678 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 1
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     compatible_brands: 
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg: isommp41mp42
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     encoder         : 
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg: Lavf58.48.100
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     Stream #0:0
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg: (und)
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg: : Video: h264 (libx264) (avc1 / 0x31637661), yuv420p(bt709), 540x538, q=-1--1
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg: , 
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 30 fps, 
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 15360 tbn, 
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 30 tbc
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg:  (default)
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     Metadata:
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg:       creation_time   : 
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 2022-04-05T14:20:18.000000Z
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg:       handler_name    : 
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg: Core Media Video
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg:       encoder         : 
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg: Lavc58.96.100 libx264
2022-05-26 11:40:52.681 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.681 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     Side data:
2022-05-26 11:40:52.681 5308-9485/com.bipin.myapp I/mobile-ffmpeg:       
2022-05-26 11:40:52.681 5308-9485/com.bipin.myapp I/mobile-ffmpeg: cpb: 
2022-05-26 11:40:52.682 5308-9485/com.bipin.myapp I/mobile-ffmpeg: bitrate max/min/avg: 0/0/0 buffer size: 0 
2022-05-26 11:40:52.684 5308-9485/com.bipin.myapp I/mobile-ffmpeg: vbv_delay: N/A
2022-05-26 11:40:52.684 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.797 5308-5308/com.bipin.myapp D/[main;BaseDaggerFragment#onDestroyView:90]: Debug - PostMediaTabFragment onDestroyView called
2022-05-26 11:40:52.798 5308-5308/com.bipin.myapp D/[main;ViewBindingBaseFragment#onDestroyView:32]: Debug - PostMediaTabFragment onDestroyView called
2022-05-26 11:40:52.895 5308-9521/com.bipin.myapp A/libc: Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xb400007a53e6d000 in tid 9521 (RxCachedThreadS), pid 5308 (com.bipin.myapp)
2022-05-26 11:40:54.302 9524-9524/? A/DEBUG: Cmdline: com.bipin.myapp
2022-05-26 11:40:54.302 9524-9524/? A/DEBUG: pid: 5308, tid: 9521, name: RxCachedThreadS  >>> com.bipin.myapp <<<
2022-05-26 11:40:54.302 9524-9524/? A/DEBUG:       #00 pc 000000000058b8d0  /data/app/~~QE7_ItG7A3ZSxt4PIZf-2w==/com.bipin.myapp-o6_afbhi9zItP6DEnUAd6w==/base.apk!libavcodec.so
2022-05-26 11:40:54.398 1189-1447/? W/ActivityManager: Missing app error report, app = com.bipin.myapp crashing = true notResponding = false
2022-05-26 11:40:54.407 1189-9530/? W/ActivityManager: crash : com.bipin.myapp,10342