Recherche avancée

Médias (0)

Mot : - Tags -/presse-papier

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

Autres articles (77)

  • Pas question de marché, de cloud etc...

    10 avril 2011

    Le vocabulaire utilisé sur ce site essaie d’éviter toute référence à la mode qui fleurit allègrement
    sur le web 2.0 et dans les entreprises qui en vivent.
    Vous êtes donc invité à bannir l’utilisation des termes "Brand", "Cloud", "Marché" etc...
    Notre motivation est avant tout de créer un outil simple, accessible à pour tout le monde, favorisant
    le partage de créations sur Internet et permettant aux auteurs de garder une autonomie optimale.
    Aucun "contrat Gold ou Premium" n’est donc prévu, aucun (...)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

Sur d’autres sites (10117)

  • Compiling static libs of ffmpeg with x264 in Msys2 for Visual Studio, but libx264 is never found

    29 mai 2020, par Blake Senftner

    Having previously downloaded and compiled ffmpeg 4.2.2 to static libraries using MSYS2 and the Visual Studio 2015 x64 tool chain. I want to add the x264 codec from VLC/VideoLan, compiling that to a static library as well. However, running Configure for ffmpeg produces an error saying "libx264 not found."

    



    I built ffmpeg without VideoLAN's x264 at "/c/ThirdParty/opt/ffmpeg-4.2.2" with "make install" installing to "/c/ThirdParty/opt/ffmpeg-4.2.2/ffmpeg_build" .

    



    I am using the following steps to compile from source x264 and add it to the ffmpeg build using the same VS2015 tool chain :

    



      

    1. Launch an "VS2015 x64 Natice Tools Command Prompt"
    2. 


    3. From that VS2015 command prompt, run "c :\msys64\msys2_shell.cmd -mingw64 -use-full-path"
    4. 


    5. From inside the MSYS2 shell, run "cd /c/ThirdParty/opt"
    6. 


    7. git clone http://git.videolan.org/git/x264.git
    8. 


    9. cd x264
    10. 


    11. CC=cl ./configure —enable-static —prefix=/c/ThirdParty/opt/ffmpeg-4.2.2/ffmpeg_build —disable-cli
    12. 


    13. make
    14. 


    15. make install
    16. 


    17. cd ../ffmpeg-4.2.2
    18. 


    19. PKG_CONFIG_PATH=/c/ThirdParty/opt/ffmpeg-4.2.2/ffmpeg_build/lib \
./configure —prefix=./ffmpeg_build —toolchain=msvc —arch=x86_64 \
—target-os=win64 —extra-cflags=-MT —extra-cxxflags=-MT \
—extra-ldflags=-L/c/ThirdParty/opt/ffmpeg-4.2.2/ffmpeg_build/lib \
—enable-x86asm —enable-asm —enable-static —disable-shared \
—disable-debug —enable-gpl —enable-avresample —enable-libx264

    20. 


    



    The steps work, compiling x264 fine, but the output for ffmpeg's Configure is "ERROR : libx264 not found".

    



    I have also tried the variation of using these two lines in place of steps 6 and 10 above :

    



      

    • CC=cl ./configure —enable-static —prefix=/usr/local —disable-cli
    • 


    • PKG_CONFIG_PATH=/usr/local/lib/pkgconfig :$PKG_CONFIG_PATH ./configure —prefix=./ffmpeg_build —toolchain=msvc —arch=x86_64 —target-os=win64 —extra-cflags=-MT —extra-libs=/usr/local/lib/libx264.lib —extra-cxxflags=-MT —enable-x86asm —enable-asm —enable-static —disable-shared —disable-debug —enable-gpl —enable-avresample —enable-libx264
    • 


    



    This version will get past Configure, where I am able to run "make", but the make fails with a series of unresolved X264_* functions while linking ffmpeg_g.exe, 14 unresolved functions in total. The errors at shown at the bottom, but first :

    



    When I look in /c/ThirdParty/opt/ffmpeg-4.2.2/ffmpeg_build/lib I see :

    



    $ ls -l ./ffmpeg_build/lib
total 50988
-rw-r--r-- 1 blake blake 27184250 May 11 16:29 libavcodec.a
-rw-r--r-- 1 blake blake   231304 May 11 16:29 libavdevice.a
-rw-r--r-- 1 blake blake  8574628 May 11 16:29 libavfilter.a
-rw-r--r-- 1 blake blake  8081930 May 11 16:29 libavformat.a
-rw-r--r-- 1 blake blake  1300118 May 11 16:29 libavutil.a
-rw-r--r-- 1 blake blake    61844 May 11 16:29 libpostproc.a
-rw-r--r-- 1 blake blake   348732 May 11 16:29 libswresample.a
-rw-r--r-- 1 blake blake  1316008 May 11 16:29 libswscale.a
-rw-r--r-- 1 blake blake  5086976 May 28 18:08 libx264.lib
drwxr-xr-x 1 blake blake        0 May 28 18:08 pkgconfig


    



    Likewise for /c/ThirdParty/opt/ffmpeg-4.2.2/ffmpeg_build/lib/pkgconfig :

    



    $ ls -l ./ffmpeg_build/lib/pkgconfig/
