This wonderful free software is available from
http://www.yawcam.com/download.php

The only features I miss are:
- support for more than one camera, using a single instance of the program;
- full support for Logitech’s latest driver version, which does NOT allow the camera’s full native resolution (2 MP) to be used by any third party app I know of.

I am making this post so that I don’t forget the file format for my automatic snapshots.
Although the program is fully documented, it takes a few seconds to find and understand the variables for file names.

Initially, my filename format for time lapsed captures was:

sphere_{num6}_{dateY}{dateM}{dateD}{tstampH}{tstampM}{tstampS}.png

but the {num6} variable – which corresponds to an auto increasing 6 digits number – only works if the files’ names are exactly the same, snap after snap, which they are not when using date/time with resolution down to the second.

So now I use:

sphere_{dateY}{dateM}{dateD}{tstampH}{tstampM}{tstampS}.png

and this gives names like

sphere_20110130_124728.png

“sphere” is just the prefix I picked for making it clear that the snapshots were taken with a Logitech Quickcam Sphere camera.

To access these settings do settings > edit settings

And here is one shot from my current location:

After hundreds of photos with exactly the same “bad pixels” problem, at the exact same locations – (218, 392) and (2218, 1052) –, I am 100% sure that I wil return the product to the vendor (Pixmania). 

You can download one of those photos (the most uninteresting of them all), but keep in mind that it has a resolution of 2216×1052 [2.5 MB].

Picture 1 (of 4) – 320 pixels version of SANY009.JPG: a 2816×2112 (6 MPixels) original, taken with a Sanyo Xacti 6Ex, with bad pixels.

Picture 2 (of 4) – This is picture #2, with small red arrows pointing to the bad pixels, which are only easily visible on the original 2816×2112 (6 MPixels) file, or in the full size snaps below.

Picture 3 (of 4) – A full size cut of the region with the bad pixel at coordinates 218, 392.

 Picture 4 (of 4) – A full size cut of the region with the bad pixel at coordinates 2218, 1052.