
Recherche avancée
Médias (2)
-
Rennes Emotion Map 2010-11
19 octobre 2011, par
Mis à jour : Juillet 2013
Langue : français
Type : Texte
-
Carte de Schillerkiez
13 mai 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Texte
Autres articles (44)
-
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 -
Contribute to a better visual interface
13 avril 2011MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community. -
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 (6070)
-
ffprobe on windows no output beyond " { " (ffmpeg-6.0-essentials_build) [closed]
6 avril 2023, par StahkubI'm attempting to use ffprobe on an rtsp stream using the following command :


ffprobe -loglevel quiet -rtsp_transport tcp -select_streams v:0 -show_entries stream=width,height -of json rtsp://stream



however the only thing showing in the console after this command is "" on windows, but works on wsl






the windows command will never return and must be killed. Any ideas ?


Reinstalled ffmpeg, different versions, rebooted pc, tried absolute path to ffprobe, tried running ffprobe using python. Tried piping output to a file, same result. I've searched around and haven't found a similar issue.


-
ffprobe on windows no output beyond " { " (ffmpeg-6.0-essentials_build) (in a python script) [closed]
7 avril 2023, par StahkubI'm attempting to use ffprobe (in a python script) on an rtsp stream using the following command :


ffprobe -loglevel quiet -rtsp_transport tcp -select_streams v:0 -show_entries stream=width,height -of json rtsp://stream



however the only thing showing in the console after this command is "" on windows, but works on wsl where it produces full json output and not just a single ""


the windows command will never return and must be killed. Any ideas ?


Reinstalled ffmpeg, different versions, rebooted pc, tried absolute path to ffprobe, tried running ffprobe using python. Tried piping output to a file, same result. I've searched around and haven't found a similar issue.


-
ffmpeg wont "gracefully" terminate using q or kill -2
24 mai 2023, par Jeff ThompsonI am trying to run a bash command on Ubuntu to pull video from a stream and make an .mp4 with it. Here is the command I am using.


ffmpeg -rtsp_transport tcp -i 'rtsp://username:password!@ipaddress/?inst=1' -c copy -f segment -segment_time 180 -reset_timestamps 1 ipaddress_day_3_2_%d.mp4


It connects and begins copying the stream fine, the issue comes with trying to stop the process. It states press [q] to stop, which does not work. I have also tried kill -2 pid and kill -15 pid. Where pid is the process id. However kill -9 pid works and ctrl+c works. The issue with killing it this way is it corrupts the .mp4 rendering it useless. This is the error I get when using ctrl+c or kill -9.


av_interleaved_write_frame(): Immediate exit requested [segment @ 0x56337ec42980] Failure occurred when ending segment 'ipaddress_day_3_2_0.mp4' Error writing trailer of ipaddress_day_3_2_0%d.mp4: Immediate exit requested


One thing to note is pressing [q] did work once, when I first started working on this but has not since.


Thank You.


I have tried kill -2 pid, kill -15 pid and [q], which I expected to "gracefully" terminate it.
kill -9 pid and ctrl+c will forcefully terminate it but corrupt the file.