On Fri, May 12, 2017 at 7:09 PM, Alexander Rabtchevich <alexander.v.rabtchev...@gmx.net> wrote: > I know well what is Bayern pattern and how demosaicing works ;) . In > previous discussion I was told the time spending was due raw denoise,
> Two opearations during regular jpg export do not use OpenCl - > raw demosaic (or decompression) and applying of final gamma Ah, well, "raw demosaic (or decompression)" sounds kind-of gibberish, non-raw demosaic makes no sense, so i just assumed that you meant "raw denoise" But regardless, amaze demosaic algo is also not implemented in opencl, and to be honest, without prior knowledge about internals of the algo, and thus, possibility of the implementation) i don't really expect it to be implemented in opencl, at least in any near future. > not > demosaic. And there is no raw denoise active settings in demosaic module, > maybe except the AMaZe algorithm itself. > > > With respect, > Alexander Rabtchevich Roman. > Joel Brunetti wrote: >> >> Demosaic is the process of going from three pixels (one each for red, >> green and blue) beside each other on the camera sensor to a single RGB >> pixel. >> >> On 12 May 2017 at 09:44, Alexander Rabtchevich >> <alexander.v.rabtchev...@gmx.net> wrote: >>> >>> Could you correct me one more time - does "demosaic" mean raw denoise? >>> >>> [dev_pixelpipe] took 0.000 secs (0.000 CPU) initing base buffer [export] >>> [dev_pixelpipe] took 0.040 secs (0.020 CPU) processed `raw black/white >>> point' on GPU, blended on GPU [export] >>> [dev_pixelpipe] took 0.006 secs (0.012 CPU) processed `white balance' on >>> GPU, blended on GPU [export] >>> [dev_pixelpipe] took 0.004 secs (0.008 CPU) processed `highlight >>> reconstruction' on GPU, blended on GPU [export] >>> [dev_pixelpipe] took 1.007 secs (3.816 CPU) processed `demosaic ' on >>> CPU, >>> blended on CPU [export] >>> [dev_pixelpipe] took 0.208 secs (0.000 CPU) processed `orientation' on >>> GPU, >>> blended on GPU [export] >>> [dev_pixelpipe] took 0.014 secs (0.000 CPU) processed `base curve' on >>> GPU, >>> blended on GPU [export] >>> [dev_pixelpipe] took 0.009 secs (0.000 CPU) processed `input color >>> profile' >>> on GPU, blended on GPU [export] >>> [dev_pixelpipe] took 0.020 secs (0.000 CPU) processed `sharpen' on GPU, >>> blended on GPU [export] >>> [dev_pixelpipe] took 0.019 secs (0.004 CPU) processed `output color >>> profile' >>> on GPU, blended on GPU [export] >>> [dev_pixelpipe] took 0.644 secs (0.356 CPU) processed `gamma' on CPU, >>> blended on CPU [export] >>> >>> AMaZe settings are: color smoothing off, match greens disabled. >>> >>> With respect, >>> Alexander Rabtchevich >>> >>> >>> >>> >>> Ulrich Pegelow wrote: >>>> >>>> Am 12.05.2017 um 08:21 schrieb Alexander Rabtchevich: >>>>> >>>>> Hello >>>>> I've installed a new graphics card with Radeon 580 chip (8Gb) and so >>>>> examined darktable performance. Two opearations during regular jpg >>>>> export do >>>>> not use OpenCl - raw demosaic (or decompression) and applying of final >>>>> gamma. Their common time equals or even prewails a whole bunch of all >>>>> other >>>>> operations. The OpenCl setting in GUI is - powerful graphics card. Is >>>>> there >>>>> a way to increase the performance? Darktable is from current git. >>>> >>>> >>>> Absolutely! You could just write the needed OpenCL processing code for >>>> raw >>>> denoise. >>>> >>>> Concerning gamma: this is the last module in the pixelpipe. Latest in >>>> that >>>> module we need all data been transferred back to CPU memory. The time >>>> that >>>> darktable reports to spend in this module is an artifact. The reason is >>>> that >>>> the GPU and the CPU run idepenently. The CPU code just registers the >>>> needed >>>> GPU calls and then waits until the GPU terminates. This waiting happens >>>> (among other places) in module gamma. If you need to see the real >>>> timings >>>> you could set opencl_async_pixelpipe=FALSE. This way darktable will wait >>>> for >>>> OpenCL processing to finish after each module. >>>> >>>> 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
