Recherche avancée

Sur d’autres sites (11331)

• How to store a raw RTSP video stream to a file ?

  12 janvier 2016, par Siva Prasanna

  I’m playing around with the open source FFMpeg tool. I want to save an RTSP video stream to a local file. I came across this question and I tried executing a similar command, but its not working. It doesn’t throw any error either. My command is :
  ffmpeg -i rtsp://test.vibrtech.com/mov/video.sav?MAC=00C2100F124^&channel=2^&GUID=betauser -acodec copy -vcodec copy c:/video.mp4

  but when I execute this command all I’m getting is this(with the cursor being blinked like forever, until I manually invoke ctrl+c) :

  D:\..\bin>ffmpeg -i rtsp://test.vibrtech.com/mov/video.sav?MAC=00C2100F124^&channel=2^&GUID=betauser -acodec copy -vcodec copy c:/video.mp4
  
  
  
  ffmpeg version N-77704-g68eb208 Copyright (c) 2000-2016 the FFmpeg developers
  
    built with gcc 5.2.0 (GCC)
  
    configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av
  
  isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls 
  
  --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca 
  
  --enable-libdcadec --enable-libfreetype --enable-libgme --enable-libgsm 
  
  --enable-libilbc --enable-libmodplug --enable-libmp3lame 
  
  --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg 
  
  --enable-libopus --enable-librtmp --enable-libschroedinger 
  
  --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame 
  
  --enable-libvidstab --enable-libvo-aacenc --enable-libvo-amrwbenc
  
  --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp 
  
  --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid 
  
  --enable-libzimg --enable-lzma --enable-decklink --enable-zlib
  
    libavutil      55. 12.100 / 55. 12.100
  
    libavcodec     57. 21.100 / 57. 21.100
  
    libavformat    57. 21.100 / 57. 21.100
  
    libavdevice    57.  0.100 / 57.  0.100
  
    libavfilter     6. 23.100 /  6. 23.100
  
    libswscale      4.  0.100 /  4.  0.100
  
    libswresample   2.  0.101 /  2.  0.101
  
    libpostproc    54.  0.100 / 54.  0.100
  
  _

  Can anyone tell me what I’m doing wrong here ? Or is there any way this could be achieved by using other commands ?

  P.S : I’m getting the stream from this url : rtsp ://test.vibrtech.com/mov/video.sav ?MAC=00C2100F124&channel=2&GUID=betaUser

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

