Recherche avancée

Médias (1)

Mot : - Tags -/censure

Autres articles (90)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Menus personnalisés

    14 novembre 2010, par

    MediaSPIP utilise le plugin Menus pour gérer plusieurs menus configurables pour la navigation.
    Cela permet de laisser aux administrateurs de canaux la possibilité de configurer finement ces menus.
    Menus créés à l’initialisation du site
    Par défaut trois menus sont créés automatiquement à l’initialisation du site : Le menu principal ; Identifiant : barrenav ; Ce menu s’insère en général en haut de la page après le bloc d’entête, son identifiant le rend compatible avec les squelettes basés sur Zpip ; (...)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

Sur d’autres sites (11335)

  • Initializing hwaccel_context in libavcodec

    3 janvier 2018, par dloman

    I am trying to get hardware accelerated video working using libavcodec. I am using the hw_decode.c example as a starting point and am unable to get it to work. both AVCodecContext->hwaccel and AVCodecContext->hwaccel_context are NULL

    I belive some part of the hwaccel is working as I see the output

    libva info: VA-API version 0.39.0
    
libva info: va_getDriverName() returns 0
    
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
    
libva info: Found init function __vaDriverInit_0_39
    
libva info: va_openDriver() returns 0

    Which is the same as when I run

    ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format vaapi -i input.mpg -f null -

    but immediately after that I get the following error message

    [h264 @ 0x1df2cc0] Hardware acceleration context (hwaccel_context) does not exist.
    
Failed to get HW surface format.
    
[h264 @ 0x1df2cc0] decode_slice_header error
    
[h264 @ 0x1df2cc0] no frame!

    I looked at the similar question and the answer to this shows how to get a AVCodecContext->hwaccel. But even with the AVCodecContext->hwaccel being a valid VAApih264 decoder I still get the same error message.

    How do I initialize a AVCodecContext->hwaccel_context and after that what else do I need to do to get hardware accelerated video working in ffmpeg ?

  • ffmpeg closes with return code 137

    25 septembre 2014, par Adi Ulici

    I am using ffmpeg to convert videos and about 66% of the times doesn’t do it’s job until the end. It simply gets killed, closes before it ends the job, and returns "137" instead of "0".

    I can’t seem to find anywhere some information about this return code. Does anyone know some tips or where can I find further guidance ? Thanks

  • ffmpeg closes with return code 137

    26 juin 2022, par Adi Ulici

    I am using ffmpeg to convert videos and about 66% of the times doesn't do it's job until the end. It simply gets killed, closes before it ends the job, and returns "137" instead of "0".

    



    I can't seem to find anywhere some information about this return code. Does anyone know some tips or where can I find further guidance ? Thanks

    


Navigation