
Recherche avancée
Autres articles (108)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Ajouter des informations spécifiques aux utilisateurs et autres modifications de comportement liées aux auteurs
12 avril 2011, parLa manière la plus simple d’ajouter des informations aux auteurs est d’installer le plugin Inscription3. Il permet également de modifier certains comportements liés aux utilisateurs (référez-vous à sa documentation pour plus d’informations).
Il est également possible d’ajouter des champs aux auteurs en installant les plugins champs extras 2 et Interface pour champs extras. -
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
Sur d’autres sites (15084)
-
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)


-
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>
-
lavf/dashenc : Don't put non-mp4 streams in HLS manifests.
28 novembre 2018, par Andrey Semashevlavf/dashenc : Don't put non-mp4 streams in HLS manifests.
The only native HLS implementation in the wild (Safari browser) doesn't
support WebM. And at least some MSE-based players (e.g. shaka-player)
cannot handle WebM media segments when playing HLS. So just skip non-mp4
streams from HLS manifests. Note that such streams will still be described
by the DASH manifest and therefore consumed by players supporting DASH.