Recherche avancée

Médias (2)

Mot : - Tags -/kml

Autres articles (35)

  • Installation en mode ferme

    4 février 2011, par

    Le mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
    C’est la méthode que nous utilisons sur cette même plateforme.
    L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
    Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...)

  • Configuration spécifique d’Apache

    4 février 2011, par

    Modules spécifiques
    Pour la configuration d’Apache, il est conseillé d’activer certains modules non spécifiques à MediaSPIP, mais permettant d’améliorer les performances : mod_deflate et mod_headers pour compresser automatiquement via Apache les pages. Cf ce tutoriel ; mode_expires pour gérer correctement l’expiration des hits. Cf ce tutoriel ;
    Il est également conseillé d’ajouter la prise en charge par apache du mime-type pour les fichiers WebM comme indiqué dans ce tutoriel.
    Création d’un (...)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

Sur d’autres sites (4740)

  • support auto birate based on internet speed using nginx-vod-module

    30 juillet 2020, par Maurya Shubham

    Allow multiple resolution video streaming from single video url - It's possible with nginx-vod-module package or I need to create different-different resolution file and set them ?

    


    Currently I've manually crated master.m3u8 file.

    


    


    #EXTM3U

    


    #EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=2149280,RESOLUTION=1280x720 index-v1-a1.m3u8

    


    #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=2149280,RESOLUTION=1280x720,URI="iframes-v1-a1.m3u8"

    


    #EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=246440,RESOLUTION=320x184 index-v1-a1.m3u8

    


    #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=246440,RESOLUTION=320x184,URI="iframes-v1-a1.m3u8"

    


    #EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=460560,RESOLUTION=512x288 index-v1-a1.m3u8

    


    #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=460560,RESOLUTION=512x288,URI="iframes-v1-a1.m3u8"

    


    #EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=836280,RESOLUTION=848x480 index-v1-a1.m3u8

    


    #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=836280,RESOLUTION=848x480,URI="iframes-v1-a1.m3u8"

    


    #EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=6221600,RESOLUTION=1920x1080 index-v1-a1.m3u8

    


    #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=6221600,RESOLUTION=1920x1080,URI="iframes-v1-a1.m3u8"

    


    


    but when I crul video url the master.m3u8 file contain only one resolution.

    


    


    #EXTM3U

    


    #EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=4742713,RESOLUTION=1920x1080,FRAMERATE=30.000,CODECS="avc1.640028,mp4a.40.2",VIDEO-RANGE=SDR
index-v1-a1.m3u8

    


    #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=633524,RESOLUTION=1920x1080,CODECS="avc1.640028",URI="iframes-v1-a1.m3u8",VIDEO-RANGE=SDR

    


    


  • How to send RTP stream to Janus from NGINX RTMP module ? [closed]

    25 novembre 2024, par Matéo

    I'm trying to create a stream and display it in a browser. I have already configured NGINX with the rtmp module and my stream works very well with HLS (between 5 and 10 seconds of latency).

    


    Now I would like to set up a low-latency stream and that's why I have installed the janus-gateway webRTC server that allows to take in input an RTP stream and provide in output a webRTC stream.

    


    Here's the schema I'd like to follow :

    


    OBS -> RTMP -> Nginx-rtmp-module -> ffmpeg -> RTP -> Janus -> webRTC -> Browser

    


    But I have a problem with this part : "nginx-rtmp-module -> ffmpeg -> janus"

    


    In fact, my janus's server is running and demos streaming works very well in localhost, but when i try to provide an RTP stream, Janus don't detect the stream in the demos (it shows "No remote video available").

    


    Anyone can help me, please ?

    


    Ressources :

    


      

    • My janus.plugin.streaming.jcfg configuration :
    • 


    


    rtp-sample: {
        type = "rtp"
        id = 1
        description = "Opus/VP8 live stream coming from external source"
        metadata = "You can use this metadata section to put any info you want!"
        audio = true
        video = true
        audioport = 5002
        audiopt = 111
        audiortpmap = "opus/48000/2"
        videoport = 5004
        videopt = 100
        videortpmap = "VP8/90000"
        secret = "adminpwd"
}



    


      

    • My nginx.conf application :
    • 


    


    application test {

        deny play all;

        live on;
        on_publish http://localhost/test/backend/sec/live_auth.php;

        exec ffmpeg -i rtmp://localhost/test/$name -an -c:v copy -flags global_header -bsf dump_extra -f rtp rtp://localhost:5004;

}


    


  • Trouble getting the Node ffmpeg module to work with paths that have spaces in them

    26 juin 2020, par Jacob

    Title is pretty self-explanatory. I'm having trouble getting the Node ffmpeg module to work with paths to have spaces in them.

    


    import ffmpeg from "ffmpeg"

try {
    let process = new ffmpeg("C:\\Users\\JR\\Desktop\\new folder\\test.m4a");
    process.then(video => {
        video.save("C:\\Users\\JR\\Desktop\\test.mp3", (error, file) => {
            if (!error) {
                console.log("converted!");
            } else {
                console.log("uh oh error: " + error);
            }
        });
    },
    error => {
        console.log("Error: " + error);
    });
} catch (error) {
    console.log(error.code);
    console.log(error.msg);
}


    


    Below are all the variations I've tried. They all result in either an error from the module itself saying The input file does not exist or an error from ffmpeg saying No such file or directory.

    


    let process = new ffmpeg("C:\\Users\\JR\\Desktop\\new folder\\test.m4a");

let process = new ffmpeg('C:\\Users\\JR\\Desktop\\new folder\\test.m4a');

let process = new ffmpeg('"C:\\Users\\JR\\Desktop\\new folder\\test.m4a"');

let process = new ffmpeg("C:/Users/JR/Desktop/new folder/test.m4a");

let process = new ffmpeg('C:/Users/JR/Desktop/new folder/test.m4a');

let process = new ffmpeg("C:\\Users\\JR\\Desktop\\new\ folder\test.m4a");

let process = new ffmpeg('C:\\Users\\JR\\Desktop\\new\ folder\test.m4a');


    


    And probably several other variations that I'm forgetting. Any ideas ?