Recherche avancée

Sur d’autres sites (13326)

• Can't write .mp4 files - Could not open codec 'libx264' : Unspecified error

  17 février 2015, par margaridagomes

  Days ago I installed the latest 2.4 branch withou ffmpeg. I’m using Ubuntu 14.04 and I don’t have at all ffmpeg in my Virtual Machine.

  I want to write .mp4 video files and the input files are also .mp4. The input codec is avc1.

  I can’t obtain any results, the errors can be seen below.

  Error

  [libx264 @ 0x9357bc0] broken ffmpeg default settings detected
  
  [libx264 @ 0x9357bc0] use an encoding preset (e.g. -vpre medium)
  
  [libx264 @ 0x9357bc0] preset usage: -vpre <speed> -vpre <profile>
  
  [libx264 @ 0x9357bc0] speed presets are listed in x264 --help
  
  [libx264 @ 0x9357bc0] profile is optional; x264 defaults to high
  
  Could not open codec 'libx264': Unspecified error
  
  Could not open the output video for write: /home/margarida/exams_2014/Output.mp4
  
  </profile></speed>

  Simplified Code

  int main(int argc, char *argv[]) {
  
              VideoWriter outputVideo;
  
  
  
              // Get Codec Type
  
              int ex = static_cast<int>(cap.get(CV_CAP_PROP_FOURCC));
  
  
  
              // Transform from int to char via Bitwise operators
  
              char EXT[] = { (char) (ex &amp; 0XFF), (char) ((ex &amp; 0XFF00) >> 8),
  
                              (char) ((ex &amp; 0XFF0000) >> 16), (char) ((ex &amp; 0XFF000000)
  
                                      >> 24), 0 };
  
  
  
              // Acquire input size
  
              Size S = Size((int) cap.get(CV_CAP_PROP_FRAME_WIDTH),
  
                              (int) cap.get(CV_CAP_PROP_FRAME_HEIGHT));
  
  
  
              cout &lt;&lt; "Input codec type: " &lt;&lt; EXT &lt;&lt; endl;
  
  
  
              // Open the output
  
              outputVideo.open(newname, ex, cap.get(CV_CAP_PROP_FPS), S, true);
  
  
  
              if (!outputVideo.isOpened()) {
  
                  cout &lt;&lt; "Could not open the output video for write " &lt;&lt; endl;
  
                          return -1;
  
                      }
  
  
  
                      while (true) {
  
                          cap >> frame;
  
                          if (frame.empty()) {
  
                              cerr &lt;&lt; "nao apanhou frame" &lt;&lt; endl;
  
                              break;
  
                          }
  
  
  
                          cinzento = acinzentar(frame);
  
                          imshow("Cinzento", cinzento);
  
  
  
                          outputVideo.write(cinzento);
  
  
  
                          switch(waitKey(10)){
  
  
  
                          case 27:
  
                              //'esc' has been pressed (ASCII value for 'esc' is 27)
  
                              //exit program.
  
                              return 0;
  
  
  
                          }
  
                      }
  
                     return 0;
  
                  }
  
  </int>

  My cmake was this :

  cmake -D WITH_TBB=ON -D CMAKE_INSTALL_PREFIX=/usr/local -D BUILD_NEW_PYTHON_SUPPORT=ON -D WITH_V4L=ON -D INSTALL_C_EXAMPLES=ON -D INSTALL_PYTHON_EXAMPLES=ON -D BUILD_EXAMPLES=ON -D WITH_QT=ON -D WITH_OPENGL=ON -D WITH_VTK=ON -D WITH_FFMPEG=OFF -D WITH_IPP=OFF ..

  Can anyone help solving my problem ?

  Thanks in advance.

