Recherche avancée

Sur d’autres sites (10384)

• How can i make the dashjs player respect the stream window from ffmpeg ?

  7 mars 2021, par Octavia Kitsune

  I created the following command to i run on the serverside turn a source url into a cmaf dash stream :

  


  ffmpeg -loglevel error -re -i SOURCEURL -c copy -f dash -dash_segment_type mp4 -remove_at_exit 1 -seg_duration 2 -target_latency 1 -frag_type duration -frag_duration 0.1 -window_size 10 -extra_window_size 3 -streaming 1 -ldash 1 -use_template 1 -use_timeline 0 -index_correction 1 -tune zerolatency -fflags "+nobuffer+flush_packets" -format_options "movflags=cmaf" -adaptation_sets "id=0,streams=0 id=1,streams=1" -utc_timing_url "http://time.akamai.com/?iso&ms" stream/main.mpd


  


  And on the clientside i run a dashjs player with the following configuration :

  


    const video = document.getElementById('video')
  const player = dashjs.MediaPlayer().create()

  player.initialize(video, false, true)
  player.updateSettings({
    streaming: {
      stallThreshold: 0.05,
      lowLatencyEnabled: true,
      liveDelay: 1,
      liveCatchup: {
        minDrift: 1,
        playbackRate: 0.3,
        mode: 'liveCatchupModeDefault'
      },
      abr: {
        useDefaultABRRules: true,
        ABRStrategy: 'abrLoLP',
        fetchThroughputCalculationMode:
          'abrFetchThroughputCalculationMoofParsing'
      }
    }
  })


  


  My problem is, that dashjs loads a few segements and then tries to grab segments that error with a 404. It seems the segments it asks for fall out ot the window the stream defines.

  


  So i wonder how i can align my dashjs with my stream configuration so that it does respect the window defined by the stream, to basically simulate a livestream from any kind of videosource ?

  


• How can i make the dashjs player respect the stream window ?

  6 mars 2021, par Octavia Kitsune

  I created the following command to i run on the serverside turn a source url into a cmaf dash stream :

  


  ffmpeg -loglevel error -re -i SOURCEURL -c copy -f dash -dash_segment_type mp4 -remove_at_exit 1 -seg_duration 2 -target_latency 1 -frag_type duration -frag_duration 0.1 -window_size 10 -extra_window_size 3 -streaming 1 -ldash 1 -use_template 1 -use_timeline 0 -index_correction 1 -tune zerolatency -fflags "+nobuffer+flush_packets" -format_options "movflags=cmaf" -adaptation_sets "id=0,streams=0 id=1,streams=1" -utc_timing_url "http://time.akamai.com/?iso&ms" stream/main.mpd


  


  And on the clientside i run a dashjs player with the following configuration :

  


    const video = document.getElementById('video')
  const player = dashjs.MediaPlayer().create()

  player.initialize(video, false, true)
  player.updateSettings({
    streaming: {
      stallThreshold: 0.05,
      lowLatencyEnabled: true,
      liveDelay: 1,
      liveCatchup: {
        minDrift: 1,
        playbackRate: 0.3,
        mode: 'liveCatchupModeDefault'
      },
      abr: {
        useDefaultABRRules: true,
        ABRStrategy: 'abrLoLP',
        fetchThroughputCalculationMode:
          'abrFetchThroughputCalculationMoofParsing'
      }
    }
  })


  


  My problem is, that dashjs loads a few segements and then tries to grab segments that error with a 404. It seems the segments it asks for fall out ot the window the stream defines.

  


  So i wonder how i can align my dashjs with my stream configuration so that it does respect the window defined by the stream, to basically simulate a livestream from any kind of videosource ?

  


• confused about lhls in ffmpeg

  27 décembre 2020, par JohnL

  I am more than a little confused about trying to use the experimental lhls option in ffmpeg.

  


  I have built ffmpeg from source (which takes a while), and currently have version 4.1.6 running.

  


  Reading other threads here, and the ffmpeg docs, it appears that the lhls option is available only in the Dash muxer.

  


  I gravitated to HLS because of its support in Apple devices, and I thought that lhls was related (and Apple was drafting the spec).

  


  Then there is the comment in the ffmpeg docs that states that the hls.js folks are working on supporting lhls in their library, which I also use to support browsers like Chrome.

  


  Should I be using dash instead of hls for my prototype ? I want to try and get very low latency for a construction inspection app I am considering building. Right now, the latency I am seeing is 10-15 seconds.

  


  Any insights would be appreciated. TIA

  


  See my comment below. I have many of the dash format flags working, but can't get -lhls to work. Here are some of the build flags used :

  


  conversion : avcodec configuration : —prefix=/usr —extra-version='1 deb10u1+rpt1' —toolchain=hardened —incdir=/usr/include/arm-linux-gnueabihf —enable-gpl —disable-stripping —enable-avresample —disable-filter=resample —enable-avisynth —enable-gnutls —enable-ladspa —enable-libaom —enable-libass —enable-libbluray —enable-libbs2b —enable-libcaca —enable-libcdio —enable-libcodec2 —enable-libflite —enable-libfontconfig —enable-libfreetype —enable-libfribidi —enable-libgme —enable-libgsm —enable-libjack —enable-libmp3lame —enable-libmysofa —enable-libopenjpeg —enable-libopenmpt —enable-libopus —enable-libpulse —enable-librsvg —enable-librubberband —enable-libshine —enable-libsnappy —enable-libsoxr —enable-libspeex —enable-libssh —enable-libtheora —enable-libtwolame —enable-libvidstab —enable-libvorbis —enable-libvpx —enable-libwavpack —enable-libwebp —enable-libx265 —enable-libxml2 —enable-libxvid —enable-libzmq —enable-libzvbi —enable-lv2 —enable-omx —enable-openal —enable-opengl —enable-sdl2 —enable-omx-rpi —enable-mmal —enable-neon —enable-rpi —enable-libdc1394 —enable-libdrm —enable-libiec61883 —enable-chromaprint —enable-frei0r —enable-libx264 —libdir=/usr/lib/arm-linux-gnueabihf/neon/vfp —cpu=cortex-a7 —arch=armv6t2 —disable-thumb —enable-shared —disable-doc —disable-programs