
Recherche avancée
Autres articles (39)
-
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 (...)
-
Le plugin : Podcasts.
14 juillet 2010, parLe problème du podcasting est à nouveau un problème révélateur de la normalisation des transports de données sur Internet.
Deux formats intéressants existent : Celui développé par Apple, très axé sur l’utilisation d’iTunes dont la SPEC est ici ; Le format "Media RSS Module" qui est plus "libre" notamment soutenu par Yahoo et le logiciel Miro ;
Types de fichiers supportés dans les flux
Le format d’Apple n’autorise que les formats suivants dans ses flux : .mp3 audio/mpeg .m4a audio/x-m4a .mp4 (...) -
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 0.2 is the first MediaSPIP stable release.
Its official release date is June 21, 2013 and is announced here.
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)
Sur d’autres sites (6683)
-
ffmpeg, HLS options, ffmpeg components for dummies ? [closed]
10 juin 2013, par VetalI am trying to make some HLS encoding with ffmpeg
After playing a lot (in Ubuntu 12.04) with ffmpeg I realized I do not understand basic questions.
How to make a ffmpeg "by the book" ?
I've started a "sudo apt-get install ffmpeg"
I finished with a manual install :
Latter needed a following command to get rid of build error, where I spent quite some time with :
sudo apt-get remove ffmpeg x264 libx264-dev
So, now I've got to the documentation for HLS : http://ffmpeg.org/ffmpeg-all.html#hls-2
Trying to run some stuff :
ffmpeg -i 3.mp4 hls.m3u8
Error : Unable to find a suitable output format for 'hls.m3u8'
ffmpeg -i 3.mp4 -hls_time 10 hls.m3u8
Error :
Unrecognized option 'hls_time'
Failed to set value '10' for option 'hls_time'Anyway, looks like an options specified in different formats, e.g. 'vbsf' vs 'v:bsf', -vcodec and -v:c, etc. etc. Like there are few alternative versions
After starting with it some time ago, I feel more pessimistic now like I missed some fundametals. Any Ideas for the things above ?
Thank you
-
video created by moviepy doesn't play on web
18 février 2016, par R. GlennI’m playing around with moviepy, with the intent of creating videos to imbed in webpages. However, I’m having trouble getting the videos that I create to actually play in chrome and firefox (it does play in safari :/ ).
Firefox claims the "file is corrupt".I find it extremely likely I haven’t installed something properly. I followed (among other things, since I’m not yet authorized to post enough links so as to fully describe my situation, #thanksStackOverflow ;P) http://wiki.webmproject.org/ffmpeg/building-with-libvpx, but according to [link I would have shared if allowed :P] that stuff is all "automatically installed during MoviePy’s installation", so I’m not sure how I could have messed it up.
see example code (I’ve tried it with ’python’, ’python3’ and ’python3.5’) :
from moviepy.editor import *
filepath = "../read_videos/MOVI0011.avi"
file = VideoFileClip(filepath)
clips = []
clips.append(file.subclip(10, 12))
clips.append(file.subclip(20, 22))
clips.append(file.subclip(30, 32))
clips.append(file.subclip(40, 42))
concatenated_clip = concatenate_videoclips(clips)
concatenated_clip.write_videofile("../write_videos/clip.mp4", fps=24, codec='mpeg4')OSX El Capitan (10.11.3)
-
Evolution #4798 : Suppression des mises à jour de BDD SPIP 3.0 (ou 3.1 ?)
25 mai 2021D’après https://core.spip.net/projects/spip/wiki/WikiStart#Anciennes-versions
Et le fait que le premier numéro de https://git.spip.net/spip/spip/src/branch/master/ecrire/maj/legacy/svn10000.php est le 10990 (1.9.2d = 11132), on pourrait conserver pour la 4.0 la migration probablement depuis 1.9.2d. Sans que ça soit très gênant pour le moment.
Mais même, le fichier maj/v019.php a la nouvelle écriture, et commence en 1931 (1.7.0 = 2414)...
On pourrait même conserver depuis 1.7.0.Mais le veut-on vraiment ?
On peut conserver « à partir de 2.0.0 » (13469), pourquoi pas ? ou toute version au dessus…
Ou à partir de 1.9.2 ou 1.8… ou je ne sais pas…Bref… pour moi tant qu’on vire les maj/vxxx.php antérieurs à l’ancien formalisme, déjà ça me va.
Mais indépendamment de ça, conserver ad-vitam les trucs, ça a pas forcément trop de sens quand même.