Sur d’autres sites (3445)

• Feeding a series of images to ffmpeg as each image is created [closed]

  5 février 2013, par Mark Schneider

  I'm trying to use ffmpeg to build a 1280x720 slide-show from a sequence of pictures and videos, but I have concerns about potential disk I/O bottleneck.

  I expect a typical slide-show to have about 50 pictures and 2-3 videos (10-15 seconds each at 30 fps). I would like to show each picture for 3-4 seconds (possibly with a
  Ken Burns effect) with a smooth 2 second crossfade between each set of pictures (or for pictures adjacent to videos - between the picture and the first/last frame of the video).

  Given about 50 pictures, the crossfades alone would amount to about 3,000 images (50 transitions x 2 secs/transition x 30 fps). And I suppose if I implement a Ken Burns effect during each picture's 3-4 second showing, I'd have to provide ffmpeg with individual images for each of those frames. (I'm writing a script in Ruby that will pull a list of images from a database and in turn call ImageMagick to create the individual images for each frame. As I understand it, the RMagick library interfaces with ImageMagick such that the output images come back as in-memory objects without needing to write to disk. FWIW, I'm developing in Windows 8 and will deploy to Heroku.)

  All of the slideshow examples I've found online feed ffmpeg a set of images which have already been created. However, in an effort to avoid waiting on considerable disk I/O, I'd like to feed each image to ffmpeg as the image is created rather than create them all in advance.

  Is there a way to send each image file to ffmpeg on the fly as the file is created in memory ?

