Recherche avancée

Médias (0)

Mot : - Tags -/signalement

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

Autres articles (22)

  • Déploiements possibles

    31 janvier 2010, par

    Deux types de déploiements sont envisageable dépendant de deux aspects : La méthode d’installation envisagée (en standalone ou en ferme) ; Le nombre d’encodages journaliers et la fréquentation envisagés ;
    L’encodage de vidéos est un processus lourd consommant énormément de ressources système (CPU et RAM), il est nécessaire de prendre tout cela en considération. Ce système n’est donc possible que sur un ou plusieurs serveurs dédiés.
    Version mono serveur
    La version mono serveur consiste à n’utiliser qu’une (...)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 is the first MediaSPIP stable release.
    Its official release date is June 21, 2013 and is announced here.
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

Sur d’autres sites (5155)

  • How to build ffmpeg as a Position independent executable (PIE) or PIC on Android ?

    22 avril 2016, par Parth Doshi

    I have checked out the latest source of ffmpeg from the official website. I now want to compile and build ffmpeg as a position independent executable.

    Here is what my configure command looks like

    ./configure --prefix=/usr/local --enable-gpl --enable-pic --enable-nonfree --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265

    I have added the option --enable-pic to make it a PIE. However when the build process completes successfully and when I do a hardening check as follows then I get below output

    hardening-check ffmpeg

    ffmpeg:
    
Position Independent Executable: no, normal executable!
    
Stack protected: yes
    
Fortify Source functions: yes (some protected functions found)
    
Read-only relocations: yes
    
Immediate binding: no, not found!

    This tells me that ffmpeg is still not a PIE. Can anyone tell me what am I missing here ? Is there any other changes that need to be done for adding PIE support.

  • avcodec/prores_aw : add support for prores 444 with alpha

    8 novembre 2018, par Martin Vignali
    avcodec/prores_aw : add support for prores 444 with alpha

    only 16b alpha is supported (not 8 bits)
    

    following official encoder, alpha data doesn't impact
    
yuv plane quality.
    

    So the alpha data encoding is done after the yuv part.
    
It's also avoid to loose quality in yuv part when
    
alpha is not uniform.
    

    the alpha encoding funcs is mainly take from prores_ks
    
encoder, except for the alpha data reorganization
    • [DH] libavcodec/proresenc_anatoliy.c

  • MLT framework windows build melt failed to load avformat

    22 juillet 2015, par Philip

    I build mlt framework on windows following the official guide http://www.mltframework.org/bin/view/MLT/WindowsBuild and the solution of Error building MLT framework on Windows for the errors.

    But when I call the command melt it doesn’t work correctly. (melt noise does work)

    Using melt -query "video_codecs" I get # No video codecs - failed to load avformat consumer.

    So it cannot load ffmpeg. Is there a problem with the compilation or is something related to Windows ?

Navigation