Definitely this doesn't touch the HDR module. Calculating an HDR image
from x-trans data may even work with the existing Bayer math. The
challenge then being to write the results in some form which darktable
can turn around and read. Perhaps this would mean teaching dt to write
DNGs with the x-trans sensor's CFA pattern and then adding reading of
such DNGs to RawSpeed... I'm happy to look into this more.
On Tue, Jan 19, 2016, at 07:20 PM, Robert William Hutton wrote:
> It's my understanding that the HDR module relies on Bayer pattern data,
> so no.
>
> -R
>
> On 20/01/16 03:18, David Vincent-Jones wrote:
> > Will the merge now permit X-Trans raw images to be used in the HDR module?
> >
> > David
> >
> > On 01/19/2016 08:42 PM, Ulrich Pegelow wrote:
> >> Hi,
> >>
> >> I just merged my OpenCL implementation of the Markesteijn demosaicing
> >> algorithm into master. Markesteijn with one or three passes ("-1" and
> >> "-3", respectively) is darktable's preferred method for demosaicing
> >> images of cameras with Fuji's X-Trans sensor.
> >>
> >> The algorithm is rather complex and has a significant memory overhead.
> >> Therefore the performance advantage over the already well established
> >> CPU codepath will depend a lot on the GPU hardware. In my case (AMD
> >> Radeon HD7950) I get roughly a 2 times faster processing compared to
> >> my i7-2600@3.4GHz.
> >>
> >> But that's just one system. Slower GPUs might even underperform versus
> >> the CPU. I would like to gather more benchmarking data in order to
> >> decide if the OpenCL codepath for Markesteijn should be enabled by
> >> default or not.
> >>
> >> So if you are running master and if you have a working OpenCL system I
> >> am highly interested in your comparison of OpenCL versus CPU speed.
> >> Please start darktable with '-d opencl -d perf' and do a few test:
> >>
> >> 1) with OpenCL enabled in preferences
> >> 2) with OpenCL disabled in preferences
> >>
> >> Please perform:
> >>
> >> a) exporting an X-Trans image with default history stack
> >> b) as above but now with demosaic set to Markesteijn-3
> >>
> >> Don't forget to tell me your hardware setup (Graphics Card, GPU
> >> memory, CPU type, system memory).
> >>
> >> I am also interested how reactive darktable acts in darkroom mode if
> >> you pan the image or change some module parameters (take exposure
> >> correction as an example). Please zoom into the image with a zoom
> >> level of 67% or a bit more. This test is more about "look and feel"
> >> rather than an exact measurement. Does darktable react more "snappy"
> >> with OpenCL or just the opposite?
> >>
> >> If you don't have an X-Trans sensor raw at hand you can download one
> >> from here:
> >>
> >> https://www.dropbox.com/s/gef9qkapkktrjn5/DSCF6768.RAF?dl=0
> >>
> >> Thanks for your support!
> >>
> >> Ulrich
> >>
> >> ___________________________________________________________________________
> >>
> >> darktable developer mailing list
> >> to unsubscribe send a mail to
> >> darktable-dev+unsubscr...@lists.darktable.org
> >>
> >
> > ___________________________________________________________________________
> > darktable developer mailing list
> > to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
> >
> ___________________________________________________________________________
> darktable developer mailing list
> to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
