
Recherche avancée
Autres articles (45)
-
La file d’attente de SPIPmotion
28 novembre 2010, parUne file d’attente stockée dans la base de donnée
Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...) -
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
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" (...)
Sur d’autres sites (9698)
-
How to use RTSP server to streaming the H264 stream received by RTSP server in Live555
8 août 2012, par KangI'm use the RTSP client in Live555 to receive the H264 stream and decode it for processing (in DummySink where in live555/testProgs/testRTSPClient.cpp), and now I wanna create an RTSP server to transport the stream that add the metadata(processed result from video analyzer), how to use RTSP server to transport the h264 frame buffer received from DummySink ?
-
h264 : print num_reorder_frames in debug output
4 août 2012, par Michael Niedermayerh264 : print num_reorder_frames in debug output
-
ffprobe shows bitrate of 0.0 or N/A for h264 stream
30 mai 2012, par DanI have a 11-minute .mkv file with a h264 video stream, taking up 184MB of space. I would like to reduce the size of this file. I figured I could just reduce the bit-rate. But ffprobe doesn't output any. In fact, it says the length of the file is calculated from the bitrate and thus could be inaccurate, but there's no bitrate either in the summary or in the [FORMAT] entry :
> ffprobe -show_format file.mkv
[matroska,webm @ 0x7f8e8084b200] Estimating duration from bitrate, this may be inaccurate
Input #0, matroska,webm, from 'file.mkv':
Duration: 00:11:11.59, start: 0.000000, bitrate: N/A
Stream #0.0: Video: h264 (High), yuv420p, 1280x720 [PAR 1:1 DAR 16:9], 29.97 fps, 29.97 tbr, 1k tbn, 59.94 tbc (default)
Stream #0.1: Audio: aac, 48000 Hz, 5.1, s16 (default)
[FORMAT]
...
bit_rate=0.000000
[/FORMAT]Thank you.
EDIT : My understanding is that H.264 is a protocol. As such, I cannot tell, based on the ffprobe documentation, what implementation the h264 codec uses. If anyone knows that, I'd be grateful.