Recherche avancée

Sur d’autres sites (6337)

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

• Using GDIgrab in FFmpeg with dshow Audio produces black screen

  16 mars 2016, par Spreadys

  here is my command :

  ffmpeg -f gdigrab -framerate 25 -offset_x 10 -offset_y 10 -show_region 1 -draw_mouse 1 -video_size 1280x720 -i desktop -f dshow -i audio="Microphone (2- ATR USB microphone)" -r 25 -threads 4 -c:v libx264 -pix_fmt yuv422p -preset superfast -tune fastdecode -x264opts keyint=25:min-keyint=1 -crf 4 -c:a aac -profile:a aac_low -async 25 "C:\Users\david\Desktop\%output%.mp4"

  The gdigrab video works great when it is on its own (no audio). The audio works fine when it is on its own (no video). When I join the two commands to capture both together, as soon as I move a window within my capture area, the area goes black.

  In Windows 7, I used to get around this by stopping the desktop composition service prior to capture, (SC stop uxsms), but this is now not possible in Win10.

  I thought it may be something graphics card related.
  My main monitor is on an Nvidia card, with my second running from the onboard Intel. This is setup for Quicksync H264 playback and encoding with my NLE.

  I know that I could use a dshow screen capture driver such as UScreen but am trying to avoid that as I need the capture area to be specified each time from a simple batch.

  Any help appreciated to solve this black area problem- its driving me crazy !
  David

• video.js record timestamp blob is invalid after the first one [closed]

  10 octobre 2022, par Codengine

  I am building a video messaging service. I have used video.js and videojs record to record video and audio.

  


  I have used timeSlice option of record plugin to 2 second so every 2 second I get blobs which I cans save in server and then merge later.

  


  Everything is fine. I can get the blob and upload ins server.

  


  But the issue is - only the first blob is correct and othr blobs I cannot concate altogether. I have tried ffmpeg and opencv both to merge the videos in backend. Both says all but the first blob is incorrect.

  


  Need help on this. I have been strugging with this last few days with no solution yet.