Recherche avancée

Sur d’autres sites (11679)

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

• Discovering our premium on-premise features

  28 novembre 2023, par Erin — Community, Plugins

  In our latest release (Matomo 4.16), we’ve enhanced visibility to the premium On-Premise features within Matomo. Now, it’s easier to maximise the potential of your Matomo On-Premise setup while also supporting our open-source project.

  By default, Matomo On-Premise instances will now display available premium features in the left-menu navigation bar. If you prefer, we’ve made it easy to hide or disable the menu items (steps provided below). Note that no features were removed and you still have full access to the same features as before.

  We would encourage you to check out our premium features, as thousands of users already find them powerful additions to their analytics.

  How to hide or disable menu items

  We understand that not everyone will need these premium features listed in their left-menu navigation. That’s why we’ve made it very easy to remove them. 

  • If you prefer not to see these features listed, each user can hide them by clicking the link “hide this section”. This option is available in each of the new feature pages.
  • Alternatively, for administrators wanting to disable these features at an organisational level and for all users at once, you simply need to follow these steps :
    • Login as Super User (to your On-Premise Matomo instance)
    • Go to Administration > System > Plugins
    • Scroll down to the “ProfessionalServices” plugin, and click “Deactivate”

  The revenue from premium features helps us innovate and improve Matomo, fueling our strong commitment to the open-source ethos that’s at the heart of everything we do.

  Explore the complete range of Matomo On-Premise premium features, developed by Matomo and our passionate community, available in our marketplace. Start a 30-day free trial today and unlock a new level of analytics excellence.

