Recherche avancée

Sur d’autres sites (6180)

• Announcing Long Term Support in Piwik 2 – The analytics platform for your mission critical projects

  11 janvier 2016, par Matthieu Aubry — About, Development

  We are proud to announce our Long Term Support (LTS) for Piwik 2.X !

  Why Long Term Support (LTS) ?

  Part of our mission is to ready Piwik for the enterprise — and ready the enterprise for Piwik. Our fast release cycle and our ability to quickly innovate has served us well for the past seven years and has lead Piwik to being one of the most popular open source projects, used by over one million websites worldwide. But Piwik’s success today has also shown us that this fast release cycle is not suited for all users and customers. Like most large open source projects (such as Ubuntu, Firefox, Debian, Symfony, Node.js, etc.) at Piwik we now also offer a Long Term Support release which gives users the confidence that Piwik can be used for mission critical projects for months to come.

  What does LTS mean for Piwik ?

  For the duration of the LTS period, Piwik 2.X will continue to receive the following fixes :

  • Critical bugs causing data loss or data corruption.
  • Major and Critical security issues.

  Our goal is to offer you a Piwik LTS release that you can trust for all your mission critical projects.

  How long will Piwik 2.X be supported ?

  Piwik 2.X will be supported for at least 12 months after the initial release of Piwik 3.0.0.
  Piwik 3.0.0 is expected to be released in the second half of 2016.
  This means that Piwik 2.X will be supported at least until the second half of 2017.

  Which Piwik version is LTS ?

  The latest Piwik 2.16.X release is our Long Term Support version.

  How do I benefit from the LTS version ?

  To get the full benefits of Piwik LTS, please make sure you are using the latest LTS version. First, update to the latest Piwik 2.X version, then Configure Piwik to use the LTS release channel and then update to the latest LTS version.

  How do I configure Piwik to use the LTS version ?

  By default, Piwik will not use the LTS version. When you use the one-click update your Piwik instance will be updated to the very latest release : when Piwik 3.0.0 will be released, the one click update will update your instance to 3.0.0. It is however possible to configure your Piwik so that you will stay on Piwik 2.X and keep using the LTS Long Term Support version :

  • Login Piwik as the Super User,
  • Go to Settings > General > Update settings,
  • Under “Release channel” click “Latest stable 2.X Long Term Support version”, and click “Save”.
    

  How do I get professional Piwik Support ?

  If you need professional support for your Piwik service get in touch with the Piwik PRO experts.

  ---

  For other questions, feedback or discussion, feel free to join our forums and comment on this LTS forum post.

  We wish you all a fantastic year 2016 !

• avcodec/hevcdec : Pass HEVCLocalContext when slice-threading

  30 juin 2022, par Andreas Rheinhardt

  avcodec/hevcdec : Pass HEVCLocalContext when slice-threading
  The HEVC decoder has both HEVCContext and HEVCLocalContext
  
  structures. The latter is supposed to be the structure
  
  containing the per-slicethread state.
  Yet that is not how it is handled in practice : Each HEVCLocalContext
  
  has a unique HEVCContext allocated for it and each of these
  
  coincides except in exactly one field : The corresponding
  
  HEVCLocalContext. This makes it possible to pass the HEVCContext
  
  everywhere where logically a HEVCLocalContext should be used.
  This commit stops doing this for lavc/hevcdec.c itself.
  
  It also constifies what can be constified in order to make
  
  the nonconst stuff stand out more.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
  

  • [DH] libavcodec/hevcdec.c

• Randomly silencing part of input audio in real time

  3 septembre 2021, par Nobody

  My machine is running Ubuntu 20 LTS. I want to manipulate the input live audio in real-time. I have achieved pitch shifting using sox. The command being -

  


   sox -t pulseaudio default -t pulseaudio null pitch +1000


  


  and then routing the audio from "Monitor of Nullsink" .

  


  What I actually want to do is, silence randomized parts of the input audio, with a range. What I mean is, randomly mute 1-2s of the input audio.

  


  The final goal of this project will be to write a script that manipulates my voice and makes it seems like my network is bad.

  


  There is no restriction in method of achieving. That is we may use any language, make an extension, directly manipulate the input audio with sox, ffmpeg etc. Anything goes.