CHDK-based RAW images not detected and paired
Submitted by an unknown user
Link to original bug (#718330)
Description
---- Reported by shotwell-maint@gnome.bugs 2012-03-25 10:18:00 -0700 ----
Original Redmine bug id: 4916
Original URL: http://redmine.yorba.org/issues/4916
Searchable id: yorba-bug-4916
Original author: Jeremy Nickurak
Original description:
I'm using a Canon digital camera with CHDK, which enables the camera to shoot with RAW. Unfortunately, Shotwell doesn't seem to pick up on the fact that there are JPG/RAW pairs.
Since the raw is too big to attach here, please see: http://nickurak.ca/~atrus /shotwell-crw-pair/ for an example pair of images.
Related issues:
- related to shotwell - Feature #4040: combine/separate RAW+JPEG photos (Open)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-16 14:44:00 -0700 ----
History
Comment 1
Updated by Adam Dingle over 1 year ago
- Priority changed from Normal to High
Comment 2
Updated by Eric Gregory over 1 year ago
Normally when you have a RAW+JPEG pair, only the extensions of the file name differ. But not so in this case, which explains why Shotwell's import mechanism doesn't pair them.
Comment 3
Updated by Jeremy Nickurak over 1 year ago
Interesting. Per http://chdk.wikia.com/wiki/CHDK_User_Manual , this is configurable on my side.
Do you know if renaming them in place will cause Shotwell to notice the changes in past imports?
Comment 4
Updated by Eric Gregory over 1 year ago
A-ha! Interesting find. Also, you'll need to make sure "RAW File in Dir with JPEG" is enabled, though it appears that's the default.
Are other photo managers able to pair your RAW+JPEG photos with your current settings? If so, I wonder how they're able to do it...
Comment 5
Updated by Jeremy Nickurak over 1 year ago
Never used anything else with RAW support, so I couldn't say :)
Comment 6
Updated by Adam Dingle over 1 year ago
Jeremy: renaming the files in place will not cause Shotwell to associate the photos as RAW+JPEG pairs. Shotwell currently isn't super flexible in this regard. We hope to improve the situation in future releases; see #4040, for example.
Comment 7
Updated by Jeremy Nickurak over 1 year ago
I can confirm that this works correctly when I change the prefix, for new files at least. I'll watch 4040 :)
Comment 8
Updated by Jim Nelson 11 months ago
- Target version set to 0.14.0
Comment 9
Updated by Jim Nelson 11 months ago
- Category set to raw
Comment 10
Updated by Jim Nelson 11 months ago
- Status changed from Open to Need Information
Jeremy, the link you provided is now 404. Could you (or anyone interested in this ticket) supply us with a couple of CHDK+JPEG pairs to test with, or point us to a web site with some? I've looked and can't find any with the CHDK files, only JPEGs.
Comment 11
Updated by Joe Bylund 10 months ago
I've put a pair at: http://www.columbia.edu/~jhb2147/shotwell/issue_4916/ (obviously let me know if you have any issues accessing)
Comment 12
Updated by Jim Nelson 10 months ago
- Status changed from Need Information to Open
Thanks for the photos, Joseph, this helps me confirm the issue.
The files Joseph link to will not be paired by Shotwell when they're imported. It's not because of CHDK explicitly, but because of how they're named. One is CRW_1001.DNG and the other is IMG_1001.JPG. If you rename the second to CRW_1001.JPG (or vice-versa, IMG_1001.DNG), they will be paired at import. The entire requirement for pairing is the same file title (i.e. the name without the extension) in the same directory. Renaming after import will not work, as explained above. #4040 is how we plan on allowing users to solve this problem in that case.
Joseph, I assume that you did not alter these filenames before posting them on the Internet. That tells me that this is CHDK's naming convention. We'll probably have to make an exception in the import code to fix this.
Comment 13
Updated by Jeremy Nickurak 10 months ago
It's worth noting that you can reconfigure CHDK's prefixes so this works right with Shotwell. But it would be nice if the default was handled. (Sorry I haven't had time to update this ticket with my own pair...)
Comment 14
Updated by Jim Nelson 10 months ago
Ah -- that's a useful data point. That means it's possible for a CHDK user to pick anything, I presume? Is CRW/IMG the default?
Comment 15
Updated by Jim Nelson 10 months ago
- Target version changed from 0.14.0 to 0.15.0
This looks like a more complicated problem than we can deal with in the time remaining. We'll see if we can get to this in 0.15.
Comment 16
Updated by Jim Nelson 8 months ago
- Target version changed from 0.15.0 to 0.16.0
Comment 17
Updated by Jim Nelson 6 months ago
-
Target version deleted (
<strike>
_0.16.0_</strike>
)
--- Bug imported by chaz@yorba.org 2013-11-25 21:56 UTC ---
This bug was previously known as bug 4916 at http://redmine.yorba.org/show_bug.cgi?id=4916
Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one. Resolution set on an open status. Dropping resolution