• Trying to use FFMPEG for android. Compiling but still not working

  15 avril 2014, par Austin Mueller

  So to start off... Im trying to use ffmpeg to compile an array of images into a video on Android.

  I have followed a variety of tutorials online and have gotten as far as being able to compile the lib for Android and still have to project run.
  The repo im now using can be found here : https://github.com/Batterii/android-ffmpeg-x264

  I made a couple tweaks to the setttings.sh just to correct ndk location. Besides that, I followed the instructions and it seemed to work flawlessly.

  After that, I converted the "Project" project into an Android stdio library module.
  

  I am not getting any compile errors, nor am I getting any runtime errors, or any other errors that I can detect... Nothing on logcat... But I am definitely not getting any video called out.mp4.
  In an onCreate of a particular activity, I am running this code :

  Videokit vk = new Videokit();
  
  vk.run(new String[]{"ffmpeg", "-r", "1/5", "-i", "%d.jpg", "-c:v", "libx264", "-r", "30", "-pix_fmt", "yuv420p", project.getProjectDirectory() + "/out.mp4"});

  This command is taken from the command line example found here :
  https://trac.ffmpeg.org/wiki/Create%20a%20video%20slideshow%20from%20images

  Thank you in advance for anyone taking the time to look through this post... I am pretty baffled at this point, as there are no errors I can find and no video...
  Thanks

  ======================================================================

  Update

  Turns out it is not actually compiling correctly... but i have found a few things.
  here is the make file from the Eclipse version of the project

  LOCAL_PATH := $(call my-dir)
  
  
  
  include $(CLEAR_VARS)
  
  LOCAL_MODULE  := videokit
  
  # These need to be in the right order
  
  FFMPEG_LIBS := $(addprefix ffmpeg/, \
  
   libavdevice/libavdevice.a \
  
   libavformat/libavformat.a \
  
   libavfilter/libavfilter.a \
  
   libavcodec/libavcodec.a \
  
   libswscale/libswscale.a \
  
   libavutil/libavutil.a \
  
   libswresample/libswresample.a \
  
   libpostproc/libpostproc.a )
  
  # ffmpeg uses its own deprecated functions liberally, so turn off that annoying noise
  
  LOCAL_CFLAGS += -g -Iffmpeg -Ivideokit -Wno-deprecated-declarations 
  
  LOCAL_LDLIBS += -llog -lz $(FFMPEG_LIBS) x264/libx264.a
  
  LOCAL_SRC_FILES :=  ffmpeg/cmdutils.c ffmpeg/ffmpeg.c videokit/uk_co_halfninja_videokit_Videokit.c
  
  include $(BUILD_SHARED_LIBRARY)

  and here is the make file that gradle is auto-generating for me... thanks to Android Studio...

  LOCAL_PATH := $(call my-dir)
  
  include $(CLEAR_VARS)
  
  
  
  LOCAL_MODULE := videokit
  
  LOCAL_CFLAGS := -g -Isrc/main/jni/ffmpeg -Isrc/main/jni/videokit -Wno-deprecated-declarations
  
  LOCAL_LDLIBS := \
  
      -lffmpeg/libavformat/libavformat.a \
  
      -lffmpeg/libavcodec/libavcodec.a \
  
      -lffmpeg/libswresample/libswresample.a \
  
      -lffmpeg/libavfilter/libavfilter.a \
  
      -lffmpeg/libpostproc/libpostproc.a \
  
      -lffmpeg/libavdevice/libavdevice.a \
  
      -lx264/libx264.a \
  
      -lffmpeg/libavutil/libavutil.a \
  
      -llog \
  
      -lz \
  
      -lffmpeg/libswscale/libswscale.a \
  
  
  
  LOCAL_SRC_FILES := \
  
      Project/Module/src/main/jni/ffmpeg/cmdutils.c \
  
      Project/Module/src/main/jni/ffmpeg/ffmpeg.c \
  
      Project/Module/src/main/jni/videokit/com_t10_project_util_FfmpegHelper.c \
  
  
  
  LOCAL_C_INCLUDES += Project/Module/src/main/jni/ffmpeg/cmdutils.c
  
  LOCAL_C_INCLUDES += Project/Module/src/main/jni/ffmpeg/ffmpeg.c
  
  LOCAL_C_INCLUDES += Project/Module/src/main/jni/videokit/com_t10_project_util_FfmpegHelper.c
  
  LOCAL_C_INCLUDES += Project/Module/src/arm/jni
  
  LOCAL_C_INCLUDES += Project/Module/src/debug/jni
  
  LOCAL_C_INCLUDES += Project/Module/src/armDebug/jni
  
  
  
  include $(BUILD_SHARED_LIBRARY)

  And finally, here is my build.gradle

  apply plugin: 'android'
  
  
  
  android {
  
      compileSdkVersion 19
  
      buildToolsVersion '19.0.1'
  
  
  
      defaultConfig {
  
          minSdkVersion 14
  
          targetSdkVersion 19
  
          versionCode 1
  
          versionName "1.0"
  
  
  
          ndk {
  
              moduleName "videokit"
  
              stl "stlport_shared"
  
              ldLibs "log", "z",
  
                      "ffmpeg/libavdevice/libavdevice.a",
  
                      "ffmpeg/libavformat/libavformat.a",
  
                      "ffmpeg/libavfilter/libavfilter.a",
  
                      "ffmpeg/libavcodec/libavcodec.a",
  
                      "ffmpeg/libswscale/libswscale.a",
  
                      "ffmpeg/libavutil/libavutil.a",
  
                      "ffmpeg/libswresample/libswresample.a",
  
  
  
  
  
                "ffmpeg/libpostproc/libpostproc.a",
  
                  "x264/libx264.a"
  
              cFlags "-g -Isrc/main/jni/ffmpeg -Isrc/main/jni/videokit -Wno-deprecated-declarations"
  
  
  
          }
  
      }
  
  
  
      sourceSets.main {
  
          jniLibs.srcDir 'src/main/libs'
  
          jni.srcDirs = ['src/main/jni/ffmpeg/cmdutils.c',
  
                         'src/main/jni/ffmpeg/ffmpeg.c',
  
                         'src/main/jni/videokit/com_t10_project_util_FfmpegHelper.c']
  
      }
  
  
  
      productFlavors {
  
          x86 {
  
              versionCode Integer.parseInt("6" + defaultConfig.versionCode)
  
              ndk {
  
                  abiFilter "x86"
  
              }
  
          }
  
          mips {
  
              versionCode Integer.parseInt("4" + defaultConfig.versionCode)
  
              ndk {
  
                  abiFilter "mips"
  
              }
  
          }
  
          armv7 {
  
              versionCode Integer.parseInt("2" + defaultConfig.versionCode)
  
              ndk {
  
                  abiFilter "armeabi-v7a"
  
              }
  
          }
  
          arm {
  
              versionCode Integer.parseInt("1" + defaultConfig.versionCode)
  
              ndk {
  
                  abiFilter "armeabi"
  
              }
  
          }
  
          fat
  
      }
  
  
  
      buildTypes {
  
          release {
  
              runProguard false
  
              proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.txt'
  
          }
  
      }
  
  }
  
  
  
  dependencies {
  
      compile 'com.android.support:support-v4:19.0.0'
  
      compile fileTree(dir: 'libs', include: ['*.jar', '*.aar'])
  
  }

  As you can see, my build.gradle generates something that is pretty close to the original... but not the same. When i try to run/compile it, gradle spits this out

  Executing tasks: [:Project:assembleArmDebug]
  
  
  
  :Project:compileArmDebugNdkcc1: warning: Project/Module/src/main/jni/ffmpeg/cmdutils.c: not a directory [enabled by default]
  
  cc1: warning: Project/Module/src/main/jni/ffmpeg/ffmpeg.c: not a directory [enabled by default]
  
  cc1: warning: Project/Module/src/main/jni/videokit/com_t10_project_util_FfmpegHelper.c: not a directory [enabled by default]
  
  In file included from Project/Module/src/main/jni/ffmpeg/cmdutils.c:32:0:
  
  Project/Module/src/main/jni/ffmpeg/libavformat/avformat.h:82:32: fatal error: libavcodec/avcodec.h: No such file or directory
  
  compilation terminated.
  
  make: *** [Project/Module/build/ndk/arm/debug/obj/local/armeabi/objs/videokit/Project/Module/src/main/jni/ffmpeg/cmdutils.o] Error 1
  
   FAILED
  
  
  
  FAILURE: Build failed with an exception.
  
  
  
  * What went wrong:
  
  Execution failed for task ':Project:compileArmDebugNdk'.
  
  > com.android.ide.common.internal.LoggedErrorException: Failed to run command:
  
      android-ndk-r9d/ndk-build NDK_PROJECT_PATH=null APP_BUILD_SCRIPT=Project/Module/build/ndk/arm/debug/Android.mk APP_PLATFORM=android-19 NDK_OUT=Project/Module/build/ndk/arm/debug/obj NDK_LIBS_OUT=Project/Module/build/ndk/arm/debug/lib APP_STL=stlport_shared APP_ABI=armeabi
  
    Error Code:
  
      2
  
    Output:
  
      cc1: warning: Project/Module/src/main/jni/ffmpeg/cmdutils.c: not a directory [enabled by default]
  
      cc1: warning: Project/Module/src/main/jni/ffmpeg/ffmpeg.c: not a directory [enabled by default]
  
      cc1: warning: Project/Module/src/main/jni/videokit/com_t10_project_util_FfmpegHelper.c: not a directory [enabled by default]
  
      In file included from Project/Module/src/main/jni/ffmpeg/cmdutils.c:32:0:
  
      Project/Module/src/main/jni/ffmpeg/libavformat/avformat.h:82:32: fatal error: libavcodec/avcodec.h: No such file or directory
  
      compilation terminated.
  
      make: *** [Project/Module/build/ndk/arm/debug/obj/local/armeabi/objs/videokit/Project/Module/src/main/jni/ffmpeg/cmdutils.o] Error 1
  
  
  
  
  
  * Try:
  
  Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
  
  
  
  BUILD FAILED
  
  
  
  Total time: 8.184 secs

  I've been messing around with it for a couple hours now and pretty much every time, i get gradle yelling at me about the fact that it can't find some file. I'm beginning to think that maybe it is because my LOCAL_LDLIBS aren't in the same order as the original...? Im not entirely sure... Does anyone else have any ideas...?

