Recherche avancée

Médias (0)

Mot : - Tags -/albums

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (86)

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

Sur d’autres sites (12711)

  • How To Implement FFMPEG LL-HLS

    8 septembre 2022, par Devin Dixon

    How is Low Latency HLS achieved with FFMPEG ? From my understanding thus far, I am seeing changes around the -f option. For example :

    


    -f dash -method PUT http://example.com/live/manifest.mpd


    


    But there isn't much information researching on LL-HLS with ffmpeg. Making smaller segments I am finding comes at the cost of choppiness in the stream. Has anyone done this ? And is the protocol actually adopted or just in "theory".

    


  • 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 ?