
Recherche avancée
Médias (91)
-
Les Miserables
9 décembre 2019, par
Mis à jour : Décembre 2019
Langue : français
Type : Textuel
-
VideoHandle
8 novembre 2019, par
Mis à jour : Novembre 2019
Langue : français
Type : Video
-
Somos millones 1
21 juillet 2014, par
Mis à jour : Juin 2015
Langue : français
Type : Video
-
Un test - mauritanie
3 avril 2014, par
Mis à jour : Avril 2014
Langue : français
Type : Textuel
-
Pourquoi Obama lit il mes mails ?
4 février 2014, par
Mis à jour : Février 2014
Langue : français
-
IMG 0222
6 octobre 2013, par
Mis à jour : Octobre 2013
Langue : français
Type : Image
Autres articles (104)
-
Support de tous types de médias
10 avril 2011Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)
-
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...) -
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 (...)
Sur d’autres sites (11077)
-
ffmpeg , 2 network cards and multicast stream
18 juin 2015, par dropbasketmy knowledge of networks are very poor !!, am a newbie !! ;-)
I have a small server streaming ffmpeg installed on nginx with 2 network interfaces
p2p1 is used for WAN which provides http/ssh....
p4p1 is used to receive multicast data from intranet.
192.168.0.1 is public network gateway.
192.168.1.1 is private network gateway (commented for not have internet exit this network)
239.0.0.*/24 is multicast address.
Linux distribution
3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Distributor ID : Ubuntu
Description: Ubuntu 14.04.2 LTS
Release : 14.04
Codename : trustyMy network interfaces config
auto lo
iface lo inet loopback
# NET1
auto p2p1
iface p2p1 inet static
address 192.168.0.100
netmask 255.255.255.0
gateway 192.168.0.1
# NET2
auto p4p1
iface p4p1 inet static
address 192.168.1.100
netmask 255.255.255.0
### gateway 192.168.1.1Now my route table
root@srv:# route
Tabla de rutas IP del núcleo
Destino Pasarela Genmask Indic Métric Ref Uso Interfaz
default 192.168.0.1 0.0.0.0 UG 0 0 0 p2p1
192.168.0.0 * 255.255.255.0 U 0 0 0 p2p1
192.168.1.0 * 255.255.255.0 U 0 0 0 p4p1I’m using udpxy on port 4022 for converting IPTV multicast to unicast HTTP
udpxy -p 4022
I execute this
/usr/bin/ffmpeg -i "http://127.0.0.1:4022/rtp/239.0.0.76:8208" -map 0:0 -map 0:1 -c:v libx264 -vf scale=-1:720 -r 25 -profile:v high -level:v 4.0 -crf 18 -preset veryfast -maxrate 2000k -bufsize 2200k -c:a aac -ab 128k -strict -2 -ac 2 -f flv rtmp://127.0.0.1:11111/rtmp/channel1;
ffmpeg version 2.7 Copyright (c) 2000-2015 the FFmpeg developers
built with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1)
configuration: --extra-libs=-ldl --prefix=/opt/ffmpeg --enable-avresample --disable-debug --enable-nonfree --enable-gpl --enable-version3 --enable-libopencore-amrnb --enable-libopencore-amrwb --disable-decoder=amrnb --disable-decoder=amrwb --enable-libpulse --enable-libx264 --enable-libx265 --enable-libfdk-aac --enable-libvorbis --enable-libmp3lame --enable-libopus --enable-libvpx --enable-libspeex --enable-libass --enable-avisynth --enable-libsoxr --enable-libxvid --enable-libvo-aacenc --enable-libvidstab
libavutil 54. 27.100 / 54. 27.100
libavcodec 56. 41.100 / 56. 41.100
libavformat 56. 36.100 / 56. 36.100
libavdevice 56. 4.100 / 56. 4.100
libavfilter 5. 16.101 / 5. 16.101
libavresample 2. 1. 0 / 2. 1. 0
libswscale 3. 1.101 / 3. 1.101
libswresample 1. 2.100 / 1. 2.100
libpostproc 53. 3.100 / 53. 3.100
http://127.0.0.1:4022/rtp/239.0.0.76:8208: Invalid data found when processing inputas I can solve this problem ??
Thanks in advance -
Flush & Latency Issue with Fragmented MP4 Creation in FFMPEG
30 septembre 2015, par galbarmI’m creating a fragmented mp4 for html5 streaming, using the following command :
-i rtsp://172.20.28.52:554/h264 -vcodec copy -an -f mp4 -reset_timestamps 1 -movflags empty_moov+default_base_moof+frag_keyframe -loglevel quiet -
- "-i rtsp ://172.20.28.52:554/h264" because the source is h264 in rtp packets stream from an ip camera.
For the sake of testing, the camera is set with GOP of 1 (i.e. all frames are key frames) - "-vcodec copy" because I don’t need transcoding, only remuxing to mp4.
- "-movflags empty_moov+default_base_moof+frag_keyframe" to create a fragmented mp4 according to the media source extensions spec.
- "-" at the end in order to output the mp4 to stdout. I’m grabbing the ouput and sending it to the webclient through web sockets.
Everything is working well, expect for a latency issue which I’m trying to solve.
If I’m logging every time a data is coming in from stdout, with the timestamp of arrival, I get this output :16/06/2015 15:40:45.239 got data size = 24
16/06/2015 15:40:45.240 got data size = 7197
16/06/2015 15:40:45.241 got data size = 32768
16/06/2015 15:40:45.241 got data size = 4941
16/06/2015 15:40:45.241 got data size = 12606
16/06/2015 15:40:45.241 got data size = 6345
16/06/2015 15:40:45.241 got data size = 6339
16/06/2015 15:40:45.242 got data size = 6336
16/06/2015 15:40:45.242 got data size = 6361
16/06/2015 15:40:45.242 got data size = 6337
16/06/2015 15:40:45.242 got data size = 6331
16/06/2015 15:40:45.242 got data size = 6359
16/06/2015 15:40:45.243 got data size = 6346
16/06/2015 15:40:45.243 got data size = 6336
16/06/2015 15:40:45.243 got data size = 6338
16/06/2015 15:40:45.243 got data size = 6357
16/06/2015 15:40:45.243 got data size = 6357
16/06/2015 15:40:45.243 got data size = 6322
16/06/2015 15:40:45.243 got data size = 6359
16/06/2015 15:40:45.244 got data size = 6349
16/06/2015 15:40:45.244 got data size = 6353
16/06/2015 15:40:45.244 got data size = 6382
16/06/2015 15:40:45.244 got data size = 6403
16/06/2015 15:40:45.304 got data size = 6393
16/06/2015 15:40:45.371 got data size = 6372
16/06/2015 15:40:45.437 got data size = 6345
16/06/2015 15:40:45.504 got data size = 6352
16/06/2015 15:40:45.571 got data size = 6340
16/06/2015 15:40:45.637 got data size = 6331
16/06/2015 15:40:45.704 got data size = 6326
16/06/2015 15:40:45.771 got data size = 6360
16/06/2015 15:40:45.838 got data size = 6294
16/06/2015 15:40:45.904 got data size = 6328
16/06/2015 15:40:45.971 got data size = 6326
16/06/2015 15:40:46.038 got data size = 6326
16/06/2015 15:40:46.105 got data size = 6340
16/06/2015 15:40:46.171 got data size = 6341
16/06/2015 15:40:46.238 got data size = 6332
As you can see, the first 23 lines (which contain data of about 1.5 secs of video) are arriving almost instantly, and then the delay between each 2 consecutive lines is 70ms which makes sense because the video is 15 frames per sec.
This behavior introduces a latency of about 1.5 sec.It looks like a flushing issue because I don’t see any reason why would ffmpeg need to hold the first 23 frames in memory, especially since each frame is a fragment of it’s own inside the mp4.
I couldn’t however, find any method that would cause ffmpeg to flush this data faster.Has anyone got a suggestion ?
I’d like to note that this is a follow up question to this one :
Live streaming dash content using mp4box - "-i rtsp ://172.20.28.52:554/h264" because the source is h264 in rtp packets stream from an ip camera.
-
Ffmpeg performance issue when transcoding to webm
14 septembre 2015, par AlgoldI have recently updated ffmpeg from version 2.0.2 to the most recent release 2.7. I installed it using the same building configuration as the old version and the same codecs version (libvpx and h264). When I tried to transcode an mp4 video to webm, I found out that the speed of the new version is significantly lower (3 times) than the old one. I run this on two identical 8 core machines (Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz) - OS : Ubuntu 14.04. Below is the command I run :
/usr/local/bin/ffmpeg -i in.mp4 -f webm -vcodec libvpx -b:v 1000K out.webm
These are the outputs for the two versions :
v 2.0.2
ffmpeg version 2.0.2 Copyright (c) 2000-2013 the FFmpeg developers
built on Jan 7 2015 13:51:25 with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1)
configuration: --disable-ffplay --disable-ffserver --enable-libxvid --enable-gpl --enable-nonfree --enable-pthreads --enable-libmp3lame --enable-libx264 --enable-libfaac --enable-zlib --enable-avfilter --enable-libfreetype --enable-libfdk_aac --enable-libtheora --enable-libvorbis --enable-libvpx --enable-pic --enable-shared
libavutil 52. 38.100 / 52. 38.100
libavcodec 55. 18.102 / 55. 18.102
libavformat 55. 12.100 / 55. 12.100
libavdevice 55. 3.100 / 55. 3.100
libavfilter 3. 79.101 / 3. 79.101
libswscale 2. 3.100 / 2. 3.100
libswresample 0. 17.102 / 0. 17.102
libpostproc 52. 3.100 / 52. 3.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'in.mp4':
Metadata:
major_brand : isom
minor_version : 512
compatible_brands: isomiso2avc1mp41
encoder : Lavf55.12.100
Duration: 00:00:10.19, start: 0.000000, bitrate: 1724 kb/s
Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 1480 kb/s, 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc
Metadata:
handler_name : VideoHandler
Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 253 kb/s
Metadata:
handler_name : SoundHandler
[libvpx @ 0x22f3760] v1.3.0
Output #0, webm, to 'out.webm':
Metadata:
major_brand : isom
minor_version : 512
compatible_brands: isomiso2avc1mp41
encoder : Lavf55.12.100
Stream #0:0(und): Video: vp8 (libvpx), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], q=-1--1, 1000 kb/s, 1k tbn, 29.97 tbc
Metadata:
handler_name : VideoHandler
Stream #0:1(und): Audio: vorbis (libvorbis), 44100 Hz, stereo, fltp
Metadata:
handler_name : SoundHandler
Stream mapping:
Stream #0:0 -> #0:0 (h264 -> libvpx)
Stream #0:1 -> #0:1 (aac -> libvorbis)
Press [q] to stop, [?] for help
frame= 302 fps= 23 q=0.0 Lsize= 1445kB time=00:00:10.18 bitrate=1161.9kbits/s
video:1304kB audio:128kB subtitle:0 global headers:4kB muxing overhead 0.644833%v 2.7
ffmpeg version 2.7 Copyright (c) 2000-2015 the FFmpeg developer built with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1)
configuration: --disable-ffplay --disable-ffserver --enable-libxvid --enable-gpl --enable-nonfree --enable-libmp3lame --enable-libx264 --enable-libfaac --enable-zlib --enable-libass --enable-pthreads --enable-avfilter --enable-libfreetype --enable-libfdk_aac --enable-libtheora --enable-libvorbis --enable-libvpx --enable-pic --enable-shared --enable-openssl
libavutil 54. 27.100 / 54. 27.100
libavcodec 56. 41.100 / 56. 41.100
libavformat 56. 36.100 / 56. 36.100
libavdevice 56. 4.100 / 56. 4.100
libavfilter 5. 16.101 / 5. 16.101
libswscale 3. 1.101 / 3. 1.101
libswresample 1. 2.100 / 1. 2.100
libpostproc 53. 3.100 / 53. 3.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'in.mp4':
Metadata:
major_brand : isom
minor_version : 512
compatible_brands: isomiso2avc1mp41
encoder : Lavf56.36.100
Duration: 00:00:10.19, start: 0.000000, bitrate: 1596 kb/s
Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 1480 kb/s, 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc (default)
Metadata:
handler_name : VideoHandler
Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 125 kb/s (default)
Metadata:
handler_name : SoundHandler
[libvpx @ 0xfe4640] v1.3.0
Output #0, webm, to 'out.webm':
Metadata:
major_brand : isom
minor_version : 512
compatible_brands: isomiso2avc1mp41
encoder : Lavf56.36.100
Stream #0:0(und): Video: vp8 (libvpx), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], q=-1--1, 1000 kb/s, 29.97 fps, 1k tbn, 29.97 tbc (default)
Metadata:
handler_name : VideoHandler
encoder : Lavc56.41.100 libvpx
Stream #0:1(und): Audio: vorbis (libvorbis), 44100 Hz, stereo, fltp (default)
Metadata:
handler_name : SoundHandler
encoder : Lavc56.41.100 libvorbis
Stream mapping:
Stream #0:0 -> #0:0 (h264 (native) -> vp8 (libvpx))
Stream #0:1 -> #0:1 (aac (native) -> vorbis (libvorbis))
Press [q] to stop, [?] for help
frame= 302 fps=8.3 q=0.0 Lsize= 1410kB time=00:00:10.18 bitrate=1133.4kbits/s
video:1274kB audio:123kB subtitle:0kB other streams:0kB global headers:4kB muxing overhead: 0.909304%I tried ffmpeg 2.6.3 and the performance the same as for 2.7. Also it looks like when I transcode webm to mp4 2.7 is 30% faster than webm.
I tried to look if there are building configuration options for the new version but couldn’t find anything.
Can anyone suggest a possible reason for the worse speed performance of the new version when transcoding to webm ?