
Recherche avancée
Autres articles (25)
-
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...) -
Des sites réalisés avec MediaSPIP
2 mai 2011, parCette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page. -
Ajouter notes et légendes aux images
7 février 2011, parPour pouvoir ajouter notes et légendes aux images, la première étape est d’installer le plugin "Légendes".
Une fois le plugin activé, vous pouvez le configurer dans l’espace de configuration afin de modifier les droits de création / modification et de suppression des notes. Par défaut seuls les administrateurs du site peuvent ajouter des notes aux images.
Modification lors de l’ajout d’un média
Lors de l’ajout d’un média de type "image" un nouveau bouton apparait au dessus de la prévisualisation (...)
Sur d’autres sites (4797)
-
Anomalie #3520 : [3.1 22372] Le clic du milieu de la souris referme le détail observé
2 août 2015, par realet RealETEn fait, le comportement sur ces triangles est dérogatoire par rapport à celui habituel : au lieu que ce soit au survol de la souris que ça se déplie, c’est au clic.
Cependant, c’est peut-être mieux pour les tablettes et mobiles.
-
FFMPEG Extra just codec information
18 juin 2014, par JimI am planning on using FFMPeg with Java, to detect a specific codec and convert this to another. Using the FFMpeg line -
ffprobe -v quiet -print_format json -show_streams "input.avi"
I can print off all of the stream information of the video, but this includes video information, audio information, all metadata, all tags and other information which I just don’t need.
Question : Is it possible to launch an FFMpeg command which only returns the video codec, so I don’t have to wave through unnecessary information ?
-
How to Configure nginx with stunnel to accept parameters for different FB Live Streams OR rtmps with FFMPEG
15 septembre 2020, par Yogesh AgarwalI want to setup RTMPS and learned that only way around is by using nginx and stunnel. I have the setup and it works with just one configured key.



I have several different keys and all are dynamic. A lot of different urls too.



My Goal is to add a parameter or some way by which i can send the custom url to nginx and it can send to Stunnel, and it can read the custom url and forward the encrypted stream to that url.



I am able to get everything done right via ngnix and stunnel but with preconfigured key only - But i want Dynamic key here.. just like a parameter where you can simply plug and send the stream.



I even tried to set this way.



push rtmp ://127.0.0.1:19350/rtmp/ ;



so i can simple forward the stream to rtmp ://127.0.0.1:19350/rtmp/my-key and it takes my-key and forward the stream via stunnel to facebook. but i cannot get it work.



I am about to bang my heads in walls. Kindly give me some pointers.. I am not sure how to do it via ffmpeg as it says it cannot find rtmps protocol.



My Nginx Config :



# RTMP configuration
rtmp {
 server {
 listen 1935; # Listen on standard RTMP port
 chunk_size 4000;
 # This application is to accept incoming stream
 application live {


 live on; # Allows live input from above
 exec_push rtmp://127.0.0.1:19350/rtmp/$name;
 allow play 127.0.0.1;
 dash on;
 dash_path /var/tmp/dashme;

 hls on; # Enable HTTP Live Streaming
 hls_cleanup on;
 hls_sync 100ms;
 hls_fragment 2s;
 hls_path /var/tmp/live/;


 }




and My Stunnel Config :



setuid = nobody
setgid = nobody
pid=/tmp/stunnel.pid
output = /var/log/stunnel.log
;include = /etc/stunnel/conf.d

[fb-live]
client = yes
accept = 127.0.0.1:19350
connect = live-api-s.facebook.com:443
;verifyChain = no