Recherche avancée

Médias (91)

Autres articles (86)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP 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 (...)

  • Le profil des utilisateurs

    12 avril 2011, par

    Chaque 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, par

    Accé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 (11855)

  • lavu/pixdesc : favour formats where depth and subsampling exactly match

    8 septembre 2022, par Philip Langdale
    lavu/pixdesc : favour formats where depth and subsampling exactly match

    Since introducing the various packed formats used by VAAPI (and p012),
    
we've noticed that there's actually a gap in how
    
av_find_best_pix_fmt_of_2 works. It doesn't actually assign any value
    
to having the same bit depth as the source format, when comparing
    
against formats with a higher bit depth. This usually doesn't matter,
    
because av_get_padded_bits_per_pixel() will account for it.
    

    However, as many of these formats use padding internally, we find that
    
av_get_padded_bits_per_pixel() actually returns the same value for the
    
10 bit, 12 bit, 16 bit flavours, etc. In these tied situations, we end
    
up just picking the first of the two provided formats, even if the
    
second one should be preferred because it matches the actual bit depth.
    

    This bug already existed if you tried to compare yuv420p10 against p016
    
and p010, for example, but it simply hadn't come up before so we never
    
noticed.
    

    But now, we actually got a situation in the VAAPI VP9 decoder where it
    
offers both p010 and p012 because Profile 3 could be either depth and
    
ends up picking p012 for 10 bit content due to the ordering of the
    
testing.
    

    In addition, in the process of testing the fix, I realised we have the
    
same gap when it comes to chroma subsampling - we do not favour a
    
format that has exactly the same subsampling vs one with less
    
subsampling when all else is equal.
    

    To fix this, I'm introducing a small score penalty if the bit depth or
    
subsampling doesn't exactly match the source format. This will break
    
the tie in favour of the format with the exact match, but not offset
    
any of the other scoring penalties we already have.
    

    I have added a set of tests around these formats which will fail
    
without this fix.
    • [DH] libavutil/pixdesc.c
    • [DH] libavutil/pixdesc.h
    • [DH] libavutil/tests/pixfmt_best.c
    • [DH] libavutil/version.h
    • [DH] tests/ref/fate/pixfmt_best

  • libsvtav1 : Fix the documentation to match the actual options

    30 juillet 2020, par Mark Thompson
    libsvtav1 : Fix the documentation to match the actual options
    • [DH] doc/encoders.texi
    • [DH] libavcodec/libsvtav1.c

  • aarch64 : vp8 : Reorder the function pointer inits to match the arm original

    31 janvier 2019, par Martin Storsjö
    aarch64 : vp8 : Reorder the function pointer inits to match the arm original

    Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DBH] libavcodec/aarch64/vp8dsp_init_aarch64.c

Navigation