Recherche avancée

Sur d’autres sites (7201)

• Concatenate DASH audio and video to single file

  18 mars 2019, par Andreas

  First of all, I have a folder with about 200 video and audio segments (m4v and m4a) of a video that was live streamed as DASH video. Now - without having the original file - I want to concatenate those parts to a single, playable video file.

  To mention what I already tested :

  • concatenate via the Unix terminal command cat ; unfortunately this won’t help to make the video playable in any media player again
  • using ffmpeg’s merge abilities via files.txt ; with the same unsuccessful result

  I’m definitely not an expert (otherwise I probably wouldn’t ask) but the problem may be also the missing mpd and/or init file (as far as I could skim in the standard).

  Don’t get me wrong : I don’t want to get a bit to bit identical result of the original file. All I want to achieve is a single playable mp4 file of aforesaid video.

  I also tried to make a own mpd file, but the "stream" won’t play. FYI, I tried playing it in the current VLC 3.0.0 git, since the current stable versions seems not to support DASH.
  If it helps, here the video codec :

  id="live-hd_H264"
  
  mimeType="video/mp4"
  
  codecs="avc1.4d401f"
  
  width="396"
  
  height="704"

  So, can anybody help me ?

  Kind regards !

• fate/vpx : Move webm-dash-manifest tests to a new file

  28 avril 2022, par Andreas Rheinhardt

  fate/vpx : Move webm-dash-manifest tests to a new file
  These tests have basically nothing to do with VPX (they do not even
  
  require the decoder).
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
  

  • [DH] tests/Makefile
  • [DH] tests/fate/vpx.mak
  • [DH] tests/fate/webm-dash-manifest.mak

• MPEG-DASH MPD file not playing correctly

  24 juin 2017, par CMOS

  So I am working on generating a very simple MPD manifest file for my MPEG-DASH videos and I cannot figure out what is wrong. Here is my current manifest file

  <?xml version="1.0" ?>
  
  <mpd xmlns="urn:mpeg:dash:schema:mpd:2011" minbuffertime="PT1.500S" type="static" mediapresentationduration="PT0H9M21.795S" maxsegmentduration="PT0H0M1.001S" profiles="urn:mpeg:dash:profile:isoff-on-demand:2011">
  
      <period>
  
          <baseurl>https://mysite/uploads/sources/resolution_640/bitrate_1400/</baseurl>
  
          <adaptationset mimetype="video/mp4">
  
              <contentcomponent contenttype="video"></contentcomponent>
  
              <representation bandwidth="1400000">
  
                <segmentlist duration="119">
  
                  <initialization sourceurl="https://mysite/uploads/sources/resolution_640/bitrate_1400/640x360_1400Kpbs_0.mp4"></initialization>
  
                  <segmenturl media="https://mysite/uploads/sources/resolution_640/bitrate_1400/640x360_1400Kpbs_1.mp4"></segmenturl>
  
                  <segmenturl media="https://mysite/uploads/sources/resolution_640/bitrate_1400/640x360_1400Kpbs_2.mp4"></segmenturl>
  
                  <segmenturl media="https://mysite/uploads/sources/resolution_640/bitrate_1400/640x360_1400Kpbs_3.mp4"></segmenturl>
  
                </segmentlist>
  
              </representation>
  
          </adaptationset>
  
      </period>
  
  </mpd>

  This MPD file validates using every validator I can find. The urls for the segments are obscured for security reasons but they are all open, public and viewable individually. But when I try to run the manifest file, depending on the player I get. "No supported source found within manifest" or simply nothing happens.

  Any idea how this could be wrong ? I am currently using media url’s as absolute paths but I have also tried paths relative to the BaseURL with no luck. Any info on how I can make a very simple MPEG-Dash manifest structure would be great. I am using FFMPEG to split my video up into 150 frame segments. Thanks !