Recherche avancée

Sur d’autres sites (4304)

• Building ffmpeg-kit for Android fails with arm-linux-androideabi-strip not found

  8 juillet 2022, par dnz

  I am trying to build ffmpeg-kit for Android with "android.sh". The build.log ends with :

  


  ^~~~~~~~~~~~~~~~~~~~~&#xA;In file included from :370:&#xA;<command line="line">:13:9: warning: &#x27;__ANDROID_API__&#x27; macro redefined [-Wmacro-redefined]&#xA;#define __ANDROID_API__ 24&#xA;        ^&#xA;:363:9: note: previous definition is here&#xA;#define __ANDROID_API__ __ANDROID_MIN_SDK_VERSION__&#xA;        ^&#xA;6 warnings generated.&#xA;GEN     libavdevice/libavdevice.pc&#xA;1 warning generated.&#xA;GEN     libavfilter/libavfilter.pc&#xA;1 warning generated.&#xA;GEN     libavformat/libavformat.pc&#xA;1 warning generated.&#xA;GEN     libavcodec/libavcodec.pc&#xA;1 warning generated.&#xA;GEN     libswresample/libswresample.pc&#xA;1 warning generated.&#xA;GEN     libswscale/libswscale.pc&#xA;1 warning generated.&#xA;GEN     libavutil/libavutil.pc&#xA;</command>

  


  ...

  


  INSTALL doc/examples/scaling_video.c
INSTALL doc/examples/README
INSTALL doc/examples/Makefile
INSTALL libavdevice/libavdevice.so
STRIP   install-libavdevice-shared
/bin/sh: 1: arm-linux-androideabi-strip: not found
make: *** [ffbuild/library.mak:104: install-libavdevice-shared] Error 127


  


  I have no idea what goes wrong. I have cloned the github repository again, with the same result.

  


• Merge commit ’faa3f17a76333b672ce4a40cf80f678ab68bdbae’

  24 août 2015, par Hendrik Leppkes

  Merge commit ’faa3f17a76333b672ce4a40cf80f678ab68bdbae’
  * commit ’faa3f17a76333b672ce4a40cf80f678ab68bdbae’ :
  
    fate : test only demuxing in asf-repldata
  Merged-by : Hendrik Leppkes <h.leppkes@gmail.com>
  

  • [DH] tests/fate/microsoft.mak
  • [DH] tests/ref/fate/asf-repldata

• Solving The XVD Puzzle

  15 avril 2012, par Multimedia Mike — General, multimedi archaeology, silicon valley, vg2, xvd, zygo

  I downloaded a multimedia file a long time ago (at least, I strongly suspected it was a multimedia file which is why I downloaded it). It went by the name of ‘lamborghini_850kbps.vg2′. I have had it in my collection for at least 7 years. I couldn’t remember where I found it. I downloaded it before it occurred to me to take notes about this sort of stuff.

  I found myself staring at the file again today and Googled the filename. This led me to a few Japanese sites which also contained working URLs for a few more .vg2 samples. Some other clues led me to a Russian language forum where someone had linked to a site that had Win32 codec modules that could process the files. The site was defunct but the Internet Archive Wayback Machine kept a copy for me, as well as copies of several more .vg2 samples from a defunct Japanese site previously involved with this codec.

  Sometimes this internet technology works really well. But I digress.

  Anyway, through all this, I finally found a clue : XVD. and wouldn’t you know, there is already a basic page on the MultimediaWiki describing the technology. In fact, while VG2 is a custom container, the MultimediaWiki states that the video component has a FourCC of VGMV, and there is already a file named VGMV.avi in the root V-codecs/ samples directory, something I vow to correct (that’s a big pet peeve of mine– putting samples in the root V-codecs/ or A-codecs/ directories).

  XVD… XVD… XVD… why does that sound so familiar ? Oh, of course ; there is a company named XVD and they have an office in the Bay Area which I have passed on numerous occasions, like this morning :

  
  <

  Someone originally connected with the multimedia technology in question operates a website which contains an unofficial history of the XVD tech. At first, I was wondering if the technology was completely defunct (and should therefore be open sourced). But if XVD’s solutions page (dated 2010) is to be believed, the technology is still in service, and purported to be better than H.264 and VC-1 : “The current generation of XVD video compression technology provides better video quality at any given data rate than standards-based codecs (H.264 or VC-1) with four times lower encoding complexity (when compared with H.264 Main Profile).”

  If they say so. For my part, I’m just happy that I have finally figured out what this lamborghini_850kbps.vg2 is so that I can properly catalog it on the samples site, which I have now done, along with other samples and various codecs modules.

  This episode reminds me that there’s a branch office of Zygo Corporation close to my home (though the headquarters are far, far away). The companies you see in Silicon Valley. Anyway, long-time open source multimedia hackers will no doubt recognize Zygo from the ZyGo FourCC & video codec transported in QuickTime files that was almost decode-able using an H.263 decoder.

  
  
  

  I may never learn what Zygo’s core competency actually is, but I will always remember their multimedia tech every time I run past their office.