
Recherche avancée
Médias (1)
-
MediaSPIP Simple : futur thème graphique par défaut ?
26 septembre 2013, par
Mis à jour : Octobre 2013
Langue : français
Type : Video
Autres articles (52)
-
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...) -
De l’upload à la vidéo finale [version standalone]
31 janvier 2010, parLe chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
Upload et récupération d’informations de la vidéo source
Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...) -
Librairies et binaires spécifiques au traitement vidéo et sonore
31 janvier 2010, parLes logiciels et librairies suivantes sont utilisées par SPIPmotion d’une manière ou d’une autre.
Binaires obligatoires FFMpeg : encodeur principal, permet de transcoder presque tous les types de fichiers vidéo et sonores dans les formats lisibles sur Internet. CF ce tutoriel pour son installation ; Oggz-tools : outils d’inspection de fichiers ogg ; Mediainfo : récupération d’informations depuis la plupart des formats vidéos et sonores ;
Binaires complémentaires et facultatifs flvtool2 : (...)
Sur d’autres sites (9840)
-
How to download live stream that consists out of separate .ts and .aac segments ?
10 juin 2020, par JanThere is a m3u8 file with only the containing links to video segments and a different one with only the audio segments. Because it is a live streaming I have to start downloading both video and audio streams at the same time.
When just writing "ffmpeg input output" for video and the same command for audio in the following line, the program is trying to download the video file "until the end" before starting the audio stream — which does naturally not work since the live stream is indefinite.


-
FFmpeg drawtext and live coordinates with sendcmd/zmq
9 mai 2019, par DavidKI’d like to use a marker on a live video source which has external live data to set x,y coordinates. sendcmd can read the text file but it won’t update it, so later updates are not executed. Is it possible only with zmq ? And if so, can I use zmq as a single filter (with drawtext), not with filter complex ?
I have a python that exports live coordinates in the appropriate format to a cmd.txt file. I use unix time for the coordinates and I also copy the input timestamps from the live loopback device so they have almost the same time. There’s a small delay so I have compensated the exported timestamps with +1.5s. This means the marker is moving for this extra period (while timestamps in cmd.txt are a bit ahead of the live source), but it won’t update any more. I assume that FFmpeg reads this cmd.txt and won’t update it any more but my python is writing it continuously.
Example line of the cmd.txt :
1557402120.3119707 drawtext reinit 'x=752:y=480';
This is the actual ffmpeg pipe :
ffmpeg -fflags nobuffer -vaapi_device /dev/dri/renderD128 -f v4l2 -i /dev/video0 -vf "sendcmd=f=cmd.txt,drawtext=fontfile=font.ttf:fontsize=30:fontcolor=white:r=25:text='o',format=nv12,hwupload" -copyts -c:v h264_vaapi -qp 24 -y 0.mp4
Source is a loopback device with unix time as input timestamp.
-
http-flv live broadcast with flv.js error
29 mars 2019, par Forest YangWhen I try nginx + nginx-http-flv-module + flv.js to play video from camera, error happened, but play with VLC works fine.
log in nginx :
flv live: app args MUST be specified, client: 192.168.89.1, server: myserver, request: "GET /live.html HTTP/1.1", host: "192.168.89.134:8080"
Some key configurations,
nginx.conf :
http{
...
server{
...
location /live {
flv_live on;
chunked_transfer_encoding on; #open 'Transfer-Encoding: chunked' response
add_header 'Access-Control-Allow-Origin' '*'; #add additional HTTP header
add_header 'Access-Control-Allow-Credentials' 'true'; #add additional HTTP header
}
}
}
rtmp {
server {
listen 1935;
server_name 192.168.89.134;
application myapp {
live on;
gop_cache on;
}
}
}ffmpeg command :
ffmpeg -f avfoundation -s 1280x720 -r 30 -i 0 -f flv rtmp://192.168.89.134:1935/myapp/test
VLC network url :
http://192.168.89.134:8080/live?port=1935&app=myapp&stream=test
HTML with flv.js :
if (flvjs.isSupported()) {
var videoElement = document.getElementById('videoElement');
var flvPlayer = flvjs.createPlayer({
type: 'flv',
'isLive': true,
url: 'http://192.168.89.134:8080/live?port=1935&app=myapp&stream=test'
});
flvPlayer.attachMediaElement(videoElement);
flvPlayer.load();
flvPlayer.play();
}Can anyone tell me why based your experience ? thank you.