
Recherche avancée
Autres articles (60)
-
Publier sur MédiaSpip
13 juin 2013Puis-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 -
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...) -
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs
Sur d’autres sites (9541)
-
dashenc : move UTCTiming element to the end of the manifest
27 octobre 2017, par Peter Großedashenc : move UTCTiming element to the end of the manifest
Required by comformance XSD [1].
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
-
How to run ffmpeg on demand when someone opens my website with the player where a remote IP camera is displayed ?
8 mai 2023, par alexiterI set up an nginx server to stream from an IP camera located elsewhere, I used a windows server because it was the one I had no use for (I usually prefer linux), I would need to know how I can make the ffmpeg command run only when someone opens the website where the player is located.


This is my nginx.conf server code :


worker_processes 1;

error_log logs/error.log info;

events {
 worker_connections 1024;
}
rtmp {
 server {
 listen 1935;
 ping 30s;
 notify_method get;
 application live {
 live on;
 on_publish http://*******:8080/auth;
 dash on; 
 dash_path tmp/dash;
 
 
 }
 }
}
http{

 server {
 listen 8080;
 location /auth {
 if ($arg_psk = '*****') {
 return 201;
 }
 return 404;
 }
}
 
 server {
 listen 8443 ssl;
 server_name stream.*****.com;
 
 ssl on;
 ssl_certificate C:/Certbot/live/stream.*****.com/fullchain.pem;
 ssl_certificate_key C:/Certbot/live/stream.****.com/privkey.pem;
 ssl_session_timeout 5m;
 charset utf-8;
 location /dash {
 root tmp;
 add_header Cache-Control no-cache;
 }
 location / {
 root www;
 }
 

 }
}




The command that I use from the DOS console in windows is this :


ffmpeg -rtsp_transport tcp -i rtsp://*****:******@******.com:557/Streaming/Channels/101 -c copy -f flv -y -t 35 rtmp://********:1935/live/stream?psk=********



Basically what I need is that ffmpeg is not running constantly, only when someone wants to view the video from the IP camera. (I have programmed ffmpeg to finish after 35 seconds, although I will put five minutes later)


-
lavf/dashenc : update bitrates on dash_write_trailer
3 mars 2017, par Przemysław Sobalalavf/dashenc : update bitrates on dash_write_trailer
Provides a way to change bandwidth parameter inside DASH manifest after a non-CBR H.264 encoding.
Caller now is able to compute the bitrate by itself, after all packets have been written, and then set that value in AVFormatContext->streams->codecpar->bit_rate before calling av_write_trailer. As a result that value will be set in DASH manifest.Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>