Maximilian,
On 05/04/2011 03:27 AM, Maximilian Blömer wrote:
Hi all,
most of the time I develop my raw photos in ufraw to jpg, opening them
via shotwell. That creates a jpg with the same name of the photo in
the original folder and the developed photo appears next to the
original raw in shotwell. Than I crop the new jpg versions in
shotwell.
Glad to hear this works for you at least some of the time. RAW support
in Shotwell is still immature and you've run into some of its
limitations. I hope we can improve this later this year.
The problem I find here is that I cannot crate a new developed jpg
without overwriting the already existing one by default when accessing
ufraw out of shotwell.
I'm not sure I understand. I *think* you mean this:
1. Right click a RAW photo in Shotwell and choose Open With RAW Editor
to open UFRaw.
2. Edit some parameters and press Save. UFRaw will save a JPEG
(assuming you've configured it to do that).
3. Repeat step 1 on the same photo.
4. Once again, edit some parameters and press save. UFRaw will, by
default, want to save to the same JPEG file you saved in step 2.
Is this the problem you're describing?
I don't like the "revert to original" way to version photos in
shotwell, also I rely on ufraw since shotwell lacks some features in
developing raw files.
I've seen a versioning feature in f-spot working nice with my jpgs
from my small digital cam and with jpgs scanned from my analog photos
using gimp via f-spot to edit them. Unfortunately using f-spot for my
raw photos seems to be unstable.
So, my two questions:
1. Do you plan a versioning feature. Having all the time two or more
versions of the same photo side by side in shotwell looks
inappropriate.
Yes, we'd like to implement something like this. See
http://trac.yorba.org/ticket/1772
http://trac.yorba.org/ticket/2474
2. can you please fix the way to call ufraw from shotwell without
overwriting already existing photos by default by giving the new copy
an other name.
As I said above, I'm not sure I understand your request. If the problem
is as I described above, I don't see a terribly easy fix. If there is
already an existing JPEG photo for a RAW photo, then when you open the
RAW photo again in an external RAW editor I suppose that Shotwell could
copy the RAW photo to a new location so that when you save it again the
filenames won't conflict. But that seems like an odd workaround. The
right solution to this would be to add RAW editing capabilities to
Shotwell itself and then let each photo have multiple developed
versions. Maybe someday.
3. Is there already a way to handle this workflow (or how users
“should” use the program) I have not considered since I'm coming from
f-spot?
I'll leave it to others on the mailing list to discuss that. If you
look through the Shotwell mailing list archives you may find some other
discussions about RAW workflow as well.
adam
_______________________________________________
Shotwell mailing list
[email protected]
http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
