Recherche avancée

Sur d’autres sites (6995)

• Using ffmpeg to generate dash manifest and it cannot be played by dash.js

  18 mars 2019, par Punkhead

  I’m using ffmpeg to encode incoming stream via rtmp protocol, the code as following :

  ffmpeg -re -i rtmp://localhost:1935${StreamPath} -use_timeline 1 /
  
  -use_template 1 -window_size 10 -min_seg_duration 5000 -f dash out.mpd

  The manifest looks like this :

  <?xml version="1.0" encoding="utf-8"?>
  
  <mpd xmlns="urn:mpeg:dash:schema:mpd:2011" profiles="urn:mpeg:dash:profile:isoff-live:2011" type="static" mediapresentationduration="PT1M36.4S" minbuffertime="PT8.3S">
  
      <programinformation>
  
      </programinformation>
  
      <period start="PT0.0S">
  
          <adaptationset contenttype="video" segmentalignment="true" bitstreamswitching="true" framerate="30/1">
  
          <representation mimetype="video/mp4" codecs="avc1.640028" width="1920" height="1080" framerate="30/1">
  
              <segmenttemplate timescale="15360" initialization="init-stream$RepresentationID$.m4s" media="chunk-stream$RepresentationID$-$Number%05d$.m4s" startnumber="4">
  
                  <segmenttimeline>
  
                      <s t="384000" d="128000"></s>
  
                      <s d="71680"></s>
  
                      <s d="128000" r="4"></s>
  
                      <s d="56832"></s>
  
                      <s d="128000"></s>
  
                      <s d="72704"></s>
  
                  </segmenttimeline>
  
              </segmenttemplate>
  
          </representation>
  
      </adaptationset>
  
      <adaptationset contenttype="audio" segmentalignment="true" bitstreamswitching="true">
  
          <representation mimetype="audio/mp4" codecs="mp4a.40.2" bandwidth="128000" audiosamplingrate="44100">
  
              <audiochannelconfiguration schemeiduri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="2"></audiochannelconfiguration>
  
              <segmenttemplate timescale="44100" initialization="init-stream$RepresentationID$.m4s" media="chunk-stream$RepresentationID$-$Number%05d$.m4s" startnumber="4">
  
                  <segmenttimeline>
  
                      <s t="1099755" d="367616"></s>
  
                      <s d="205824"></s>
  
                      <s d="367616" r="4"></s>
  
                      <s d="162816"></s>
  
                      <s d="367616"></s>
  
                      <s d="207872"></s>
  
                  </segmenttimeline>
  
              </segmenttemplate>
  
          </representation>
  
      </adaptationset>
  
  </period>
  
  </mpd>

  When I try to play it on dash.js player, a error occured :

  [112] Parsing complete: ( xml2json: 3.50ms, objectiron: 1.76ms, total: 0.00526s) Debug.js:127 
  
  [116] SegmentTimeline detected using calculated Live Edge Time Debug.js:127 
  
  [118] MediaSource attached to element.  Waiting on open... Debug.js:127 
  
  [119] Manifest has been refreshed at Tue Jan 02 2018 01:57:35 GMT+0800 [1514829455.1] Debug.js:127 
  
  [155] MediaSource is open! Debug.js:127 
  
  [156] Duration successfully set to: 96.4 Debug.js:127 
  
  [157] Added 0 inline events Debug.js:127 
  
  [158] video codec: video/mp4;codecs="avc1.640028" Stream.js:225 
  
  Uncaught TypeError: Cannot read property 'type' of null
  
      at z (Stream.js:225)
  
      at C (Stream.js:285)
  
      at D (Stream.js:373)
  
      at E (Stream.js:398)
  
      at Object.d [as activate] (Stream.js:107)
  
      at y (StreamController.js:363)
  
      at MediaSource.c (StreamController.js:342)

  then it fails to playback...

  Is it because I didn’t set the parameters right on ffmpeg or this is a bug in dash.js ?

  I really stuck here !

• AAC to network using ffmpeg libraries

  17 juin 2013, par HaneTV

  I'm trying to send an aac adts stream to rtp with ffmpeg.
  I only know sample rate (22050) and channel (1)
  With command line it's quite easy with :

  ffmpeg -i udp://localhost:xxxx -acodec copy -absf aac_adtstoasc -f rtp rtp://localhost:yyyy

  But I need to use the C++ lib instead and I'm quite lost even with examples files in ffmpeg sources. Any help would be apreciated

• Mingw+msys2 : Failed to connect to bitbucket.org : Network is unreachable

  12 juin 2017, par Mitra M

  I want to build ffmpeg under windows 8.1 by using this script and last version of Mingw+Msys2 , but it gets error for any hg clone from bitbucket.org , e.g :

  $ hg clone https://bitbucket.org/multicoreware/x265

  abort : error:Network is unreachable

  After searching on the Internet I saw this page and realized it is because that bitbucket.org has IPv6 and I can not access to it .
  Please see results of the following commands :

  $ ping -n 10 bitbucket.org
  
  
  
  Pinging bitbucket.org [104.192.143.2] with 32 bytes of data:
  
  Request timed out.
  
  Request timed out.
  
  Request timed out.
  
  Request timed out.
  
  Request timed out.
  
  Request timed out.
  
  Request timed out.
  
  Request timed out.
  
  Request timed out.
  
  Request timed out.
  
  
  
  Ping statistics for 104.192.143.2:
  
      Packets: Sent = 10, Received = 0, Lost = 10 (100% loss),
  
  
  
  
  
  
  
  $ ping -n 10 -6 bitbucket.org
  
  Ping request could not find host bitbucket.org. Please check the name and try again
  
  
  
  
  
  $ tracert bitbucket.org
  
  
  
  Tracing route to bitbucket.org [104.192.143.1]
  
  over a maximum of 30 hops:
  
  
  
    1    <1 ms    <1 ms    <1 ms  192.168.1.1
  
    2    30 ms    29 ms     9 ms  81.12.120.2
  
    3    20 ms    40 ms    12 ms  81.12.120.1
  
    4     6 ms     8 ms    10 ms  192.168.8.41
  
    5    21 ms    24 ms    19 ms  192.168.8.1
  
    6     *        *        *     Request timed out.
  
    7    52 ms    56 ms    54 ms  192.168.170.241
  
    8    35 ms    25 ms     *     10.10.53.61
  
    9    27 ms    32 ms    32 ms  10.201.47.142
  
   10    30 ms    44 ms    38 ms  10.201.42.117
  
   11    40 ms    33 ms    67 ms  10.201.147.242
  
   12    46 ms    38 ms    59 ms  85.132.90.201
  
   13     *        *        *     Request timed out.
  
   14     *        *        *     Request timed out.
  
   15     *        *        *     Request timed out.
  
   16     *        *        *     Request timed out.
  
    ...

  NOTE : Also, I’ve seen some posts on the stackoverflow.com like this. But it seems works only for Linux, Because I added 104.192.143.2 bitbucket.org to my /etc/hosts but not worked.

  Please guide me.