Sur d’autres sites (8348)

• Unable to port FFmpeg C library into android

  28 avril 2016, par Navjot Bedi

  What i exactly want to-do : Access the ffmpeg.c file to modify the int main(int argc, char **argv) function to JNI and passing the command of ffmpeg as string.

  I have tried to port ffmpeg C library to android(ARM processor). I followed following different ways to do this.

  1st Try : using official ffmpeg installation documentation. Steps as follows

  a) git clone git ://source.ffmpeg.org/ffmpeg.git ffmpeg

  b) Read the INSTALL file.

  c) Download x264 library and build by using build_x264.sh which build successfully.

      NDK=/home/nav/Work/android/ndk
  
      PREBUILT=$NDK/toolchains/arm-linux-androideabi-4.4.3/prebuilt
  
      PLATFORM=$NDK/platforms/android-8/arch-arm
  
      PREFIX=/home/nav/28ffmpeg/android-ffmpeg                
  
      ./configure --prefix=$PREFIX --enable-static --enable-pic --disable-asm --disable-cli --host=arm-linux --cross-prefix=$PREBUILT/linux-x86/bin/arm-linux-androideabi- --sysroot=$PLATFORM
  
    make
  
    sudo make install
  
    sudo ldconfig

  d) Then i download ffmpeg library from (http://ffmpeg.org/releases/ffmpeg-snapshot.tar.bz2) build it by using build_android.sh

  #!/bin/bash
  
  
  
  NDK=/home/nav/Work/android/ndk
  
  PLATFORM=$NDK/platforms/android-8/arch-arm
  
  PREBUILT=$NDK/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86
  
  PREFIX=/home/nav/28ffmpeg/android-ffmpeg
  
  
  
  function build_one
  
                  {
  
                  ./configure --target-os=linux --prefix=$PREFIX \
  
                  --enable-cross-compile \
  
                  --enable-runtime-cpudetect \
  
                  --disable-asm \
  
                  --arch=arm \
  
                  --cc=$PREBUILT/bin/arm-linux-androideabi-gcc \
  
                  --cross-prefix=$PREBUILT/bin/arm-linux-androideabi- \
  
                  --disable-stripping \
  
                  --nm=$PREBUILT/bin/arm-linux-androideabi-nm \
  
                  --sysroot=$PLATFORM \
  
                  --enable-nonfree \
  
                  --enable-version3 \
  
                  --disable-everything \
  
                  --enable-gpl \
  
                  --disable-doc \
  
                  --enable-avresample \
  
                  --enable-demuxer=rtsp \
  
                  --enable-muxer=rtsp \
  
                  --disable-ffplay \
  
                  --disable-ffserver \
  
                  --enable-ffmpeg \
  
                  --disable-ffprobe \
  
                  --enable-libx264 \
  
                  --enable-encoder=libx264 \
  
                  --enable-decoder=h264 \
  
                  --enable-protocol=rtp \
  
                  --enable-hwaccels \
  
                  --enable-zlib \
  
                  --disable-devices \
  
                  --disable-avdevice \
  
  --extra-cflags="-I/home/android-ffmpeg/include -fPIC -DANDROID -D__thumb__ -mthumb -Wfatal-errors -Wno-deprecated -mfloat-abi=softfp -mfpu=vfpv3-d16 -marm -march=armv7-a" \
  
                  --extra-ldflags="-L/home/android-ffmpeg/lib"
  
                  make -j4 install
  
  
  
  $PREBUILT/bin/arm-linux-androideabi-ar d libavcodec/libavcodec.a inverse.o
  
  $PREBUILT/bin/arm-linux-androideabi-ld -rpath-link=$PLATFORM/usr/lib -L$PLATFORM/usr/lib -L$PREFIX/lib  -soname libffmpeg.so -shared -nostdlib  -z,noexecstack -Bsymbolic --whole-archive --no-undefined -o $PREFIX/libffmpeg.so libavcodec/libavcodec.a libavfilter/libavfilter.a libavresample/libavresample.a libavformat/libavformat.a libavutil/libavutil.a libswscale/libswscale.a -lc -lm -lz -ldl -llog -lx264 --warn-once --dynamic-linker=/system/bin/linker $PREBUILT/lib/gcc/arm-linux-androideabi/4.4.3/libgcc.a
  
                  }
  
  
  
                  build_one

  e) Initially it works perfectly. But after that error comes :

  libavformat/libavformat.a(log2_tab.o):(.rodata+0x0): multiple definition of `ff_log2_tab'
  
  libavcodec/libavcodec.a(log2_tab.o):(.rodata+0x0): first defined here
  
  libavutil/libavutil.a(log2_tab.o):(.rodata+0x0): multiple definition of `ff_log2_tab'
  
  libavcodec/libavcodec.a(log2_tab.o):(.rodata+0x0): first defined here
  
  build_android.sh: 48: build_one: not found

  Result : *libffmpeg.so* not found.

  2nd Try : Then I follow steps in http://dl.dropbox.com/u/22605641/ffmpeg_android/main.html-> Builds

  a) I downloaded Pre-Build libffmpeg.so from above link.

  b) Add libffmpeg.so to libs/armeabi/ .

  c) Make Android.mk

  include $(CLEAR_VARS)
  
  LOCAL_MODULE := ffmpeg
  
  LOCAL_SRC_FILES := libffmpeg.so
  
  include $(PREBUILT_SHARED_LIBRARY)
  
  
  
  LOCAL_PATH := $(call my-dir)
  
  
  
  include $(CLEAR_VARS)
  
  LOCAL_MODULE := main
  
  LOCAL_STATIC_LIBRARIES += ffmpeg
  
  LOCAL_SRC_FILES := ffmpeg-test.c
  
  include $(BUILD_SHARED_LIBRARY)

  d) Then I do all ndk set up and all.Copy ffmpeg.c from library to ffmpeg-test.c by changing its int main function to my JNI functin and include all necessary include files.

  Error :

  Console :

    /home/nav/Work/android/ndk/ndk-build all 
  
  Prebuilt       : libffmpeg.so <= jni/
  
  Install        : libffmpeg.so => libs/armeabi/libffmpeg.so
  
  Compile thumb  : main <= ffmpeg-test.c
  
  jni/ffmpeg-test.c: In function 'print_report':
  
  jni/ffmpeg-test.c:1139:94: warning: incompatible implicit declaration of built-in function 'log2' [enabled by default]
  
  SharedLibrary  : libmain.so
  
  /home/nav/Work/android/ndk/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86/bin/../lib/gcc/arm-linux-androideabi/4.6/../../../../arm-linux-androideabi/bin/ld: ./obj/local/armeabi/objs/main/ffmpeg-test.o: in function check_keyboard_interaction:jni/ffmpeg-test.c:2496: error: undefined reference to 'qp_hist'

  and many other undefined references.....

  Tell me where I am getting wrong. Needed Urgently.....

