I have seen this from time to time. I thought it was because of some
module version diff when editing an old picture... Not sure.
Anyway for me I have always been able to "fix" that by compressing the
history stack.
Regards,
--
Pascal Obry / Magny Les Hameaux (78)
The best way to travel
It would be intersting to know WHEN this happpens.
If I use "crop and rotate" (for example) many times, I get several entries
in the history.
But this is normal and when I clic on one entry in the history, I get how
was the image at this point of the history.
So, in this case, it is normal and desi
Hello,
I would like to use the geotagging of darktable 2.2.3, but it does not work
properly.
I have a raw file created on 2016: 12: 23 at 11:41:00 o'clock. My GPX file with
the track/waypoint has the same date and exactly the same time stamp.
If I used the geotagging without time offset, then n
Here:
https://developers.google.com/picasa-web/docs/2.0/developers_guide_protocol
In section "creation an album":
<<<
Important: As part of the Picasa Web Albums Data API changes, support
for this feature has been removed from the API. Read more about this in
the Release Notes.
>>>
And indeed,
It started on my system when I used the 'whisker' to rotate the image
and after that other modules gave multiple entries.
David
On 02/11/2017 01:07 AM, Jean-Luc Coulon (f5ibh) wrote:
> It would be intersting to know WHEN this happpens.
> If I use "crop and rotate" (for example) many times, I get
Hello,
recently I became interested in the problem of automatic haze removal.
Poking around in the scientific literature I found a method that is
(relatively) easy to implement and gives quite satisfactory results
(depending to some degree on the quality of the input file). For
testing purpo
* Is an automatic haze removal module something that you would like to
have in Darktable?
Abso-fucking-lutely. :)
.mm
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.dark
