Recherche avancée

Médias (1)

Mot : - Tags -/ogv

Autres articles (57)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

  • Gestion des droits de création et d’édition des objets

    8 février 2011, par

    Par défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;

Sur d’autres sites (7904)

  • Static ffmpeg library windows

    29 novembre 2022, par peter

    Im trying to use the ffmpeg libraries (libavutil, libswscale, ...) in a bigger project by statically linking them, im not interested in the binaries. Now the issue comes down to getting them statically built. I tried searching for pre-compiled builds but without success.

    


    Following the docs, i compiled them on wsl2 for win64 with

    


    ./configure --arch=x86_64 --target-os=mingw32 --cross-prefix=i686-w64-mingw32- --disable-shared --enable-static
make


    


    After that i copied the libavformat/libavformat.a as libavformat.lib (which should be fine since they are cross-compiled ar archives ?) into my project and linked them with CMake.

    


    When compiling smth like

    


    AVFormatContext* pFormatContext = avformat_alloc_context();


    


    i get a linker error saying

    


    lld-link : error : undefined symbol: avformat_alloc_context


    


    When looking at the libs with dumpbin -linkermember libavformat.lib, i can see

    


    >dumpbin -linkermember libavformat.lib
...
  135CD92 _avformat_alloc_context
...


    


    notice the underscore.

    


    Can i not link the cross-compiled *.a files directly into a windows executable ?

    


    Honestly at this point any ideas are welcome.

    


    Thanks

    


  • AV1 libaom encoder option aq-mode description

    6 juin 2023, par Chinmaey Shende

    I could not find the official description for AOM encoding options. There are some documentations available online. However I get following contradicting explanations for aq-mode.
can someone help me with the correct documentation ?

    


    https://api.encoding.com/reference/adv-av1-libaom says the default value for aq-mode is 0 and "ffmpeg -h encoder=libaom-av1" gives default value = -1.

    


  • Error : Unknown type name 'AVFormatParameters' , using ffmpeg

    12 mars 2019, par muraad malik

    I was trying to compile the old code with the latest ffmpeg installed. During compilation it shows the error for AVFormatParameters api and is unable to recognise it, which used to be in "avformat.h" header file.
    I could not find any proper resource online about this. If this api is deprecated, what is the replacement for this api ?
    The following is the error for the code,

    AVFormatParameters *formatParams;

    Error :

    Unknown type name 'AVFormatParameters'; did you mean 'AVCodecParameters'?

    Thanks

Navigation