• FFmpeg Integration in .NET MAUI for Android [closed]

  15 juin 2024, par Billy Vanegas

  I'm facing a challenge with integrating FFmpeg into my .NET MAUI project for Android. While everything works smoothly on Windows with Visual Studio 2022, I'm having a hard time replicating this on the Android platform. Despite exploring various NuGet packages like FFMpegCore, which appear to be wrappers around FFmpeg but don't include FFmpeg itself, I'm still at a loss.

  


  I've tried following the instructions for integrating ffmpeg-kit for Android, but I keep running into issues, resulting in repeated failures and growing confusion. It feels like there is no straightforward way to seamlessly incorporate FFmpeg into a .NET MAUI project that works consistently across both iOS and Android.

  


  The Problem :

  


  I need to convert MP3 files to WAV format using FFmpeg on the Android platform within a .NET MAUI project. I’m using the FFMpegCore library and have downloaded the FFmpeg binaries from the official FFmpeg website.

  


  However, when attempting to use these binaries on an Android emulator, I encounter a permission denied error in the working directory : /data/user/0/com.companyname.projectname/files/ffmpeg

  


  Here’s the code snippet where the issue occurs :

  


  await FFMpegArguments
      .FromFileInput(mp3Path)
      .OutputToFile(wavPath, true, options => options
          .WithAudioCodec("pcm_s16le")
          .WithAudioSamplingRate(44100)
          .WithAudioBitrate(320000)
          )
      .ProcessAsynchronously();
    


  


  I've updated AndroidManifest.xml with permissions, but the issue persists.

  


  I've created a method ConvertMp3ToWav to handle the conversion.
