Recherche avancée
Autres articles (82)
-
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" (...) -
Participer à sa traduction
10 avril 2011Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
Actuellement MediaSPIP n’est disponible qu’en français et (...)
Sur d’autres sites (15831)
-
avfilter/vf_crop : make possible to do exact cropping for subsampled videos
21 août 2016, par Paul B Mahol -
vc2enc : do not allocate packet until exact frame size is known
2 mars 2016, par Rostislav Pehlivanovvc2enc : do not allocate packet until exact frame size is known
This commit solves most of the crashes and issues with the encoder and
the bitrate setting. Now the encoder will always allocate the absolute
lowest amount of memory regardless of what the bitrate has been set to.
Therefore if a user inputs a very low bitrate the encoder will use the
maximum possible quantization (basically zero out all coefficients),
allocate a packet and encode it. There is no coupling between the
bitrate and the allocation size and so no crashes because the buffer
isn’t large enough.The maximum quantizer was raised to the size of the table now to both
keep the overshoot at ridiculous bitrates low and to improve quality
with higher bit depths (since the coefficients grow larger per transform
quantizing them to the same relative level requires larger quantization
indices).Since the quantization index start follows the previous quantization
index for that slice, the quantization step was reduced to a static 1
to improve performance. Previously with quant/5 the step was usually
set to 0 upon start (and was later clipped to 1), that isn’t a big change.
As the step size increases so does the amount of bits leftover and so
the redistribution algorithm has to iterate more and thus waste more
time.Signed-off-by : Rostislav Pehlivanov <atomnuker@gmail.com>
-
ffmpeg not splitting into EXACT same length chunks
4 octobre 2018, par jupiarI am trying to use ffmpeg to split a long video into exactly 20second long clips, and accomplishing that by :
inside docker as a python sub-processsubprocess.run(["/usr/sbin/ffmpeg",
"-i", video_loc,
"-async", "1",
"-map", "0",
"-segment_time", "20",
"-f", "segment",
"-reset_timestamps", "1",
"n-%05d.mp4"], cwd=r'/clips')My problem is that each are roughly 20seconds, some are as low as 10seconds, some as high as 27 seconds, i would say most are around 16-23. Is there something else that I can do to ensure the split of exactly 20 seconds ? I am open to any technique possible, aside from anything manual...