Ulf Rompe wrote:
> Am Sonntag, den 04.11.2007, 20:14 -0500 schrieb Daniel Falk:
>
>> I'm wondering if this fits in with a workflow that doesn't want to
>> keep the raws forever. I'm wondering this because that's the boat I'm
>> in. I take way too many pictures and have too little hard drive
>>
Am Sonntag, den 04.11.2007, 20:14 -0500 schrieb Daniel Falk:
> I'm wondering if this fits in with a workflow that doesn't want to
> keep the raws forever. I'm wondering this because that's the boat I'm
> in. I take way too many pictures and have too little hard drive
> capacity to keep the raws a
I'm wondering if this fits in with a workflow that doesn't want to keep
the raws forever. I'm wondering this because that's the boat I'm in. I
take way too many pictures and have too little hard drive capacity to
keep the raws around, but the actual jpgs I'd like to keep. What would
be the best
it's always better to attach patches to bug entries. to the list, if the
patch is not applied i nthe next few days, it's lost forever...
i'm pushing this one right now...
s
On Tue, 2007-10-23 at 08:52 +1000, Tim Thomson wrote:
> I just discovered svn diff, lots easier than diff -u.
>
> The atta
I just discovered svn diff, lots easier than diff -u.
The attached diff simply adds Pentax RAW file extensions to the list
in the IsRaw function.
I'm had a slow time compiling and installing the DevelopInUFraw
extension. Will have another go tonight. Hopefully have another small
diff by tomorrow.
Nice sugestions. Patches are welcome...
s
On Mon, 2007-10-22 at 22:36 +1000, Tim Thomson wrote:
> Hi everyone,
>
> I'm liking the way things are going with RAW processing recently, I
> think I might be about to make a full switch back from digikam.
>
> Just a couple of issues I've noticed, Pen
Hi everyone,
I'm liking the way things are going with RAW processing recently, I
think I might be about to make a full switch back from digikam.
Just a couple of issues I've noticed, Pentax's .pef and .dng
extensions aren't in the IsRaw function so it won't shell out to
ufraw. (src/Imaging/ImageF
Great !!
I think I will re-use f-spot at a more regular basis now.
The raw/jpeg merging addins was not working for the same reasons btw.
Stephane Delcroix a écrit :
> enabled in r3419
>
> s
>
>
___
F-spot-list mailing list
F-spot-list@gnome.org
http:
enabled in r3419
s
On Thu, 2007-10-11 at 20:40 +0200, vescovi christophe wrote:
> Hi,
> I do not know if I have to file a bug but it seems that the "develop in
> ufraw" extension does not recognise Konica Minolta raw files (.mrw) has
> valid raw files.
> I have the following message in the co
Hi,
I do not know if I have to file a bug but it seems that the "develop in
ufraw" extension does not recognise Konica Minolta raw files (.mrw) has
valid raw files.
I have the following message in the console when trying to use the
extention on .mrw files :
EXECUTING DEVELOP IN UFRAW EXTENSIO
Am Montag, den 24.09.2007, 12:04 + schrieb Olafur Arason:
> > "Develop in ufraw" appears in everyone's contextual menu.
> Please use something like "Develop the raw image", because
> some people don't know what ufraw is. And also it should not show
> up if the user does not have ufraw installed
Great work.
Just some HIG..
On 9/6/07, Stephane Delcroix <[EMAIL PROTECTED]> wrote:
> An update on the RAW status...
>
> - since a few days, db supports versions of images with different
> extensions
> - I wrote an addin that'll help you fix your actual db by merging raw
> +jpeg files of the same
On Wed, 2007-09-19 at 22:06 +0200, Ulf Rompe wrote:
> Am Donnerstag, den 06.09.2007, 11:12 +0200 schrieb Stephane Delcroix:
> > - the code for reparenting an image as version of another dy drag'n
> > drop is already in trunk, just not compiled yet (compile with
> > -d:ENABLE_REPARENTING if you want
Am Donnerstag, den 06.09.2007, 11:12 +0200 schrieb Stephane Delcroix:
> - the code for reparenting an image as version of another dy drag'n
> drop is already in trunk, just not compiled yet (compile with
> -d:ENABLE_REPARENTING if you want to give it a try)
I have just tried it out. It works like
On 9/14/07, Ulf Rompe <[EMAIL PROTECTED]> wrote:
> Am Donnerstag, den 06.09.2007, 11:12 +0200 schrieb Stephane Delcroix:
> > An update on the RAW status...
> >
> > - since a few days, db supports versions of images with different
> > extensions
> > - I wrote an addin that'll help you fix your actua
On 9/14/07, Ulf Rompe wrote:
> (see http://exiflow.sf.net/ for the naming scheme)
I stumbled upon this tool about a year ago and wanted to raise the
issue, but never felt justified enough. Not that you mention it, I do
:)
Using naming scheme like this would fix one of most irritating things
in c
On 9/14/07, Ulf Rompe wrote:
> (see http://exiflow.sf.net/ for the naming scheme)
I stumbled upon this tool about a year ago and wanted to raise the
issue, but never felt justified enough. Not that you mention it, I do
:)
Using naming scheme like this would fix one of most irritating things
in c
Am Donnerstag, den 06.09.2007, 11:12 +0200 schrieb Stephane Delcroix:
> An update on the RAW status...
>
> - since a few days, db supports versions of images with different
> extensions
> - I wrote an addin that'll help you fix your actual db by merging raw
> +jpeg files of the same image as only
David Collett-3 wrote:
>
> WooHoo! You rock!
>
>
May I play the role of the dumb-one again? I just updated to latest SVN,
found the add-ins, installed them. Then tried for a while, but could not
locate any new menu options etc. Then I realized that you need to restart
f-spot for this to take
On Thu, 2007-09-06 at 11:12 +0200, Stephane Delcroix wrote:
> An update on the RAW status...
> - I wrote an addin that'll help you fix your actual db by merging raw
> +jpeg files of the same image as only one image with versions. This will
> be available very soon via the 'Manage extensions' menu e
This is great news! Great work and thanks for the update!
Peter
On 9/6/07, Stephane Delcroix <[EMAIL PROTECTED]> wrote:
>
> An update on the RAW status...
>
> - since a few days, db supports versions of images with different
> extensions
> - I wrote an addin that'll help you fix your actual db b
WooHoo! You rock!
Since writing the original email, I too discovered the extension thing,
and also realised that I incorrectly assumed I could force the output
file with ufraw. Now you've fixed both :)
Good times! Please do keep us posted, I'm more than happy to test svn
when you give me the sig
An update on the RAW status...
- since a few days, db supports versions of images with different
extensions
- I wrote an addin that'll help you fix your actual db by merging raw
+jpeg files of the same image as only one image with versions. This will
be available very soon via the 'Manage extensio
I looked into doing something similar a while ago. I dug around in the code
a bit and if I remember right, I found that the biggest issue with this is
that the database doesn't support versions of an image with different file
type extensions. This means that a JPEG can't be stored as version of
Stephane Delcroix wrote:
>
>
>> My ideal workflow would be something like this:
>>
>> 1. import RAW files directly from camera/memcard
>> 2. right-click desired photo and select "develop in UFRAW"
>> 3. UFRAW would be launched where I can perform RAW developing.
>> 4. When UFRAW is closed, th
Sounds like a very good and simple way to do it. Export to converter and
automated import back as a version are essential rawconversion things
that should be imlemented as soon as possible.
Another thing that has been discussed in this list before, but I do not know
if anything have hapened to it
> My ideal workflow would be something like this:
>
> 1. import RAW files directly from camera/memcard
> 2. right-click desired photo and select "develop in UFRAW"
> 3. UFRAW would be launched where I can perform RAW developing.
> 4. When UFRAW is closed, the resulting jpeg would be automatically
27 matches
Mail list logo
