
Recherche avancée
Autres articles (91)
-
Keeping control of your media in your hands
13 avril 2011, parThe vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...) -
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 (...) -
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 (21004)
-
exporting ogg videos from video slideshow (mp4) and audio (wav) using ffmpeg in python
17 septembre 2018, par jtzI have tried to find a solution already, but just cannot make it work. I want to export an .ogg-video by combining a video slideshow (mp4) with an audio file (wav) by using ffmpeg in python. The audio is shorter than the video and should have an offset of 2000 milliseconds, so that it starts approximately in the middle of the video. The code that I tried is essentially this :
subprocess.call(’ffmpeg.exe -itsoffset 0 -i slideshows/slideshow.mp4 -itsoffset 2000 -i sounds/audio.wav -codec:v libtheora -codec:a libvorbis output.ogg’, shell= True)
FYI : I need to create a couple of different video formats from the video and audio input, so substituting the ogg with a different format is no option. I have already successfully created .mp4-video-files and .webm-video-files from the material, but need the .ogg in addition. Also, Power Point does not like any of the exported videos, maybe this might be relevant for finding the problem here (I also unsuccessfully tried to fix this issue).
-
Revision 399823b6f5 : Add support for setting byte alignment. Add support for setting byte alignment
13 novembre 2014, par Frank GalliganChanged Paths :
Add /test/byte_alignment_test.cc
Modify /test/decode_test_driver.h
Modify /test/test.mk
Modify /vp9/common/vp9_alloccommon.c
Modify /vp9/common/vp9_onyxc_int.h
Modify /vp9/decoder/vp9_decodeframe.c
Modify /vp9/encoder/vp9_denoiser.c
Modify /vp9/encoder/vp9_encoder.c
Modify /vp9/encoder/vp9_lookahead.c
Modify /vp9/encoder/vp9_svc_layercontext.c
Modify /vp9/encoder/vp9_temporal_filter.c
Modify /vp9/vp9_dx_iface.c
Modify /vpx/vp8dx.h
Modify /vpx_scale/generic/yv12config.c
Modify /vpx_scale/yv12config.h
Add support for setting byte alignment.Add support for setting byte alignment on the Y, U, and V plane of the
reference buffers. The byte alignment must be a power of 2, from 32 to
1024. A value of 0 sets legacy alignment.Change-Id : I7c1399622f7aa68e123646369216b32047dda73d
-
vc2enc : zero padding of the coefficient buffer
17 décembre 2019, par Lynnevc2enc : zero padding of the coefficient buffer
Wavelet types with large amounts of overreading/writing like 9_7 would
write into the padding at high wavelet depths, which would remain and be
read by the next frame's transform and quickly cause artifacts to appear
for subsequent frames.
This fix affects all frames encoded with a non-power-of-two width, with
the artifacts varying between non-observable to very noticeable,
depending on encoder settings, so reencoding is advisable.