Re: [darktable-dev] Deconvolution and Python framework

2017-10-12 Thread Aurélien PIERRE
Hi Tobias and Johannes ! @ Tobias : The standard deconvolution has to be computed on the whole picture since the iterations stack represents the approximated numeric solution of the equation we try to solve with an implicit method, so there is no way to just store a bunch of parameters for a late

Re: [darktable-dev] possible data loss scenario

2017-10-12 Thread Marcello Mamino
On Thu, Oct 12, 2017 at 11:57 PM, Tobias Ellinghaus wrote: > Am Donnerstag, 12. Oktober 2017, 17:24:30 CEST schrieb Marcello Mamino: >> I can reproduce the bug on Debian stable, under Xfce, master branch >> just compiled, every setting default. The steps to follow are >> *exactly* these >> >> 1. O

Re: [darktable-dev] possible data loss scenario

2017-10-12 Thread Jonathan Richards
On 12/10/17 22:57, Tobias Ellinghaus wrote: > Am Donnerstag, 12. Oktober 2017, 17:24:30 CEST schrieb Marcello Mamino: >> I can reproduce the bug on Debian stable, under Xfce, master branch >> just compiled, every setting default. The steps to follow are >> *exactly* these >> >> 1. Open the "export

Re: [darktable-dev] Olympus lens name mismatch

2017-10-12 Thread Roman Lebedev
On Fri, Oct 13, 2017 at 1:47 AM, Felipe Contreras Salinas wrote: > The list of lenses of the Lens Correction Module lists the "Olympus M.Zuiko > Digital ED 60mm f/2.8 Macro" as "Olympus M.Zuiko Digital 60mm f/2.8 Macro" > (without the ED). This results in that you must select the lens manually, >

[darktable-dev] Olympus lens name mismatch

2017-10-12 Thread Felipe Contreras Salinas
The list of lenses of the Lens Correction Module lists the "Olympus M.Zuiko Digital ED 60mm f/2.8 Macro" as "Olympus M.Zuiko Digital 60mm f/2.8 Macro" (without the ED). This results in that you must select the lens manually, because DT says that the lens is not found. If I understand correctly

Re: [darktable-dev] possible data loss scenario

2017-10-12 Thread Tobias Ellinghaus
Am Donnerstag, 12. Oktober 2017, 17:24:30 CEST schrieb Marcello Mamino: > I can reproduce the bug on Debian stable, under Xfce, master branch > just compiled, every setting default. The steps to follow are > *exactly* these > > 1. Open the "export selected" tab > 2. Click in the "max size" filed.

Re: [darktable-dev] possible data loss scenario

2017-10-12 Thread Marcello Mamino
I can reproduce the bug on Debian stable, under Xfce, master branch just compiled, every setting default. The steps to follow are *exactly* these 1. Open the "export selected" tab 2. Click in the "max size" filed. 3. Slowly move the pointer *downwards* 4. As soon as the pointer reaches the "allow

Re: [darktable-dev] Fixing the scroll-bar issue

2017-10-12 Thread Jørn Villesen Christensen
Hi there, On 2017-10-12 09:50, Tobias Ellinghaus wrote: Am Mittwoch, 11. Oktober 2017, 20:04:34 CEST schrieb Rolf Meyerhoff: DT has actually two scrollbars for the lighttable. One is located at the outer most right edge and one at the outer most left edge of the main window. However, they are

Re: [darktable-dev] Deconvolution and Python framework

2017-10-12 Thread Tobias Ellinghaus
Am Donnerstag, 12. Oktober 2017, 00:23:42 CEST schrieb Aurélien PIERRE: > Hi ! > > I understand the performance concerns and I'm working on some trade off. > But… [...] > 3 - The most computation-demanding operation is convolution product (2 > FFT-convolve by non blind iteration, 4 by blind iter

Re: [darktable-dev] Fixing the scroll-bar issue

2017-10-12 Thread Tobias Ellinghaus
Am Mittwoch, 11. Oktober 2017, 20:04:34 CEST schrieb Rolf Meyerhoff: > Hi > > DT has actually two scrollbars for the lighttable. One is located at the > outer most right edge and one at the outer most left edge of the main > window. > > However, they are not accessible with a mouse because they'r

Re: [darktable-dev] Deconvolution and Python framework

2017-10-12 Thread johannes hanika
hi, 1) 16s in single-thread python sounds like it would be possible to do < 100ms in a programming language. 4) that depends on the order of modules. if you want to do it in the current sharpen module as an option, it'll come pretty much last. if you do it early, dt will transparently cache the o