I also have a method ExtractFFmpegBinaries to manage FFmpeg binaries extraction, but it seems the permission issue might be tied to how these binaries are accessed or executed.

  


  AndroidManifest.xml :

  


  &lt;?xml version="1.0" encoding="utf-8"?>&#xA;<manifest>&#xA;    <application></application>&#xA;    &#xA;    &#xA;    &#xA;    &#xA;</manifest>&#xA;

  


  Method ConvertMp3ToWav :

  


  private async Task ConvertMp3ToWav(string mp3Path, string wavPath)
{
    try
    {
        // Check directory and create if not exists
        var directory = Path.GetDirectoryName(wavPath);
        if (!Directory.Exists(directory))
            Directory.CreateDirectory(directory!);

        // Check if WAV file exists
        if (!File.Exists(wavPath))
            Console.WriteLine($"File not found {wavPath}, creating empty file.");
            using var fs = new FileStream(wavPath, FileMode.CreateNew);

        // Check if MP3 file exists
        if (!File.Exists(mp3Path))
            Console.WriteLine($"File not found {mp3Path}");

        // Extract FFmpeg binaries
        string? ffmpegBinaryPath = await ExtractFFmpegBinaries(Platform.AppContext);

        // Configure FFmpeg options
        FFMpegCore.GlobalFFOptions.Configure(new FFOptions { BinaryFolder = Path.GetDirectoryName(ffmpegBinaryPath!)! });

        // Convert MP3 to WAV
        await FFMpegArguments
              .FromFileInput(mp3Path)
              .OutputToFile(wavPath, true, options => options
                  .WithAudioCodec("pcm_s16le")
                  .WithAudioSamplingRate(44100)
                  .WithAudioBitrate(320000)
                  )
              .ProcessAsynchronously();
    }
    catch (Exception ex)
    {
        Console.WriteLine($"An error occurred during the conversion process: {ex.Message}");
        throw;
    }
}


  


  Method ExtractFFmpegBinaries :

  


  private async Task<string> ExtractFFmpegBinaries(Context context)&#xA;{&#xA;    var architectureFolder = "x86"; // Adjust according to device architecture&#xA;    var ffmpegBinaryName = "ffmpeg"; &#xA;    var ffmpegBinaryPath = Path.Combine(context.FilesDir!.AbsolutePath, ffmpegBinaryName);&#xA;    var tempFFMpegFileName = Path.Combine(FileSystem.AppDataDirectory, ffmpegBinaryName);&#xA;&#xA;    if (!File.Exists(ffmpegBinaryPath))&#xA;    {&#xA;        try&#xA;        {&#xA;            var assetPath = $"Libs/{architectureFolder}/{ffmpegBinaryName}";&#xA;            using var assetStream = context.Assets!.Open(assetPath);&#xA;           &#xA;            await using var tempFFMpegFile = File.OpenWrite(tempFFMpegFileName);&#xA;            await assetStream.CopyToAsync(tempFFMpegFile);&#xA;&#xA;            // Adjust permissions for FFmpeg binary&#xA;            Java.Lang.Runtime.GetRuntime()!.Exec($"chmod 755 {tempFFMpegFileName}");&#xA;        }&#xA;        catch (Exception ex)&#xA;        {&#xA;            Console.WriteLine($"An error occurred while extracting FFmpeg binaries: {ex.Message}");&#xA;            throw;&#xA;        }&#xA;    }&#xA;    else&#xA;    {&#xA;        Console.WriteLine($"FFmpeg binaries already extracted to: {ffmpegBinaryPath}");&#xA;    }&#xA;&#xA;    return tempFFMpegFileName!;&#xA;}&#xA;</string>

  


  What I Need :

  


  How to correctly integrate and use FFmpeg in my .NET MAUI project for Android ? Specifically :

  


  

  • How to properly set up and configure FFmpeg binaries for use on Android within a .NET MAUI project.

  


  • How to resolve the permission denied issue when attempting to execute FFmpeg binaries.

  


  


