Recherche avancée

Sur d’autres sites (7452)

• How to compile ffmpeg for Windows statically with MSYS2 environment ?

  17 janvier 2024, par username

  I want to build myself standalone statically linked ffmpeg binaries for Windows from official git source code with MSYS2 environment tools. But every time I get .exe file dynamically linked to mingw libraries that crashes with "The application was unable to start correctly (0xc000007b)" error even if I put required libbz2-1.dll, libiconv-2.dll and libwinpthread-1.dll libraries in it's folder.

  



  I'm running MSYS2 environment with

  



  msys2_shell.cmd -mingw64


  



  line, and use mingw64/mingw-w64-x86_64-gcc 8.2.1+20181214-1 compiler package. Then I run ./configure with

  



  ./configure --pkg-config-flags=--static --disable-shared --enable-static


  



  line - the best options I have googled at all my efforts. Then proceed with general

  



  make
make install


  



  sequence.

  



  As a result, I get binaries that run smoothly in MSYS2 environment itself, but when I run it from host Windows explorer or cmd, first of all it ask for libbz2-1.dll, libiconv-2.dll and libwinpthread-1.dll libraries and when I put them in binaries' folder, they crash with "The application was unable to start correctly (0xc000007b)" error.

  



  I've asked about this case at official https://ffmpeg.zeranoe.com/forum/viewtopic.php?f=5&t=6439 forum but still have no response for already 5 days.

  



  Regarding dynamic linking libraries somehow I got bandaid solution with removing *.dll.a files from mingw64\x86_64-w64-mingw32\lib folder. But it looks not very clean for me. I wish to know if it is possible to do static linkage with some compiler/make/linker parameters or with editing ./configure or Makefile files somehow ?

  



  Also 0xc000007b error still remaining.

  



  I've managed to have desired result with media-autobuild_suite based on the same MSYS2 environment, so I know it is possible to do this somehow. But I'm very new to all this *nix things so don't understand it's bash script at all, not to mention it is pretty sophisticated by itself. The only thing I see it's producing correct ffmpeg executables running under native Windows environment not requiring dlls listed above.

  



  According to all guides in internet I found at the moment, I should get standalone Windows executables with this toolset, but it just don't work and I'm stuck. Please, help.

  


• Revision 26496c52bf : Quick modifications to wide loopfilter intrinsic functions Modified to work wit

  12 juin 2013, par Scott LaVarnway

  Changed Paths :
   Modify /vp9/common/vp9_loopfilter.c

  
   Modify /vp9/common/vp9_loopfilter.h

  
   Modify /vp9/common/vp9_loopfilter_filters.c

  
   Modify /vp9/common/vp9_rtcd_defs.sh

  
   Modify /vp9/common/x86/vp9_loopfilter_intrin_sse2.c

  
  
  Quick modifications to wide loopfilter intrinsic functions

  Modified to work with 8x8 blocks of memory. Will revisit
  later for further optimizations. For the HD clip used, the
  decoder improved my 20%.

  Change-Id : Ia0057f55d66d1445882351ea6c43b595a5a980e5

• How can I catch when source network down in ffmpeg ?

  12 mai 2022, par Tlaloc-ES

  Hello I am running the following command

  


  CONECTION_REFUSED="Connection refused"

OUTPUT=$(ffmpeg -i rtsp://192.168.1.46:8080/h264_ulaw.sdp -vcodec copy output.mp4  -loglevel 16 -report 2>&1)

if [[ "$OUTPUT" == *"$CONECTION_REFUSED"* ]]; then
  echo "It's there."
fi

echo $?


  


  In order to test several crashes, if the script starts without RTSP server up, FFmpeg fails with an error that says "Connection refused", but if I run the command with the RTSP server up and down after running, FFmpeg only stops without notifying any kind of error.

  


  Is there any way to catch the lost-connection error ?

  


  Thanks