Recherche avancée

Sur d’autres sites (7478)

• How to avoid the "text relocation" error by ffmpeg library on Android x86

  16 octobre 2017, par Tank2005

  My environment is Qt 5.9 for Android on Windows 10 64bit. NDK is r10e and SDK Level is 16(Those sdks are recommended version by Qt development team).

  I built a ffmpeg 3.4 source code as .so files on Ubuntu 16.04.3 LTS. Those library has no error on ARM architecture Android. But, on x86 Emulator, "Text realocations" alart is shown like this.

  

  I rewrite configure with "disable-asm, disable-yasm" referd from this site’s old posts.

  This hereby removed some errors. But only one library has a problem.
  

  I also tried the method of deleting "strtod.o", But it seems no effect. My current build configure is that. Does anyone know a better way ?

  #!/bin/bash
  
  NDK=/home/my/data/ndk
  
  SYSROOT=$NDK/platforms/android-14/arch-x86/
  
  TOOLCHAIN=$NDK/linux-x86-48
  
  CPU=x86
  
  PREFIX=$(pwd)/android/x86
  
  PATH=$TOOLCHAIN/bin:$PATH
  
  
  
  function build_one
  
  {
  
  ./configure \
  
      --cc="$TOOLCHAIN/bin/i686-linux-android-gcc-4.8" \
  
      --enable-cross-compile \
  
      --target-os=linux \
  
      --arch=x86 \
  
      --prefix=$PREFIX \
  
      --enable-shared \
  
      --disable-static \
  
      --disable-avdevice \
  
      --disable-doc \
  
      --disable-encoders \
  
      --disable-decoders \
  
      --enable-decoder=h264 \
  
      --enable-decoder=aac \
  
      --disable-protocols \
  
      --disable-demuxers \
  
      --disable-muxers \
  
      --disable-filters \
  
      --disable-network \
  
      --disable-ffplay \
  
      --disable-ffmpeg \
  
      --disable-ffprobe \
  
      --disable-ffserver \
  
      --enable-parsers \
  
      --cross-prefix=i686-linux-android- \
  
      --enable-cross-compile \
  
      --target-os=linux \
  
      --arch=x86 \
  
      --disable-doc \
  
      --sysroot=$SYSROOT \
  
      --disable-x86asm -disable-yasm --enable-pic \
  
      --extra-cflags="-std=c99 -O3 -Wall -fpic -pipe -DANDROID -DNDEBUG -march=atom -msse3 -ffast-math -mfpmath=sse" \
  
      --extra-ldflags='-lm -lz -Wl,--no-undefined -Wl,-z,noexecstack' \
  
      $ADDITIONAL_CONFIGURE_FLAG
  
  make clean
  
  rm -f $(pwd)/compat/strtod.o
  
  rm -f $(pwd)/compat/strtod.d
  
  make 
  
  make install
  
  }
  
  build_one

• Libavcodec "the procedure entry point for av_frame_alloc could not be located" error in Visual Studio 2017 C++ project

  25 novembre 2019, par Aves

  I am trying to use libavcodec from ffmpeg library in C++ with Visual Studio 2017 Community. I downloaded the latest x64 dev and shared builds from zeranoe (version 20171217), set up include directories and additional libraries in Visual Studio for x64 build, added DLL files from shared package to my PATH.

  This is my sample test code :

  extern "C" {
  
  #include 
  
  }
  
  int main() {
  
      avcodec_register_all();
  
      AVFrame *pAvFrame = av_frame_alloc();
  
      av_frame_free(&pAvFrame);
  
      return 0;
  
  }

  The code compiles without problems but when I run the application I see a dialogue window with error message "the procedure entry point for av_frame_alloc could not be located in DLL" (actual message is not in English, this is the translated version).

  I tried to set Linker->Optimization->References to /OPT:NOREF as it was advised in the similar questions but it did not help.

  Dependency walker shows that av_frame_alloc is exported, "Entry Point" is not bound. A little bit strange is that av_frame_alloc is displayed in both avcodec-58.dll (as red) and avutil-56.dll (as green). Maybe the reason is that the application is trying to get this function from avcodec instead of avutil, but I’m not sure, since I did not check the source code of these libraries.

  So the question is how to set up such a simple FFMPEG-based C++ project in VS2017, where I’m wrong ?

  UPD. 1.

  Linker flags : /OUT :"C :\work\code\TestFfmpeg\x64\Release\TestFfmpeg.exe" /MANIFEST /NXCOMPAT /PDB :"C :\work\code\TestFfmpeg\x64\Release\TestFfmpeg.pdb" /DYNAMICBASE "c :\work\dev\ffmpeg-20171217-387ee1d-win64-dev\lib*.lib" "kernel32.lib" "user32.lib" "gdi32.lib" "winspool.lib" "comdlg32.lib" "advapi32.lib" "shell32.lib" "ole32.lib" "oleaut32.lib" "uuid.lib" "odbc32.lib" "odbccp32.lib" /DEBUG:FULL /MACHINE:X64 /OPT:NOREF /PGD :"C :\work\code\TestFfmpeg\x64\Release\TestFfmpeg.pgd" /MANIFESTUAC :"level=’asInvoker’ uiAccess=’false’" /ManifestFile :"x64\Release\TestFfmpeg.exe.intermediate.manifest" /OPT:ICF /ERRORREPORT:PROMPT /NOLOGO /TLBID:1

• ffmpeg osx error while writing file : "Unrecognized option 'preset'.Error splitting the argument list : Option not found

  22 décembre 2023, par asabbah

  I have the following simple Python Code :

  



  yellow_output = 'test_videos_output/solidYellowleft.mp4'
clip1 = VideoFileClip("test_videos/solidYellowLeft.mp4")
yellow_clip = clip1.fl_image(process_image)
yellow_clip.write_videofile(yellow_output, audio=False)


  



  The "process_image" function just returns what you give it (created for testing purposes).

  



  Running Python 3.5.4, ffmpeg 2.8.6, on OSX 10.11.6

  



  I get the error :

  



  OSError: [Errno 32] Broken pipe

MoviePy error: FFMPEG encountered the following error while writing file test_videos_output/solidWwhiteright.mp4:

 b"Unrecognized option 'preset'.\nError splitting the argument list: Option not found\n"


  



  the video file is not generated ; how to get rid of this error ; so I can generate the MP4 file ?

  



  Note : the same code runs happily on Ubuntu 16.04