
Recherche avancée
Autres articles (106)
-
Gestion des droits de création et d’édition des objets
8 février 2011, parPar défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;
-
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 (...)
-
Dépôt de média et thèmes par FTP
31 mai 2013, parL’outil MédiaSPIP traite aussi les média transférés par la voie FTP. Si vous préférez déposer par cette voie, récupérez les identifiants d’accès vers votre site MédiaSPIP et utilisez votre client FTP favori.
Vous trouverez dès le départ les dossiers suivants dans votre espace FTP : config/ : dossier de configuration du site IMG/ : dossier des média déjà traités et en ligne sur le site local/ : répertoire cache du site web themes/ : les thèmes ou les feuilles de style personnalisées tmp/ : dossier de travail (...)
Sur d’autres sites (10469)
-
Why does iftop show no bandwidth from a multicast IP but tcpdump does ? ffmpeg also cannot capture from the multicast
22 mars 2018, par LennyI ran into a puzzling problem when trying to receive a multicast IP (of a video from 239.193.140.11:1234).
When
$tcpdump dst 239.193.140.11 -w capturedData.pcap
, the packets are captured correctly.eg, 11:05:25.357138 IP 192.168.34.34.46192 > 239.193.140.11.1234 : UDP, length 1328
This means that my machine is receiving the multicast IP packets.
However, when
$iftop -i any
is run, iftop doesn’t show any bandwidth from 239.193.140.11. Furthermore, when I try to capture the multicast packets with ffmpeg :$ffmpeg -i udp://239.193.140.11:1234?localaddr=192.168.34.34
, no packets are captured.Why is there a discrepancy between what tcpdump and iftop shows, and how to resolve it so that ffmpeg can capture correctly ?
-
compile the ffmpeg3.3 for Mac OS show ERROR : libmp3lame >= 3.98.3 not found
4 mars 2018, par MR.PJI use my mac to compile the ffmpeg3.3 for Mac OS according to https://trac.ffmpeg.org/wiki/CompilationGuide/macOS.I tried the first(which through Homebrew) and third(which builds it yourself) method,the first method is ok.
But the third, compiling FFmpeg myself and Installing dependencies with Homebrew.I don’t know the meaning of this sentence enter image description here
after this step :
./configure --prefix=/usr/local --enable-gpl --enable-nonfree --enable-libass \
--enable-libfdk-aac --enable-libfreetype --enable-libmp3lame \
--enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libopus --enable-libxvid \
--samples=fate-suite/terminal show :
RROR: libmp3lame >= 3.98.3 not found
when I use
locate libmp3lame.a
,it is at ’/usr/local/Cellar/lame/3.99.5/lib/libmp3lame.a’.I also try
--enable-libmp3lame --extra-ldflags=-L/usr/local/lib
to solve,but it is no effect.How to solve this
ERROR: libmp3lame >= 3.98.3 not found
-
Streaming UDP packets to two different ports (for video and audio). Video works fine, but the audio does not show
8 avril 2018, par Winston ChenI am taking a rtsp stream, split the video and audio out, and stream them to two different ports respectively using
gstreamer
so that myffserver
would be able to display the stream on my browser.My gstreamer pipeline :
gst-launch-1.0 -v rtspsrc location=rtsp://wowzaec2demo.streamlock.net/vod/mp4:BigBuckBunny_115k.mov latency=300 timeout=0 drop-on-latency=true rtp-blocksize=4096 name=rtsp_source ! \
queue ! capsfilter caps="application/x-rtp,media=video" ! rtph264depay ! h264parse ! rtph264pay config-interval=1 pt=96 ! udpsink host=127.0.0.1 port=9527 rtsp_source. ! \
queue ! rtpmp4apay pt=97 ! udpsink host=127.0.0.1 port=9327Here comes the sdp and my ffmpeg commnad :
m=video 9527 RTP/AVP 96
a=rtpmap:96 H264/90000
c=IN IP4 127.0.0.1
m=audio 9327 RTP/AVP 97
a=rtpmap:97 mpeg4-generic/48000/6
c=IN IP4 127.0.0.1ffmpeg -protocol_whitelist "file,tcp,rtp,udp" -i ~/test.sdp -max_muxing_queue_size 1024 http://localhost:8090/feed1.ffm
And finally, this is my ffserver config (the important part) :
<feed> # This is the input feed where FFmpeg will send
File ./feed1.ffm # video stream.
FileMaxSize 1GB # Maximum file size for buffering video
ACL allow 127.0.0.1 # Allowed IPs
</feed>
<stream> # Output stream URL definition
Feed feed1.ffm # Feed from which to receive video
Format webm
# NoDefaults
# NoAudio
# Audio settings
AudioCodec vorbis
AudioBitRate 64 # Audio bitrate
# Video settings
VideoCodec libvpx
VideoSize 240x160 # Video resolution
VideoFrameRate 10 # Video FPS
AVOptionVideo flags +global_header # Parameters passed to encoder
# (same as ffmpeg command-line parameters)
PreRoll 0
StartSendOnKey
VideoGopSize 12
VideoBitRate 256
</stream>The thing is that if I take away the audio part and apply
NoAudio
, the video streams fine. However, I could not get the audio to work. Am I doing anything wrong ?