Data for Phil

[c++]

Hi Phil,

regarding https://exiftool.org/sample_images.html
You'll find several you might want in the enclosed.

For each of 'em I took one of your tiny JPEGs from the existing archive and essentially did:
exiftool -all= -tagsFromFile my_original.jpg -overwrite_original tiny_target.jpg

All of these are production models, no weird beta cameras.

[StarGeek]

Unfortunately, the command you used does not result in a new file with the original data. Tag locations can be changed unless explicitly corrected for (see FAQ #9).  And even if you do use -All:All, exiftool will not copy any obscure tags that it doesn't know about.

And even after that, exiftool can change the structure and order of the metadata when writing (see FAQ #13).

When creating the test images he's almost certainly using a custom script to make an exact copy.

The best solution would be to email a sample file or DM him with a link. 

[Phil Harvey]

Yes, I'll need original images for the collection.  I have a special script that swaps the image and preserves the original metadata structure for the samples page.

- Phil

[c++]

Yes, I'll need original images for the collection.  I have a special script that swaps the image and preserves the original metadata structure for the samples page.

Too bad, thought I could help you with this. Intersted in sharing said script? If not it's a no go the image data these come from does not leave here :-) Maybe I have a second set of images I'm willing to share. If so I'll send them by wetransfer one day.

[Phil Harvey]

Here is a post where I give the script that I use.

You need to run it in a folder that contains t/images/Writer.jpg because it uses this as the source image.

- Phil

[c++]

This is the first bunch using said script.

[c++]

And the rest of the lot. Obviously you were right these are way bigger now.

[c++]

since I made a windows executable of the script, now using a ./writer.jpg in the same dir as the *.exe. I figured I might as well share that here, too.

[c++]

Images from newer cams are ~600kb rather than ~12 like the rest, and appear to contain a pretty large thumbnail of some kind. I don't see this on the exiftool samples of the same cameras (some are on the list in the archive already). How do I remove said thumbnail or is it fine?

Well, these are from the secondary set I mentioned and thusI don't mind this too much but the likes of

Code Select Expand

dd if=Canon\ PowerShot\ N.jpg of=n-test.jpg bs=1 skip=19730sure give me a small jpeg...

[Phil Harvey]

Images from newer cams are ~600kb rather than ~12 like the rest, and appear to contain a pretty large thumbnail of some kind. I don't see this on the exiftool samples of the same cameras (some are on the list in the archive already).

Can you give me a specific model name and I'll take a look?

- Phil

[Phil Harvey]

Out of all those files, there were only 2 new ones:

    CanonDIGITAL_IXUSi_Zoom.jpg
    CanonIXUS175.jpg

- Phil

[c++]

Do update the CanonPowerShotA800 as well yours is some weird FW version of a camera. Same holds true for CanonPowerShotS110-new CanonPowerShotN100 CanonPowerShotG9 but I have neither of those three. Actually for uses like feature testing the CHDK camera select routines that work by FW revision different FWs of the cameras would be worthwhile but I did not look into how to quickly rename the files based on that. So up to you whether you would like to keep different versions.

Can you give me a specific model name and I'll take a look?

Nice, let's take the Powershot N I mentioned, I'll give you the full image also. And the stripped down one that kept the thumbnail I spoke of. Would still be nice to get this fully working, so perhaps I'll just make the different FW meta data collection myself one day, don't have all cameras though just maybe 150.

[c++]

It would still be nice to know how to remove that thumbnail while keeping the exifdata extracted stay accurate. It's not urgent but would be nice to know.