Recherche avancée

Médias (0)

Mot : - Tags -/médias

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

Autres articles (89)

  • Amélioration de la version de base

    13 septembre 2013

    Jolie sélection multiple
    Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
    Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

Sur d’autres sites (5753)

  • avcodec/mjpeg_parser : skip markers after EOI, not by size

    25 novembre 2021, par Alex Xu (Hello71)
    avcodec/mjpeg_parser : skip markers after EOI, not by size
    

    The check for m->size >= 0xF000 is intended to avoid skipping too much
    garbage data between JPEG frames in test_roman (thus missing next SOI),
    but it erroneously also skips valid markers between SOI and SOS. Instead
    of this, we should simply skip parsing markers other than SOI after EOI.
    That way, we will not accidentally skip over SOI due to some garbage
    between frames. There is still a small risk of encountering FFD8 in the
    garbage data, but the chance of this is fairly low.

    Fixes : https://trac.ffmpeg.org/ticket/8967
    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>

    • [DH] libavcodec/mjpeg_parser.c
  • Updating ffmpeg on Ubuntu 12.04 ; conflicts with old version from standard repository

    29 octobre 2016, par Frank van Wensveen

    I have never used ffmpeg on my Ubuntu Linux 12.04 (Precise Pangolin) box until now. Typing ’ffmpeg’ at the command prompt revealed that ffmpeg 0.8.17 (listed as ffmpeg 0.8.17-4:0.8.17-0ubuntu0.12.04.2) was installed. Seeing as I need to convert h.265 to h.264, an update was obviously required.

    Following posted instructions, I installed a ream of packages :

    $ sudo apt-get install faad libmp4v2-dev libfaac0 libfaac-dev
    libxvidcore4 libxvidcore4-dev liba52-0.7.4 liba52-0.7.4-dev libx264-dev
    libgsm-tools libogg-dev libtheora-bin libfaad-dev libvorbis-dev
    libtheora-dev libdts-dev git-core yasm texi2html checkinstall

    followed by

    $ sudo apt-get purge ffmpeg

    in order to get rid of the old stuff from the original repo.

    Downloaded the latest ffmpeg, and a ."/configure ; make ; sudo make install" later, I should be in business.

    Except that typing ’ffmpeg’ at the prompt still fired up the old version. A quick look revealed that the old ffmpeg binary was still sitting in /usr/bin with the new one being installed in /usr/local/bin. But ffmpeg is no longer listed as an installed package, and sudo apt-get remove ffmpeg tells me that "Package ffmpeg is not installed, so not removed".

    Running /usr/local/bin/ffmpeg directly works, however then fails in an Unknown encoder ’libx264’ error. Which is puzzling because the package libx264-120 is installed and /usr/lib/i386-linux-gnu/libx264.so.120 (with the appropriate symlink to /usr/lib/i386-linux-gnu/libx264.so) does exist.

    Maybe I’ve been looking at this for too long, because I’m sure this is a simple issue but I just can’t see it.

    Can someone please hand me the stupid had and point out why I deserve to wear it ?

    Tnx !

  • Updating ffmpeg on Ubuntu 12.04 ; conflicts with old version from standard repository

    29 octobre 2016, par Frank van Wensveen

    I have never used ffmpeg on my Ubuntu Linux 12.04 (Precise Pangolin) box until now. Typing ’ffmpeg’ at the command prompt revealed that ffmpeg 0.8.17 (listed as ffmpeg 0.8.17-4:0.8.17-0ubuntu0.12.04.2) was installed. Seeing as I need to convert h.265 to h.264, an update was obviously required.

    Following posted instructions, I installed a ream of packages :

    $ sudo apt-get install faad libmp4v2-dev libfaac0 libfaac-dev
    libxvidcore4 libxvidcore4-dev liba52-0.7.4 liba52-0.7.4-dev libx264-dev
    libgsm-tools libogg-dev libtheora-bin libfaad-dev libvorbis-dev
    libtheora-dev libdts-dev git-core yasm texi2html checkinstall

    followed by

    $ sudo apt-get purge ffmpeg

    in order to get rid of the old stuff from the original repo.

    Downloaded the latest ffmpeg, and a ."/configure ; make ; sudo make install" later, I should be in business.

    Except that typing ’ffmpeg’ at the prompt still fired up the old version. A quick look revealed that the old ffmpeg binary was still sitting in /usr/bin with the new one being installed in /usr/local/bin. But ffmpeg is no longer listed as an installed package, and sudo apt-get remove ffmpeg tells me that "Package ffmpeg is not installed, so not removed".

    Running /usr/local/bin/ffmpeg directly works, however then fails in an Unknown encoder ’libx264’ error. Which is puzzling because the package libx264-120 is installed and /usr/lib/i386-linux-gnu/libx264.so.120 (with the appropriate symlink to /usr/lib/i386-linux-gnu/libx264.so) does exist.

    Maybe I’ve been looking at this for too long, because I’m sure this is a simple issue but I just can’t see it.

    Can someone please hand me the stupid had and point out why I deserve to wear it ?

    Tnx !