Recherche avancée

Médias (1)

Mot : - Tags -/bug

Autres articles (52)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

  • 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

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

Sur d’autres sites (15231)

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

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