+1 for me too. Right now, I do this with tags to keep track of them, but I like the idea of keeping things explicitly together. It would be nice if this can be combined with different versions of the image (e.g. different RAW exports, externally modified versions, other HDR renders of the same base images), with an image of your choice as 'key image' to show in the viewer (this can be useful for exporting a bunch of pictures, among which a set, so the key image is the only one exported)
I don't do panorama's or HDRs for each image, so I would probably not use an import feature. Rather, I'd select the images when imported and push on some 'create set' button. 2011/9/14 Ian Molton <[email protected]>: > Hey, > > I shoot a lot of pano and HDR shots. > > I'd love to be able to tell Shotwell that x source photos belong to y > 'processed' photos (I'd like to be able to have shotwell show several > exposure configurations or projections for the input files). > > To be clear, I dont want shotwell (for now) to handle generating the > pano/hdr shots - merely to have it collate the source images and present > a choice of views of the finished image - let hugin or whatever do the > hard work. > > I want this because otherwise, my holiday shots totalling about 150 > images, actually looks like 2000 images, right now. > > The way I see this working is that during import, I group select the > pano components, and right click and choose "set as panorama source". > > After import, all these images do NOT show individually. > > Shotwell will pick one image (temporarily) from the group to display as > output (so something is visible in the view after import). > > Later, I can right click the 'image group' and click "render images" and > have shotwell launch (for example) hugin, and pass it the images. > > I create a panorama or HDR image in hugin and hit render/stitch/save. > > Hugin does its thing, then saves the image and quits. > > Shotwell updates the view image to the new panorama. > > Right now, I have to tag all the source images as (say) pano-0001, then > manually find them in the filesystem and load them into hugin, process, > save, import into the library, and re-tag. > > Not only is that a pain, but also means in library view I have to scroll > through thousands of pano components. > > Thoughts? > > -Ian > > _______________________________________________ > Shotwell mailing list > [email protected] > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
