Recherche avancée

Médias (0)

Mot : - Tags -/tags

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

Autres articles (67)

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

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Amélioration de la version de base

    13 septembre 2013

    Jolie sélection multiple
    Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
    Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)

Sur d’autres sites (9487)

  • libavformat/hlsplaylist : add subtitle_varname for naming subtitle streams

    28 septembre 2024, par Jonathan Baecker
    libavformat/hlsplaylist : add subtitle_varname for naming subtitle streams
    

    If 'sname :*' is set in the var_stream_map variable, use it as
    the NAME attribute for subtitles. This improves the naming of
    subtitle streams in HTML players, providing clearer and more
    descriptive labels for users.

    Reviewed-by : Steven Liu <lq@chinaffmpeg.org>

    • [DH] doc/muxers.texi
    • [DH] libavformat/hlsenc.c
    • [DH] libavformat/hlsplaylist.c
    • [DH] libavformat/hlsplaylist.h
  • How are ARM GPUs supported by Video display/decoding/encoding Programs ?

    7 juillet 2020, par John Allard

    I often see ARM-based chips advertising onboard GPUs, like the RPI3 that came with "Broadcom VideoCore IV @ 250 MHz" and the OdroidC2 that comes with a "Mali-450 GPU". These chips advertise stuff like "Decode 4k/30FPS, Encode 1080p,30FPS" as the capabilities of the GPU for encoding and decoding videos.

    &#xA;

    My question is this - how does a program like Kodi, VLC, or FFMPEG come to make use of these GPUs for actual encoding and decoding ? When I do research on how to make use of the Mali-450 GPU, for example, I find some esoteric and poorly documented C-examples of sending compressed frames to the GPU and getting decoded frames back. If I were to use a device like the OdroidC2 and install VLC on it, how does VLC make use of the GPU ? Did someone have to write logic into VLC to use the specific encoding/decoding API exposed by the Mali GPU in order to use it or do these GPUs follow some sort of consistent API that is exposed by all GPUs and VLC/Kodi can just program against this system API ?

    &#xA;

    The reason I ask this question is that VLC and Kodi tend to support these GPUs out of the Box, but a very popular program like FFMPEG that prides itself on supporting as many codecs and accelerators as possible has no support for decoding and encoding with the Mali GPU series. Why would VLC/Kodi support encoding/decoding and not FFMPEG ? Why do these manufacturers claim wild decoding and encoding support if these GPUs are difficult to program against and one must use their custom esoteric APIs instead of something like libavcodec ?

    &#xA;

    I hope my question makes sense, I guess what I'm curious about is that GPUs on most systems whether it be the Intel HD Graphics, Nvidia cards, AMD cards, etc seem to be used automatically by most video players but when it comes to using something like FFMPEG against these devices the process becomes much more process and you need to custom compile the build and give special flags to use the device as intended. Is there something I'm missing here ? Is VLC programmed to make use of all of these different type of GPUs ? And why, in that case, does FFMEPG not support Mali GPUs out of the Box ?

    &#xA;

  • Add MKV tags for AVS2 and AVS3 codecs.

    10 janvier 2022, par TianBo Zheng
    Add MKV tags for AVS2 and AVS3 codecs.
    

    Signed-off-by : TianBo Zheng <naturalwalker@hotmail.com>

    MKV codec mappings :
    V_AVS2 and V_AVS3 (https://github.com/ietf-wg-cellar/matroska-specification/blob/master/codec_specs.md)

    Encoding tool :
    Ffmpeg with AVS2/AVS3 enabled : https://github.com/xatabhk/FFmpeg-avs2-avs3/releases
    Command line :

    ffmpeg -i xxxx.mp4 -vcodec avs2 -acodec copy xxxx_avs2.mkv
    ffmpeg -i xxxx.mp4 -vcodec avs2 -speed_level 4 -acodec copy xxxx_avs2.mkv`

    Players :
    (1) Ffmpeg with avs2/avs3 enabled : (https://github.com/xatabhk/FFmpeg-avs2-avs3/releases) :
    Command line :

    ffplay xxxx_avs2.mkv
    ffplay xxxx_avs3.mkv
    (2) VLC 3.0.x with AVS2/AVS3 enabled : https://github.com/xatabhk/vlc-3.0-avs2-avs3/releases
    (3) Mpc-hc 1.9.x with AVS2/AVS3 enabled : https://gitee.com/zhengtianbo/cavs-avs2-avs3_decoder_added_to_mpc_hc/releases

    AVS2/AVS3 MKV samples :
    https://github.com/xatabhk/avs2-avs3-video-samples

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>

    • [DH] libavformat/matroska.c