Recherche avancée

Sur d’autres sites (2468)

• How to successfully install avconv 9.12 on ubuntu 13.10 saucy ?

  14 mars 2014, par Justus Kenklies

  I have found several Instructions on how to install ffmpeg or avconv, but nothing worked for me. I am infact able to install avconv 0.8.x via apt-get, but the features I like to use (such as -start_number) are only available in younger versions.

  I would appreciate something like "take this binary, place it there, hack this into console and use it in any directory you want", but a fully functional compiler guide would also be okay.

  I followed this guide :
  How to compile avconv with libx264 on Ubuntu 12.04.?

  I was finally able to compile everything after hours of searching, but in the end it did not work at all.

• Is Google Analytics Accurate ? 6 Important Caveats

  8 novembre 2022, par Erin

  It’s no secret that accurate website analytics is crucial for growing your online business — and Google Analytics is often the go-to source for insights. 

  But is Google Analytics data accurate ? Can you fully trust the provided numbers ? Here’s a detailed explainer.

  How Accurate is Google Analytics ? A Data-Backed Answer 

  When properly configured, Google Analytics (Universal Analytics and Google Analytics 4) is moderately accurate for global traffic collection. That said : Google Analytics doesn’t accurately report European traffic. 

  According to GDPR provisions, sites using GA products must display a cookie consent banner. This consent is required to collect third-party cookies — a tracking mechanism for identifying users across web properties.

  Google Analytics (GA) cannot process data about the user’s visit if they rejected cookies. In such cases, your analytics reports will be incomplete.

  Cookie rejection refers to visitors declining or blocking cookies from ever being collected by a specific website (or within their browser). It immediately affects the accuracy of all metrics in Google Analytics.

  Google Analytics is not accurate in locations where cookie consent to tracking is legally required. Most consumers don’t like disruptive cookie banners or harbour concerns about their privacy — and chose to reject tracking. 

  This leaves businesses with incomplete data, which, in turn, results in : 

  • Lower traffic counts as you’re not collecting 100% of the visitor data. 
  • Loss of website optimisation capabilities. You can’t make data-backed decisions due to inconsistent reporting

  For the above reasons, many companies now consider cookieless website tracking apps that don’t require consent screen displays. 

  Why is Google Analytics Not Accurate ? 6 Causes and Solutions 

  A high rejection rate of cookie banners is the main reason for inaccurate Google Analytics reporting. In addition, your account settings can also hinder Google Analytics’ accuracy.

  If your analytics data looks wonky, check for these six Google Analytics accuracy problems. 

  You Need to Secure Consent to Cookies Collection 

  To be GDPR-compliant, you must display a cookie consent screen to all European users. Likewise, other jurisdictions and industries require similar measures for user data collection. 

  This is a nuisance for many businesses since cookie rejection undermines their remarketing capabilities. Hence, some try to maximise cookie acceptance rates with dark patterns. For example : hide the option to decline tracking or make the texts too small. 

  

  Sadly, not everyone’s treating users with respect. A joint study by German and American researchers found that only 11% of US websites (from a sample of 5,000+) use GDPR-compliant cookie banners.

  As a result, many users aren’t aware of the background data collection to which they have (or have not) given consent. Another analysis of 200,000 cookies discovered that 70% of third-party marketing cookies transfer user data outside of the EU — a practice in breach of GDPR.

  Naturally, data regulators and activities are after this issue. In April 2022, Google was pressured to introduce a ‘reject all’ cookies button to all of its products (a €150 million compliance fine likely helped with that). Whereas, noyb has lodged over 220 complaints against individual websites with deceptive cookie consent banners.

  The takeaway ? Messing up with the cookie consent mechanism can get you in legal trouble. Don’t use sneaky banners as there are better ways to collect website traffic statistics. 

  Solution : Try Matomo GDPR-Friendly Analytics 

  Fill in the gaps in your traffic analytics with Matomo – a fully GDPR-compliant product that doesn’t rely on third-party cookies for tracking web visitors. Because of how it is designed, the French data protection authority (CNIL) confirmed that Matomo can be used to collect data without tracking consent.

  With Matomo, you can track website users without asking for cookie consent. And when you do, we supply you with a compact, compliant, non-disruptive cookie banner design. 

  Your Google Tag Isn’t Embedded Correctly 

  Google Tag (gtag.js) is a web tracking script that sends data to your Google Analytics, Google Ads and Google Marketing Platform.

  A corrupted gtag.js installation can create two accuracy issues : 

  • Duplicate page tracking 
  • Missing script installation 

  Is there a way to tell if you’re affected ?

  Yes. You may have duplicate scripts installed if you have a very low bounce rate on most website pages (below 15% – 20%). The above can happen if you’re using a WordPress GA plugin and additionally embed gtag.js straight in your website code. 

  A tell-tale sign of a missing script on some pages is low/no traffic stats. Google alerts you about this with a banner : 

  

  Solution : Use Available Troubleshooting Tools 

  Use Google Analytics Debugger extension to analyse pages with low bounce rates. Use the search bar to locate duplicate code-tracking elements. 

  Alternatively, you can use Google Tag Assistant for diagnosing snippet install and troubleshooting issues on individual pages. 

  If the above didn’t work, re-install your analytics script. 

  Machine Learning and Blended Data Are Applied

  Google Analytics 4 (GA4) relies a lot on machine learning and algorithmic predictions.

  By applying Google’s advanced machine learning models, the new Analytics can automatically alert you to significant trends in your data. [...] For example, it calculates churn probability so you can more efficiently invest in retaining customers.

  Vidhya Srinivasan, VP of Measurement, Analytics and Buying Platforms at Google

  On the surface, the above sounds exciting. In practice, Google’s application of predictive algorithms means you’re not seeing actual data. 

  To offer a variation of cookieless tracking, Google algorithms close the gaps in reporting by creating models (i.e., data-backed predictions) instead of reporting on actual user behaviours. Therefore, your GA4 numbers may not be accurate.

  For bigger web properties (think websites with 1+ million users), Google also relies on data sampling — a practice of extrapolating data analytics, based on a data subset, rather than the entire dataset. Once again, this can lead to inconsistencies in reporting with some numbers (e.g., average conversion rates) being inflated or downplayed. 

  Solution : Try an Alternative Website Analytics App 

  Unlike GA4, Matomo reports consist of 100% unsampled data. All the aggregated reporting you see is based on real user data (not guesstimation). 

  Moreover, you can migrate from Universal Analytics (UA) to Matomo without losing access to your historical records. GA4 doesn’t yet have any backward compatibility.

  Spam and Bot Traffic Isn’t Filtered Out 

  Surprise ! 42% of all Internet traffic is generated by bots, of which 27.7% are bad ones.

  Good bots (aka crawlers) do essential web “housekeeping” tasks like indexing web pages. Bad bots distribute malware, spam contact forms, hack user accounts and do other nasty stuff. 

  A lot of such spam bots are designed specifically for web analytics apps. The goal ? Flood your dashboard with bogus data in hopes of getting some return action from your side. 

  Types of Google Analytics Spam :

  • Referral spam. Spambots hijack the referrer, displayed in your GA referral traffic report to indicate a page visit from some random website (which didn’t actually occur). 
  • Event spam. Bots generate fake events with free language entries enticing you to visit their website. 
  • Ghost traffic spam. Malicious parties can also inject fake pageviews, containing URLs that they want you to click. 

  Obviously, such spammy entities distort the real website analytics numbers. 

  Solution : Set Up Bot/Spam Filters 

  Google Analytics 4 has automatic filtering of bot traffic enabled for all tracked Web and App properties. 

  But if you’re using Universal Analytics, you’ll have to manually configure spam filtering. First, create a new view and then set up a custom filter. Program it to exclude :

  • Filter Field : Request URI
  • Filter Pattern : Bot traffic URL

  Once you’ve configured everything, validate the results using Verify this filter feature. Then repeat the process for other fishy URLs, hostnames and IP addresses. 

  You Don’t Filter Internal Traffic 

  Your team(s) spend a lot of time on your website — and their sporadic behaviours can impair your traffic counts and other website metrics.

  To keep your data “employee-free”, exclude traffic from : 

  • Your corporate IPs addresses 
  • Known personal IPs of employees (for remote workers) 

  If you also have a separate stage version of your website, you should also filter out all traffic coming from it. Your developers, contractors and marketing people spend a lot of time fiddling with your website. This can cause a big discrepancy in average time on page and engagement rates. 

  Solution : Set Internal Traffic Filters 

  Google provides instructions for excluding internal traffic from your reports using IPv4/IPv6 address filters. 

  

  Session Timeouts After 30 Minutes 

  After 30 minutes of inactivity, Google Analytics tracking sessions start over. Inactivity means no recorded interaction hits during this time. 

  Session timeouts can be a problem for some websites as users often pin a tab to check it back later. Because of this, you can count the same user twice or more — and this leads to skewed reporting. 

  Solution : Programme Custom Timeout Sessions

  You can codify custom cookie timeout sessions with the following code snippets : 

  • _setSessionCookieTimeout. Set a custom new session cookie timeout in milliseconds.
  • _setVisitorCookieTimeout. Sets a custom Google Analytics visitor cookie expiration time frame in milliseconds.

  Final Thoughts 

  Thanks to its scale and longevity, Google Analytics has some strong sides, but its data accuracy isn’t 100% perfect.

  The inability to capture analytics data from users who don’t consent to cookie tracking and data sampling applied to bigger web properties may be a deal-breaker for your business. 

  If that’s the case, try Matomo — a GDPR-compliant, accurate web analytics solution. Start your 21-day free trial now. No credit card required.

  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 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

  

