Recherche avancée

Médias (0)

Mot : - Tags -/inscription3

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

Autres articles (79)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

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

Sur d’autres sites (13256)

  • How to "extend" aws docker base image (.net core from scratch) by ... libs/ubuntu/ffmpeg ?

    26 avril 2022, par Nigrimmist

    i would like to use AWS Lambda through the image containers using .net core 3.1 and it is works fine for me in simplest code case. But i stucked with next scenario :

    


    By default, aws provide base image with .net core with aws libs based on "from scratch". So as i know, it minimal Linux that does not contains even package manager.

    


    I need to work with ffmpeg in the code, but to do it i need to install few packages and ... fmpeg. I have working code on image

    


    FROM mcr.microsoft.com/dotnet/runtime:3.1-bionic


    


    It is ubuntu with .net core runtime. But what is the right strategic in case of AWS Lambda image ? How can i ... merge them ?.

    


    Have few ideas, but not sure :

    


      

    1. use as is FROM public.ecr.aws/lambda/dotnet:core3.1 and try to install package manager, all depenendencies to use ffmpeg and so on ?

      2. 


    2. Use mcr.microsoft.com/dotnet/runtime:3.1-bionic, somehow add required by amazon dependencies (how ? download content and attach from local ?) and configure it to run in Lambda runtime ?

      3. 


    3. ... ?

      4. 


    


    Will be glad to hear where is the solution here. Thanks !

    


  • Building ffmpeg on mac results in undefined symbols

    9 juin 2017, par Peter

    Environment : macOS 10.12.5, Xcode 8.3.3, pkg-config installed via brew

    I need to build a minimal version of ffmpeg that supports H.264 decoding. I have downloaded the source for ffmpeg version 3.3.1 and have successfully built it for Windows and Linux. Now, I am trying to build it for mac.

    The specific flags of the configuration that are relevant are :

    --disable-yasm
    
--disable-everything
    
--enable-decoder=h264
    
--enable-decoder=h264_vda
    
--enable-vda

    After running the configuration, when I run make, all the libraries such as libavcodec.a, libavfilter.a, libavformat.a, are built. However, ffmpeg itself does not get built. The error I get is :

    Undefined symbols for architecture x86_64:
    
  "_ff_vda_create_decoder", referenced from:
    
      _vdadec_init in libavcodec.a(vda_h264_dec.o)
    
  "_ff_vda_destroy_decoder", referenced from:
    
      _vdadec_init in libavcodec.a(vda_h264_dec.o)
    
      _vdadec_close in libavcodec.a(vda_h264_dec.o)
    
ld: symbol(s) not found for architecture x86_64

    Looks like the functions are defined in ./libavcodec/vda_h264.c. However, it appears vda_h264.c is never compiled. Other vda related files such as vda.c and vda_h264_dec.c do get compiled (and added to libavcodec.a).

    I am thinking perhaps I am missing a configuration flag. Can someone please help ? Regards.

  • avcodec/eatgv : Check remaining size after the keyframe header

    28 juillet 2019, par Michael Niedermayer
    avcodec/eatgv : Check remaining size after the keyframe header

    The minimal size which unpack() will not fail on is 5 bytes
    
Fixes : Timeout (14sec -> 77ms) (testcase 15508)
    
Fixes : 15508/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_EATGV_fuzzer-5700053513011200
    
Fixes : 15996/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_EATGV_fuzzer-5751353223151616
    

    Found-by : continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
    
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] libavcodec/eatgv.c

Navigation