• How To Play Hardware Accelerated Video on A Mac

  28 mai 2013, par Multimedia Mike — General

  I have a friend who was considering purchasing a Mac Mini recently. At the time of this writing, there are 3 desktop models (and 2 more “server” models).

  
  
  

  The cheapest one is a Core i5 2.5 GHz. Then there are 2 Core i7 models : 2.3 GHz and 2.6 GHz. The difference between the latter 2 is US$100. The only appreciable technical difference is the extra 0.3 GHz and the choice came down to those 2.

  He asked me which one would be able to play HD video at full frame rate. I found this query puzzling. But then, I have been “in the biz” for a bit too long. Whether or not a computer or device can play a video well depends on a lot of factors.

  Hardware Support
  First of all, looking at the raw speed of the general-purpose CPU inside of a computer as a gauge of video playback performance is generally misguided in this day and age. In general, we have a video standard (H.264, which I’ll focus on for this post) and many bits of hardware are able to accelerate decoding. So, the question is not whether the CPU can decode the data in real time, but can any other hardware in the device (likely the graphics hardware) handle it ? These machines have Intel HD 4000 graphics and, per my reading of the literature, they are capable of accelerating H.264 video decoding.

  Great, so the hardware supports accelerated decoding. So it’s a done deal, right ? Not quite…

  Operating System Support
  An application can’t do anything pertaining to hardware without permission from the operating system. So the next question is : Does Mac OS X allow an application to access accelerated video decoding hardware if it’s available ? This used to be a contentious matter (notably, Adobe Flash Player was unable to accelerate H.264 playback on Mac in the absence of such an API) but then Apple released an official API detailed in Technical Note TN2267.

  So, does this mean that video is magically accelerated ? Nope, we’re still not there yet…

  Application Support
  It’s great that all of these underlying pieces are in place, but if an individual application chooses to decode the video directly on the CPU, it’s all for naught. An application needs to query the facilities and direct data through the API if it wants to leverage the acceleration. Obviously, at this point it becomes a matter of “which application ?”

  My friend eventually opted to get the pricier of the desktop Mac Mini models and we ran some ad-hoc tests since I was curious how widespread the acceleration support is among Mac multimedia players. Here are some programs I wanted to test, playing 1080p H.264 :

  • Apple QuickTime Player
  • VLC
  • YouTube with Flash Player (any browser)
  • YouTube with Safari/HTML5
  • YouTube with Chrome/HTML5
  • YouTube with Firefox/HTML5
  • Netflix

  I didn’t take exhaustive notes but my impromptu tests revealed QuickTime Player was, far and away, the most performant player, occupying only around 5% of the CPU according to the Mac OS X System Profiler graph (which is likely largely spent on audio decoding).

  VLC consistently required 20-30% CPU, so it’s probably leveraging some acceleration facilities. I think that Flash Player and the various HTML5 elements performed similarly (their multi-process architectures can make such a trivial profiling test difficult).

  The outlier was Netflix running in Firefox via Microsoft’s Silverlight plugin. Of course, the inner workings of Netflix’s technology are opaque to outsiders and we don’t even know if it uses H.264. It may very well use Microsoft’s VC-1 which is not a capability provided by the Mac OS X acceleration API (it doesn’t look like the Intel HD 4000 chip can handle it either). I have never seen any data one way or another about how Netflix encodes video. However, I was able to see that Netflix required an enormous amount of CPU muscle on the Mac platform.

  Conclusion
  The foregoing is a slight simplification of the video playback pipeline. There are some other considerations, most notably how the video is displayed afterwards. To circle back around to the original question : Can the Mac Mini handle full HD video playback ? As my friend found, the meager Mac Mini can do an admirable job at playing full HD video without loading down the CPU.