Many apologies. This was carelessness on my part. PR 1431 should fix this.
The bug was in changes I made to the Bayer downscaling code. For certain raw
image dimensions, the downscaling to produce the preview would look at a pixel
past the edge of the image.
Thank you very much for reporting &
A test today: I imported a new folder from today's shoot with my Fuji
(16 Mp.) and was able to fully process all of the files without any
problem. I then closed dt, reopened and moved to an older folder (2012)
where the images were from a Canon (16 Mp.). On this second folder ..
during the
Am Sonntag, 29. Januar 2017, 12:50:55 CET schrieb David Vincent-Jones:
> Is it possible that older sidecar files have compatibility problems with
> gkt3?
Nothing is ever impossible, but I wouldn't know of a way to achieve that.
> David
Tobias
[...]
signature.asc
Description: This is a
Is it possible that older sidecar files have compatibility problems with
gkt3?
David
On 01/29/2017 09:46 AM, David Vincent-Jones wrote:
I am on openSUSE Leap 42.2 with gtk3 3.20.9 and dt
2.3.0+git309.0f2cfb2-1.1 also from Darix's repo. The problem is very
real on my system but seen when
Hallo,
i have writen a Lua script with a combox. I have set the option:
editable = true
but is it not possible to type a string in the combobox. The option editable =
true doesn't working with darktable 2.2.1
Holger
___
I am on openSUSE Leap 42.2 with gtk3 3.20.9 and dt
2.3.0+git309.0f2cfb2-1.1 also from Darix's repo. The problem is very
real on my system but seen when working on older files and is not seen
on my current images.
David
On 01/29/2017 05:02 AM, Patrick Shanahan wrote:
* Ulrich Pegelow
* Pascal Obry [01-29-17 11:24]:
>
> Hi Hans,
>
> > I'm getting problems also when exporting to G+.
>
> Thanks for the feedback. I have also tested with 2.2.1 with two
> different accounts and it always fail. So that look like a Google Photo
> issue or a change in the API but I
Hi!
I cannot export today to Google Photo (this is with darktable compiled
from Git master). Am I the only one?
The export is fine, but during the upload I get a 400 bad request
response from Google! This has always worked for me and for sure on Jan
12 it was working:
< HTTP/1.1 400 Bad
I checked further and it's obviously not (only) related to my system
upgrade, 'cause if I go back a few commits darktable runs stable.
git bisect helped me to find the offending part:
07dc9664df548c7f775ade36cbdb7875a4aa4c9f is the first bad commit
commit
On Sat, Jan 28, 2017 at 4:41 PM, Moritz Moeller wrote:
> On 28.1.17 12:06 , Roman Lebedev wrote:
> I did. Same error.
Fixed, thank you for reporting!
> .mm
Roman.
___
darktable developer mailing list
* Ulrich Pegelow [01-29-17 03:41]:
> I need to investigate a bit further. Different from what I thought before it
> does not seem to be related to specific image dimensions. Several images in
> a recent film roll crash immediately when opening them, many others lead
This is a bit different but some time ago, I failed to build darktable with
git version of lensfun.
I've opened a bug on lensfun (#72).
I received the following reply:
As a quick workaround, you may use the environment variable
CFLAGS=-Wno-error=deprecated-declarations
Regards
Jean-Luc
Hi,
I'm having this error when using latest darktable from git and latest
lensfun from git:
[iop_lens]: could not load lensfun database in
`/usr/share/lensfun/version_2'!
[iop_lens]: could not load lensfun database in `/usr/share/lensfun'!
I have no lens correction when I get this error, of
Hi Ulrich,
> As I have just moved from OpenSUSE 13.2 to Leap 42.1 this might well
> be related to gtk/x as many libraries are now updated.
For the record I'm using GNU/Debian sid and have no crash on my side
using darktable compiled from master (I have used it extensively
yesterday).
My Gtk
14 matches
Mail list logo