Recherche avancée

Médias (2)

Mot : - Tags -/kml

Autres articles (28)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Ecrire une actualité

    21 juin 2013, par

    Présentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
    Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
    Vous pouvez personnaliser le formulaire de création d’une actualité.
    Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)

  • 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

Sur d’autres sites (6568)

  • Building x264 with YASM : failing the ASM check

    11 janvier 2020, par radiofreemyourenji

    My question up front is, "I have new yasm, I think x264 is supposed to be cool with that, why is x264 not cool with that ?"

    For reasons, I am building a CentOS docker image (based on centos:latest) that contains a from-scratch ffmpeg build, following the guide here. It’s a good guide, it’s worked for me before, so I was feeling good about it.

    Today I’m hitting a choke point on the libx264 build point : specifically, I say

    PKG_CONFIG_PATH="/tmp/ffmpeg_build/lib/pkgconfig" \
     ./configure \
     --prefix="/tmp/ffmpeg_build" \
     --bindir="/tmp/bin" \
     --enable-static

    And I get a reply back

    Found no assembler

    Minimum version is nasm-2.13

    If you really want to compile without asm, configure with —disable-asm.

    That’s unexpected. I have yasm, which I understand to be 1) there to do the things nasm does but better, and 2) to be the daisy-fresh most modern version given that I pulled it from its repo about an hour ago, and built it about fifty-nine minutes ago. For what it’s worth, nasm is on the box too since the instructions request it, but it’s below their stated version (i.e. it’s "NASM version 2.10.07 compiled on Jun 9 2014")

    So it seems like yasm is not being found. There’s another StackExchange question that mentions that problem, which came out to a pathing issue. So, I added yasm to my path like so :

    PATH=/tmp/ffmpeg_sources/yasm:$PATH \
     PKG_CONFIG_PATH="/tmp/ffmpeg_build/lib/pkgconfig" \
     ./configure
     ...etc

    That still gave the Found-no-assembler problem. As a last, confused resort, I told the script explicitly what I wanted to use for the variable $AS, because based on my quick look into configure, that looked like where yasm/nasm was meant to go. The command becomes :

    AS=`which yasm`
     PKG_CONFIG_PATH="/tmp/ffmpeg_build/lib/pkgconfig" \
     ./configure
     ...etc

    That at least gave

    Found yasm 1.3.0

    Minimum version is nasm-2.13

    If you really want to compile without asm, configure with —disable-asm.

    Looking in the config.log I see the following :

    checking whether /tmp/bin/yasm supports vmovdqa32 [eax]{k1}{z}, zmm0... no
    Failed commandline was:
    --------------------------------------------------
    /tmp/bin/yasm conftest.asm  -I. -I$(SRCPATH) -DARCH_X86_64=1 -I$(SRCPATH)/common/x86/ -f elf64  -o conftest.o
    conftest.asm:1: error: instruction expected after label
    conftest.asm:1: warning: ignoring unrecognized character `{'
    conftest.asm:1: warning: ignoring unrecognized character `}'
    conftest.asm:1: warning: ignoring unrecognized character `{'
    conftest.asm:1: warning: ignoring unrecognized character `}'
    --------------------------------------------------
    Failed program was:
    --------------------------------------------------
    vmovdqa32 [eax]{k1}{z}, zmm0
    --------------------------------------------------

    So : what’s the deal here ? Is my assumption that yasm drop-in replaces nasm bad ? Is yasm good for this purpose, but I’m not providing the right information to ./configure ? Are my instructions for building ffmpeg for CentOS simply out of date with respect to this prerequisite and I should just try harder to get a modern nasm ?

  • Anomalie #2732 : interclassement table spip_urls

    8 juin 2012, par denisb -

    de fait (pfff) le problème provient d’une double définition de CHARACTER SET à la création de la table : celui, par défaut, des globales charset_sql_base et charset_collation_sql_base plus celui arrivant par le dump. mysql couine et ne crée pas la table (on voit ça dans les logs : url varchar(255) (...)

  • German umlauts in ffmpeg drawtext filter

    15 août 2020, par Gert Gottschalk

    I need help getting german umlauts 'äüö' displayed properly/(at all) in ffmpeg drawtext filter. I can't say at this time if my inability comes from lack of ffmpeg know-how or machine configuration or both. Your input is much appreciated.

    



    In ffmpeg cmd line I have :

    



    /home/tools/bin/ffmpeg -loop 1 -i RAW2TIF_01_png_1080/IMG_1119.png -c:v libx264 -vf drawtext="fontsize=60:fontcolor=yellow:fontfile=/usr/share/fonts/truetype/freefont/FreeSans.ttf:textfile=./Scripts/header_text.txt:x=(w-text_w)/2:y=(h-text_h-line_h)/2" -t 10 -pix_fmt yuv420p  -crf 16 -r 24 -y ./Video/header_txt.mp4


    



    Note the 'drawtext' call.

    



    My linux machine where I run ffmpeg is setup for US keyboard and characters. So my first roadblock is to get the umlauts into the text in some editor. I tried typing 'alt-numerical' sequences, but the special characters will not show in vi, vim, emacs.

    



    If I were to have the special characters in a textfile I would not know if/how ffmpeg is able to handle them.

    



    A search on popular engine for 'ffmpeg drawtext umlaut' does not return any (for me) meaningful returns.

    



    Thanks,
Gert