
Recherche avancée
Autres articles (76)
-
Use, discuss, criticize
13 avril 2011, parTalk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
A discussion list is available for all exchanges between users. -
Le profil des utilisateurs
12 avril 2011, parChaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...) -
Configurer la prise en compte des langues
15 novembre 2010, parAccéder à la configuration et ajouter des langues prises en compte
Afin de configurer la prise en compte de nouvelles langues, il est nécessaire de se rendre dans la partie "Administrer" du site.
De là, dans le menu de navigation, vous pouvez accéder à une partie "Gestion des langues" permettant d’activer la prise en compte de nouvelles langues.
Chaque nouvelle langue ajoutée reste désactivable tant qu’aucun objet n’est créé dans cette langue. Dans ce cas, elle devient grisée dans la configuration et (...)
Sur d’autres sites (14022)
-
avfilter/vf_blackdetect : support full-range YUV
8 décembre 2022, par Niklas Haasavfilter/vf_blackdetect : support full-range YUV
This filter currently makes the distinction between limited and full
range by testing for the deprecated YUVJ pixel formats at link setup
time. This is deprecated and should be improved to perform the detection
based on the per-frame metadata.Rewrite it to calculate the black pixel threshold at the time of
filtering a frame, when metadata about the frame's color range is known.
Doing it this way has the small side benefit of being able to handle
streams with variable metadata, and is not a meaningful performance
cost.Signed-off-by : Niklas Haas <git@haasn.dev>
-
Accurately calculate concatenated audio file size without actually concatenating for rss enclosure length
19 décembre 2024, par askrillA little background. Im working on implementing DAI into a podcast hosting and the solution I’m working with is splitting the audio file for mid role ads and then just concatenating the files with the ad in middle. All files will be the same encoding, bitrate… what I need to figure out is what to put as the length of the encloser in the rss feed. In addition if the ad is gonna change per request then there’s no way to keep that encloser length accurate unless all the ads are the same size.


-
avformat/matroskadec : Accept more unknown-length elements
17 mai 2019, par Andreas Rheinhardtavformat/matroskadec : Accept more unknown-length elements
The current Matroska specifications mandate that only two elements may
use an unknown-length length : Segments and clusters. But this was not
always so : For the greater part of Matroska's existence, all master
elements were allowed to make use of the unknown-length feature.And there were muxers creating such files : For several years
libavformat's Matroska muxer used unknown-length for all master
elements when the output wasn't seekable. This only stopped in March
2010 with 2529bb30. And even afterwards it was possible (albeit
unlikely) for libavformat to create unknown-length master elements
that are in violation of today's specifications, namely if the master
element was so big that the seek backwards to update the size could
no longer be performed inside the AVIOContext's write buffer. This
has only been fixed in October 2016 (with the patches that introduced
support for writing CRC-32 elements).Libavformat's Matroska demuxer meanwhile has never really supported
unknown-length elements besides segments and clusters. Support for the
latter was hardcoded. This commit changes this : Now all master elements
for which a syntax to parse them is available are supported. This
includes the files produced by old versions of libavformat's muxer.More precisely, master elements that have unknown length and are about
to be parsed (not skipped) are supported ; only a warning is emitted for
them. For normal files, this means that level 1 elements after the
clusters that are encountered after the clusters have been parsed (i.e.
not because they are referenced by the seekhead at the beginning of the
file) are still unsupported (they would be skipped at this point if
their length were known).Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>