• Prevent FFmpeg from closing when a named pipe has been read completely

  21 octobre 2019, par Werther Berselli

  I’m doing a C++ application for a university project that takes a video file (e.g. matroska) and using FFmpeg (embedding commands inside std::system() instructions) apply these steps :

  • Extract chunks of frames (e.g. 10 seconds per chunk) and chunks of .aac audio

  • Apply some filters to frames

  • Encode video chunk and audio chunk with x264 and send it to a listening client using RTSP. This step is achieved using two named pipes, one for video and one for audio.

  • Receive the stream into another process and play it using ffplay (on localhost or lan).

  I need to divide my stream in chunks because I need eventually to satisfy real-time constraints, so I can’t apply filters before to my entire input video file and only then start streaming to client.
  My primary problem here is that once FFmpeg has emptied the two pipes, it close ; but other chunks of video and audio have still to be piped and streamed. I need FFmpeg to listen to the pipes waiting for new data.

  In bash I achieved this with the following commands.

  Start to listen in a prompt for a RTSP stream :

  ffplay -rtsp_flags listen rtsp://127.0.0.1@127.0.0.1:8090

  Create a video named pipe and an audio named pipe :

  mkfifo video_pipe
  
  mkfifo audio_pipe

  Use this command to prevent FFmpeg to close when video pipe is emptied :

  exec 7<>video_pipe

  (it is sufficient to apply it to the pipe video and neither will the audio pipe give problems)

  Activate FFmpeg command

  ffmpeg -probesize 2147483647 -re -s 1280x720 -pix_fmt rgb24 -i pipe:0 -vsync 0 -i audio_pipe -r 25 -vcodec libx264 -crf 23 -preset ultrafast -f rtsp -rtsp_transport tcp rtsp://127.0.0.1@127.0.0.1:8090 < video_pipe

  And then feed the pipes in another prompt :

  cat audiochunk.aac > audio_pipe & cat frame*.bmp > video_pipe

  These commands work well using 3 prompts, then I tried them in C++ embedding commands in std::system() instructions (using different threads) ; everything works, but once ffmpeg command empty the video pipe (finishing first chunk), it closes.
  exec command seems to be uneffective here.
  How could I prevent FFmpeg from closing ?

  Two days struggling on that problem, viewing all possible internet solution. I hope I was clear despite a great headache, thanks for your suggestions in advance.

  UPDATE :
  My C++ code is something like this ; I putted it in a single function on a single thread, but it doesn’t change it’s behaviour.
  I’m on Ubuntu 18.04.2

  void CameraThread::ffmpegJob()
  
  {
  
      std::string strvideo_length, command, timing;
  
      long video_length, begin_chunk, end_chunk;
  
      int begin_h, begin_m, begin_s, end_h, end_m, end_s;
  
  
  
      command = "ffprobe -v error -show_entries format=duration -of default=noprint_wrappers=1:nokey=1 " + Configurations::file_name;
  
      strvideo_length = execCmd(command.c_str());
  
      strvideo_length.pop_back(); // remove \n character
  
      video_length = strToPositiveDigit(strvideo_length);
  
  
  
      if(video_length == -1)
  
      {
  
          std::cout << "Invalid input file";
  
          return;
  
      }
  
  
  
      std::system("bash -c \"rm mst-temp/mst_video_pipe\"");
  
      std::system("bash -c \"rm mst-temp/mst_audio_pipe\"");
  
      std::system("bash -c \"mkfifo mst-temp/mst_video_pipe\"");
  
      std::system("bash -c \"mkfifo mst-temp/mst_audio_pipe\"");
  
      // Keep video pipe opened
  
      std::system("bash -c \"exec 7<>mst-temp/mst_video_pipe\"");
  
  
  
      std::string rtsp_url = "rtsp://" + Configurations::my_own_used_ip + "@" + Configurations::client_ip +
  
              ":" + std::to_string(Configurations::port + 1);
  
  
  
      command = "ffmpeg -probesize 2147483647 -re -s 1280x720 -pix_fmt rgb24 -i pipe:0 "
  
                "-i mst-temp/mst_audio_pipe -r 25 -vcodec libx264 -crf 23 -preset ultrafast -f rtsp "
  
                "-rtsp_transport tcp " + rtsp_url + " < mst-temp/mst_video_pipe &"; // Using & to continue without block on command
  
      std::system(command.c_str());
  
  
  
      begin_chunk = -1 * VIDEO_CHUNK;
  
      end_chunk = 0;
  
  
  
      // Extract the complete audio track
  
      command = "bash -c \"ffmpeg -i " + Configurations::file_name + " -vn mst-temp/audio/complete.aac -y\"";
  
      std::system(command.c_str());
  
  
  
      while(true)
  
      {
  
          // Define the actual video chunk (in seconds) to use, if EOF is reached, exit
  
          begin_chunk += (end_chunk - begin_chunk);
  
          if(begin_chunk == video_length)
  
              break;
  
          if(end_chunk + VIDEO_CHUNK <= video_length)
  
              end_chunk += VIDEO_CHUNK;
  
          else
  
              end_chunk += (video_length - end_chunk);
  
  
  
          // Set begin and end H, M, S variables
  
          begin_h = static_cast<int>(begin_chunk / 3600);
  
          begin_chunk -= (begin_h * 3600);
  
          begin_m = static_cast<int>(begin_chunk / 60);
  
          begin_chunk -= (begin_m * 60);
  
          begin_s = static_cast<int>(begin_chunk);
  
          end_h = static_cast<int>(end_chunk / 3600);
  
          end_chunk -= (end_h * 3600);
  
          end_m = static_cast<int>(end_chunk / 60);
  
          end_chunk -= (end_m * 60);
  
          end_s = static_cast<int>(end_chunk);
  
  
  
          // Extract bmp frames and audio from video chunk
  
          // Extract frames
  
          timing = " -ss " + std::to_string(begin_h) + ":" + std::to_string(begin_m) +
  
                  ":" + std::to_string(begin_s) + " -to " + std::to_string(end_h) +
  
                  ":" + std::to_string(end_m) + ":" + std::to_string(end_s);
  
          command = "bash -c \"ffmpeg -i " + Configurations::file_name + timing +
  
                  " -compression_algo raw -pix_fmt rgb24 mst-temp/frames/output%03d.bmp\"";
  
          std::system(command.c_str());
  
          // Extract audio
  
          command = "bash -c \"ffmpeg -i mst-temp/audio/complete.aac" + timing +
  
                  " -vn mst-temp/audio/audiochunk.aac -y\"";
  
          std::system(command.c_str());
  
  
  
          // Apply elaborations on audio and frames.........................
  
  
  
          // Write modified audio and frames to streaming pipes
  
          command = "bash -c \"cat mst-temp/audio/audiochunk.aac > mst-temp/mst_audio_pipe &amp; "
  
                    "cat mst-temp/frames/output*.bmp > mst-temp/mst_video_pipe\"";
  
          std::system(command.c_str());
  
      }
  
  }
  
  </int></int></int></int></int></int>