• Fun With Tablets And Amazon’s App Store

  24 décembre 2011, par Multimedia Mike — General, amazon, android, app store, cyanogenmod, ios, smurfs, tablet

  I bought an Android tablet a few months ago. It is less expensive than the best tablets but no where near the bottom end of the market. I think it’s pretty good. However, one downside is that it’s not “certified” to use Google’s official marketplace. That would seem to be somewhat limiting, however…

  Enter Amazon’s Android App Store
  Amazon got into the business of selling Android Apps some time ago. I started experimenting with this on a Nexus One phone that Google gave me. When I installed the App Store on the Android tablet and logged in, I was pleasantly surprised to see all of my Amazon apps ready for downloading onto the tablet.

  So I have an App Store for use with this Android tablet.

  Anyway, the reason I bring this up is because I managed to screw up this tablet in an unusual and humorous manner. You might be wondering if an app downloaded from the Amazon App Store requires the App Store to be present in order to run. The answer is : Oh yeah ! It works like this :

  
  
  

  This means that if — perhaps out of curiosity, for example — you login to the Amazon App Store, download an app, install it, and then subsequently log out of the App Store or uninstall it altogether, the downloaded app will decline to run until you log back into the store.

  Here’s the thing– I wanted to provide a minimal level of security for my Android tablet. At the very least, I wished to lock the Amazon App Store itself since Amazon is famously (and, let’s face it, understandably) reluctant to deliberately add any friction to their shopping processes. I.e., without any external protection app, the App Store app would allow anyone to purchase any app using my tablet.

  So I purchased App Protector Pro from the Amazon App Store and it worked quite well. By default, it also password protects against modifying any system settings as well as installing new apps.

  So, here’s where I screwed up : App Protector Pro was doing its faithful duty and I uninstalled the Amazon App Store as an experiment. Suddenly, no apps obtained from the App Store would work unless I reinstalled the App Store. Okay, fair enough, except for one thing– App Protector Pro wouldn’t run without the App Store. Well, it did, it started to, tried to, but then exited. So I couldn’t re-install the App Store :

  
  
  Oops
  

  I eventually learned how to perform a factory reset of the unit which solved the problem. And, as indicated earlier, all of my apps were available for me to re-download.

  Modding, Cyanogen-style
  Open source aficionados will likely point out that there are alternate firmware options which allow me to take control of my Android tablet in a free and open manner. Among these options is CyanogenMod. After I got stuck in the situation described above, I thought I would have to resort to such an option.

  On the plus side, researching alternative firmware options is what taught me to boot the device into a recovery mode and ultimately restore to a factory default setting. But if you’ll allow me to indulge in a mini-rant regarding accessibility of open source software : I was more than a little frustrated in trying to understand what CyanogenMod could possibly offer me. Their homepage says it’s “an aftermarket firmware”. I’m not entirely sure what that means or how it can benefit me. Fortunately, they have a full feature list linked from the front page. They are, in order : Lockscreen gestures, phone goggles, OpenVPN, incognito mode, themes support, and DSP equalizer. I can’t say that any of those really add any value for me. I’d love to know if CyanogenMod supports Google Android Market and various other Google apps (such as maps and GMail). That’s a question that I can’t seem to find the answer to.

  The themes feature opens another old wound for me. Back around 1999 when I was first getting into Linux in a serious way, I remember that themes were a big theme at the Linux User Groups I would attend. I also remember lots are online articles at the time that emphasized how highly customizable the Linux desktop was in comparison to Windows 9x. I was bothered for 2 reasons : First, I thought there were more pressing problems that needed to be addressed in Linux ; and second, none of these customization options seemed particularly straightforward ; many apparently required hours of compiling and tinkering.

  Small digression. Anyway, back to CyanogenMod, I was glad to see that they prominently display a button in order to “View Video Tour”. Ah, internet video has us so spoiled these days. I was eager to see this aftermarket firmware in action to see what it could do for me. However, the link leads to… a forum post ? The thread seems to discuss how it would be a cool idea if the community could put together a video tour. At this point, the investigation just seems bizarre. It feels like a bunch of kids doing their best to do things the grown-up way.

  Okay, sorry, rant over. I try to stay positive these days. I’m sure the CyanogenMod folks are doing great, fun, and interesting work on their project. The problems they choose to solve might lack mainstream appeal, however.

  Free iPad
  Ultimately, I recently unloaded the little Android tablet because, well… when a free iPad comes your way, lower spec tablets feel a little silly to keep around. Yeah, it’s great to play around with. Though here’s one unsettling thing I noticed about Apple’s App Store. While browsing for worthwhile games to indulge in, I noticed that they had a section for “Top Grossing Games”. This was a separate list from the “Top Apps” charts. I found the list weird for 2 reasons : 1) Why do I care which games are raking in the most cash ? How does this communicate value to me, personally ? Seriously, why would I base a purchasing decision around which vendor has earned the most money ?

  Anyway, let’s move on to reason #2 this was scary : Most of the games in this list had a price of FREE. One of them was that Capcom Smurfs game that stirred up controversy some months ago because of kids making unsupervised in-app purchases of virtual smurfberries. I tend to think that a top-grossing, free to play game is probably one that heavily encourages in-app purchases. Strange how this emerging trend actually encourages me to seek out games from the “top paid” list vs. “top free”.