Recherche avancée

Sur d’autres sites (6083)

• Adding prebuild static library to android studio

  24 mars 2017, par David Barishev

  I have build ffmpeg libraries statically for x86 android using a custom configuration.Now i wanted to add them in my android project.

  Im using ffmpeg 3.2.git, android studio 2.3.

  I created a folder named distribution which had my binaries, located the root of my project.
  Here is a file tree :

  |__distribution
  
  | |__avcodec
  
  | | |__include
  
  | | | |__avcodec.h
  
  | | |__lib
  
  | | | |__x86
  
  | | | | |__libavcodec.a
  
  | |__avfilter
  
  | | |__include
  
  | | | |__avfilter.h
  
  | | |__lib
  
  | | | |__x86
  
  | | | | |__libavfilter.a
  
  | |__avformat
  
  | | |__include
  
  | | | |__avformat.h
  
  | | |__lib
  
  | | | |__x86
  
  | | | | |__libavformat.a
  
  | |__avutil
  
  | | |__include
  
  | | | |__avutil.h
  
  | | |__lib
  
  | | | |__x86
  
  | | | | |__libavutil.a
  
  | |__swresample
  
  | | |__include
  
  | | | |__swresample.h
  
  | | |__lib
  
  | | | |__x86
  
  | | | | |__libswresample.a

  I edited my cmake to include the libraries :

  add_library(
  
           native-lib
  
           SHARED
  
           src/main/cpp/native-lib.cpp )
  
  
  
  set(distribution_DIR ${CMAKE_SOURCE_DIR}/../distribution)
  
  
  
  add_library(lib_avcodec STATIC IMPORTED)
  
  set_target_properties(lib_avcodec PROPERTIES IMPORTED_LOCATION
  
      ${distribution_DIR}/avcodec/lib/${ANDROID_ABI}/libavcodec.a)
  
  
  
  add_library(lib_avfilter STATIC IMPORTED)
  
  set_target_properties(lib_avfilter PROPERTIES IMPORTED_LOCATION
  
      ${distribution_DIR}/avfilter/lib/${ANDROID_ABI}/libavfilter.a)
  
  
  
  add_library(lib_avformat STATIC IMPORTED)
  
  set_target_properties(lib_avformat PROPERTIES IMPORTED_LOCATION
  
      ${distribution_DIR}/avformat/lib/${ANDROID_ABI}/libavformat.a)
  
  
  
  add_library(lib_avutil STATIC IMPORTED)
  
  set_target_properties(lib_avutil PROPERTIES IMPORTED_LOCATION
  
      ${distribution_DIR}/avutil/lib/${ANDROID_ABI}/libavutil.a)
  
  
  
  add_library(lib_swresample STATIC IMPORTED)
  
  set_target_properties(lib_swresample PROPERTIES IMPORTED_LOCATION
  
      ${distribution_DIR}/swresample/lib/${ANDROID_ABI}/libswresample.a)
  
  
  
  
  
  
  
  include_directories(
  
                             ${distribution_DIR}/avcodec/include
  
                             ${distribution_DIR}/avfilter/include
  
                             ${distribution_DIR}/avformat/include
  
                             ${distribution_DIR}/avutil/include
  
                             ${distribution_DIR}/swresample/include)
  
  
  
  
  
  target_link_libraries( 
  
                         native-lib
  
  
  
                         lib_avcodec
  
                         lib_avfilter
  
                         lib_avformat
  
                         lib_avutil
  
                         lib_swresample
  
                          )

  I also restricted the build to only x86, in my app build.gradle :

  ndk {
  
              // Specifies the ABI configurations of your native
  
              // libraries Gradle should build and package with your APK.
  
              abiFilters 'x86'
  
      }

  The project gradle sync worked successfully.
  I edited my cpp file to try to use the libraries, and i noticed something weird,i couldn’t reference the headers with the library beforehand, only the header name itself (eg. #include "libavformat/avformat.h" doesn’t work, #include "avformat.h" works).
  I suspect this is because of the headers reference, that they are not tied to a library.
  How can i fix it ?

  Also this makes the project build fail, since in the static libraries headers, there is a reference to other part of the library (eg avformat includes avcodec),but they reference it with the library name beforehand, and as i have said earlier, it doesn’t work.

  Here is the relevant build log part :

  ../../../../../distribution/avformat/include\avformat.h:319:10: fatal error: 'libavcodec/avcodec.h' file not found
  
    #include "libavcodec/avcodec.h"
  
             ^

• How I can overlay video onto another video start from 2 second to 4 second ?

  23 janvier 2023, par KoliK

  I need overlay video onto another video start from 2 second to 4 second.

  


  I use ffmpeg for overlaying video onto another video for this command
ffmpeg -i tmp/test_screen_1672755242397.mp4 -vf "movie=tmp/test_camera_1672755249551.mp4, scale=250: -1 [inner]; [in][inner] overlay =10: 10 [out]" completed.mp4
But video test_camera_1672755249551 must be to star from 2 second and end to 4 second. What I need to add in command for result ?

  


• lavu/frame : deprecate AVFrame.pkt_{pos,size}

  10 mars 2023, par Anton Khirnov

  lavu/frame : deprecate AVFrame.pkt_pos,size
  These fields are supposed to store information about the packet the
  
  frame was decoded from, specifically the byte offset it was stored at
  
  and its size.
  However,
  
   the fields are highly ad-hoc - there is no strong reason why
  
    specifically those (and not any other) packet properties should have a
  
    dedicated field in AVFrame ; unlike e.g. the timestamps, there is no
  
    fundamental link between coded packet offset/size and decoded frames
  
   they only make sense for frames produced by decoding demuxed packets,
  
    and even then it is not always the case that the encoded data was
  
    stored in the file as a contiguous sequence of bytes (in order for pos
  
    to be well-defined)
  
   pkt_pos was added without much explanation, apparently to allow
  
    passthrough of this information through lavfi in order to handle byte
  
    seeking in ffplay. That is now implemented using arbitrary user data
  
    passthrough in AVFrame.opaque_ref.
  
   several filters use pkt_pos as a variable available to user-supplied
  
    expressions, but there seems to be no established motivation for using them.
  
   pkt_size was added for use in ffprobe, but that too is now handled
  
    without using this field. Additonally, the values of this field
  
    produced by libavcodec are flawed, as described in the previous
  
    ffprobe conversion commit.
  In summary - these fields are ill-defined and insufficiently motivated,
  
  so deprecate them.
  

  • [DH] doc/filters.texi
  • [DH] libavcodec/av1dec.c
  • [DH] libavcodec/crystalhd.c
  • [DH] libavcodec/cuviddec.c
  • [DH] libavcodec/decode.c
  • [DH] libavcodec/libuavs3d.c
  • [DH] libavdevice/lavfi.c
  • [DH] libavfilter/af_ashowinfo.c
  • [DH] libavfilter/af_volume.c
  • [DH] libavfilter/asrc_flite.c
  • [DH] libavfilter/avfilter.c
  • [DH] libavfilter/f_select.c
  • [DH] libavfilter/f_sendcmd.c
  • [DH] libavfilter/setpts.c
  • [DH] libavfilter/vf_crop.c
  • [DH] libavfilter/vf_drawtext.c
  • [DH] libavfilter/vf_eq.c
  • [DH] libavfilter/vf_eq.h
  • [DH] libavfilter/vf_overlay.c
  • [DH] libavfilter/vf_overlay.h
  • [DH] libavfilter/vf_overlay_cuda.c
  • [DH] libavfilter/vf_scale.c
  • [DH] libavfilter/vf_scale_npp.c
  • [DH] libavfilter/vf_showinfo.c
  • [DH] libavfilter/vf_swaprect.c
  • [DH] libavutil/frame.c
  • [DH] libavutil/frame.h
  • [DH] libavutil/version.h