Recherche avancée

Médias (91)

Autres articles (21)

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

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

  • Les statuts des instances de mutualisation

    13 mars 2010, par

    Pour des raisons de compatibilité générale du plugin de gestion de mutualisations avec les fonctions originales de SPIP, les statuts des instances sont les mêmes que pour tout autre objets (articles...), seuls leurs noms dans l’interface change quelque peu.
    Les différents statuts possibles sont : prepa (demandé) qui correspond à une instance demandée par un utilisateur. Si le site a déjà été créé par le passé, il est passé en mode désactivé. publie (validé) qui correspond à une instance validée par un (...)

Sur d’autres sites (3596)

  • Issue #2 when compiling Xuggler for Raspberry pi with libx264

    2 août 2014, par Ashish Sharma

    I am trying to compile Xuggler for Raspberry Pi(Running on Debian OS aka Raspbian),

    I followed the ’Basic Build Instructions’ available here for compiling Xuggler.

    After I successfully installed all the prerequisites and set the correct paths, I ran the following command :

    ant run-tests

    After sometime I am facing the following error and the ant build fails at libx264 :

    scroll at the end of log to see the issue

    common/arm/mc-c.c: In function âx264_weight_cache_neonâ:
    
common/arm/mc-c.c:89:25: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
    
common/arm/mc-c.c:94:25: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
    
common/arm/mc-c.c:99:21: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
    
common/arm/mc-c.c:101:21: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
    
common/arm/mc-c.c: In function âx264_mc_init_armâ:
    
common/arm/mc-c.c:236:19: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
    
common/arm/mc-c.c:237:19: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
    
common/arm/mc-c.c:238:19: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
    
gcc -Wshadow -O3 -fno-fast-math -I/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include  -Wall -I. -I.  -I'/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include' -std=gnu99 -mcpu=cortex-a8 -mfpu=neon -fPIC -fomit-frame-pointer -fno-tree-vectorize   -c -o common/arm/predict-c.o common/arm/predict-c.c
    
as -I/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include  -Wall -I. -I.  -I'/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include' -std=gnu99 -mcpu=cortex-a8 -mfpu=neon -c -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/arm/cpu-a.o common/arm/cpu-a.S
    
as: unrecognized option '-std=gnu99'
    
make[1]: *** [common/arm/cpu-a.o] Error 1
    
make[1]: Leaving directory `/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/libx264/csrc'
    
make: *** [all-local] Error 2

    I am unable to understand the problem statment "unrecognized option ’-std=gnu99’" here, Can someone please tell me how can I resolve this or circumvent it in xuggler ?

  • Issue #2 when compiling Xuggler for Raspberry pi with libx264

    2 août 2014, par Ashish Sharma

    I am trying to compile Xuggler for Raspberry Pi(Running on Debian OS aka Raspbian),

    I followed the ’Basic Build Instructions’ available here for compiling Xuggler.

    After I successfully installed all the prerequisites and set the correct paths, I ran the following command :

    ant run-tests

    After sometime I am facing the following error and the ant build fails at libx264 :

    scroll at the end of log to see the issue

    common/arm/mc-c.c: In function âx264_weight_cache_neonâ:
    
common/arm/mc-c.c:89:25: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
    
common/arm/mc-c.c:94:25: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
    
common/arm/mc-c.c:99:21: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
    
common/arm/mc-c.c:101:21: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
    
common/arm/mc-c.c: In function âx264_mc_init_armâ:
    
common/arm/mc-c.c:236:19: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
    
common/arm/mc-c.c:237:19: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
    
common/arm/mc-c.c:238:19: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
    
gcc -Wshadow -O3 -fno-fast-math -I/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include  -Wall -I. -I.  -I'/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include' -std=gnu99 -mcpu=cortex-a8 -mfpu=neon -fPIC -fomit-frame-pointer -fno-tree-vectorize   -c -o common/arm/predict-c.o common/arm/predict-c.c
    
as -I/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include  -Wall -I. -I.  -I'/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include' -std=gnu99 -mcpu=cortex-a8 -mfpu=neon -c -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/arm/cpu-a.o common/arm/cpu-a.S
    
as: unrecognized option '-std=gnu99'
    
make[1]: *** [common/arm/cpu-a.o] Error 1
    
make[1]: Leaving directory `/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/libx264/csrc'
    
make: *** [all-local] Error 2

    I am unable to understand the problem statment "unrecognized option ’-std=gnu99’" here, Can someone please tell me how can I resolve this or circumvent it in xuggler ?

  • How to speed up my video creating/encoding pipeline

    23 septembre 2015, par user606521

    I am creating a video from 120 JPEG images and concatening it with intro video.

    • video (and images) dimmensions : 960x540
    • video/audio output format that I need : mp4 H.264, AAC

    I am creating video from JPEG images using following command :

    ffmpeg -f lavfi -i anullsrc -r 60 -i pipe:0 -y -acodec aac -strict experimental \
    
-shortest -movflags frag_keyframe+empty_moov -f mp4 video.mp4

    It creates 2 seconds (120 frames with 60FPS) mp4 video with "silence" (silent audio). video.mp4 size is 94KB. This process takes 1 second. (Note that I am passing images through pipe:0).

    Next I concatenate it with existing intro.mp4 video (H.264, AAC, 931KB, lasts 6 seconds) using following command :

    ffmpeg -i intro.mp4 -i video.mp4 -y \
    
-filter_complex "[0:0] [0:1] [1:0] [1:1] concat=n=2:v=1:a=1 [v] [a]" \
    
-map "[v]" -map "[a]" -acodec aac -strict experimental \
    
-movflags frag_keyframe+empty_moov -f mp4 final.mp4

    It creates final mp4 H.254, AAC video which lasts 2 + 6 = 8 seconds and it’s size 990KB. This process takes 3.5 seconds.

    So the whole process takes 5.5 seconds on my Mac. I have to speed it up, especially concatening videos. I am not familiar with video encoding and video formats, but I thought that maybe creating first video in mp4 and then concatening it with another mp4 video is not efficient. Are there any other formats in which I could create video (and intro) that will be faster to create/concatenate so I could encode only final video as mp4 ?

    For example I could create video.<format></format>, concatenate it with intro.<format></format> and finally encode it as final.mp4.

    Use case : I have to create videos in almost real time. 5.5 secs is ok on my Mac, but I have to execute my app on a weaker machine on which this process currently takes 3 + 15 = 18 seconds.

    Also maybe there are some cool flags I could pass to ffmpeg to make it faster ?

Navigation