Recherche avancée

Médias (91)

Autres articles (11)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

Sur d’autres sites (2473)

  • Hardware decoding using vaapi [on hold]

    15 août 2017, par Orient

    I am trying to replicate hardware decoding using vaapi. My ultimate goal is to get an OpenGL texture wich I whant to get from a vasurface buffer.

    I took as a base https://github.com/gbeauchesne/ffvademo/tree/master/src
    which looks less intimidating than other examples. My initial understanding was that packets were somehow rendered to surfaces (render targets) and at the same time got converted. But it looks like the loop after some nested calls boils down to avcodec_decode_video2 (app_decode_frame -> ffva_decoder_get_frame -> decoder_get_frame -> decoder_run -> decode_packet -> avcodec_decode_video2), which in turn would call codec->decode. So it resembles the way decoding is done on CPU.

    Could anybody explain why this whoud be considered hw decoding ?

  • avcodec/nvenc : fix segfault in intra-only mode

    21 juin 2024, par Josh Allmann
    avcodec/nvenc : fix segfault in intra-only mode

    In intra-only mode, frameIntervalP is 0, which means the frame
    
data array is smaller than the number of surfaces.
    

    Together with using the wrong size on deallocation of the
    
frame_data_array, this lead to a crash.
    

    Signed-off-by : Timo Rothenpieler <timo@rothenpieler.org>
    • [DH] libavcodec/nvenc.c

  • amfenc : Add DXVA2 hardware frame input support

    14 avril 2018, par Alexander Kravchenko
    amfenc : Add DXVA2 hardware frame input support

    Adds support for AMF initialisation from a DXVA2 (Direct3D9) device, and
    
then allows passing DXVA2 surfaces into an AMF encoder.
    

    Signed-off-by : Mark Thompson <sw@jkqxz.net>
    • [DH] libavcodec/amfenc.c

Navigation