
Recherche avancée
Médias (1)
-
Rennes Emotion Map 2010-11
19 octobre 2011, par
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (55)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Gestion générale des documents
13 mai 2011, parMédiaSPIP ne modifie jamais le document original mis en ligne.
Pour chaque document mis en ligne il effectue deux opérations successives : la création d’une version supplémentaire qui peut être facilement consultée en ligne tout en laissant l’original téléchargeable dans le cas où le document original ne peut être lu dans un navigateur Internet ; la récupération des métadonnées du document original pour illustrer textuellement le fichier ;
Les tableaux ci-dessous expliquent ce que peut faire MédiaSPIP (...) -
Creating farms of unique websites
13 avril 2011, parMediaSPIP 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" (...)
Sur d’autres sites (5330)
-
Initializing hwaccel_context in libavcodec
3 janvier 2018, par dlomanI 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
andAVCodecContext->hwaccel_context
areNULL
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 0Which 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 theAVCodecContext->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 UliciI 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 UliciI 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