Recherche avancée

Médias (2)

Mot : - Tags -/plugins

Autres articles (63)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

Sur d’autres sites (8117)

  • Create dash manifest-file for mp4-videos

    10 juillet 2020, par Werner

    I took a video and created 3 versions of it in different sizes (including a watermark, no audio here) with :

    


    ffmpeg -i "input.mov" -i "watermark.png" -an -c:v libx264 -x264opts "keyint=24:min-keyint=24:no-scenecut" -b:v 2400k -maxrate 2400k -bufsize 1200k -filter_complex "overlay=24:960,scale=640:480" -y "output_640_480.mp4"

ffmpeg -i "input.mov" -i "watermark.png" -an -c:v libx264 -x264opts "keyint=24:min-keyint=24:no-scenecut" -b:v 3200k -maxrate 3200k -bufsize 1600k -filter_complex "overlay=24:960,scale=800:600" -y "output_800_600.mp4"

ffmpeg -i "input.mov" -i "watermark.png" -an -c:v libx264 -x264opts "keyint=24:min-keyint=24:no-scenecut" -b:v 5300k -maxrate 5300k -bufsize 5300k -filter_complex "overlay=24:960,scale=1920:1080" -y "output_1920:1080.mp4"


    


    Now I want to create the manifest mpd file. The problem is that MB4Box is not available on the target-system, so I tried to do it with ffmpeg :

    


    ffmpeg
-f dash -i "output_640_480.mp4"
-f dash -i "output_800_600.mp4"
-f dash -i "output_1920_1080.mp4"
-c copy -map 0 -map 1 -map 2
-f dash -adaptation_sets "id=0,streams=0,1,2"
-y
"manifest.mpd"


    


    But I get errors :

    


    [dash @ 0000015ed965db40] Manifest too large: 6654253
output_640_480.mp4: Invalid data found when processing input


    


    The single videos do play without problems, but how do I create the manifest-file correctly ?

    


  • Low Latency DASH Nginx RTMP

    10 mai 2017, par Kenan Christian

    I use arut nginx-rtmp-module (https://github.com/arut/nginx-rtmp-module) on the media server, then I tried to stream using FFmpeg to the dash application, then I test the stream by playing it using VLC.

    And it waits around 30secs to start playing, and it plays from the beginning, not the current timestamp.

    This is my current config on the RTMP block

    rtmp {
       server {
           listen 1935;

           application live {
               live on;

              exec ffmpeg -re -i rtmp://localhost:1935/live/$name
                 -c:a libfdk_aac -b:a 32k  -c:v libx264 -b:v 128K -f flv rtmp://localhost:1935/hls/$name_low
                 -c:a libfdk_aac -b:a 64k  -c:v libx264 -b:v 256k -f flv rtmp://localhost:1935/hls/$name_mid
                 -c:a libfdk_aac -b:a 128k -c:v libx264 -b:v 512K -f flv rtmp://localhost:1935/hls/$name_hi
                 -c:a libfdk_aac -b:a 128k -c:v libx264 -b:v 512K -f flv rtmp://localhost:1935/dash/$name_dash;
           }

           application hls {
                live on;

                hls on;
                hls_path /tmp/hls;
                hls_nested on;

                hls_variant _low BANDWIDTH=160000;
                hls_variant _mid BANDWIDTH=320000;
                hls_variant _hi  BANDWIDTH=640000;
           }

           application dash {
               live on;

               dash on;
               dash_path /tmp/dash;
               dash_nested on;
           }
       }
    }

    This is the command I use for streaming

    ffmpeg -re -i 2014\ SPRING.mp4 -c copy -f flv
    rtmp://52.221.221.163:1935/dash/spring

    How can I reduce the delay, and make it play from the same timestamp as the streamer ?

    Can I achieve under 5s latency ?

    UPDATE

    Tried to change the playlist length and fragment length, using this directive

    dash_playlist_length 10s;
    dash_fragment 2s;

    But still got some latency problem, sometimes it’s smaller than before, sometimes it’s the same

  • Low Latency DASH Nginx RTMP

    3 août 2017, par Kenan Christian

    I use arut nginx-rtmp-module (https://github.com/arut/nginx-rtmp-module) on the media server, then I tried to stream using FFmpeg to the dash application, then I test the stream by playing it using VLC.

    And it waits around 30secs to start playing, and it plays from the beginning, not the current timestamp.

    This is my current config on the RTMP block

    rtmp {
       server {
           listen 1935;

           application live {
               live on;

              exec ffmpeg -re -i rtmp://localhost:1935/live/$name
                 -c:a libfdk_aac -b:a 32k  -c:v libx264 -b:v 128K -f flv rtmp://localhost:1935/hls/$name_low
                 -c:a libfdk_aac -b:a 64k  -c:v libx264 -b:v 256k -f flv rtmp://localhost:1935/hls/$name_mid
                 -c:a libfdk_aac -b:a 128k -c:v libx264 -b:v 512K -f flv rtmp://localhost:1935/hls/$name_hi
                 -c:a libfdk_aac -b:a 128k -c:v libx264 -b:v 512K -f flv rtmp://localhost:1935/dash/$name_dash;
           }

           application hls {
                live on;

                hls on;
                hls_path /tmp/hls;
                hls_nested on;

                hls_variant _low BANDWIDTH=160000;
                hls_variant _mid BANDWIDTH=320000;
                hls_variant _hi  BANDWIDTH=640000;
           }

           application dash {
               live on;

               dash on;
               dash_path /tmp/dash;
               dash_nested on;
           }
       }
    }

    This is the command I use for streaming

    ffmpeg -re -i 2014\ SPRING.mp4 -c copy -f flv
    rtmp://52.221.221.163:1935/dash/spring

    How can I reduce the delay, and make it play from the same timestamp as the streamer ?

    Can I achieve under 5s latency ?

    UPDATE

    Tried to change the playlist length and fragment length, using this directive

    dash_playlist_length 10s;
    dash_fragment 2s;

    But still got some latency problem, sometimes it’s smaller than before, sometimes it’s the same