
Recherche avancée
Médias (1)
-
Publier une image simplement
13 avril 2011, par ,
Mis à jour : Février 2012
Langue : français
Type : Video
Autres articles (60)
-
Supporting all media types
13 avril 2011, parUnlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)
-
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 (...) -
Configuration spécifique d’Apache
4 février 2011, parModules spécifiques
Pour la configuration d’Apache, il est conseillé d’activer certains modules non spécifiques à MediaSPIP, mais permettant d’améliorer les performances : mod_deflate et mod_headers pour compresser automatiquement via Apache les pages. Cf ce tutoriel ; mode_expires pour gérer correctement l’expiration des hits. Cf ce tutoriel ;
Il est également conseillé d’ajouter la prise en charge par apache du mime-type pour les fichiers WebM comme indiqué dans ce tutoriel.
Création d’un (...)
Sur d’autres sites (9080)
-
ffmpeg : VLC won’t open .sdp files generated by ffmpeg
8 mai 2020, par tiredamage42TLDR : VLC or Quicktime won’t open .sdp video stream files generated by ffmpeg, even though ffplay does.



Web development and ffmpeg noob, so apologies if I’m using the wrong terminology :



I’m trying to stream my desktop capture (on OSX) using ffmpeg, sending it out via rtp protocol. 
As of right now I’m just testing it out by streaming it over a port in my localhost (4000). And trying to play it locally.



The problem is that when I try and open the .sdp file generated by the ffmpeg command, VLC opens it and immediately stops, no errors or anything, and shows that it has a duration of 0:00. Quicktime won’t event open the file in the first place.



ffplay does play the stream and I can see my desktop in the player window (with a significant loss in quality though). Even so there are a ton of warning and errors that show up intermittently (outlined below)



I’m not sure if it’s a problem in the way I start the ffmpeg stream, the command is after a ton of iterations of trying to just make it work, so my options might be way wrong.



command to 'serve' the desktop capture :



./ffmpeg -f avfoundation -s 1920x1080 -r 60 -i "1" -an \
-vcodec libx264 -preset ultrafast -tune zerolatency -pix_fmt yuv420p \
-sdp_file video.sdp -rtsp_transport tcp -f rtp rtp://127.0.0.1:4000




SDP file that’s generated with the ffmpeg command :



SDP:
v=0
o=- 0 0 IN IP4 127.0.0.1
s=No Name
c=IN IP4 127.0.0.1
t=0 0
a=tool:libavformat 58.29.100
m=video 4000 RTP/AVP 96
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1




ffplay command used to play the stream :



./ffplay -probesize 32 -analyzeduration 0 -sync ext \
-fflags nobuffer -fflags discardcorrupt -flags low_delay -framedrop \
-strict experimental -avioflags direct \
-protocol_whitelist file,rtp,udp -I video.sdp




For a while before ffplay starts I see a bunch of these errors repeating (in red) :



[h264 @ 0x7ff6b788de00] non-existing PPS 0 referenced
[h264 @ 0x7ff6b788de00] decode_slice_header error
[h264 @ 0x7ff6b788de00] no frame!




then the window seems to 'catch up' to the stream and actually shows the desktop capture, and I get these errors and warnings on a regular interval :



1- in a yellow warning color :



[sdp @ 0x7fc85b830600] RTP: missed 4 packets
[sdp @ 0x7fc85b830600] max delay reached. need to consume packet




2-in a red error color :



[h264 @ 0x7fc85b02aa00] out of range intra chroma pred mode
[h264 @ 0x7fc85b02aa00] error while decoding MB 132 32




(I have a feeling that the above errors have to do with previewing the desktop capture in the desktop I’m capturing and causing pixels in the display to overflow)



Edit :
So, I solved the issue soon after posting, but will leave this up in case anyone runs into the same problem.



The solution was to remove the top line in the .sdp file that said
SDP:


-
Revision 32596 : minuscules et fin pour aujourd’hui
1er novembre 2009, par fil@… — Logminuscules et fin pour aujourd’hui
-
Introducing Crash Analytics for Matomo