Recherche avancée

Sur d’autres sites (5238)

• dashjs can't find initialization segment on manifest.mpd

  30 avril 2016, par Abelardo Mendoza

  I am following this tutorial to stream a WebM. I have no issues running the ffmpeg commands to generate the videos/audio/manifest files but when I try to run it locally, there’s no video or audio at all and dashjs floods the console with :

  Searching for initialization.    
  
  Start searching for initialization.     
  
  Perform init search: http://localhost:8080/video_1280x720_500k.webm    
  
  Perform SIDX load: http://localhost:8080/video_640x360_750k.webm     
  
  Perform SIDX load: http://localhost:8080/video_1280x720_500k.webm 

  Writing that to console until I stop the server. I have tried using other mpd files such as this, which is used on the dashjs quickstart and it plays the video without any problems.

  I used this guide to install the latest version of ffmpeg on Ubuntu 14.04 LTS :

  ffmpeg version N-79688-g3cb3ddd Copyright (c) 2000-2016 the FFmpeg developers
  
  built with gcc 5.3.0 (Ubuntu 5.3.0-3ubuntu1~14.04) 20151204
  
  configuration: --prefix=/home/ab/cpp/ffmpeg_build --pkg-config-flags=--static --extra-cflags=-I/home/ab/cpp/ffmpeg_build/include --extra-ldflags=-L/home/ab/cpp/ffmpeg/lib --bindir=/home/ab/bin --enable-gpl --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-nonfree
  
  libavutil      55. 23.100 / 55. 23.100
  
  libavcodec     57. 38.100 / 57. 38.100
  
  libavformat    57. 34.103 / 57. 34.103
  
  libavdevice    57.  0.101 / 57.  0.101
  
  libavfilter     6. 44.100 /  6. 44.100
  
  libswscale      4.  1.100 /  4.  1.100
  
  libswresample   2.  0.101 /  2.  0.101
  
  libpostproc    54.  0.100 / 54.  0.100

  When running on ffmpeg :

  ffmpeg \
  
   -f webm_dash_manifest -i video_160x90_250k.webm \
  
   -f webm_dash_manifest -i video_320x180_500k.webm \
  
   -f webm_dash_manifest -i video_640x360_750k.webm \
  
   -f webm_dash_manifest -i video_640x360_1000k.webm \
  
   -f webm_dash_manifest -i video_1280x720_500k.webm \
  
   -f webm_dash_manifest -i audio_128k.webm \
  
   -c copy -map 0 -map 1 -map 2 -map 3 -map 4 -map 5 \
  
   -f webm_dash_manifest \
  
   -adaptation_sets "id=0,streams=0,1,2,3,4 id=1,streams=5" \
  
   manifest.mpd

  It generates the following manifest.mpd :

  <?xml version="1.0" encoding="UTF-8"?>
  
  <mpd xmlns="urn:mpeg:DASH:schema:MPD:2011" type="static" mediapresentationduration="PT117.726S" minbuffertime="PT1S" profiles="urn:webm:dash:profile:webm-on-demand:2012">
  
    <period start="PT0S" duration="PT117.726S">
  
      <adaptationset mimetype="video/webm" codecs="vp9" lang="eng" bitstreamswitching="true" subsegmentalignment="true" subsegmentstartswithsap="1">
  
        <representation bandwidth="198155" width="160" height="90">
  
          <baseurl>video_160x90_250k.webm</baseurl>
  
          <segmentbase indexrange="2007834-2008211">
  
            <initialization range="0-437"></initialization>
  
          </segmentbase>
  
        </representation>
  
        <representation bandwidth="459264" width="320" height="180">
  
          <baseurl>video_320x180_500k.webm</baseurl>
  
          <segmentbase indexrange="4459996-4460374">
  
            <initialization range="0-439"></initialization>
  
          </segmentbase>
  
        </representation>
  
        <representation bandwidth="718495" width="640" height="360">
  
          <baseurl>video_640x360_750k.webm</baseurl>
  
          <segmentbase indexrange="6614036-6614414">
  
            <initialization range="0-441"></initialization>
  
          </segmentbase>
  
        </representation>
  
        <representation bandwidth="931445" width="640" height="360">
  
          <baseurl>video_640x360_1000k.webm</baseurl>
  
          <segmentbase indexrange="8309082-8309460">
  
            <initialization range="0-441"></initialization>
  
          </segmentbase>
  
        </representation>
  
        <representation bandwidth="821274" width="1280" height="720">
  
          <baseurl>video_1280x720_500k.webm</baseurl>
  
          <segmentbase indexrange="8728812-8729190">
  
            <initialization range="0-441"></initialization>
  
          </segmentbase>
  
        </representation>
  
      </adaptationset>
  
      <adaptationset mimetype="audio/webm" codecs="vorbis" lang="eng" audiosamplingrate="44100" bitstreamswitching="true" subsegmentalignment="true" subsegmentstartswithsap="1">
  
        <representation bandwidth="107104">
  
          <baseurl>audio_128k.webm</baseurl>
  
          <segmentbase indexrange="1538710-1539184">
  
            <initialization range="0-4112"></initialization>
  
          </segmentbase>
  
        </representation>
  
      </adaptationset>
  
    </period>
  
  </mpd>

  The index.html has a few changes because dash.js changed the way the player gets initialized.

      
  
          
  
          
  
          <code class="echappe-js">&lt;script src=&quot;http://cdn.dashjs.org/latest/dash.all.debug.js&quot;&gt;&lt;/script&gt;
  
              
          
  

  And here is Chromium’s log file. I’m converting this webm from this site.

  If I missed out any other relevant information or if anyone can guide me into the right direction, please let me know.

  Edit :

  Like Will Law mentioned, using the Shaka Player worked without any issues with my current manifest. Hope this helps anyone else.