total 9
-rw-r--r-- 1 blake blake 353 May 11 16:29 libavcodec.pc
-rw-r--r-- 1 blake blake 554 May 11 16:29 libavdevice.pc
-rw-r--r-- 1 blake blake 449 May 11 16:29 libavfilter.pc
-rw-r--r-- 1 blake blake 393 May 11 16:29 libavformat.pc
-rw-r--r-- 1 blake blake 306 May 11 16:29 libavutil.pc
-rw-r--r-- 1 blake blake 317 May 11 16:29 libpostproc.pc
-rw-r--r-- 1 blake blake 322 May 11 16:29 libswresample.pc
-rw-r--r-- 1 blake blake 315 May 11 16:29 libswscale.pc
-rw-r--r-- 1 blake blake 300 May 28 18:08 x264.pc


    



    And looking in /usr/local/lib I see libx264.lib and the pkgconfig directory.

    



    The errors generated by my most recent attempts look like :

    



    LD      ffmpeg_g.exe
libavcodec.a(libx264.o) : error LNK2019: unresolved external symbol __imp_x264_param_default referenced in function X264_init
libavcodec.a(libx264.o) : error LNK2019: unresolved external symbol __imp_x264_param_parse referenced in function X264_init
libavcodec.a(libx264.o) : error LNK2019: unresolved external symbol __imp_x264_param_default_preset referenced in function X264_init
libavcodec.a(libx264.o) : error LNK2019: unresolved external symbol __imp_x264_param_apply_fastfirstpass referenced in function X264_init
libavcodec.a(libx264.o) : error LNK2019: unresolved external symbol __imp_x264_param_apply_profile referenced in function X264_init
libavcodec.a(libx264.o) : error LNK2019: unresolved external symbol __imp_x264_picture_init referenced in function X264_frame
libavcodec.a(libx264.o) : error LNK2019: unresolved external symbol __imp_x264_encoder_open_160 referenced in function X264_init
libavcodec.a(libx264.o) : error LNK2019: unresolved external symbol __imp_x264_encoder_reconfig referenced in function reconfig_encoder
libavcodec.a(libx264.o) : error LNK2019: unresolved external symbol __imp_x264_encoder_headers referenced in function X264_init
libavcodec.a(libx264.o) : error LNK2019: unresolved external symbol __imp_x264_encoder_encode referenced in function X264_frame
libavcodec.a(libx264.o) : error LNK2019: unresolved external symbol __imp_x264_encoder_close referenced in function X264_close
libavcodec.a(libx264.o) : error LNK2019: unresolved external symbol __imp_x264_encoder_delayed_frames referenced in function X264_frame
libavcodec.a(libx264.o) : error LNK2019: unresolved external symbol __imp_x264_encoder_maximum_delayed_frames referenced in function X264_init
libavcodec.a(libx264.o) : error LNK2019: unresolved external symbol __imp_x264_levels referenced in function X264_init
ffmpeg_g.exe : fatal error LNK1120: 14 unresolved externals
make: *** [Makefile:111: ffmpeg_g.exe] Error 96


    



    Maybe something wrong with the —extra-ldflags or —extra-libs options of ffmpeg's Configure, but after trying variations and google searching, I come asking you. Do you know what is wrong with this ffmpeg Configure line ? Step 10, above.

    


  • macOS compile FFMpeg as static standalone binary

    27 octobre 2019, par ColdSteel

    I am trying to compile ffmpeg for macOS (from macOS) as static binary for several days with no luck.
    Here is a script I am running to compile the FFmpeg binary

    cd /Users/$USER/ffmpeg/macOSBuild
    basePath=/macOSdependencies/DependenciesOutput

    export LD_LIBRARY_PATH="/Users/romanlevin/ffmpeg/macOSdependencies/DependenciesOutputbasePath/SDL2/lib/“

    ../configure --disable-autodetect --pkg-config-flags="--static" --extra-cflags="-I$basePath/SDL2/include/" --extra-ldflags="-L/Users/romanlevin/ffmpeg/macOSdependencies/DependenciesOutput/SDL2/lib/" --prefix=/usr/local --enable-gpl --enable-version3 --enable-sdl2 --enable-static --disable-shared

    make clean
    make -j8

    However it is always linking SDL2 as dynamic lib.

    Please note I have compiled the SDL2 by myself and put it in the directory I am trying to add to ld

    enter image description here

    However I also have SDL2 installed with brew, but I don’t want to use it.
    I want Ffmpeg to pick compiled SDL2.

    It does looking for my Compiled library but only asdylib in a hardcoded path - which means I can’t get a portable binaries :(.

    Could some1 open my eyes on what am I doing wrong please ?

  • FATE/dnn : let fate/dnn tests depend on ffmpeg static libraries

    7 août 2019, par Guo, Yejun
    FATE/dnn : let fate/dnn tests depend on ffmpeg static libraries
    

    background :
    DNN (deep neural network) is a sub module of libavfilter, and FATE/dnn
    is unit test for the DNN module, one unit test for one dnn layer.
    The unit tests are not based on the APIs exported by libavfilter,
    they just directly call into the functions within DNN submodule.

    There is an issue when run the following command :
    build$ ../ffmpeg/configure —disable-static —enable-shared
    make
    make fate-dnn-layer-pad

    And part of error message :
    tests/dnn/dnn-layer-pad-test.o : In function `test_with_mode_symmetric' :
    /work/media/ffmpeg/build/src/tests/dnn/dnn-layer-pad-test.c:73 : undefined reference to `dnn_execute_layer_pad'

    The root cause is that function dnn_execute_layer_pad is a LOCAL symbol
    in libavfilter.so, and so the linker could not find it when build dnn-layer-pad-test.
    To check it, just run : readelf -s libavfilter/libavfilter.so | grep dnn

    So, add dependency in fate/dnn Makefile with ffmpeg static libraries.
    This is the same method used in fate/checkasm

    Signed-off-by : Guo, Yejun <yejun.guo@intel.com>
    Signed-off-by : Pedro Arthur <bygrandao@gmail.com>

    • [DH] tests/dnn/Makefile