While rlvm plays music and sounds, rlvm still does not support voices. nwatowav does not support the voice format used on the Planetarian CD edition. If anyone knows anything about the voice file format used in Planetarian, please contact me at .

This version is not backwards compatible with rlvm 0.1’s save files. I’ve added versioning information to the save files so hopefully future versions of rlvm will be compatible with the save game files produced by version 0.2. No user action is required to upgrade; save files are written in a different location and are now compressed with zlib.

rlvm compiles on Ubuntu Hardy Heron (and most likely any modern Linux distribution), Mac OSX 10.4 Tiger, and Mac OSX 10.5 Leopard.

Download

Ubuntu (Hardy) package (version 0.02)
Mac OSX Application (Universal) (version 0.02)
Source code (0.02)

As this is the first publicly released version, there are bound to be
bugs. The machine is missing major features. (See KNOWN ISSUES in
README.TXT.) Right now, only Planetarian is playable through the end.

rlvm compiles on Ubuntu Gutsy Gibbon (and most likely any modern Linux
distribution), Mac OSX 10.4 Tiger, and Mac OSX 10.5 Leopard.

Download

Ubuntu (Gutsy) package (version 0.01)
Mac OSX Application (Universal) (version 0.01)
Source code (0.01)

VitaminSEE v0.7.1.2 (Universal Binary)
VitaminSEE v0.7.1.2 (for 10.3.x)
VitaminSEE v0.7.1.2 Source

But right now, I want to talk about the conditions under which VitaminSEE consumes ridiculous amounts of memory (which won’t be fixed in this release). You may have noticed that on folders with a large number of image files, VitaminSEE will consume really large amounts of memory.

For example, I have an “Unsorted” folder with 1,666 images in it. VitaminSEE starts from a resting memory position of 8 megabytes. After giving VitaminSEE a few moments to load all the thumbnails, Activity Monitor tells me that VitaminSEE is using 25 megs of real memory. Not optimal, but more then acceptable. After scrolling from the first file in the folder to the last file, VitaminSEE’s memory consumption jumps all the way up to 122 megabytes. Note that it already had the thumbnails in memory before the jump.

From what I can make out from MallocDebug, it appears that the implementation of either NSBrowser or NSMatrix in Cocoa render their contents into an NSImage offscreen, and then copy that cached version onto the screen.

Solving this will require me to do one of the two things:

• Find a magic way to tell whatever class is at fault to not cache things this way (Quick, unlikely)
• Look at other controls and see if I can coerce them to do what I want to do.
• Write my own control that doesn’t do things this way. (Hard, would take a long time)

This is a beta build; the final version will be released in two days if no serious problems are found with it. Please leave a comment if you find a defect (that isn’t present in previous builds). Please do NOT submit this build to the release announcement sites.

VitaminSEE 0.7.1.2 Beta
VitaminSEE 0.7.1.2 Beta (for 10.3.9)
VitaminSEE 0.7.1.2 Beta source code

• When I upgraded to IconFamily 0.9.1, I forgot to port my changes that would restore a file’s modification date. Fix this so building a thumbnail of a file does set the modification date.
• Back/Forward will now focus on the file/folder you were on previously, instead of always starting at the beginning of the list.

VitaminSEE v0.7.1.1 (Universal Binary)
VitaminSEE v0.7.1.1 (for 10.3.x)
VitaminSEE v0.7.1.1 Source

What’s new:

• Upgrade IconFamily to 0.9.1
• Make rename sheet handle extensions like the Save… dialogs do
• Add a fullscreen mode
• Don’t display document types that OSX treats as images, such as postscript
  files, and PDFs.

Download

VitaminSEE v0.7.1 (Universal Binary)
VitaminSEE v0.7.1 (for 10.3.x)
VitaminSEE v0.7.1 Source

GQView looks like the simplest algorithm: It subdivides the image into a 32 x 32 grid, and then takes the average pixel color of each block. The difference is simply the sum of the difference between each block in the two images, normalized to a value between 0 and 1. The similar.c code in GQView is really that simple. I’m surprised that I got such good results back when I used it. Unless I find something better, I’m guessing that this is going to be the base algorithm, after I figure out how GQView scales with it to deal with hundreds (thousands?) of files.

And after 0.7.2 is released, of course.

(Beta links removed, since 0.7.1 final is out.)

• Fullscreen mode
• Better extension handling in the rename dialog
• Crash reporter, update checker and feedback reporter

(Beta links removed, since 0.7.1 final is out.)

The Japanese translation for this release is not yet complete.