Recherche avancée

Médias (1)

Mot : - Tags -/MediaSPIP

Autres articles (74)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

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

  • FFmpeg — Using hardware acceleration for video decoding

    5 novembre 2018, par Paul Belanger

    I have a project that uses FFmpeg to decode video streams and I want to make use of hardware decoding where available. According to this answer, the use of ff_find_hwaccel and friends is deprecated in newer FFmpeg builds.

    The answer states that ff_find_hwaccel is deprecated. I want to know how the new method for allocating a hardware accelerated decoder works. Is it done automatically ? Can I just pass hwaccel in an AvDictionary as the third option to avcodec_open2, or do I have to do something more involved ?

    Currently the code for allocating an AVCodecContext looks like this :

    auto video_codec = avcodec_find_decoder(codec_id);
    
auto context = avcodec_alloc_context3(video_codec);
    
auto retcode = avcodec_open2(context, video_codec, nullptr);

    with error checking, of course.

    I then push AVPackets into the decoder using avcodec_decode_video2.

  • hwaccel : Deinitialize hardware acceleration early enough

    29 octobre 2014, par Rémi Denis-Courmont
    hwaccel : Deinitialize hardware acceleration early enough

    The application will destroy the underlying hardware handles when
    
get_format() gets called again. Also this ensures the
    
deinitialization takes place if the get_format callback returns an
    
error.
    

    Regression from 1c80c9d7ef809180042257200c7b5f6b81d0b0e2.
    

    Signed-off-by : Luca Barbato <lu_zero@gentoo.org>
    • [DBH] libavcodec/utils.c

  • How to use hardware accelearation with ffmpeg

    25 avril 2014, par ixSci

    I need to have ffmpeg decode my video(e.g. h264) using hardware acceleration. I’m using the usual way of decoding frames : read packet -> decode frame. And I’d like to have ffmpeg speed up decoding. So I’ve built it with --enable-vaapi and --enable-hwaccel=h264. But I don’t really know what should I do next. I’ve tried to use avcodec_find_decoder_by_name("h264_vaapi") but it returns nullptr.
    Anyway, I might want to use others API and not just VA API. How one is supposed to speed up ffmpeg decoding ?

    P.S. I didn’t find any examples on Internet which uses ffmpeg with hwaccel.

Navigation