Recherche avancée

Sur d’autres sites (3268)

• Introducing the Matomo Connector for Looker Studio (Formerly Google Data Studio)

  26 janvier 2024, par Erin — Community

  Explore Matomo data like never before with the official Matomo Connector for Looker Studio. Matomo users can now securely display accurate web analytics data in Looker Studio for free.

  Connect Matomo to Looker Studio (formerly known as Google Data Studio) in a few clicks and start building dashboards instantly. Get access to a range of data visualisation capabilities and chart types in Looker Studio’s easy-to-use interface. 

  Leave behind manual, error-prone spreadsheet entries and disparate data. With the Matomo Connector for Looker Studio, you get unified, automated reporting and interactive dashboards for faster insights and smoother collaboration.

  What sets the official Matomo Connector for Looker Studio apart ?

  Our open-source connector puts security first by providing a reliable connection without relying on third-party intermediaries. It’s free, with no hidden charges, and no limits on the number of users or Matomo instances. Connect as many instances as you need. 

  Plus, our Support team is here anytime you need help.

  

  Who is this connector made for ?

  The Matomo Connector for Looker Studio is a good fit for institutions and corporations using Looker Studio, NGOs handling multiple entities, marketing agencies with various clients, and small to medium-sized businesses with advanced data practices.

  When is this connector not the best fit ?

  If you prioritise privacy and compliance, this might not be the right fit. The Looker Studio app operates on Google servers, and while we don’t log or store any data, privacy considerations should be carefully evaluated. Transferring data, especially visitor data, to external platforms can have privacy implications.

  Getting started

  Check out our documentation for an easy setup.

  To help, we’ve also created a template report so you can visualise your Matomo data instantly.

  Here’s how to get started :

  1. Visit the demo template report in Looker Studio
  2. Click the more options button then Make a copy

  

  3. Click Create data source within the New Data Source dropdown.

  

  4. Connect your Matomo (Full Connection Guide)
  5. Select the API > Main Metrics report
  6. Click Connect and then Add to Report
  7. Click Copy Report to finalise

  For additional support, visit our Matomo Looker Studio forum or reach out to our Looker Studio support team via email at support-lookerstudio@matomo.org

• 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

• avfilter/vf_libplacebo : don't force dovi frames to bt.2020-ncl

  30 octobre 2023, par Niklas Haas

  avfilter/vf_libplacebo : don't force dovi frames to bt.2020-ncl
  This is at odds with the YUV matrix negotiation API, in which such
  
  dynamic changes in YUV encoding are no longer easily possible. There is
  
  also no really strong motivating reason to do this, since the choice of
  
  YUV matrix is essentially arbitrary and not actually related to the
  
  Dolby Vision decoding process.
  

  • [DH] libavfilter/vf_libplacebo.c