
Recherche avancée
Autres articles (95)
-
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
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 (...) -
Multilang : améliorer l’interface pour les blocs multilingues
18 février 2011, parMultilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela. -
ANNEXE : Les plugins utilisés spécifiquement pour la ferme
5 mars 2010, parLe site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)
Sur d’autres sites (5708)
-
ffmpeg : improving MP4 to webm ogg conversions
14 juillet 2017, par Randy(Edited to include some of the things I’ve tried)
I’m a musician, and occasional web coder. I’ve been using video editing software (old version of Roxio Videowave from 2011) to build promotional videos from clips of some of my performances, and I’d like to put some of them on my own web pages in HTML5 video format. So that currently means I need MP4, WEBM, and OGG conversions. Fortunately the editing software churns out some very nice MP4 (H264) files, and has plenty of options for doing so. I purposely output the output size about 2X the likely display size, in hopes of offering more detail for better conversions. Specifically, the video output was AVC/H.264, 800 x 450, 30fps, variable bit rate, but with 600000 as a base line (that was the default for this setting anyway).
Now I’m nowhere near expert at this stuff, and I probably left out some important data. But bottom line, the resulting MP4 looked very good. Unfortunately, to put it on my own web page means at least converting to WEBM and OGG formats. It would be nice if all browsers just supported MP4, but then there would be licensing fees, so conversions are needed. Sadly, I’ve been wasting days now trying to do this with ffmpeg. Its easy to do, its doing it WELL that is a mystery to me. Just letting ffmpeg work using its defaults (meaning I just specify an input and output file) results in pretty terrible video. But I’ve also tried most of the settings for better quality available, and the resulting conversions are nowhere near as good as youtube’s conversions.
Based on the info about my original MP4 file, can someone suggest some better settings for ffmpeg conversions to WEBM and OGG ? Am I going about this all wrong ? The best I’ve done so far was with a string like this, which specified a high quality and a fairly robust bit rate...
ffmpeg -i input-file.mp4 -c:v libvpx -crf 10 -b:v 1M -c:a libvorbis output-file.webm
That was much better than the default settings, but still nowhere near the quality of YOUTUBE conversions. In my resulting WEBM video, you can pretty plainly see how the picture degrades, and will snap into focus every few seconds when a "key frame" comes up. These artifacts should not be so obvious. Thanks for any help.
-
Revision 33982 : oups, layout.html devient structure.html
27 décembre 2009, par cedric@… — Logoups, layout.html devient structure.html
-
Revision 37670 : Juste un lien vers la doc
25 avril 2010, par kent1@… — LogJuste un lien vers la doc