Recherche avancée

Médias (0)

Mot : - Tags -/utilisateurs

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

Autres articles (46)

  • Installation en mode ferme

    4 février 2011, par

    Le mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
    C’est la méthode que nous utilisons sur cette même plateforme.
    L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
    Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...)

  • 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

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

Sur d’autres sites (8297)

  • 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 ?

  • 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

  • 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.

Navigation