
Recherche avancée
Autres articles (9)
-
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 (...)
-
Gestion générale des documents
13 mai 2011, parMédiaSPIP ne modifie jamais le document original mis en ligne.
Pour chaque document mis en ligne il effectue deux opérations successives : la création d’une version supplémentaire qui peut être facilement consultée en ligne tout en laissant l’original téléchargeable dans le cas où le document original ne peut être lu dans un navigateur Internet ; la récupération des métadonnées du document original pour illustrer textuellement le fichier ;
Les tableaux ci-dessous expliquent ce que peut faire MédiaSPIP (...) -
Les vidéos
21 avril 2011, parComme les documents de type "audio", Mediaspip affiche dans la mesure du possible les vidéos grâce à la balise html5 .
Un des inconvénients de cette balise est qu’elle n’est pas reconnue correctement par certains navigateurs (Internet Explorer pour ne pas le nommer) et que chaque navigateur ne gère en natif que certains formats de vidéos.
Son avantage principal quant à lui est de bénéficier de la prise en charge native de vidéos dans les navigateur et donc de se passer de l’utilisation de Flash et (...)
Sur d’autres sites (4770)
-
Use audio stream overs ssh with ffmpeg on web page
12 février 2020, par MauricioI need to broadcast the audio stream (WiFi camera at my home) on the website hosted on a VPS.
Here is the command executed from my home :
ffmpeg -i "rtsp://172.16.0.201:554/user=admin&password=root&channel=1&stream=1.sdp" -bufsize 24k -vn -acodec copy -f mpegts - | ssh -p 22222 root@mydomain.org 'ffmpeg -i - -vn -acodec libvorbis -ac 1 -ar 8000 -ab 64k -f mpegts "rtsp://127.0.0.1:53350/live.sdp"'
It seems to work because I get
ffmpeg version n4.2.2 Copyright (c) 2000-2019 the FFmpeg developers
built with gcc 9.2.0 (GCC)
configuration: --prefix=/usr --disable-debug --disable-static --disable-stripping --enable-fontconfig --enable-gmp --enable-gnutls --enable-gpl --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libdav1d --enable-libdrm --enable-libfreetype --enable-libfribidi --enable-libgsm --enable-libiec61883 --enable-libjack --enable-libmfx --enable-libmodplug --enable-libmp3lame --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libv4l2 --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxcb --enable-libxml2 --enable-libxvid --enable-nvdec --enable-nvenc --enable-omx --enable-shared --enable-version3
libavutil 56. 31.100 / 56. 31.100
libavcodec 58. 54.100 / 58. 54.100
libavformat 58. 29.100 / 58. 29.100
libavdevice 58. 8.100 / 58. 8.100
libavfilter 7. 57.100 / 7. 57.100
libswscale 5. 5.100 / 5. 5.100
libswresample 3. 5.100 / 3. 5.100
libpostproc 55. 5.100 / 55. 5.100
ffmpeg version 4.1.4-1~deb10u1 Copyright (c) 2000-2019 the FFmpeg developers
built with gcc 8 (Debian 8.3.0-6)
configuration: --prefix=/usr --extra-version='1~deb10u1' --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-avresample --disable-filter=resample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librsvg --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared
libavutil 56. 22.100 / 56. 22.100
libavcodec 58. 35.100 / 58. 35.100
libavformat 58. 20.100 / 58. 20.100
libavdevice 58. 5.100 / 58. 5.100
libavfilter 7. 40.101 / 7. 40.101
libavresample 4. 0. 0 / 4. 0. 0
libswscale 5. 3.100 / 5. 3.100
libswresample 3. 3.100 / 3. 3.100
libpostproc 55. 3.100 / 55. 3.100
Guessed Channel Layout for Input Stream #0.1 : mono
Input #0, rtsp, from 'rtsp://172.16.0.201:554/user=admin&password=root&channel=1&stream=1.sdp':
Metadata:
title : RTSP Session
Duration: N/A, start: 0.000000, bitrate: N/A
Stream #0:0: Video: h264 (Main), yuv420p(progressive), 640x360, 12 fps, 12 tbr, 90k tbn, 24 tbc
Stream #0:1: Audio: pcm_alaw, 8000 Hz, mono, s16, 64 kb/s
[mpegts @ 0x5582b6b14c40] frame size not set
Output #0, mpegts, to 'pipe:':
Metadata:
title : RTSP Session
encoder : Lavf58.29.100
Stream #0:0: Audio: pcm_alaw, 8000 Hz, mono, s16, 64 kb/s
Stream mapping:
Stream #0:1 -> #0:0 (copy)
Press [q] to stop, [?] for help
size= 146kB time=00:00:17.06 bitrate= 70.0kbits/s speed=1.16xBut when I look on the VPS I don’t see the port open with netstat.
Yet the process seems to be running
root 21801 0.2 2.1 265916 42188 ? SLs 15:03 0:00 ffmpeg -i - -vn -acodec libvorbis -ac 1 -ar 8000 -ab 64k -f mpegts rtsp://127.0.0.1:53350/live.sdp
I thought I would access the feed with a simple html page with this kind of code
<audio controls="controls">
<source type="audio/ogg"></source>
<em>Désolé, votre navigateur ne supporte pas l'audio HTML5</em>
</audio>iptables
Chain INPUT (policy DROP)
....
ACCEPT tcp -- anywhere anywhere tcp dpt:53350
ACCEPT udp -- anywhere anywhere udp dpt:53350
....
Chain FORWARD (policy DROP)
ACCEPT tcp -- anywhere anywhere tcp dpt:53350
ACCEPT udp -- anywhere anywhere udp dpt:53350
....
Chain OUTPUT (policy DROP)
ACCEPT tcp -- anywhere anywhere tcp dpt:53350
ACCEPT udp -- anywhere anywhere udp dpt:53350
.... -
ffmpeg audio stream retiming for infinite input
26 février 2020, par AeonI have a ffmpeg process that reads input data from stdout infinitely.
Its input data are mkv (matroska) containers (sent to stdin by another process), each container contains 4 audio streams (without any video) - 3 ACC streams and 1 FLAC stream. The output of this process isdash
muxer.ffmpeg -hide_banner -re -fflags +getpts -avoid_negative_ts make_non_negative -stream_loop -1 -f matroska -i pipe: -map 0 -c:a copy -strict -2 -f dash -use_timeline 1 -use_template 1 -seg_duration 5 -dash_segment_type mp4 manifest.mpd
The problem occurs after the first muxing of obtained mkv file. When it’s time to mux the next one from pipe, I get following messages :
[matroska,webm @ 000001d3050bba40] Found unknown-length element with ID 0x18538067 at pos. 0x54c766 for which no syntax for parsing is available.
[matroska,webm @ 000001d3050bba40] Seek to desired resync point failed. Seeking to earliest point available instead.
[dash @ 000001ac98349080] Non-monotonous DTS in output stream 0:0; previous: 881714, current: 51200; changing to 881715. This may result in incorrect timestamps in the output file.
[dash @ 000001ac98349080] Non-monotonous DTS in output stream 0:1; previous: 881714, current: 51200; changing to 881715. This may result in incorrect timestamps in the output file.
[dash @ 000001ac98349080] Non-monotonous DTS in output stream 0:2; previous: 881714, current: 51200; changing to 881715. This may result in incorrect timestamps in the output file.
[dash @ 000001ac98349080] Non-monotonous DTS in output stream 0:3; previous: 884005, current: 51200; changing to 884006. This may result in incorrect timestamps in the output file.
[dash @ 000001ac98349080] Non-monotonous DTS in output stream 0:3; previous: 884006, current: 51244; changing to 884007. This may result in incorrect timestamps in the output file.
[dash @ 000001ac98349080] Non-monotonous DTS in output stream 0:3; previous: 884007, current: 51244; changing to 884008. This may result in incorrect timestamps in the output file.
[dash @ 000001ac98349080] Non-monotonous DTS in output stream 0:3; previous: 884008, current: 51288; changing to 884009. This may result in incorrect timestamps in the output file.
[dash @ 000001ac98349080] Non-monotonous DTS in output stream 0:3; previous: 884009, current: 51288; changing to 884010. This may result in incorrect timestamps in the output file.
[dash @ 000001ac98349080] Non-monotonous DTS in output stream 0:3; previous: 884010, current: 51332; changing to 884011. This may result in incorrect timestamps in the output file.
[dash @ 000001ac98349080] Non-monotonous DTS in output stream 0:3; previous: 884011, current: 51332; changing to 884012. This may resul
...and
dash
muxer simply stops generating new segments. I do understand that it’s an issue with timestamps, but I don’t know how to fix that.I’ve tried to use
-fflags +getpts
- no success.
use_wallclock_as_timestamps 1
solves the "Non-monotonous DTS..." issue, but brings in a bunch of issues with playback, like freezing, breaking, etc., so the playback becomes completely unlistenable.
Something strange also happens to the SegmentTemplate node of the manifest - itstimescale
attribute is set to 44100, although there should be 1000000 (-frag_duration 1
is ignored in this case)Question : I’m asking for your help in re-timing, i.e. generating the correct timestamps for dash muxing for each new incoming file in the pipe.
-
Timeout error while running FFmpeg as a process in php
13 août 2021, par Karthikeyan BalusamyI'm trying to create a process for FFmpeg video compression at runtime. In my local system, it runs within 30 seconds. When I tried to run it in the server, it starts throwing a timeout error after 60 seconds. When I manually ran the command in the server, it took around 2 minutes. I came to know that some configuration in
php.ini
needs to be modified. I tried changing the configuration of the process to 300 seconds. Still, the same timeout error is being outputted.


The process "/usr/bin/ffmpeg -i '/var/temp/5e7de5a9de7c2/creme bulee-01-infuse
the cream and milk.mp4' -s 1668x2224 -c:a copy '/var/temp/5e7de5a9de7c2/compre
ssed/temp_creme bulee-01-infuse the cream and milk_1668x2224.mp4'" exceeded th
e timeout of 60 seconds.




In
php.ini
, I have the following configuration :


max_execution_time = 300 
max_input_time = 300




How do I stop my process from timing out ?