Recherche avancée

Sur d’autres sites (9047)

• Command build failed ndk

  1er janvier 2021, par ALI RAZA

  I want to integrate ffmpeg lib in my android app . So i am using ndk ,but i am stuck on this issue,I dont know why the error is appearing ,Thanks in advance ;

  


  It is the gradle code that i am using in my app and also the ffmpeg-android-maker path is provided

  


  plugins {
id 'com.android.application'


  


  


  android 
compileSdkVersion 30
buildToolsVersion "30.0.3"

  


  defaultConfig {
    applicationId "com.reactive.myapplication"
    minSdkVersion 16
    targetSdkVersion 30
    versionCode 1
    versionName "1.0"

    testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    externalNativeBuild {
        cmake {
            cppFlags ""
        }
    }
}
flavorDimensions "market"
productFlavors {
    google {
        dimension "market"
        ndk {
            // Since the App Bundle is used, there is no problem in packaging all these ABIs
            abiFilters 'x86', 'x86_64', 'armeabi-v7a', 'arm64-v8a'
        }
    }
    amazon {
        dimension "market"
        applicationIdSuffix ".amzn"
        ndk {
            // Amazon Appstore doesn't support multiple APKs for non-Amazon devices.
            // There is no point in x86 support here, as the majority of devices with the
            // Amazon Appstore are ARM-based. And it seems to be a common practice for other
            // apps in this market.
            abiFilters 'armeabi-v7a'
        }
    }
    huawei {
        dimension "market"
        applicationIdSuffix ".huawei"
        ndk {
            // Huawei App Gallery supports App Bundle format
            abiFilters 'x86', 'x86_64', 'armeabi-v7a', 'arm64-v8a'
        }
    }
}
sourceSets {
    main {
        // let gradle pack the shared library into the apk
        jniLibs.srcDirs = ['../ffmpeg-android-maker/output/lib']
    }
}

bundle {
    language {
        enableSplit = true
    }
    density {
        enableSplit = true
    }
    abi {
        enableSplit = true
    }
}

buildTypes {
    release {
        minifyEnabled false
        proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
    }
}
externalNativeBuild {
    cmake {
        path "src/main/cpp/CMakeLists.txt"
        version "3.10.2"
    }
}
compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_8

    targetCompatibility JavaVersion.VERSION_1_8
}


  


  


  dependencies

  


  implementation 'androidx.appcompat:appcompat:1.1.0'
implementation 'com.google.android.material:material:1.1.0'
implementation 'androidx.constraintlayout:constraintlayout:1.1.3'
testImplementation 'junit:junit:4.+'
androidTestImplementation 'androidx.test.ext:junit:1.1.1'
androidTestImplementation 'androidx.test.espresso:espresso-core:3.2.0'


  


  


  And It is cmake ,


  


  And this is error i am facing :
Build command failed.
Error while executing process /home/ali/Android/Sdk/cmake/3.10.2.4988404/bin/ninja with arguments -C /home/ali/AndroidStudioProjects/FfmpegApp/app/.cxx/cmake/amazonDebug/armeabi-v7a native-lib
ninja : Entering directory `/home/ali/AndroidStudioProjects/FfmpegApp/app/.cxx/cmake/amazonDebug/armeabi-v7a'

  


  ninja : error : '/home/ali/AndroidStudioProjects/FfmpegApp/app/src/main/ffmpeg-android-maker/output/lib/armeabi-v7a/libavutil.so', needed by '/home/ali/AndroidStudioProjects/FfmpegApp/app/build/intermediates/cmake/amazonDebug/obj/armeabi-v7a/libnative-lib.so', missing and no known rule to make it

  


• AWS elastic beanstalk UnhandledPromiseRejectionWarning : Cannot find ffprobe

  1er janvier 2021, par Ali Ahmed

  Using elasticbeanstalk with Node.js 10 running on 64bit Amazon Linux 2/5.2.3. I have a packages.config file under .ebextensions folder.

  


     packages:
  yum:
    ImageMagick: []
    ImageMagick-devel: []
commands:
  01-wget:
    command: "wget -O /tmp/ffmpeg.tar.xz http://ffmpeg.org/releases/ffmpeg-4.1.tar.gz"
  02-mkdir:
    command: "if [ ! -d /opt/ffmpeg ] ; then mkdir -p /opt/ffmpeg; fi"
  03-tar:
    command: "tar xvf /tmp/ffmpeg.tar.xz -C /opt/ffmpeg"
  04-ln:
    command: "if [[ ! -f /usr/bin/ffmpeg ]] ; then ln -sf /opt/ffmpeg/ffmpeg-4.1/ffmpeg /usr/bin/ffmpeg; fi"
  05-ln:
    command: "if [[ ! -f /usr/bin/ffprobe ]] ; then ln -sf /opt/ffmpeg/ffmpeg-4.1/ffprobe /usr/bin/ffprobe; fi"
  06-pecl:
    command: "if [ `pecl list | grep imagick` ] ; then pecl install -f imagick; fi"


  


  I am using fluent-ffmpeg@2.1.2 module for saving screenshot.

  


• AWS Lambda execution time for FFMPEG transcoding

  4 janvier 2023, par FlamingMoe

  I'm using AWS Lambda for converting files from WEBM to MP4

  


  I'm using ffmpeg version 4.3.1-static https://johnvansickle.com/ffmpeg/ (I have done the following tests also with the ffmpeg in serverless AWS ffmpeg layer (that includes de 4.1.3), but results are even worse (about 25% slower)

  


  I'm using Node 10x as container.

  


  WEBM size   Time to convert.  Memory Lambda.  Memory used (as shown in log)

80Mb             ~44s              3008            410
40Mb             ~44s              3008            375

80Mb             ~70s              1024            321
40Mb             ~70s              1024            279


  


  All videos are 80s length. So as far as I can see, it does not matter the size of the WEBM, if the length of the video is the same, it takes the same to convert. So ffmpeg takes more time if the video length is higher, not if the file size is higher ... curious ;-)

  


  But in the other hand, I'm confused with Lambda memory. I know memory and CPU comes together in Lambda ... the more memory you choose, the more CPU is assigned.

  


  But...

  


  

  1. Why ffmpeg just take about 300/400Mb if it has more to run ?

  


  2. How can I tell ffmpeg to use more memory ?

  


  3. Is there any option to accelerate the process in Lambda ?

  


  


  Btw, In all tests, all ffmpeg are the same, and

  


  cpu-used paramenter)

  


  

  • I added to ffmpeg parameters cpu-used=100, and it does not matter at all if I put cpu-used=5 ... times are the same, so I guess that parameter is useless (i don't know why)

  


  


  threads parameter)

  


  

  • Also I did some tests with "threads" parameters, but it's useless also.

  


  


  I know it's not a good comparison, but same files takes about 5 seconds to be converted in a simple dedicated server (8 vCores and 8GB RAM in OVH Centos VPS).

  


  Btw, Amazon Elastic Transcoder is not an option :
a) it's extremely more expensive
b) it has just his profiles to convert, and my ffmpeg commands are very complex (watermarks, effects, etc ...)