(forw) Re: CL20

...for archival. (also a test how the list handles attachments ;)

-- 
Thought is limitation. Free your mind.

attached mail follows:

First results, for you either all-nighters or early birds,

Using usblib you don't have to worry about device descriptors or syntax of 
setup messages etc, it's pretty straightforward to work with USB from it.

I am able to get thumbs etc from a small C program, check for the camera, and 
get this, I can see when you press the "Agfa Print" button on the camera! :-)

But the biiiig question I have right now .. what the hell is the format for 
the thumbnail data  ??????????

You get 64 bulk packets (it tells you how many it is going to send), of 0x100 
bytes each, for a grand total of 16384 bytes.

If you are using the lowest resolution (512x384 - but this is probably scaled 
by the windows software !!) the resulting JPEG is 38259 bytes.
AND there is no seperate picture, i.e. in low res mode (high quality mode has 
2 transfers) it only downloads ONE thing, which is used as both the thumbnail 
AND as the resulting image.

But it is constructed from 16384 bytes. I don't really know where to start to 
find out what format the received data is in.

The camera would not store it "raw", and it would also not do some custom 
image compression if it can just store as jpeg. So somehow it is probably 
JPEG data, but without the usual headers there would be in a JPEG file, at an 
unknown resolution, which is scaled by the windows software to be a 512x384 
image, 33Kb. 

Which is maybe why they don't really want to release the specs :-) They use 
the excuse of trade secret or something like that, but basically they are 
faking the whole thing :-)

I have attached (sorry) the raw data. The JPEG is probably useless since it is 
scaled and only resembles the original graphically, but in no way in binary.

At least it was received from the camera completely in Linux, using "./a.out" 
:-)

Let me know what you guys think of this format !!!

Dennis

attached mail follows:

Oops.

I looked a bit closer at your log, and you do seem to receive a proper JPEG 
file, headers, name, and everything.

I am not using a compactflash card (you said you were) so that might be why I 
am getting something else.

Can you maybe verify this by trying without compactflash?

I am getting *exactly* what USBSnoopy says I should be getting from my C 
program, but it is not anywhere near a normal JPEG file :-)

Regards,
Dennis