can't export JPEG from RAW+JPEG pair
Submitted by Adam Dingle
Assigned to cli..@..ba.org
Link to original bug (#718143)
Description
---- Reported by adam@yorba.org 2011-12-13 08:23:00 -0800 ----
Original Redmine bug id: 4482
Original URL: http://redmine.yorba.org/issues/4482
Searchable id: yorba-bug-4482
Original author: Adam Dingle
Original description:
There's no way to export the JPEG photo from a RAW+JPEG pair in Shotwell. In the export dialog, the 'unmodified' option exports the RAW picture, and the 'current' option exports either the embedded JPEG (when using the Camera developer) or a JPEG generated by Shotwell (when using the Shotwell developer).
This is related to #4149 (closed). For RAW+JPEG pairs, Shotwell should never be using a JPEG embedded in the RAW file. Instead, it should use the sibling JPEG both for rendering and for exporting. We also might want to think about changing the options in the export dialog to better suit RAW+JPEG pairs.
Related issues:
- related to shotwell - 4149: Odd behavior when importing RAW+JPEG with Camera development (Fixed)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:38:00 -0700 ----
History
Comment 1
Updated by Adam Dingle over 1 year ago
-
Target version deleted (
<strike>
_0.12_</strike>
)
Comment 2
Updated by Lucas Beeler over 1 year ago
- Category set to 4
- Assignee set to Lucas Beeler
- Target version set to 0.13
Comment 3
Updated by Adam Dingle about 1 year ago
-
Assignee deleted (
<strike>
_Lucas Beeler_</strike>
)
Comment 4
Updated by Adam Dingle about 1 year ago
- Target version changed from 0.13 to 0.14.0
Comment 5
Updated by Jim Nelson 11 months ago
- Category set to raw
Comment 6
Updated by Jim Nelson 11 months ago
- Target version changed from 0.14.0 to 0.15.0
We'll have to get this in 0.15.
Comment 7
Updated by Jim Nelson 10 months ago
- Target version changed from 0.15.0 to 0.14.0
There's a chance that #4149 (closed) will take care of this problem, so bumping to 0.14.
Comment 8
Updated by Clinton Rogers 10 months ago
I just tested this, and I can indeed confirm that [the proposed fix](http://re dmine.yorba.org/projects/shotwell/repository/revisions/11d4d2f259667ebbd1cc861 6db72598107d96cd2) for #4149 (closed) greatly improves this.
Comment 9
Updated by Jim Nelson 10 months ago
- Assignee set to Clinton Rogers
Great to hear, Clinton. Do you think your proposed fix is sufficient to close this ticket, or is there more work to do here?
Comment 10
Updated by Clinton Rogers 10 months ago
- Status changed from Open to Review
Reason: #4149 (closed)'s fix will fix this as well.
Comment 11
Updated by Clinton Rogers 10 months ago
- Status changed from Review to 5
- % Done changed from 0 to 100
- Resolution set to fixed
#4149 (closed) 's patch fixes this, too.
Comment 12
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:55 UTC ---
This bug was previously known as bug 4482 at http://redmine.yorba.org/show_bug.cgi?id=4482
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.
Version: 0.14.0
Resolution: RESOLVED FIXED