• SIGSEV when loading ffmpeg library

  20 février 2014, par gookman

  I am trying to build ffmpeg for Android similar to AndroidFFmpeg.

  I have configured ffmpeg so that I have only what I need. My android_build.sh looks like
  this :

  #!/bin/bash
  
  
  
  if [ "$NDK" = "" ]; then
  
      echo NDK variable not set, exiting
  
      echo "Use: export NDK=/your/path/to/android-ndk"
  
      exit 1
  
  fi
  
  
  
  OS=`uname -s | tr '[A-Z]' '[a-z]'`
  
  function build_ffmpeg
  
  {
  
      PLATFORM=$NDK/platforms/$PLATFORM_VERSION/arch-$ARCH/
  
      CC=$PREBUILT/bin/$EABIARCH-gcc
  
      CROSS_PREFIX=$PREBUILT/bin/$EABIARCH-
  
      PKG_CONFIG=${CROSS_PREFIX}pkg-config
  
      if [ ! -f $PKG_CONFIG ];
  
      then
  
         cat > $PKG_CONFIG << EOF
  
  #!/bin/bash
  
  pkg-config \$*
  
  EOF
  
         chmod u+x $PKG_CONFIG
  
      fi
  
      NM=$PREBUILT/bin/$EABIARCH-nm
  
      cd ffmpeg
  
      export PKG_CONFIG_LIBDIR=$(pwd)/$PREFIX/lib/pkgconfig/
  
      export PKG_CONFIG_PATH=$(pwd)/$PREFIX/lib/pkgconfig/
  
      ./configure --target-os=linux \
  
          --prefix=$PREFIX \
  
          --enable-small \
  
          --enable-cross-compile \
  
          --extra-libs="-lgcc" \
  
          --arch=$ARCH \
  
          --cc=$CC \
  
          --cross-prefix=$CROSS_PREFIX \
  
          --nm=$NM \
  
          --sysroot=$PLATFORM \
  
          --extra-cflags=" -O3 -fpic -DANDROID -DHAVE_SYS_UIO_H=1 -Dipv6mr_interface=ipv6mr_ifindex -fasm -Wno-psabi -fno-short-enums  -fno-strict-aliasing -finline-limit=300 $OPTIMIZE_CFLAGS " \
  
          --disable-shared \
  
          --enable-static \
  
          --enable-runtime-cpudetect \
  
          --extra-ldflags="-Wl,-rpath-link=$PLATFORM/usr/lib -L$PLATFORM/usr/lib  -nostdlib -lc -lm -ldl -llog -L$PREFIX/lib" \
  
          --extra-cflags="-I$PREFIX/include" \
  
          --disable-everything \
  
          --enable-muxer=mp4 \
  
          --enable-protocol=file \
  
          --enable-decoder=mpeg4 \
  
          --enable-encoder=mpeg4 \
  
          --enable-avformat \
  
          --enable-avcodec \
  
          --enable-avresample \
  
          --enable-zlib \
  
          --disable-doc \
  
          --disable-ffplay \
  
          --disable-ffmpeg \
  
          --disable-ffplay \
  
          --disable-ffprobe \
  
          --disable-ffserver \
  
          --disable-avdevice \
  
          --enable-nonfree \
  
          --enable-version3 \
  
          --enable-memalign-hack \
  
          --enable-asm \
  
          $ADDITIONAL_CONFIGURE_FLAG \
  
          || exit 1
  
      make clean || exit 1
  
      make -j4 install || exit 1
  
  
  
      cd ..
  
  }
  
  
  
  function build_one {
  
      cd ffmpeg
  
      PLATFORM=$NDK/platforms/$PLATFORM_VERSION/arch-$ARCH/
  
      $PREBUILT/bin/$EABIARCH-ld -rpath-link=$PLATFORM/usr/lib -L$PLATFORM/usr/lib -L$PREFIX/lib  -soname $SONAME -shared -nostdlib  -z noexecstack -Bsymbolic --whole-archive --no-undefined -o $OUT_LIBRARY -lavcodec -lavformat -lavresample -lavutil -lc -lm -lz -ldl -llog --dynamic-linker=/system/bin/linker -zmuldefs $PREBUILT/lib/gcc/$EABIARCH/4.6/libgcc.a || exit 1
  
     cd ..
  
  }
  
  
  
  #arm v5
  
  EABIARCH=arm-linux-androideabi
  
  ARCH=arm
  
  CPU=armv5
  
  OPTIMIZE_CFLAGS="-marm -march=$CPU"
  
  PREFIX=../ffmpeg-build/armeabi
  
  OUT_LIBRARY=$PREFIX/libffmpeg.so
  
  ADDITIONAL_CONFIGURE_FLAG=
  
  SONAME=libffmpeg.so
  
  PREBUILT=$NDK/toolchains/arm-linux-androideabi-4.6/prebuilt/$OS-x86_64
  
  PLATFORM_VERSION=android-5
  
  build_ffmpeg
  
  build_one
  
  
  
  #arm v7vfpv3
  
  EABIARCH=arm-linux-androideabi
  
  ARCH=arm
  
  CPU=armv7-a
  
  OPTIMIZE_CFLAGS="-mfloat-abi=softfp -mfpu=vfpv3-d16 -marm -march=$CPU "
  
  PREFIX=../ffmpeg-build/armeabi-v7a
  
  OUT_LIBRARY=$PREFIX/libffmpeg.so
  
  ADDITIONAL_CONFIGURE_FLAG=
  
  SONAME=libffmpeg.so
  
  PREBUILT=$NDK/toolchains/arm-linux-androideabi-4.6/prebuilt/$OS-x86_64
  
  PLATFORM_VERSION=android-5
  
  build_ffmpeg
  
  build_one

  My Android.mk file looks like this :

  LOCAL_PATH := $(call my-dir)
  
  
  
  include $(CLEAR_VARS)
  
  LOCAL_MODULE := ffmpeg-prebuilt
  
  LOCAL_SRC_FILES := ffmpeg-build/$(TARGET_ARCH_ABI)/libffmpeg.so
  
  LOCAL_EXPORT_C_INCLUDES := ffmpeg-build/$(TARGET_ARCH_ABI)/include
  
  LOCAL_EXPORT_LDLIBS := ffmpeg-build/$(TARGET_ARCH_ABI)/libffmpeg.so
  
  LOCAL_PRELINK_MODULE := true
  
  include $(PREBUILT_SHARED_LIBRARY)
  
  
  
  include $(CLEAR_VARS)
  
  LOCAL_ALLOW_UNDEFINED_SYMBOLS=false
  
  LOCAL_MODULE    := native
  
  LOCAL_SRC_FILES := native.c
  
  LOCAL_LDLIBS := -llog
  
  LOCAL_C_INCLUDES := $(LOCAL_PATH)/ffmpeg-build/$(TARGET_ARCH_ABI)/include
  
  LOCAL_SHARED_LIBRARY := ffmpeg-prebuilt
  
  include $(BUILD_SHARED_LIBRARY)

  The actual code I am trying to use is very simple and looks like this :

  #include 
  
  #include <android></android>log.h>
  
  #include <libavcodec></libavcodec>avcodec.h>
  
  #include <libavformat></libavformat>avformat.h>
  
  
  
  static jint Java_dk_bendingspoons_clipstitch_VideoLoader_start(JNIEnv * env, jobject thiz, jstring path)
  
  {
  
      __android_log_print(ANDROID_LOG_VERBOSE, "native", "Before register all.");
  
      av_register_all();
  
  
  
      return 0;
  
  }

  The compilation of both ffmpeg and my code is without any errors. The problem is that when I am loading the library in Android it fails with the error : Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 27050. This leads me to believe that there is something that I am doing wrong when compiling.

  I should mention that I am compiling on Ubuntu 13.10 x64 with NDK-r9c-x86_64.

  How should I proceed in finding out what the issue is ?