Recherche avancée

Sur d’autres sites (9452)

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

• Compile FFMPEG + x264 - undefined references

  18 juin 2013, par Tishu

  I have been trying to find a solution online for a couple of days with no luck. I am using Ubuntu and trying to compile the latest FFMPEG stable version (1.0.1) with x264 support. I made sure I uninstalled any existing x264 then I downloaded the latest x264 source and compiled it with the following config :

  ./configure --prefix=$PREFIX \
  
      --enable-shared \
  
      --enable-static \
  
      --disable-gpac \
  
      --extra-cflags=" -I$ARM_INC -fPIC -DANDROID -fpic -mthumb-interwork -ffunction-sections -funwind-tables -fno-short-enums -D__ARM_ARCH_5__ -D__ARM_ARCH_5T__ -D__ARM_ARCH_5E__ -D__ARM_ARCH_5TE__ -Wno-psabi -march=armv5te -msoft-float -mthumb -Os -fomit-frame-pointer -fno-strict-aliasing -finline-limit=64 -DANDROID -Wa,--noexecstack -MMD -MP " \
  
      --extra-ldflags=" -nostdlib -Bdynamic -Wl,--no-undefined -Wl,-z,noexecstack -Wl,-z,nocopyreloc -Wl,-soname,/usr/lib/libz.so -Wl,-rpath-link=$ARM_LIB,-dynamic-linker=/system/bin/linker -L$ARM_LIB -lc -lm -ldl -lgcc" \
  
      --cross-prefix=${ARM_PRE}- \
  
      --disable-asm \
  
      --host=arm-linux \
  
  
  
      make clean
  
      make install

  All goes well, and I checked the installed version :

  x264 -V
  
      x264 0.129.x
  
      built on Dec 27 2012, gcc: 4.6.1
  
      configuration: --bit-depth=8 --chroma-format=all
  
      x264 license: GPL version 2 or later

  I then try to compile FFMPEG with the following options :

  ./configure --target-os=linux \
  
      --enable-libx264 \
  
      --enable-gpl \
  
      --prefix=$PREFIX \
  
      --extra-cflags="-I/home/tishu/Workspaces/ffmpeg/ffmpeg/jni/ffmpeg-1.0.1/android/armv7-a/include -I/home/tishu/Workspaces/ffmpeg/ffmpeg/jni/x264 -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 " \
  
      --extra-ldflags="-Wl,-rpath-link=$PLATFORM/usr/lib -L/home/tishu/Workspaces/ffmpeg/ffmpeg/jni/ffmpeg-1.0.1/android/armv7-a/lib -L$PLATFORM/usr/lib -nostdlib -lc -lm -ldl -llog" \
  
      --enable-cross-compile \
  
      --extra-libs="-lgcc" \
  
      --arch=arm \
  
      --cc=$PREBUILT/bin/arm-linux-androideabi-gcc \
  
      --cross-prefix=$PREBUILT/bin/arm-linux-androideabi- \
  
      --nm=$PREBUILT/bin/arm-linux-androideabi-nm \
  
      --sysroot=$PLATFORM \

  The configure and make clean/make install work well, but when I try to create the .so file the following command fails :

  /home/tishu/Apps/android-ndk-r8d/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-ld 
  
      -rpath-link=./android/armv7-a/usr/lib -L/home/tishu/Apps/android-ndk-r8d/platforms/android-14/arch-arm/usr/lib -soname libffmpeg.so -shared -nostdlib  -z,noexecstack -Bsymbolic \
  
      --whole-archive --no-undefined -o ./android/armv7-a/libffmpeg.so libavcodec/libavcodec.a libavformat/libavformat.a libavutil/libavutil.a libswscale/libswscale.a -lc -lm -lz -ldl -llog  \
  
      --warn-once \
  
      --dynamic-linker=/system/bin/linker /home/tishu/Apps/android-ndk-r8d/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/lib/gcc/arm-linux-androideabi/4.4.3/libgcc.a

  This fails with the following output :

  libavcodec/libavcodec.a(libx264.o): In function `X264_frame':
  
  /home/tishu/Workspaces/ffmpeg/ffmpeg/jni/ffmpeg-1.0.1/libavcodec/libx264.c:159: undefined reference to `x264_picture_init'
  
  /home/tishu/Workspaces/ffmpeg/ffmpeg/jni/ffmpeg-1.0.1/libavcodec/libx264.c:179: undefined reference to `x264_encoder_reconfig'
  
  /home/tishu/Workspaces/ffmpeg/ffmpeg/jni/ffmpeg-1.0.1/libavcodec/libx264.c:190: undefined reference to `x264_encoder_encode'
  
  /home/tishu/Workspaces/ffmpeg/ffmpeg/jni/ffmpeg-1.0.1/libavcodec/libx264.c:196: undefined reference to `x264_encoder_delayed_frames'
  
  libavcodec/libavcodec.a(libx264.o): In function `encode_nals':
  
  /home/tishu/Workspaces/ffmpeg/ffmpeg/jni/ffmpeg-1.0.1/libavcodec/libx264.c:101: undefined reference to `x264_bit_depth'
  
  libavcodec/libavcodec.a(libx264.o): In function `X264_close':
  
  /home/tishu/Workspaces/ffmpeg/ffmpeg/jni/ffmpeg-1.0.1/libavcodec/libx264.c:231: undefined reference to `x264_encoder_close'
  
  libavcodec/libavcodec.a(libx264.o): In function `X264_init':
  
  /home/tishu/Workspaces/ffmpeg/ffmpeg/jni/ffmpeg-1.0.1/libavcodec/libx264.c:284: undefined reference to `x264_param_default'
  
  /home/tishu/Workspaces/ffmpeg/ffmpeg/jni/ffmpeg-1.0.1/libavcodec/libx264.c:292: undefined reference to `x264_param_default_preset'
  
  /home/tishu/Workspaces/ffmpeg/ffmpeg/jni/ffmpeg-1.0.1/libavcodec/libx264.c:314: undefined reference to `x264_param_parse'
  
  /home/tishu/Workspaces/ffmpeg/ffmpeg/jni/ffmpeg-1.0.1/libavcodec/libx264.c:459: undefined reference to `x264_param_apply_fastfirstpass'
  
  /home/tishu/Workspaces/ffmpeg/ffmpeg/jni/ffmpeg-1.0.1/libavcodec/libx264.c:490: undefined reference to `x264_param_apply_profile'
  
  /home/tishu/Workspaces/ffmpeg/ffmpeg/jni/ffmpeg-1.0.1/libavcodec/libx264.c:533: undefined reference to `x264_encoder_open_129'
  
  /home/tishu/Workspaces/ffmpeg/ffmpeg/jni/ffmpeg-1.0.1/libavcodec/libx264.c:544: undefined reference to `x264_encoder_headers'

  The x264 version it is looking for (129) is the one installed and compiled succesfully with —eanable-shared. Obviously all compiles fine when I do not include libx64.

  Question : How can I specify the include path for the last command ? I tried adding the path to $PATH and also adding this as an argument with no luck : -I/home/tishu/Workspaces/ffmpeg/ffmpeg/jni/x264

  Thanks

• avcodec : add DFPWM1a codec

  8 mars 2022, par Jack Bruienne

  avcodec : add DFPWM1a codec
  From the wiki page (https://wiki.vexatos.com/dfpwm) :
  
  > DFPWM (Dynamic Filter Pulse Width Modulation) is an audio codec
  
  > created by Ben “GreaseMonkey” Russell in 2012, originally to be used
  
  > as a voice codec for asiekierka's pixmess, a C remake of 64pixels.
  
  > It is a 1-bit-per-sample codec which uses a dynamic-strength one-pole
  
  > low-pass filter as a predictor. Due to the fact that a raw DPFWM decoding
  
  > creates a high-pitched whine, it is often followed by some post-processing
  
  > filters to make the stream more listenable.
  It has recently gained popularity through the ComputerCraft mod for
  
  Minecraft, which added support for audio through this codec, as well as
  
  the Computronics expansion which preceeded the official support. These
  
  both implement the slightly adjusted 1a version of the codec, which is
  
  the version I have chosen for this patch.
  This patch adds a new codec (with encoding and decoding) for DFPWM1a.
  
  The codec sources are pretty simple : they use the reference codec with
  
  a basic wrapper to connect it to the FFmpeg AVCodec system.
  To clarify, the codec does not have a specific sample rate - it is
  
  provided by the container (or user), which is typically 48000, but has
  
  also been known to be 32768. The codec does not specify channel info
  
  either, and it's pretty much always used with one mono channel.
  
  However, since it appears that libavcodec expects both sample rate and
  
  channel count to be handled by either the codec or container, I have
  
  made the decision to allow multiple channels interleaved, which as far
  
  as I know has never been used, but it works fine here nevertheless. The
  
  accompanying raw format has a channels option to set this. (I expect
  
  most users of this will not use multiple channels, but it remains an
  
  option just in case.)
  This patch will be highly useful to ComputerCraft developers who are
  
  working with audio, as it is the standard format for audio, and there
  
  are few user-friendly encoders out there, and even fewer decoders. It
  
  will streamline the process for importing and listening to audio,
  
  replacing the need to write code or use tools that require very
  
  specific input formats.
  You may use the CraftOS-PC program (https://www.craftos-pc.cc) to test
  
  out DFPWM playback. To use it, run the program and type this command :
  
  "attach left speaker" Then run "speaker play <file.dfpwm>" for each file.
  
  The app runs in a sandbox, so files have to be transferred in first ;
  
  the easiest way to do this is to simply drag the file on the window.
  
  (Or copy files to the folder at https://www.craftos-pc.cc/docs/saves.)
  Sample DFPWM files can be generated with an online tool at
  
  https://music.madefor.cc. This is the current best way to encode DFPWM
  
  files. Simply drag an audio file onto the page, and it will encode it,
  
  giving a download link on the page.
  I've made sure to update all of the docs as per Developer§7, and I've
  
  tested it as per section 8. Test files encoded to DFPWM play correctly
  
  in ComputerCraft, and other files that work in CC are correctly decoded.
  
  I have also verified that corrupt files do not crash the decoder - this
  
  should theoretically not be an issue as the result size is constant with
  
  respect to the input size.
  Signed-off-by : Jack Bruienne <jackbruienne@gmail.com>
  

  • [DH] Changelog
  • [DH] MAINTAINERS
  • [DH] doc/general_contents.texi
  • [DH] libavcodec/Makefile
  • [DH] libavcodec/allcodecs.c
  • [DH] libavcodec/codec_desc.c
  • [DH] libavcodec/codec_id.h
  • [DH] libavcodec/dfpwmdec.c
  • [DH] libavcodec/dfpwmenc.c
  • [DH] libavcodec/utils.c
  • [DH] libavcodec/version.h