Recherche avancée

Sur d’autres sites (6533)

• FFmpeg insufficient thread locking only when deploying application using homebrew

  20 décembre 2012, par Kikohs

  I have the strangest bug of my life.
  I have installed ffmpeg using homebrew. I use it from a dll.
  I have set a lock manager because I use ffmpeg from multiple threads.

  In Engine.h :

  class EXPORT_LIB Engine
  
  {
  
  public:
  
      static int initEngine();    
  
      static int closeEngine();
  
  };

  In Engine.cpp :

  static int ff_lockmgr(void **mutex, enum AVLockOp op)
  
  {
  
  if (NULL == mutex)
  
      return -1;
  
  
  
  switch(op)
  
  {
  
  case AV_LOCK_CREATE:
  
  {
  
      *mutex = NULL;
  
      boost::mutex * m = new boost::mutex();
  
      *mutex = static_cast(m);
  
      break;
  
  }
  
  case AV_LOCK_OBTAIN:
  
  {
  
      boost::mutex * m =  static_cast(*mutex);
  
      m->lock();
  
      break;
  
  }
  
  case AV_LOCK_RELEASE:
  
  {
  
      boost::mutex * m = static_cast(*mutex);
  
      m->unlock();
  
      break;
  
  }
  
  case AV_LOCK_DESTROY:
  
  {
  
      boost::mutex * m = static_cast(*mutex);
  
      delete m;
  
      break;
  
  }
  
  default:
  
      break;
  
  }
  
  return 0;
  
  }
  
  
  
  
  
  int Engine::initEngine()
  
  {
  
      int res = -1;
  
      res = av_lockmgr_register(&ff_lockmgr);
  
      av_register_all();
  
      av_log_set_level(AV_LOG_QUIET); // ERROR, PANIC
  
      // Av lock manager success
  
      if( res == 0 ) {
  
          res = MULTITHREAD;
  
      }
  
      else {
  
          res = SINGLETHREAD;
  
      }
  
      return res;
  
  }
  
  
  
  int Engine::closeEngine()
  
  {
  
      int res = 0;
  
      res = av_lockmgr_register(NULL);
  
      return res;
  
  }

  So far so good, everything works as expected.

  When I deploy my app using CMake fix_bundle. I have an error message

  insufficient thread locking around avcodec_open/close()

  If I compile ffmpeg by hand in a custom location, when I deploy the app everything works as expected. What is wrong with homebrew ?

• Recording video & audio data from RTSP stream using ffmpeg

  11 mars 2012, par Kiran Thakkar

  I am trying to record video data using FFMPEG. I have used following commands

  ffmpeg -i 'rtsp ://..' -vcodec copy -acodec copy -t 3600 -y file.mp4

  I got the following error

  Seems stream 0 codec frame rate differs from container frame rate: 180000.00
  
  
  
  (180000/1) -> 90000.00 (180000/2)
  
  Input #0, rtsp, from 'rtsp://10.17.8.138:554/h264.sdp?res=half&x0=0&y0=0&x1=1280&   
  
  
  
  y1=1024&
  
  qp=20&doublescan=0&bitrate=65535&ssn=20':
  
  Duration: N/A, bitrate: N/A
  
  Stream #0.0: Video: h264, yuv420p, 640x512, 90k tbr, 90k tbn, 180k tbc
  
  Output #0, mp4, to 'file.mp4':
  
  Stream #0.0: Video: 0x0000, yuv420p, 640x512, q=2-31, 90k tbn, 90k tbc
  
  Stream mapping:
  
  Stream #0.0 -> #0.0
  
  Press [q] to stop encoding
  
  [NULL @ 0x84c16d0]error, non monotone timestamps 50 >= 50
  
  av_interleaved_write_frame(): Error while opening file

  Can any body help me on this ?

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