Recherche avancée

Médias (9)

Mot : - Tags -/soundtrack

Autres articles (46)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 is the first MediaSPIP stable release.
    Its official release date is June 21, 2013 and is announced here.
    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 (...)

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

Sur d’autres sites (5767)

  • Transcode H264 stream into mpeg2 with ffmpeg and nginx-rtmp module

    21 mai 2015, par inside

    I am using nginix web server and nginx-rtmp module for managing my video stream encoded in h264. Here is my nginx conf :

    rtmp {
    
server {
    
    listen 1935;
    

    
    application big {
    
        live on;
    

    
    exec ffmpeg -re -i rtmp://localhost:1935/$app/$name -vcodec 
    
         libx264 -vprofile baseline -acodec libvo_aacenc -ac 1 -ar 441000 
    
         -f flv rtmp://localhost:1935/hls/${name};
    
      }
    
   }
    

    
   application hls
    
   {
    
      live on;
    
      hls_path /usr/local/nginx/html/video;
    
   }
    
}

    it works well in browser, however because my mobile client is Adobe Air it would only work on Android but not Apple, because Apple doesn’t support H264 encoding through AIR applications, so I was trying to transcode the stream to something supported for example mpeg. And this is how I changed my ffmpeg :

        exec ffmpeg -re -i rtmp://localhost:1935/$app/$name -vcodec 
    
         mpeg2video -acodec copy -b:v 10M -b:a 128k 
    
         -f mpegts rtmp://localhost:1935/hls/${name};

    However it just won’t show the video not in a browser nor on device, my assumption is that it probably failed to transcode.

    Maybe I am missing something ? Any ideas are highly appreciated.
    Thank you.

  • Révision 108893 : Bizarre, le module figure dans traduction.txt mais ne se trouve pas dans trad.sp...

    10 février 2018, par george@middleeastwatch.net

  • restream the rtmp stream by using ffmpeg and nginx-rtmp-module

    30 octobre 2014, par Stanislav

    This is my current rtmp configuration for localhost, everything works well

      # Transcoding (ffmpeg needed)
    

    
   application big {
    

    
       live on;
    

    
   exec /usr/local/bin/ffmpeg -re -i rtmp://localhost:1935/$app/$name -vcodec flv -acodec copy -f flv rtmp://localhost:1935/anotherapp/${name};
    

    
   }
    

    
application anotherapp {
    
       live on;
    
  }

    This is what I am trying to achive

      # Transcoding (ffmpeg needed)
    

    
   application big {
    

    
       live on;
    

    
   # rtmp://localhost:1935/$app/$name  -> Receive this address dynamically from outside, for example the address will be rtmp://142.204.134.93/red5app/12345
    
   # rtmp://localhost:1935/anotherapp/${name};  -> and create new stream on my server with the same name. 
    
   # So this will be the result:
    

    
   exec /usr/local/bin/ffmpeg -re -i  rtmp://142.204.134.93/red5app/12345 -vcodec flv -acodec copy -f flv rtmp://localhost:1935/anotherapp/12345;
    

    
   }
    

    
application anotherapp {
    
       live on;
    
  }

    Thank you very much in advance.

Navigation