Recherche avancée
Autres articles (42)
-
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs -
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...) -
Contribute to translation
13 avril 2011You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
MediaSPIP is currently available in French and English (...)
Sur d’autres sites (8960)
-
What H.264 encoding profile is considered "safe" in 2017 ?
12 avril 2017, par degenerateHave streaming services adopted a certain H.264 profile as "standard" or "safe" for use in 2017 ? For example are all modern Youtube videos at least "High" profile for H.264 ?
Or does Youtube continue to serve all encoding profiles, down to "Baseline" depending on hardware ?
I would like to start encoding my videos with "High" profile or higher, but cannot find any recent documentation on which profile is standard practice or safe to use.
Searching google is not fruitful :
Old blog post from 2008 :
http://blog.mediacoderhq.com/h264-profiles-and-levels/Old blog post from 2014 :
http://leightronix.com/blog/when-to-choose-high-main-and-baseline-while-encoding-h-264/I cannot find any updated 2017 information on this.
-
Evolution #3962 : Générer des JPEG progressifs
18 juin 2017, par Michel BystranowskiMmm, ça a l’air un peu plus compliqué qu’au premier abord effectivement. J’ai trouvé cet article qui compare le taux de compression et recommande de ne le faire que pour les fichiers de plus de 10k, sous peine d’obtenir des fichiers plus gros (https://yuiblog.com/blog/2008/12/05/imageopt-4/). Du coup il faudrait s’arranger pour ne cibler que les gros JPEGs.
Par côté compatibilité des navigateurs ça semble ok pour tous les navigateurs récents (https://en.wikipedia.org/wiki/Comparison_of_layout_engines_%28graphics%29#JPEG_support).
-
avcodec : Remove libaacplus
24 janvier 2016, par Timothy Guavcodec : Remove libaacplus
TODO : bump minor
It’s inferior in quality to fdk-aac and has an arguably more problematic
license.As early as 2012, a HydrogenAudio user reported :
> It has however one huge advantage : much better quality at low bitrates than
> faac and libaacplus.I myself have made a few spectrograms for a comparison of the two
encoders as well. The FDK output is consistently better than the
libaacplus one, in all bitrates I tested.libaacplus license is 3GPP + LGPLv2. 3GPP copyright notice is completely
proprietory, as follows :> No part may be reproduced except as authorized by written permission.
>
> The copyright and the foregoing restriction extend to reproduction in
> all media.
>
> © 2008, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
>
> All rights reserved.(The latest 26410-d00 zip from 3GPP has the same notice, but the copyright
year is changed to 2015)The copyright part of the FDK AAC license (section 2) is a copyleft
license that permits redistribution under certain conditions (and
therefore the LGPL + libfdk-aac combination is not prohibited by
configure) :> Redistribution and use in source and binary forms, with or without
> modification, are permitted without payment of copyright license fees
> provided that you satisfy the following conditions :
>
> You must retain the complete text of this software license in
> redistributions of the FDK AAC Codec or your modifications thereto in
> source code form.
>
> You must retain the complete text of this software license in the
> documentation and/or other materials provided with redistributions of
> the FDK AAC Codec or your modifications thereto in binary form.
>
> You must make available free of charge copies of the complete source
> code of the FDK AAC Codec and your modifications thereto to recipients
> of copies in binary form.
>
> The name of Fraunhofer may not be used to endorse or promote products
> derived from this library without prior written permission.
>
> You may not charge copyright license fees for anyone to use, copy or
> distribute the FDK AAC Codec software or your modifications thereto.
>
> Your modified versions of the FDK AAC Codec must carry prominent
> notices stating that you changed the software and the date of any
> change. For modified versions of the FDK AAC Codec, the term
> "Fraunhofer FDK AAC Codec Library for Android" must be replaced by the
> term "Third-Party Modified Version of the Fraunhofer FDK AAC Codec
> Library for Android."
Syndiquer tout le site
