Recherche avancée

Sur d’autres sites (8468)

• Playing With File

  8 septembre 2011, par Multimedia Mike — General

  I played with the ‘file’ utility a long time ago because I wanted to make it recognize a large number of multimedia formats. I had trouble getting my changes to take. But I’m prepared to try again after many years.

  Aiming at the Corpus
  In my local mirror of the MPlayerHQ samples archive, I find 9853 unique files. So I run all of them through the ‘file’ command :

    ’find /path/to/samples -type f -print0 | xargs -0 file —no-pad’
  

  My Ubuntu installation has file v5.04. I also tested against 5.07 and the latest, 5.08. Here is the number of files each version was unable to identify (generically marking as ‘data’) :

  5.04  1521
  5.07  1405
  5.08  1501
  

  That seems like a regression for v5.08 until I dug into the details and saw quite a few items like this, indicating that the MPEG detection could use some work :

  
   mov/mov-demux-infinite-loop.mpg : DOS-executable (
  +mov/mg-‹demux-infinite-loop.mpg : data
  
   image-samples/UNeedQT4.pntg : DOS-executable (
  +imY- samples/UNeedQT4.pntg : data
  

  Workflow
  These are just notes to myself and perhaps anyone else who wants to add new file formats to be identified by the ‘file’ command.

  First, download either the latest release from the FTP or clone from Github. Do the usual unpack, ‘./configure’, ‘make’ routine. To use this newly-built version and its associated magic file :

    ./src/file —magic-file magic/magic.mgc <file>
  

  To add a new format for ID, first, run the foregoing command to ensure that it’s not already identified. Then, check over the files in magic/Magdir and see which one might pertain to what you’re doing (it’s unlikely that your format will merit a new file in this directory). For example, for this round, I modified animation, audio, iff, and riff. Add or modify existing specs based on the copious examples in the directory and by consulting the appropriate man page (‘man 5 magic’).

  Finally, run ‘make’ again which will regenerate the magic file. Invoke the above command again to use the modified magic file.

  Before and After
  On a selection of formats taken from the samples archive (renamed and cut down to a kilobyte because detection typically only relies on the first few bytes), here is the “before” :

  amv :            RIFF (little-endian) data
  armovie :        data
  bbc-dirac :      data
  interplay-mve :  data
  mtv :            data
  nintendo-thp :   data
  nullsoft-video : data
  redcode :        data
  sega-film :      data
  smacker :        data
  trueaudio :      data
  vqa :            IFF data
  wavpack :        data
  wc3-mve :        IFF data
  wtv :            data
  

  And the “after” :

  amv :            RIFF (little-endian) data, AMV
  armovie :        ARMovie
  bbc-dirac :      BBC Dirac Video
  interplay-mve :  Interplay MVE Movie
  mtv :            MTV Multimedia File
  nintendo-thp :   Nintendo THP Multimedia
  nullsoft-video : Nullsoft Video
  redcode :        REDCode Video
  sega-film :      Sega FILM/CPK Multimedia, 320 x 224
  smacker :        RAD Game Tools Smacker Multimedia version 2, 320 x 200, 100 frames
  trueaudio :      True Audio Lossless Audio
  vqa :            IFF data, Westwood Studios VQA Multimedia, 418 video frames, 320 x 200
  wavpack :        WavPack Lossless Audio
  wc3-mve :        IFF data, Wing Commander III Video, PC version
  wtv :            Windows Television DVR Media
  

  After rerunning ‘file’ on the mphq corpus using the modified magic file, only 1329 files remain unidentified (down from 1501).

  Going Forward
  As mentioned, MPEG detection could probably be strengthened. However, a major weakness is QuickTime/MP4. Many files are not detected, probably owing to the many ways that QuickTime files can begin.

• Using OpenMAX (IL ?) for audio/video decoding on Android

  14 septembre 2012, par Christopher Corsi

  Many of the newer hardware platforms running Android, in particular NVIDIA's Tegra 2, support OpenMAX for media acceleration. It's effectively impossible on today's devices to decode 720p video without this support, but the number of demuxers supported on Android are quite slim. The only public API I've been able to find has been through the MediaPlayer class in the Android SDK. There are multiple places in the Android source tree with OpenMAX related tidbits, however.

  On my device (Samsung Galaxy Tab 10.1) I've got access to hardware decoders through a multitude of OpenMAX libs in /system/lib, and it would be great to interface my video application with these. Can anyone point me to information on implementing a decoder powered by OpenMAX ? I've found the documentation from Khronos, but nothing in the way of example code or tutorials. I've already got demuxing and even software decoding taken care of (via libavcodec/libavformat), I'd just like to put hooks in to enable hardware encoding. I'm also assuming here it would be necessary to link directly to the ones available on the device, which makes it pretty lackluster in terms of portability, but it works.

  Alternatively, I'm interested in anything anyone knows about private APIs for accessing the video decoding available on Tegra 2 devices. Especially if there's a vdpau interface like what NVIDIA implements for desktop linux distributions, since there's plenty available for that - but I wasn't able to find shared libraries that indicate that support.

• Revision 74164 : $GLOBALS[’profondeur_url’] = 0 ; ici pour que cela fonctionne en sous ...

  7 juillet 2013, par kent1@… — Log

  $GLOBALSprofondeur_url ? = 0 ; ici pour que cela fonctionne en sous dossiers