Recherche avancée

Sur d’autres sites (11706)

• webm dash encoding... What are the correct ffmpeg parameters ?

  4 septembre 2015, par DeanL

  I’m stumped with encoding videos into a dash compliant format. I’m going from .mp4 to .webm

  Firstly, I am running OS X and ffmpeg 2.5.4.

  Here’s the encoding commands I am using in my test (I got these from here) :

  ffmpeg -i IMG_0113.mp4 -c:v libvpx-vp9 -s 160x90 -b:v 25k -g 1 -tile-columns 4 -frame-parallel 1 -an -f webm -dash 1 video_160x90_25k.webm
  
  
  
  ffmpeg -i IMG_0113.mp4 -c:v libvpx-vp9 -s 160x90 -b:v 50k -g 1 -tile-columns 4 -frame-parallel 1 -an -f webm -dash 1 video_160x90_50k.webm
  
  
  
  ffmpeg -i IMG_0113.mp4 -vn -acodec libvorbis -ab 128k  -dash 1 audio_128k.webm
  
  
  
  ffmpeg -f webm_dash_manifest -i video_160x90_25k.webm -f webm_dash_manifest -i video_160x90_50k.webm -f webm_dash_manifest -i audio_128k.webm -c copy -map 0 -map 1 -map 2 -f webm_dash_manifest -adaptation_sets "id=0,streams=0,1 id=1,streams=2" manifest.mpd

  Secondly, the problem is not with my server, as I have downloaded the samples from here, and they work 100% on the dash.js player when served from my local server.

  Please could someone out there point me in the right direction ? Or provide a sample of the ffmpeg commands used to get the output format correct.

  Thanks,
  Dean.

• webm dash encoding... What are the correct ffmpeg parameters ?

  24 avril 2020, par Dean

  I'm stumped with encoding videos into a dash compliant format. I'm going from .mp4 to .webm

  



  Firstly, I am running OS X and ffmpeg 2.5.4.

  



  Here's the encoding commands I am using in my test (I got these from here) :

  



  ffmpeg -i IMG_0113.mp4 -c:v libvpx-vp9 -s 160x90 -b:v 25k -g 1 -tile-columns 4 -frame-parallel 1 -an -f webm -dash 1 video_160x90_25k.webm

ffmpeg -i IMG_0113.mp4 -c:v libvpx-vp9 -s 160x90 -b:v 50k -g 1 -tile-columns 4 -frame-parallel 1 -an -f webm -dash 1 video_160x90_50k.webm

ffmpeg -i IMG_0113.mp4 -vn -acodec libvorbis -ab 128k  -dash 1 audio_128k.webm

ffmpeg -f webm_dash_manifest -i video_160x90_25k.webm -f webm_dash_manifest -i video_160x90_50k.webm -f webm_dash_manifest -i audio_128k.webm -c copy -map 0 -map 1 -map 2 -f webm_dash_manifest -adaptation_sets "id=0,streams=0,1 id=1,streams=2" manifest.mpd


  



  Secondly, the problem is not with my server, as I have downloaded the samples from here, and they work 100% on the dash.js player when served from my local server.

  



  Please could someone out there point me in the right direction ? Or provide a sample of the ffmpeg commands used to get the output format correct.

  



  Thanks,
Dean.

  


• SegmentedIndexBox (SIDX) not generated when using WEBM over DASH

  11 juillet 2014, par Flock Dawson

  I’m trying to get the Industry Format DASH player to work with WEBM audio/video files. However, I’m running in the same error again and again, and Google doesn’t seem to give much help.

  To start with, I created different streams of the same file (different resolutions and bitrates) using this tutorial : https://developer.mozilla.org/en-US/docs/Web/HTML/DASH_Adaptive_Streaming_for_HTML_5_Video

  Then, I downloaded the Industry Format DASH player (http://dashif.org/software/) and pointed it to the DASH manifest I created. When I try to play the video in Chrome, I get the following log :

  Parsing complete: ( xml2json: 3ms, objectiron: 2ms, total: 0.005s) dash.all.js:3
  
  Manifest has loaded. dash.all.js:3
  
  MediaSource is open! dash.all.js:3
  
  Event {clipboardData: undefined, path: NodeList[0], cancelBubble: false, returnValue: true, srcElement: MediaSource…}
  
  dash.all.js:3
  
  Video codec: video/webm;codecs="vp8" dash.all.js:3
  
  No text tracks. dash.all.js:3
  
  Audio codec: audio/webm;codecs="vorbis" dash.all.js:3
  
  Duration successfully set to: 27.2 dash.all.js:3
  
  Perform SIDX load: https://*****/street_orig_125k_final.webm dash.all.js:3
  
  Perform SIDX load: https://*****/street_audio_final.webm dash.all.js:3
  
  Uncaught RangeError: Offset is outside the bounds of the DataView 

  From this log, I distilled that the manifest is fetched and processed correctly, but something goes wrong when trying to process the SIDX (SegmetIndexBox). I tried another (third-party) source, which works perfectly. I analysed the response returned by the server when trying to fetch the SIDX, and when converted to a readable presentation, the text ’Dsidx’ can be found in this response. So, I analyzed the WEBM file I provide (hexdump and grep), but I cannot find such a SIDX. My conclusion is that the SIDX is never added to the WEBM file.

  From the tutorial I used, I guess the generation of the SIDX is handled by the samplemuxer command, which does not offer any additional parameters. Is there anyone who has more experience in generating this SIDX ?