make a CPU variant? So far as I know, all
> of darktable is built to function on CPUs with the possibility of GPU
> speed-up in certain cases.
>
> I can't speak for the dt core developers regarding their interest &
> priorities, of course...
>
> Best,
> Dan
>
>
>
&
ualizer module in darktable to subdue
> high-frequency colour (see attached style for the dt settings). not
> sure this is the most elegant way to do it though. in the end,
> however, it describes the issue with the sensor.. high frequency
> colour cannot be captured with it.
>
&
you're losing some contrast
>> as compared to markesteijn? or is m. oversharpening?
>>
>> sad to see how the thin branches in the trees have these colourful
>> fringes. i guess that would go away with colour smoothing/median
>> filtering?
>>
>> cheers,
>>
Hi all,
I see that a lively discussion was started by my mail.
I’ll try to combine as many replies into one single e-mail as possible.
1. The trees and branches as test image: the colour artifacts in this image are
larger areas, not just one or two pixels (like in the black tie). This makes it
; On Sun, Feb 5, 2017 at 2:35 AM, Ingo Liebhardt <ingo.liebha...@ziggo.nl
> <mailto:ingo.liebha...@ziggo.nl>> wrote:
> Hi all,
>
> Thanks again for the feedback, especially to J Liles, which helped me a lot
> to find out some issues concerning the filter design.
> In t
, filtercoeff_var_4.h in
between).
Thankful for further feedback.
Cheers,
Ingo
> Am 07.02.2017 um 02:35 schrieb J. Liles <malnour...@gmail.com>:
>
>
>
> On Sun, Feb 5, 2017 at 2:35 AM, Ingo Liebhardt <ingo.liebha...@ziggo.nl
> <mailto:ingo.liebha...@ziggo.nl>>
Hi all,
Maybe you still remember that I tried an alternative approach to X-Trans
demosaicking (using guided filtering) in March / April this year…
In the end, I was not satisfied, and I gave up on that approach. The problems
were comparable to the Markesteijn algorithm, and the improvements
m>> wrote:
>
>
> On Mon, Dec 12, 2016 at 10:40 AM, Ingo Liebhardt <ingo.liebha...@ziggo.nl
> <mailto:ingo.liebha...@ziggo.nl>> wrote:
> Hi all,
>
> Maybe you still remember that I tried an alternative approach to X-Trans
> demosaicking (using guided
Ah, and by the way @J Liles: could you please explain me a bit more what you
mean by ‚textile like artifact‘, I’d like to investigate that one a bit more
in-depth.
Thx
> Am 21.12.2016 um 20:10 schrieb Ingo Liebhardt <ingo.liebha...@ziggo.nl>:
>
> Hi all,
>
> Thanks a
it up and try to prepare a proper commit, maybe it might be
possible to include it in the upcoming 2.4.0 release...
Cheers,
Ingo
> Am 14.05.2017 um 21:06 schrieb johannes hanika <hana...@gmail.com>:
>
> nice thanks! will give it a read!
>
> -jo
>
> On Mon, May 15
heers,
> jo
>
> On Mon, Jul 31, 2017 at 3:58 AM, Ingo Liebhardt <ingo.liebha...@ziggo.nl>
> wrote:
>> Hi Jo,
>>
>> In the meanwhile I applied FFTW, and I found some other ways to save
>> processing time.
>> All in all, processing time is now roug
code optimisation.
>
> cheers,
> jo
>
>
> On Tue, May 9, 2017 at 8:12 AM, Ingo Liebhardt <ingo.liebha...@ziggo.nl>
> wrote:
>> Hi Jo,
>>
>> OK, here we go, some measurements.
>> And I must admit that they are not too encouraging.
>&g
iso one shows quite a bit more
> pleasant noise behaviour in the gray center patch.
>
> how bad is the performance? do you think it could be improved? does it
> use SIMD/openmp yet and how promising would an opencl code path be?
>
> cheers,
> jo
>
> On Mon, May 8, 2017
. Code is still dirty and I
think there's potential.
I'd use FFT for convolutions. As said, some more info to come tomorrow.
Cheers,
Ingo
> Am 07.05.2017 um 20:48 schrieb johannes hanika <hana...@gmail.com>:
>
> hi,
>
>> On Mon, May 8, 2017 at 6:33 AM, Ingo Liebhardt
Hi Jo,
OK, here we go, some measurements.
And I must admit that they are not too encouraging.
see below...
> Am 07.05.2017 um 21:57 schrieb Ingo Liebhardt <ingo.liebha...@ziggo.nl>:
>
> The 30 sec are export time on a full res image.
> For darkroom mode, it's slo
See also "/home/ingo/src/darktable/build/CMakeFiles/CMakeOutput.log".
See also "/home/ingo/src/darktable/build/CMakeFiles/CMakeError.log".
- - - - -
Cheers,
Ingo
> Am 24.08.2017 um 17:27 schrieb Roman Lebedev <lebedev...@gmail.com>:
>
> On Thu, Aug 24, 2
On Thu, Aug 24, 2017 at 7:17 PM, Ingo Liebhardt <ingo.liebha...@ziggo.nl>
> wrote:
>> Hi all,
> Hi.
>
>> got a problem building, not only my fork, but also the upstream darktable
>> master.
>> Cloned a clean one to be sure, did the
>> git submodule update
17 matches
Mail list logo
