Re: [Shotwell] Why does Export enforce file conversion?
Seconded! Add to that the ability to perhaps filter which files are imported into the Shotwell library? My workflow uses an external program to edit my .RW2 files into jpeg. The output jpeg is in the same directory as the original raw file, but I only want the jpegs imported in shotwell. It's great to be able to use Shotwell for basic editing of RAW, but I'd much prefer if I could keep my workflow and use Shotwell at the end of it without having to manually remove the links to the original raw files that I want to conserve but not display. Thanks! Jon On 09/29/2010 11:17 AM, Michael Hendry wrote: > I'd welcome the ability to export a bunch of files to a working > directory for further processing, leaving the originals in place. > > Obviously, it's helpful to be able to reduce the size of images for > transmission elsewhere, but why has it been made mandatory? > > Michael > > ___ > Shotwell mailing list > Shotwell@lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > ___ Shotwell mailing list Shotwell@lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
Re: [Shotwell] Why does Export enforce file conversion?
Ühel kenal päeval, K, 2010-09-29 kell 10:17, kirjutas Michael Hendry: > I'd welcome the ability to export a bunch of files to a working > directory for further processing, leaving the originals in place. > > Obviously, it's helpful to be able to reduce the size of images for > transmission elsewhere, but why has it been made mandatory? > > Michael > 1. Select some files 2. choose File → Export 3. set "Scaling constraint" to "Original size" 4. You get original images, no mandatory scaling Best regards Mattias ___ Shotwell mailing list Shotwell@lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
Re: [Shotwell] Why does Export enforce file conversion?
I think that wasn't the question - the question was to export a number of files to a directory outside the library while keeping the original files intact. Think of it as versioning for your edits, so you can always revert to a previous version by looking at a different file, I'm guessing for the edits done from within Shotwell. Jon On 09/29/2010 11:24 AM, Mattias Põldaru wrote: > Ühel kenal päeval, K, 2010-09-29 kell 10:17, kirjutas Michael Hendry: >> I'd welcome the ability to export a bunch of files to a working >> directory for further processing, leaving the originals in place. >> >> Obviously, it's helpful to be able to reduce the size of images for >> transmission elsewhere, but why has it been made mandatory? >> >> Michael >> > > 1. Select some files > 2. choose File → Export > 3. set "Scaling constraint" to "Original size" > 4. You get original images, no mandatory scaling > > > Best regards > Mattias > > ___ > Shotwell mailing list > Shotwell@lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell -- Use Thunderbird with Enigmail for convenient and safe emails! www.getthunderbird.com ___ Shotwell mailing list Shotwell@lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
Re: [Shotwell] Why does Export enforce file conversion?
Ühel kenal päeval, K, 2010-09-29 kell 11:27, kirjutas Jonathan Charnas: > I think that wasn't the question - the question was to export a number > of files to a directory outside the library while keeping the original > files intact. > > Think of it as versioning for your edits, so you can always revert to a > previous version by looking at a different file, I'm guessing for the > edits done from within Shotwell. > > Jon 1. Right click on a photo, choose "Open With External Editor" 2. As you see, the file opens as FILENAME_modified.jpg 3. Edit your file as you wish, save it and close editor. 4. Wait a second and see how Shotwell updates the thumbnail of your image. 5. If you want your original image back, right click on the image and pick "Revert to Original". Regards Mattias ___ Shotwell mailing list Shotwell@lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
Re: [Shotwell] Why does Export enforce file conversion?
Ühel kenal päeval, K, 2010-09-29 kell 11:24, kirjutas Jonathan Charnas: > My workflow uses an external program to edit my .RW2 files into jpeg. > The output jpeg is in the same directory as the original raw file, but I > only want the jpegs imported in shotwell. > > It's great to be able to use Shotwell for basic editing of RAW, but I'd > much prefer if I could keep my workflow and use Shotwell at the end of > it without having to manually remove the links to the original raw files > that I want to conserve but not display. > > Thanks! > Jon Not exactly an answer to your question, but see Adam's post from April: http://lists.yorba.org/pipermail/shotwell/2010-April/000282.html Mattias ___ Shotwell mailing list Shotwell@lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
Re: [Shotwell] Why does Export enforce file conversion?
Ühel kenal päeval, K, 2010-09-29 kell 10:30, kirjutas Michael Hendry: > On Wed, 2010-09-29 at 12:24 +0300, Mattias Põldaru wrote: > > Ühel kenal päeval, K, 2010-09-29 kell 10:17, kirjutas Michael Hendry: > > > I'd welcome the ability to export a bunch of files to a working > > > directory for further processing, leaving the originals in place. > > > > > > Obviously, it's helpful to be able to reduce the size of images for > > > transmission elsewhere, but why has it been made mandatory? > > > > > > Michael > > > > > > But if my original file was a NEF file, I have to have it converted to a > JPG or PNG file. > > Michael > Please use Reply all button, so your answers will go to the list. I think this is worth adding a ticket. I never had NEF files, but I think at moment this applies to RAW or whatever other files as well. http://trac.yorba.org/newticket Mattias ___ Shotwell mailing list Shotwell@lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
Re: [Shotwell] Why does Export enforce file conversion?
On Wed, 2010-09-29 at 12:39 +0300, Mattias Põldaru wrote: > Ühel kenal päeval, K, 2010-09-29 kell 11:27, kirjutas Jonathan Charnas: > > I think that wasn't the question - the question was to export a number > > of files to a directory outside the library while keeping the original > > files intact. > > > > Think of it as versioning for your edits, so you can always revert to a > > previous version by looking at a different file, I'm guessing for the > > edits done from within Shotwell. > > > > Jon > > 1. Right click on a photo, choose "Open With External Editor" > 2. As you see, the file opens as FILENAME_modified.jpg > 3. Edit your file as you wish, save it and close editor. > 4. Wait a second and see how Shotwell updates the thumbnail of your > image. > 5. If you want your original image back, right click on the image and > pick "Revert to Original". > > > > Regards > Mattias But if my original file was a NEF file, I have to have it converted to a JPG or PNG file. Michael ___ Shotwell mailing list Shotwell@lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
Re: [Shotwell] Why does Export enforce file conversion?
Aha. Well that's great, but the output jpeg has an added extension. Say if I edit P10001.RW2, the jpeg will be saved as P10001_lzn.jpg If I'm reading Adam's post properly, I'd be better off saving it as P10001.jpg and just re-import the directory? Personally I'd much prefer just importing the final result - LightZone stores the action history and links between RW2 and jpg in a db similar to shotwell's, but it pertains only to the editing done. Thus having an option to force shotwell to just ignore the RAW files entirely. Alternatively you could also show images imported and filter by filetype also - that would make me just as happy. Cheers, Jon On 09/29/2010 11:55 AM, Mattias Põldaru wrote: > Ühel kenal päeval, K, 2010-09-29 kell 11:24, kirjutas Jonathan Charnas: >> My workflow uses an external program to edit my .RW2 files into jpeg. >> The output jpeg is in the same directory as the original raw file, but I >> only want the jpegs imported in shotwell. >> >> It's great to be able to use Shotwell for basic editing of RAW, but I'd >> much prefer if I could keep my workflow and use Shotwell at the end of >> it without having to manually remove the links to the original raw files >> that I want to conserve but not display. >> >> Thanks! >> Jon > Not exactly an answer to your question, but see Adam's post from April: > http://lists.yorba.org/pipermail/shotwell/2010-April/000282.html > > Mattias > > ___ Shotwell mailing list Shotwell@lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
Re: [Shotwell] Why does Export enforce file conversion?
I feel like a few things are being batted around here in this thread, but I'm still not sure what's being asked for. When you say you want Shotwell to export so files can be edited separately from their originals, do you mean by Shotwell or a different editor? First, Shotwell is a non-destructive editor; we don't write our changes to the master file, so it's easy to try edits without losing data. Second, as mentioned, Shotwell does have an "Edit with External Editor" (and "Edit with External RAW Editor") which allows the files to be monitored and managed by Shotwell, but edited (destructively) elsewhere. Shotwell makes a full-sized copy (and converts RAW files to JPEG, if using the first option) so your master is safe. Third, no one has mentioned the Edit -> Duplicate option. This creates a duplicate of the photo (including a new copy of the file) in your library. This might be what some people are asking for. -- Jim On Wed, Sep 29, 2010 at 3:20 AM, Jonathan Charnas wrote: > Aha. Well that's great, but the output jpeg has an added extension. > Say if I edit P10001.RW2, the jpeg will be saved as P10001_lzn.jpg > If I'm reading Adam's post properly, I'd be better off saving it as > P10001.jpg and just re-import the directory? > > Personally I'd much prefer just importing the final result - LightZone > stores the action history and links between RW2 and jpg in a db similar > to shotwell's, but it pertains only to the editing done. Thus having an > option to force shotwell to just ignore the RAW files entirely. > > Alternatively you could also show images imported and filter by filetype > also - that would make me just as happy. > > Cheers, > Jon > > > On 09/29/2010 11:55 AM, Mattias Põldaru wrote: > > Ühel kenal päeval, K, 2010-09-29 kell 11:24, kirjutas Jonathan Charnas: > >> My workflow uses an external program to edit my .RW2 files into jpeg. > >> The output jpeg is in the same directory as the original raw file, but I > >> only want the jpegs imported in shotwell. > >> > >> It's great to be able to use Shotwell for basic editing of RAW, but I'd > >> much prefer if I could keep my workflow and use Shotwell at the end of > >> it without having to manually remove the links to the original raw files > >> that I want to conserve but not display. > >> > >> Thanks! > >> Jon > > Not exactly an answer to your question, but see Adam's post from April: > > http://lists.yorba.org/pipermail/shotwell/2010-April/000282.html > > > > Mattias > > > > > ___ > Shotwell mailing list > Shotwell@lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > ___ Shotwell mailing list Shotwell@lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
Re: [Shotwell] Why does Export enforce file conversion?
On Wed, 2010-09-29 at 11:31 -0700, Jim Nelson wrote: > I feel like a few things are being batted around here in this thread, but > I'm still not sure what's being asked for. When you say you want Shotwell > to export so files can be edited separately from their originals, do you > mean by Shotwell or a different editor? I expected Export to allow me to select a group of image files - perhaps all the files with a particular tag in common - and make unchanged copies of them somewhere else. It seems odd to me that a file conversion (to jpg or png) would be forced on me, albeit with an option on filesize. Obviously, I could use the File Manager to make copies of these files one by one, but I'd have to identify each one of the tabbed files separately, open the relevant directory, and copy the file to the destination directory. > > First, Shotwell is a non-destructive editor; we don't write our changes to > the master file, so it's easy to try edits without losing data. But I might want to export a group of files which share the same tag to a USB stick, e.g. for a colleague to work on. I would want him to have the original NEF files to work on (e.g. to adjust exposure settings) rather than a JPG. > > Second, as mentioned, Shotwell does have an "Edit with External Editor" (and > "Edit with External RAW Editor") which allows the files to be monitored and > managed by Shotwell, but edited (destructively) elsewhere. Shotwell makes a > full-sized copy (and converts RAW files to JPEG, if using the first option) > so your master is safe. Forgive me for having some anxieties about this process, and my ability to manage it correctly. > > Third, no one has mentioned the Edit -> Duplicate option. This creates a > duplicate of the photo (including a new copy of the file) in your library. > This might be what some people are asking for. Presumably the copy is in the same folder as the original file, so I'd have to chase through various directories to find the files I wanted to edit, and which had been duplicated to protect the originals? Michael > > -- Jim > > On Wed, Sep 29, 2010 at 3:20 AM, Jonathan Charnas wrote: > > > Aha. Well that's great, but the output jpeg has an added extension. > > Say if I edit P10001.RW2, the jpeg will be saved as P10001_lzn.jpg > > If I'm reading Adam's post properly, I'd be better off saving it as > > P10001.jpg and just re-import the directory? > > > > Personally I'd much prefer just importing the final result - LightZone > > stores the action history and links between RW2 and jpg in a db similar > > to shotwell's, but it pertains only to the editing done. Thus having an > > option to force shotwell to just ignore the RAW files entirely. > > > > Alternatively you could also show images imported and filter by filetype > > also - that would make me just as happy. > > > > Cheers, > > Jon > > > > > > On 09/29/2010 11:55 AM, Mattias Põldaru wrote: > > > Ühel kenal päeval, K, 2010-09-29 kell 11:24, kirjutas Jonathan Charnas: > > >> My workflow uses an external program to edit my .RW2 files into jpeg. > > >> The output jpeg is in the same directory as the original raw file, but I > > >> only want the jpegs imported in shotwell. > > >> > > >> It's great to be able to use Shotwell for basic editing of RAW, but I'd > > >> much prefer if I could keep my workflow and use Shotwell at the end of > > >> it without having to manually remove the links to the original raw files > > >> that I want to conserve but not display. > > >> > > >> Thanks! > > >> Jon > > > Not exactly an answer to your question, but see Adam's post from April: > > > http://lists.yorba.org/pipermail/shotwell/2010-April/000282.html > > > > > > Mattias > > > > > > > > ___ > > Shotwell mailing list > > Shotwell@lists.yorba.org > > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > > > ___ > Shotwell mailing list > Shotwell@lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell ___ Shotwell mailing list Shotwell@lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
Re: [Shotwell] Why does Export enforce file conversion?
On Wed, Sep 29, 2010 at 3:00 PM, Michael Hendry wrote: > > I expected Export to allow me to select a group of image files - perhaps > all the files with a particular tag in common - and make unchanged > copies of them somewhere else. It seems odd to me that a file conversion > (to jpg or png) would be forced on me, albeit with an option on > filesize. > Ok -- I see now what you're asking for. Yes, this makes more than enough sense. I've ticketed it here: http://trac.yorba.org/ticket/2621 As I mentioned in the ticket, this would mean that no edits you've made in Shotwell (enhance, crop) would be reflected in the RAW files. We currently do not support writing metadata to RAW files either, so tags (for example) would not be written out (until this ticket is completed: http://trac.yorba.org/ticket/2622) -- Jim ___ Shotwell mailing list Shotwell@lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
Re: [Shotwell] Why does Export enforce file conversion?
On Wed, 2010-09-29 at 18:05 -0700, Jim Nelson wrote: > > On Wed, Sep 29, 2010 at 3:00 PM, Michael Hendry > wrote: > > > I expected Export to allow me to select a group of image files > - perhaps > all the files with a particular tag in common - and make > unchanged > copies of them somewhere else. It seems odd to me that a file > conversion > (to jpg or png) would be forced on me, albeit with an option > on > filesize. > > Ok -- I see now what you're asking for. Yes, this makes more than > enough sense. I've ticketed it here: > http://trac.yorba.org/ticket/2621 > > As I mentioned in the ticket, this would mean that no edits you've > made in Shotwell (enhance, crop) would be reflected in the RAW files. > We currently do not support writing metadata to RAW files either, so > tags (for example) would not be written out (until this ticket is > completed: http://trac.yorba.org/ticket/2622) > > -- Jim I wouldn't necessarily want to roll back all changes made within Shotwell since the file was originally imported, more a WYSIWYG exercise - if the file is unmodified, it should go out as it was when it came in. Now I think about it, there should probably be several options: 1. Export files in their original forms. 2. Export as original if not already modified by Shotwell, in which case a compression option is required for the latter. 3. Export all in a compressed form (as at present). I would use option 1 for photographic print competition candidates - doing the selection within Shotwell, but going back to the original files and re-editing to get the best possible quality for a big print. Option 2 would be similar, but for presentation purposes - I'd accept the edits already done within Shotwell as a time-saver. Option 3 would be for circulation by e-mail, Flickr etc., where no further editing is required, but compression is necessary for speed of transmission. Sorry my powers of communication are insufficient to get my ideas through first time round, but these ideas are themselves in a state of flux as I get used to using Shotwell! Reflecting on the above before pressing the Send button, I can see that I could achieve the same results as options 1 and 2 by creating duplicates of the original files, and invoking GIMP (or whatever) on the duplicates, with distinct lines of descendant images for different purposes. I obviously have to change a mind-set here - keeping track of competition candidates by using File Manager to copy them into a working directory becomes unnecessary when I can skim through the whole collection with Shotwell and tag the candidates as I go. Michael ___ Shotwell mailing list Shotwell@lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