• Piwik 2.10.0 – Release Candidate

  22 décembre 2014, par Piwik Core Team — Community

  We are proud to announce that the release candidate for Piwik 2.10.0 is now available !

  How do I upgrade to the release candidate ?

  You can upgrade to the release candidate in one click, by following instructions in this FAQ.

  Think you’ve found a bug ?

  Please create a bug report in our issue tracker.

  What’s new in Piwik 2.10.0 ?

  Since our last release Piwik 2.9.1 one month ago, over 100 issues have been closed. We’ve focused on fixing bugs, improving performance, and we created a new plugin that will let you better scale Piwik to very high traffic websites using Redis.

  Much improved Log Analytics

  Log Analytics is the powerful little-known feature of Piwik that lets you import dozens of different server logs into Piwik. In Piwik 2.10.0 you can now import Netscaler logs, IIS Advanced Logging Module logs, W3C extended logs and AWS CloudFront logs. Piwik will also automatically track the username as the User ID and/or the Page Generation Time when it is found in the server logs.

  Better scalability using Redis (advanced users)

  At Piwik PRO we are working on making Piwik scale when tracking millions of requests per month. In this release we have revamped the Tracking API. By using the new QueuedTracking plugin you can now queue tracking requests in a Redis database, which lets you scale the Piwik tracking service. The plugin is included as Free/libre software in the core Piwik platform. More information in the QueuedTracking user guide.

  Better performance

  A few performance challenges have been fixed in this release.

  The Visitor Log and the Live API will render much faster on very high traffic websites. Any custom date ranges that you have selected as default in your User Settings (eg. ‘Last 7 days’ or ‘Previous 30 days’) will now be pre-processed so that your analytics dashboard will always load quickly.

  For users on shared hosting, the real time widgets could be use a lot of server resource as they are refreshed every ten seconds. We’ve improved this by only requesting data when the Browser Tab containing the Real time widgets is active.

  Other changes

  We packed in many other changes in this release such as compatibility with Mysql 5.6 and Geo location support for IPv6 addresses. A community member made Piwik compatible with Internet Explorer 9 when running in compatibility mode (which is still used in several companies).

  The Tracker algorithm has been updated : when an existing visit uses a new Campaign then it will force creating a new visit (same behavior as Google Analytics).

  If you need professional support or guidance, get in touch with Piwik PRO.

  Changelog for Piwik 2.10.0 – we plan to release Piwik 2.10.0 around 2015 Jan 5th.

  Happy Analytics, and we wish you a nice holiday season !

• Nginx with rtmp-module stalls between streams

  14 janvier 2015, par churchmf

  I’m experiencing some troubles using NGINX with rtmp-module as a media server. I wish to present a continuous video as a live stream (with up to 60 second latency). However, due to some hardware constraints, I am unable to stream directly from the device. Instead, I can save out X amount of seconds from the device’s buffer as an MP4. My solution has been to save X seconds of video from the device then stream that X seconds, rise and repeat. This has been working mostly well, except for stalls ( 20 seconds) in the stream between calls.

  I have searched far and wide for a solution to this however most of the people experiencing this problem have the collection of videos before starting the stream and can simply concatenate them.

  My running theory is that when a stream finishes, it does an unpublish event in NGINX followed by a timeout period. This prevents the NGINX server from receiving the next publish until the timeout period has expired. I have tried adjusting nginx.config values related to timeouts, respawns, restarts, and publish, but to no avail.

  Pseudocode :
  while true
   > capture X seconds of video to "output.mp4" (this takes less than 300ms)
   > stream the MP4 with FFMPEG (takes X seconds using -re)

  FFMPEG call :
  ffmpeg -re -i "output.mp4" -vcodec libx264 -preset veryfast -maxrate 2000k -bufsize 4000k -g 60 -acodec libmp3lame -b:a 128k -ac 2 -ar 44100 -f flv rtmp :/MYSERVER/live/output

  I am using JWPlayer client side to watch the video stream, however I experience similar issues using VLC.

  I have been trying to figure this out for a few days and I would appreciate any insight an expert to video streaming and NGINX can give. Thank you !