Camera compatibility

Whether pictkura can pull a display JPEG out of your camera's RAW. It does not develop anything — it hands you the picture the camera embedded for its own screen.

Checked against 1,870 real files (every CC0 sample at raw.pixls.us), from 56 makers and 923 bodies. 816 on macOS and 1,054 on Windows, with no crashes. Every picture counted here was decoded, not measured from a JPEG header.

This describes the shipped 1.0.0. The measurement ran against 0.2.6, and the path that pulls the picture out has not changed since. What has changed since that bears on this table came in 0.2.7: two more extensions in the scan list (ori, arq) and the order thumbnails are generated in.

• A full-size pictureThe embedded display JPEG comes out, with its longest edge at 1600px or more
• A small pictureA picture appears, but below 1600px, so a full-screen view is soft
• Listed, but no pictureNo display JPEG was found. The file still appears in the grid as a frame, and it still sorts by date and answers the camera filter
• Mixed within this bodyThe same body lands in more than one row above depending on how the shot was taken; the split is in the notes
• Shown as an ordinary imageIt appears in the grid, but is opened as an ordinary image rather than searched as RAW
• Not supportedAn extension we chose not to add. The reason is on each row

Past 128MB the brute-force scan stops at the first 16MB. Declared offsets are read at any size, which is why some files over 200MB still give a full-size picture. Rows under “Listed, but no picture” where the search did not run to the end say so in the notes: we cannot say the file has none.

makers