Recherche avancée

Sur d’autres sites (5160)

• Revision 58232 : On évite d’utiliser ffmpeg-php qui n’est plus maintenu au profit d’un ...

  13 février 2012, par kent1@… — Log

  On évite d’utiliser ffmpeg-php qui n’est plus maintenu au profit d’un script bash de génération de vignettes
  On utilise uniquement MediaInfo ? pour la récupération des informations des documents
  Moins de lots intempestifs
  On incréments en 0.9.9

• Revision 73753 : Utiliser $GLOBALS[’mutualisation_dir’] et non sites/ en dur pour les ...

  20 juin 2013, par kent1@… — Log

  Utiliser $GLOBALSmutualisation_dir ? et non sites/ en dur pour les calculs js de taille

• Files conflict(lib/arm64-v8a/libc++_shared.so) with Jitsi and FFmpegKit

  15 mai 2022, par Riccoh

  I have a persistent problem that I can't seem to solve, I am using Android SDK 32 and have installed 2 Libraries(com.arthenica:ffmpeg-kit-full and org.jitsi.react:jitsi-meet-sdk) which are in conflict with one another.

  


  When I add these 2 libraries and tried to run it on my device I get the following error message "2 files found with path 'lib/arm64-v8a/libc++_shared.so' from inputs...".

  


  To solve this problem I applied the following solution : https://github.com/tanersener/ffmpeg-kit/wiki/Tips#2-depending-another-android-library-containing-libc_sharedso.

  


  This seems to work as my project runs succesfully on my device.
But when I am trying to call a ffmpeg command :

  


  FFmpegKit.execute("-y -i ${audioFile?.absoluteFile.toString()} -af asetrate=54100*1/2,atempo=2/1 ${audioVoice?.absoluteFile.toString()}")


  


  I get the following error..

  


  java.lang.Error: FFmpegKit failed to start on brand: google, model: Pixel 3, device: blueline, api level: 32, abis: arm64-v8a armeabi-v7a armeabi, 32bit abis: armeabi-v7a armeabi, 64bit abis: arm64-v8a.


  


  I searched further but couldn't find a solution to my problem.

  


  Is it possible to get both libraries working without issues ?