Recherche avancée

Sur d’autres sites (11164)

• Brute Force Dimensional Analysis

  15 juillet 2010, par Multimedia Mike — Game Hacking, Python

  I was poking at the data files of a really bad (is there any other kind ?) interactive movie video game known simply by one letter : D. The Sega Saturn version of the game is comprised primarily of Sega FILM/CPK files, about which I wrote the book. The second most prolific file type bears the extension ’.dg2’. Cursory examination of sample files revealed an apparently headerless format. Many of the video files are 288x144 in resolution. Multiplying that width by that height and then doubling it (as in, 2 bytes/pixel) yields 82944, which happens to be the size of a number of these DG2 files. Now, if only I had a tool that could take a suspected raw RGB file and convert it to a more standard image format.

  Here’s the FFmpeg conversion recipe I used :

   ffmpeg -f rawvideo -pix_fmt rgb555 -s 288x144 -i raw_file -y output.png
  

  So that covers the files that are suspected to be 288x144 in dimension. But what about other file sizes ? My brute force approach was to try all possible dimensions that would yield a particular file size. The Python code for performing this operation is listed at the end of this post.

  It’s interesting to view the progression as the script compresses to different sizes :

  
  
  

  That ’D’ is supposed to be red. So right away, we see that rgb555(le) is not the correct input format. Annoyingly, FFmpeg cannot handle rgb555be as a raw input format. But this little project worked well enough as a proof of concept.

  If you want to toy around with these files (and I know you do), I have uploaded a selection at : http://multimedia.cx/dg2/.

  Here is my quick Python script for converting one of these files to every acceptable resolution.

  work-out-resolution.py :
  

  PLAIN TEXT

  PYTHON :

  1. # !/usr/bin/python
  2.  
  3. import commands
  4. import math
  5. import os
  6. import sys
  7.  
  8. FFMPEG = "/path/to/ffmpeg"
  9.  
  10. def convert_file(width, height, filename) :
  11.  outfile = "%s-%dx%d.png" % (filename, width, height)
  12.  command = "%s -f rawvideo -pix_fmt rgb555 -s %dx%d -i %s -y %s" % (FFMPEG, width, height, filename, outfile)
  13.  commands.getstatusoutput(command)
  14.  
  15. if len(sys.argv) <2 :
  16.  print "USAGE : work-out-resolution.py <file>"
  17.  sys.exit(1)
  18.  
  19. filename = sys.argv[1]
  20. if not os.path.exists(filename) :
  21.  print filename + " does not exist"
  22.  sys.exit(1)
  23.  
  24. filesize = os.path.getsize(filename) / 2
  25.  
  26. limit = int(math.sqrt(filesize)) + 1
  27. for i in xrange(1, limit) :
  28.  if filesize % i == 0 and filesize & 1 == 0 :
  29.   convert_file(i, filesize / i, filename)
  30.   convert_file(filesize / i, i, filename)

• New Sanyo cameras have editing in mind

  13 octobre 2009

  Sanyo has announced some ’A’ revisions to their existing FH1 and HD2000 cameras, which add a new "iFrame" mode. It appears this is an i-frame only h264 mode, at a reduced 960x540 resolution. It’s a very interesting idea - if other manufacturers adopted it as an optional setting, and if NLE manufacturers supported it, it could turn H264 into an edit-friendly format. Right now, editing H264 is hamstrung by the extremely long GOPs and complex interframe relationships. Going to i-frame only makes it essentially a more advanced version of a codec like DV or DVCProHD.

  Interestingly, the bottom of the press release mentions that

  "The iFrame logo and the iFrame symbol are trademarks of Apple Inc."

  That’s news to me. One wonders if Sanyo jumped the gun on a release, or if this is just a format that Apple uses internally in tools like iMovie, which Sanyo has co-opted. I’ll certainly be keeping my eyes open for an Apple announcement about "iFrame."

• ARM compiler update

  15 janvier 2010, par Mans — ARM, Compilers

  Since my last shootout, all the tested vendors have updated their compilers. Here is a quick update on each of them.

  Both the 4.3 and 4.4 branches of FSF GCC have had bugfix releases, bringing them to 4.3.4 and 4.4.2, respectively. Neither update contains anything particularly noteworthy.

  The CodeSourcery 2009q3 release sees an update to a GCC 4.4 base, a significant change from the 4.3 base used in 2009q1. The update is a mixed blessing. In fact, it is mostly a curse and hardly a blessing at all. On the bright side, the floating-point speed regressions in 2009q1 are gone, 2009q3 being a few per cent faster even than 2007q3. Unfortunately, this improvement is completely overshadowed by a major speed regression on integer code, a whopping 24% in one case. This ties in with the slowdown previously observed with FSF GCC 4.4 compared to 4.3.

  ARM RVCT 4.0 is now at Build 697. This update fixes some bugs and introduces others. Notably, it no longer builds FFmpeg correctly. The issue has been reported to ARM.

  Texas Instruments, finally, have made a formal release, v4.6.1, of their TMS470 compiler incorporating various fixes allowing it to build a moderately patched FFmpeg. The performance remains somewhere between GCC and RVCT on average.

  In light of the above, my recommendations remain unchanged :

  • For a free compiler, choose CodeSourcery 2009q1. It beats GCC 4.3.4 by 5-10% in most cases.
  • GNU purists are best served by GCC 4.3.4, which is up to 20% faster than 4.4.2 and rarely slower.
  • When price is not a concern, ARM RCVT is a good option, outperforming GCC by up to a factor 2.
  • In all cases, disable any auto-vectorisation features.

  Regardless of which compiler is chosen, I cannot overstress the importance of testing. All compilers are crawling with bugs, and even the most innocent-looking code change can trigger one of them. When using a compiler other than GCC, extra caution is advised considering a lot of code is developed using only GCC and may thus fall prey to bugs unique to said other compiler.