Recherche avancée

Médias (0)

Mot : - Tags -/page unique

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

Autres articles (39)

  • Other interesting software

    13 avril 2011, par

    We don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
    The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
    We don’t know them, we didn’t try them, but you can take a peek.
    Videopress
    Website : http://videopress.com/
    License : GNU/GPL v2
    Source code : (...)

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

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

Sur d’autres sites (4853)

  • x264 static lib libx264.a occur an error : asm code, recompile with -fPIC [closed]

    20 juin 2019, par thunvan

    compile with static libs :

    yasm -I. -I. -DARCH_X86_64=1 -I./common/x86/ -f elf64 -Worphan-labels -DSTACK_ALIGNMENT=32 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/x86/cabac-a.o common/x86/cabac-a.asm

    link the libx264.a to another so libs

    occur : (cabac-a.o): relocation R_X86_64_PC32 against symbol `x264_cabac_range_lps' can not be used when making a shared object; recompile with -fPIC

    used -DPIC with yasm, also have error.

    gcc -Wno-maybe-uninitialized -Wshadow -O3 -ffast-math -m64  -Wall -I. -I. -std=gnu99 -D_GNU_SOURCE -mpreferred-stack-boundary=5  -I/usr/local/include  -I/usr/local/include -fPIC -fomit-frame-pointer -fno-tree-vectorize   -c -o encoder/cavlc.o encoder/cavlc.c
    
gcc -Wno-maybe-uninitialized -Wshadow -O3 -ffast-math -m64  -Wall -I. -I. -std=gnu99 -D_GNU_SOURCE -mpreferred-stack-boundary=5  -I/usr/local/include  -I/usr/local/include -fPIC -fomit-frame-pointer -fno-tree-vectorize   -c -o encoder/encoder.o encoder/encoder.c
    
gcc -Wno-maybe-uninitialized -Wshadow -O3 -ffast-math -m64  -Wall -I. -I. -std=gnu99 -D_GNU_SOURCE -mpreferred-stack-boundary=5  -I/usr/local/include  -I/usr/local/include -fPIC -fomit-frame-pointer -fno-tree-vectorize   -c -o encoder/lookahead.o encoder/lookahead.c
    
gcc -Wno-maybe-uninitialized -Wshadow -O3 -ffast-math -m64  -Wall -I. -I. -std=gnu99 -D_GNU_SOURCE -mpreferred-stack-boundary=5  -I/usr/local/include  -I/usr/local/include -fPIC -fomit-frame-pointer -fno-tree-vectorize   -c -o common/threadpool.o common/threadpool.c
    
gcc -Wno-maybe-uninitialized -Wshadow -O3 -ffast-math -m64  -Wall -I. -I. -std=gnu99 -D_GNU_SOURCE -mpreferred-stack-boundary=5  -I/usr/local/include  -I/usr/local/include -fPIC -fomit-frame-pointer -fno-tree-vectorize   -c -o common/x86/mc-c.o common/x86/mc-c.c
    
gcc -Wno-maybe-uninitialized -Wshadow -O3 -ffast-math -m64  -Wall -I. -I. -std=gnu99 -D_GNU_SOURCE -mpreferred-stack-boundary=5  -I/usr/local/include  -I/usr/local/include -fPIC -fomit-frame-pointer -fno-tree-vectorize   -c -o common/x86/predict-c.o common/x86/predict-c.c
    
yasm -I. -I. -DARCH_X86_64=1 -I./common/x86/ -f elf64 -Worphan-labels -DSTACK_ALIGNMENT=32 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/x86/const-a.o common/x86/const-a.asm
    
yasm -I. -I. -DARCH_X86_64=1 -I./common/x86/ -f elf64 -Worphan-labels -DSTACK_ALIGNMENT=32 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/x86/cabac-a.o common/x86/cabac-a.asm
    
yasm -I. -I. -DARCH_X86_64=1 -I./common/x86/ -f elf64 -Worphan-labels -DSTACK_ALIGNMENT=32 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/x86/dct-a.o common/x86/dct-a.asm
    
yasm -I. -I. -DARCH_X86_64=1 -I./common/x86/ -f elf64 -Worphan-labels -DSTACK_ALIGNMENT=32 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/x86/deblock-a.o common/x86/deblock-a.asm
    
yasm -I. -I. -DARCH_X86_64=1 -I./common/x86/ -f elf64 -Worphan-labels -DSTACK_ALIGNMENT=32 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/x86/mc-a.o common/x86/mc-a.asm
    
yasm -I. -I. -DARCH_X86_64=1 -I./common/x86/ -f elf64 -Worphan-labels -DSTACK_ALIGNMENT=32 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/x86/mc-a2.o common/x86/mc-a2.asm
    
yasm -I. -I. -DARCH_X86_64=1 -I./common/x86/ -f elf64 -Worphan-labels -DSTACK_ALIGNMENT=32 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/x86/pixel-a.o common/x86/pixel-a.asm
    
yasm -I. -I. -DARCH_X86_64=1 -I./common/x86/ -f elf64 -Worphan-labels -DSTACK_ALIGNMENT=32 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/x86/predict-a.o common/x86/predict-a.asm

    how to compile asm code with yasm, and result to pic code successfully ?

  • ERROR : SvtAv1Enc not found using pkg-config

    2 novembre 2023, par Dmitry Maksakov

    I am trying to compile FFmpeg with SVT-AV1 codec, following instructions from here : https://github.com/OpenVisualCloud/SVT-AV1/tree/master/ffmpeg_plugin

    



    Everything goes well, but when I try to run

    



    ./configure --enable-libsvtav1


    



    I am getting

    



    ERROR: SvtAv1Enc not found using pkg-config

If you think configure made a mistake, make sure you are using the latest
version from Git.  If the latest version fails, report the problem to the
ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net.
Include the log file "ffbuild/config.log" produced by configure as this will help
solve the problem.


    



    The content of the ffbuild/config.log : https://pastebin.com/euPriFAp

    



    There is an exact issue on the github : https://github.com/OpenVisualCloud/SVT-AV1/issues/35, but is closed as solved.

    



    I have tried both on my Mac and in the Docker container with Ubuntu 18.04, but getting the same result.

    



    Could anyone please help, what am I doing wrong ?

    


  • FFMpeg with libstagefright for hardware encoding jpeg images to mp4 on Android

    16 septembre 2015, par HashG

    I have compiled FFMpeg with libstagefright for Android. I know this can be used for hardware decoding but I would like to use it for hardware encoding a stream of jpeg images to mp4 video. Could someone please shed some light on this.

    I have looked at the post below where Alex Cohn says "Alternatively, you can compile ffmpeg with libstagefright, and it will use hardware avc encoder." - android-how-to-encode-a-stream-of-images-to-h264-with-hardware-acceleration

    Could someone explain how to do this. I have compiled ffmpeg with the following options :

    --disable-avdevice
    
--disable-decoder=h264
    
--disable-decoder=h264_vdpau
    
--enable-libstagefright-h264

    All this relates to enabling hardware decoding but what would I need to specify to enable hardware encoding ?

    My ffmpeg command to convert the images into a video looks like this :

    ffmpeg.execute(new String[]{"-framerate",
    
                "25",
    
                "-i",
    
                "/images_directory/image%07d.jpg",
    
                "-c:v",
    
                "libx264",
    
                "-preset",
    
                "ultrafast",
    
                "-tune",
    
                "zerolatency",
    
                "-r",
    
                "25",
    
                "-pix_fmt",
    
                "yuv420p",
    
                "output.mp4"})

    What should I change to enable hardware encoding ?

Navigation