• simple_idct : x86 : Drop disabled IDCT implementation

  1er août 2016, par Diego Biurrun

  simple_idct : x86 : Drop disabled IDCT implementation
  This gem has been disabled since 2001.
  

  • [DBH] libavcodec/x86/simple_idct.c

• Framerate live streaming webm with dash and ffmpeg

  14 mai 2016, par Jones

  I am streaming a live video with ffmpeg and dash.js using
  these instructions. It works well except that the video is playing at a too high framerate. No framerate is specified in the manifest.
  Creating the Chunks :

  SET VP9_LIVE_PARAMS=-speed 6 -threads 8 -static-thresh 0 -max-intra-rate 300 -deadline realtime -lag-in-frames 0 -error-resilient 1
  
  ffmpeg -re -r 25 -i tcp://localhost:8891 ^
  
  -map 0:0 ^
  
    -pix_fmt yuv420p ^
  
    -c:v libvpx-vp9 ^
  
      -s 800x600 -keyint_min 25 -g 25 %VP9_LIVE_PARAMS% ^
  
      -f webm_chunk ^
  
      -header "webm_live/glass_360.hdr" ^
  
      -chunk_start_index 1 ^
  
    webm_live\glass_360_%%d.chk ^

  Creating the Manifest :

  ffmpeg ^
  
    -f webm_dash_manifest -live 1 ^
  
     -r 25 ^
  
    -i webm_live/glass_360.hdr ^
  
    -c copy ^
  
    -map 0 ^
  
    -r 25 ^
  
    -framerate 25 ^
  
    -f webm_dash_manifest -live 1 ^
  
      -adaptation_sets "id=0,streams=0" ^
  
      -chunk_start_index 1 ^
  
      -chunk_duration_ms 1000 ^
  
      -time_shift_buffer_depth 7200 ^
  
      -minimum_update_period 7200 ^
  
    webm_live/glass_live_manifest.mpd

  Manifest :

  <?xml version="1.0" encoding="UTF-8"?>
  
  <mpd xmlns="urn:mpeg:DASH:schema:MPD:2011" type="dynamic" minbuffertime="PT1S" profiles="urn:mpeg:dash:profile:isoff-live:2011" availabilitystarttime="2016-03-30T13:02:53Z" timeshiftbufferdepth="PT7200S" minimumupdateperiod="PT7200S">
  
  <period start="PT0S">
  
  <adaptationset mimetype="video/webm" codecs="vp9" bitstreamswitching="true" subsegmentalignment="true" subsegmentstartswithsap="1">
  
  <contentcomponent type="video"></contentcomponent>
  
  <segmenttemplate timescale="1000" duration="1000" media="glass_$RepresentationID$_$Number$.chk" startnumber="1" initialization="glass_$RepresentationID$.hdr"></segmenttemplate>
  
  <representation bandwidth="1000000" width="800" height="600" codecs="vp9" mimetype="video/webm" startswithsap="1"></representation>
  
  </adaptationset>
  
  </period>
  
  </mpd>

  Any Ideas how to fix this ?