generate previews for RAW images
Submitted by Adam Dingle
Assigned to Eric Gregory
Link to original bug (#717842)
Description
---- Reported by adam@yorba.org 2011-06-03 10:18:00 -0700 ----
Original Redmine bug id: 3689
Original URL: http://redmine.yorba.org/issues/3689
Searchable id: yorba-bug-3689
Original author: Adam Dingle
Original description:
We've decided to generate preview images for RAW images in Shotwell. These previews will be generated using the thumbnail mechanism and will be large enough to display on most monitors without pixel expansion. They will allow us to quickly display RAW images when opened even when no mimics are present.
We'd rather not make the preview size monitor dependent. The standard 1080p resolution is 1920×1080, so I think this resolution will be standard for large monitors for a long time to come. So I'll suggest that we generate previews so that the smaller axis is 1080 pixels. This means that a square image would have a 1080×1080 preview, and an image with a!3:2aspect ratio (common for SLR cameras) would have a preview at 1620×1080.
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:45:00 -0700 ----
History
Comment 1
Updated by Adam Dingle over 2 years ago
- Status changed from Open to 5
- Resolution set to invalid
- % Done changed from 0 to 0
-
Target version deleted (
<strike>
_0.11_</strike>
)
We've had more discussions about RAW support and it's not so clear that we'll take the path described in this ticket. Marking as invalid for now.
Comment 2
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Invalid
--- Bug imported by chaz@yorba.org 2013-11-25 21:54 UTC ---
This bug was previously known as bug 3689 at http://redmine.yorba.org/show_bug.cgi?id=3689
Unknown Component Using default product and component set in Parameters 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: RESOLVED INVALID