Recherche avancée

Médias (91)

Autres articles (74)

  • 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 (...)

  • 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 (...)

  • 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 (12422)

  • Getting error while deploying application with node-media-serve module and ffmpeg buildpack in heroku

    16 septembre 2020, par Anurag Gautam

    I have created a MERN app with video streaming by using node-media-serve module, with following configuration

    


    trans: {
  ffmpeg: '/vendor/ffmpeg',
   tasks: [] ,
   .....
}


    


    In local I have installed ffmpeg in trans.ffmpeg. and its working fine, But how we need to install ffmpeg in heroku .

    


    I have tried by adding heroku buildpacks
heroku buildpacks:add https://github.com/jonathanong/heroku-buildpack-ffmpeg-latest.git but its showing me error. May be some issue with config only.

    


    Heroku error :
2020-09-16T11:23:54.292896+00:00 app[web.1]: 9/16/2020 11:23:54 23 [ERROR] Node Media Trans Server startup failed. ffmpeg:/vendor/ffmpeg cannot be executed.

    


    Guys can you please help me reslove this issue

    


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

}