Recherche avancée

Médias (0)

Mot : - Tags -/api

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (100)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

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

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le 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 (3232)

  • lavu/hwcontext_vulkan : support mapping VUYX, P012, and XV36

    20 août 2022, par Philip Langdale
    lavu/hwcontext_vulkan : support mapping VUYX, P012, and XV36
    

    If we want to be able to map between VAAPI and Vulkan (to do Vulkan
    filtering), we need to have matching formats on each side.

    The mappings here are not exact. In the same way that P010 is still
    mapped to full 16 bit formats, P012 has to be mapped that way as well.

    Similarly, VUYX has to be mapped to an alpha-equipped format, and XV36
    has to be mapped to a fully 16bit alpha-equipped format.

    While Vulkan seems to fundamentally lack formats with an undefined,
    but physically present, alpha channel, it has have 10X6 and 12X4
    formats that you could imagine using for P010, P012 and XV36, but these
    formats don't support the STORAGE usage flag. Today, hwcontext_vulkan
    requires all formats to be storable because it wants to be able to use
    them to create writable images. Until that changes, which might happen,
    we have to restrict the set of formats we use.

    Finally, when mapping a Vulkan image back to vaapi, I observed that
    the VK_FORMAT_R16G16B16A16_UNORM format we have to use for XV36 going
    to Vulkan is mapped to Y416 when going to vaapi (which makes sense as
    it's the exact matching format) so I had to add an entry for it even
    though we don't use it directly.

    • [DH] libavutil/hwcontext_vulkan.c
    • [DH] libavutil/version.h
  • Make mime-type award a bonus probe score

    21 novembre 2023, par Peter Zebühr
    Make mime-type award a bonus probe score
    

    This changes the default behaviour of ffmpeg where content-type headers
    on an input gives an absolut probe score (of 75) to instead give a bonus
    score (of 30). This gives the probe a better chance to arrive at the
    correct format by (hopefully) giving a large enough bonus to push edge
    cases in the right direction (MPEG-PS vs MP3, I am looking at you) while
    also not adversly punishing clearer cases (raw ADTS marked as
    "audio/mpeg" for example).

    This patch was regression tested against 20 million recent podcast
    submissions (after content-type propagation was added to
    original-storage), and 50k Juno vodcasts submissions (dito). No adverse
    effects observed (but the bonus may still need tweaking if other edge
    cases are detected in production).

    • [DH] libavformat/avformat.h
    • [DH] libavformat/format.c
    • [DH] libavformat/libopenmpt.c
  • swscale/utils : Fix color range of gray16

    18 mars 2014, par Carl Eugen Hoyos
    swscale/utils : Fix color range of gray16
    

    Improves rgb -> gray16 conversion

    Fixes Ticket3422

    The pam and png output files look visually similar, in both cases the
    dynamics increase to 0x0 -> 0xfffb.

    Signed-off-by : Michael Niedermayer <michaelni@gmx.at>

    • [DH] libswscale/utils.c
    • [DH] tests/ref/fate/filter-pixdesc
    • [DH] tests/ref/fate/filter-pixfmts-copy
    • [DH] tests/ref/fate/filter-pixfmts-crop
    • [DH] tests/ref/fate/filter-pixfmts-field
    • [DH] tests/ref/fate/filter-pixfmts-fieldorder
    • [DH] tests/ref/fate/filter-pixfmts-hflip
    • [DH] tests/ref/fate/filter-pixfmts-il
    • [DH] tests/ref/fate/filter-pixfmts-null
    • [DH] tests/ref/fate/filter-pixfmts-scale
    • [DH] tests/ref/fate/filter-pixfmts-vflip
    • [DH] tests/ref/lavf/pam
    • [DH] tests/ref/lavf/png