Recherche avancée

Sur d’autres sites (9474)

• FFMPEG issues for android lollipop. error : only position independent executables (PIE) are supported

  18 mars 2015, par Arslan Ahmad

  I was using the FFmpeg library in my application from the last 2 years and it still working fine on old version. It wont even work on android lollipop.

  I was using these library before.

  String[] libraryAssets = { "ffmpeg", "libavcodec-55.so", "libavcodec.so",
  
              "libavfilter-4.so", "libavfilter.so", "libavformat-55.so",
  
              "libavformat.so", "libavutil-52.so", "libavutil.so",
  
              "libswresample-0.so", "libswresample.so", "libswscale-2.so",
  
              "libswscale.so"
  
  
  
      };

  And I have got the answer from other link that if we use these 3 libraries it will work on lollipop aswell

  "liblicense-jni.so,","libloader-jni.so","libvideokit.so"

  But still It didnot resolve yet.
  Please check this log.

   ***Starting FFMPEG***
  
   ***error: only position independent executables (PIE) are supported.***
  
   ***Ending FFMPEG***

  Any help or any update in library ??

• Dreamcast Track Sizes

  1er mars 2015, par Multimedia Mike — Sega Dreamcast

  I’ve been playing around with Sega Dreamcast discs lately. Not playing the games on the DC discs, of course, just studying their structure. To review, the Sega Dreamcast game console used special optical discs named GD-ROMs, where the GD stands for “gigadisc”. They are capable of holding about 1 gigabyte of data.

  You know what’s weird about these discs ? Each one manages to actually store a gigabyte of data. Each disc has a CD portion and a GD portion. The CD portion occupies the first 45000 sectors and can be read in any standard CD drive. This area is divided between a brief data track and a brief (usually) audio track.

  The GD region starts at sector 45000. Sometimes, it’s just one humongous data track that consumes the entire GD region. More often, however, the data track is split between the first track and the last track in the region and there are 1 or more audio tracks in between. But the weird thing is, the GD region is always full. I made a study of it (click for a larger, interactive graph) :

  
  
  

  Some discs put special data or audio bonuses in the CD region for players to discover. But every disc manages to fill out the GD region. I checked up on a lot of those audio tracks that divide the GD data and they’re legitimate music tracks. So what’s the motivation ? Why would the data track be split in 2 pieces like that ?

  I eventually realized that I probably answered this question in this blog post from 4 years ago. The read speed from the outside of an optical disc is higher than the inside of the same disc. When I inspect the outer data tracks of some of these discs, sure enough, there seem to be timing-sensitive multimedia FMV files living on the outer stretches.

  One day, I’ll write a utility to take apart the split ISO-9660 filesystem offset from a weird sector.

• H.264 adds broken still frames to the end

  14 mai 2015, par Panupat

  I’ve been using ffmpeg to encode raw AVI into H.264 MP4 for about 2 years without problem. However, in my recent project we’re using 60 fps for the first time and face some weird results.

  Here’s an example file. It has 82 frames. FFMPEG would produce the correct result from frame 1 to 82. Here’s a capture at frame 82.

  http://imgur.com/VCIcoVH

  Then, we get this still frame added to the end, from frame 83 to 157.

  

  Am I doing something wrong in my command ? I tried with almost no options.

  ffmpeg -y -i "C:\tmp\uncompressed.avi" -r 60 -vcodec libx264 "C:\tmp\compressed.mp4"

  Tried a couple different options, the problem still occurs.

  ffmpeg -y -i "C:\tmp\uncompressed.avi" -r 60 -vcodec libx264 -keyint_min 12 -vb 4000k -vprofile high -pix_fmt yuv420p -f mp4 "C:\tmp\compressed.mp4"

  Tried with FFmpeg Win64 Static and Shared build by Kyle Schwarz.

  Appreciate any help, thank you !