• DASH package (mpd) I made freezes after raising the onratechange event

  7 mars 2016, par Nick Birke

  I am trying to created an adaptive stream from an mp4 file. I have a decent amount of experience at doing streaming, and have successfully implemented smooth streaming via Silverlight. We want a solution for everything that works in HTML5. I am pursuing DASH. So here are the steps I take...

  1. Resample the mp4 to different sizes using ffmpeg.
  2. Ensure the files are properly fragmented using Bento4s mp4Fragment utility.
  3. Create the DASH mpd file and associated segments using Bento4s mp4dash utility.

  I have done a lot of work to learn each of these utilities and create a process that gets to output that I think will work. To create reliable DASH artifacts. But it seems I am doing something wrong. Here are examples of command lines I run.

  For step one I create three different files... for three different rates and sizes... (these may not be the exact command lines, they are from old notes... but the parameter values are the ones I am using for sure)

  ffmpeg -y -i C:\_SIMULATED_SHARE_C\ff\big_buck_bunny.mp4 -c:v libx264 -x264opts keyint=24:min-keyint=24:no-scenecut -b:v 1500k -maxrate 1500k -bufsize 1000k -vf "scale=-1:720" C:\_SIMULATED_SHARE_C\ff\output\outputfile720.mp4
  
  
  
  ffmpeg -y -i C:\_SIMULATED_SHARE_C\ff\big_buck_bunny.mp4 -c:v libx264 -x264opts keyint=24:min-keyint=24:no-scenecut -b:v 800k -maxrate 800k -bufsize 500k -vf "scale=-1:540" C:\_SIMULATED_SHARE_C\ff\output\outputfile540.mp4
  
  
  
  ffmpeg -y -i C:\_SIMULATED_SHARE_C\ff\big_buck_bunny.mp4 -c:v libx264 -x264opts keyint=24:min-keyint=24:no-scenecut -b:v 400k -maxrate 400k -bufsize 400k -vf "scale=-1:360" C:\_SIMULATED_SHARE_C\ff\output\outputfile360.mp4

  So that gives you the three files that need to be fragmented. So I fragment them using the mp4fragment utility from Bento4. That command line is simple so I will not offer an example.

  The I use Bento4s mp4dash to create the dash. Something like this...

  "E:\\_INSTALL\\Bento4\\Bento4-SDK-1-4-3-607.x86-microsoft-win32-vs2010\\Bento4-SDK-1-4-3-607.x86-microsoft-win32-vs2010\\bin\\mp4dash.exe --mpd-name=\"\\\\d9fqt52\\_SIMULATED_SHARE_C\\ff\\output\\dash\\something.mpd\" -f -o \"\\\\d9fqt52\\_SIMULATED_SHARE_C\\ff\\output\\dash\" \"\\\\d9fqt52\\_SIMULATED_SHARE_C\\ff\\output\\bunny360f.mp4\" \"\\\\d9fqt52\\_SIMULATED_SHARE_C\\ff\\output\\bunny540f.mp4\" \"\\\\d9fqt52\\_SIMULATED_SHARE_C\\ff\\output\\bunny720f.mp4\" "

  This runs ok. And creates the mpd file, an audio folder with segment files, an a video folder with 3 folders each with the segment files.

  I am able to configure IIS to play the mpd ok. As well as the segement files. The video plays fine... and then it stops. It freezes between 50 and 60 seconds. Right before it freezes I can confirm that the onratechange event of the HTML5 video tag is raised. This is an event that is raised with the rate of play is changed. I do nothing to change this it just happens.

  The actual video in question is about 1hr long. Also I am using the dash.js library as a player.

  If you can identify any components or specifics I should change please let me know !

  UPDATE ON MAR 7, 2016

  As requested here is the MPD content...

  <?xml version="1.0" ?>
  
  <mpd mediapresentationduration="PT51M51.909S" minbuffertime="PT0.80S" profiles="urn:mpeg:dash:profile:isoff-live:2011" type="static" xmlns="urn:mpeg:dash:schema:mpd:2011">
  
    
  
    <period>
  
      
  
      <adaptationset lang="en" mimetype="audio/mp4" segmentalignment="true" startwithsap="1">
  
        <segmenttemplate duration="801" initialization="$RepresentationID$/init.mp4" media="$RepresentationID$/seg-$Number$.m4f" startnumber="1" timescale="1000"></segmenttemplate>
  
        <representation audiosamplingrate="48000" bandwidth="132491" codecs="mp4a.40.2">
  
          <audiochannelconfiguration schemeiduri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="2"></audiochannelconfiguration>
  
        </representation>
  
      </adaptationset>
  
      
  
      <adaptationset maxheight="720" maxwidth="1280" mimetype="video/mp4" minheight="540" minwidth="640" segmentalignment="true" startwithsap="1">
  
        <segmenttemplate duration="801" initialization="$RepresentationID$/init.mp4" media="$RepresentationID$/seg-$Number$.m4f" startnumber="1" timescale="1000"></segmenttemplate>
  
        <representation bandwidth="785536" codecs="avc1.64001F" framerate="30000/1001" height="540" scantype="progressive" width="960"></representation>
  
        <representation bandwidth="403537" codecs="avc1.64001E" framerate="30000/1001" height="360" scantype="progressive" width="640"></representation>
  
        <representation bandwidth="1496514" codecs="avc1.64001F" framerate="30000/1001" height="720" scantype="progressive" width="1280"></representation>
  
      </adaptationset>
  
    </period>
  
  </mpd>

  UPDATE ON MAR 7, 2016

  Here is the console output for two different videos that just stop for some unknown reason between 50 and 60s

  ///ABS VIDEO 
  
  
  
  58393][rulesController] [RULES]: playbackTimeRule [Fragment:download,82,MediaSegment,0video] Default 
  
  dash.all.js:11 [58395][rulesController] [RULES]: sameTimeRequestRule [Fragment:download,82,MediaSegment,0,video] Default 
  
  dash.all.js:11 [58401][indexHandler][audio] Getting the request for time: 82.082 
  
  dash.all.js:11 [58403][indexHandler][audio] Index for time 82.082 is 81 
  
  dash.all.js:11 [58405][indexHandler][audio] SegmentTemplate: 81.08099999999999 / 1361.235 
  
  dash.all.js:11 [58406][indexHandler][audio] SegmentTemplate: 82.082 / 1361.235 
  
  dash.all.js:11 [58407][rulesController] [RULES]: playbackTimeRule [Fragment:download,82,MediaSegment,0audio] Default 
  
  dash.all.js:11 [58417][fragmentLoader] loaded video:MediaSegment:82.082 (200, 18ms, 2ms) 
  
  dash.all.js:11 [58419][rulesController] [RULES]: sameTimeRequestRule [Fragment:download,82,MediaSegment,0,audio] Default 
  
  dash.all.js:11 [58435][fragmentLoader] loaded audio:MediaSegment:82.082 (200, 14ms, 0ms) 
  
  dash.all.js:11 [59390][indexHandler][video] Getting the request for time: 83.083 
  
  dash.all.js:11 [59392][indexHandler][video] Index for time 83.083 is 82 
  
  dash.all.js:11 [59393][indexHandler][video] SegmentTemplate: 82.082 / 1361.235 
  
  dash.all.js:11 [59394][indexHandler][video] SegmentTemplate: 83.08299999999998 / 1361.235 
  
  dash.all.js:11 [59395][rulesController] [RULES]: playbackTimeRule [Fragment:download,83,MediaSegment,0video] Default 
  
  dash.all.js:11 [59396][rulesController] [RULES]: sameTimeRequestRule [Fragment:download,83,MediaSegment,0,video] Default 
  
  dash.all.js:11 [59401][indexHandler][audio] Getting the request for time: 83.083 
  
  dash.all.js:11 [59403][indexHandler][audio] Index for time 83.083 is 82 
  
  dash.all.js:11 [59404][indexHandler][audio] SegmentTemplate: 82.082 / 1361.235 
  
  dash.all.js:11 [59406][indexHandler][audio] SegmentTemplate: 83.08299999999998 / 1361.235 
  
  dash.all.js:11 [59408][rulesController] [RULES]: playbackTimeRule [Fragment:download,83,MediaSegment,0audio] Default 
  
  dash.all.js:11 [59416][fragmentLoader] loaded video:MediaSegment:83.08299999999998 (200, 17ms, 1ms) 
  
  dash.all.js:11 [59418][rulesController] [RULES]: sameTimeRequestRule [Fragment:download,83,MediaSegment,0,audio] Default 
  
  dash.all.js:11 [59437][fragmentLoader] loaded audio:MediaSegment:83.08299999999998 (200, 14ms, 1ms) 
  
  dash.all.js:11 [59902][scheduleController][video] Stalling Buffer 
  
  dash.all.js:11 [59903][bufferController][video] Waiting for more buffer before starting playback. 
  
  dash.all.js:11 [59906][scheduleController][audio] Stalling Buffer 
  
  dash.all.js:11 [59907][bufferController][audio] Waiting for more buffer before starting playback. 
  
  dash.all.js:11 [63684][playbackController] <video> ratechange:  0 
  
  
  
  
  
  
  
  
  
  ///HOG VIDEO
  
  
  
  [58250][rulesController] [RULES]: playbackTimeRule [Fragment:download,105,MediaSegment,0audio] Default 
  
  dash.all.js:11 [58266][fragmentLoader] loaded video:MediaSegment:84.105 (200, 28ms, 1ms) 
  
  dash.all.js:11 [58269][rulesController] [RULES]: sameTimeRequestRule [Fragment:download,105,MediaSegment,0,audio] Default 
  
  dash.all.js:11 [58287][fragmentLoader] loaded audio:MediaSegment:84.105 (200, 14ms, 1ms) 
  
  dash.all.js:11 [58982][indexHandler][video] Getting the request for time: 84.906 
  
  dash.all.js:11 [58983][indexHandler][video] Index for time 84.906 is 105 
  
  dash.all.js:11 [58984][indexHandler][video] SegmentTemplate: 84.105 / 3111.909 
  
  dash.all.js:11 [58984][indexHandler][video] SegmentTemplate: 84.906 / 3111.909 
  
  dash.all.js:11 [58985][rulesController] [RULES]: playbackTimeRule [Fragment:download,106,MediaSegment,0video] Default 
  
  dash.all.js:11 [58986][rulesController] [RULES]: sameTimeRequestRule [Fragment:download,106,MediaSegment,0,video] Default 
  
  dash.all.js:11 [58989][indexHandler][audio] Getting the request for time: 84.906 
  
  dash.all.js:11 [58990][indexHandler][audio] Index for time 84.906 is 105 
  
  dash.all.js:11 [58991][indexHandler][audio] SegmentTemplate: 84.105 / 3111.909 
  
  dash.all.js:11 [58992][indexHandler][audio] SegmentTemplate: 84.906 / 3111.909 
  
  dash.all.js:11 [58993][rulesController] [RULES]: playbackTimeRule [Fragment:download,106,MediaSegment,0audio] Default 
  
  dash.all.js:11 [59002][fragmentLoader] loaded video:MediaSegment:84.906 (200, 14ms, 1ms) 
  
  dash.all.js:11 [59003][rulesController] [RULES]: sameTimeRequestRule [Fragment:download,106,MediaSegment,0,audio] Default 
  
  dash.all.js:11 [59014][fragmentLoader] loaded audio:MediaSegment:84.906 (200, 8ms, 1ms) 
  
  dash.all.js:11 [59735][scheduleController][video] Stalling Buffer 
  
  dash.all.js:11 [59736][bufferController][video] Waiting for more buffer before starting playback. 
  
  dash.all.js:11 [59738][scheduleController][audio] Stalling Buffer 
  
  dash.all.js:11 [59739][bufferController][audio] Waiting for more buffer before starting playback. 
  
  dash.all.js:11 [61695][playbackController] <video> ratechange:  0 
  
  </video></video>