I would go for softening in drawn masks and feathering in the
variance-thresholded edge detection of the guided filter.
What happens in drawn masks is only outside the main outline, while the
guided filter is much less predictable in its behaviour (could be in,
could be out, could cross the
darktable modules are not merely GUI widgets, they are pixels filters,
or adjustment layers if you come from Adobe.
Do you go in Photoshop or in Gimp moving layers on the stack because you
prefer to have them sorted in alphabetic order ?
sob., 12 gru 2020 o 11:07 Wiktor Nowak
Hi,
the deprecated modules have alternative modules. These alternatives
solve the original design mistakes of the deprecated ones. (Full story :
fixing the originals would break compatibility of old edits, so we have
to start fresh).
Cheers,
Aurélien.
Le 16/11/2020 à 00:43, Jeronimo
1. that still doesn't give you the jpeg cooking recipe, which is more
complicated than building an ad-hoc LUT or a tonecurve if local filters
are applied (and there are),
2. what is it with people editing jpegs ? That's nonsensical ! Not the
same workflow, not the same maths, not the same
Hi,
Camera firmwares that convert raw to jpeg internally rely on proprietary
and undisclosed algorithms. Emulating these is not merely a game of
tuning input parameters, we need to reverse-engineer what algorithms
they use, in what color space, and in which order they are applied, and
repeat ×
the filmic. Is there a
> difference in the results?
>
> With respect,
> Alexander Rabtchevich
>
> Aurélien Pierre wrote:
>>
>> The required +1 EV exposure boost is now applied automatically in
>> exposure module for new edits if you choose the scene-linear workf
plugin v 4.0 manually, I need to
>> add +1.0EV manually too? That wasn't so with 3.0.
>>
>> With respect,
>> Alexander Rabtchevich
>>
>>
>>
>> Aurélien Pierre wrote:
>>>
>>> Hi,
>>>
>>> there is a +1 EV added by
Hi,
there is a +1 EV added by default in exposure if you enable the
scene-referred workflow. I don't understand what you mean. The exposure
bias is read in image EXIF, if the bias is 0 EV, then the setting is 0
EV too.
Cheers,
Aurélien.
Le 09/06/2020 à 19:46, Alexander Rabtchevich a écrit :
>
Hi,
this looks like your compiler is too old to support the simd:static
statement. What compiler and version are you using ?
Aurélien.
Le 02/06/2020 à 09:06, Peter Johnston a écrit :
> Hello,
>
> I am having a problem building darktable 3.0.2. I seem to be able to
> complete the cmake
Hello,
1. you go from RGB to XYZ using the ICC profile of the RGB space you
are using, which gives you the coeffs of the 3×3 matrix RGB -> XYZ.
Call that matrix M. Do a matrix dot product [XYZ] = [M] * [RGB]
2. you go from XYZ to Yxy using x = X / (X + Y + Z) and y = Y / (X + Y + Z)
3.
Hi,
image-processing modules *are not moved *up and down *in the GUI* but
*in the pixel pipe, *so that changes the actual order of application of
the corresponding filters. You are on for a lot of trouble if you handle
that as a workspace widgets reordering feature.
Reordering the (non
Hi Bruce,
the abscissa are log scaled, the ordinates are display-gamma scaled.
Happy New Year !
Aurélien.
Le 03/01/2020 à 20:08, Bruce Williams a écrit :
> Aurélien,
> Just seeking some clarification. Is the read-only graph in filmic RGB
> linear or log?
> Thanks in advance.
> Cheers,
> Bruce
Hi,
… and that's where the image processing pipeline mixed with people's
misunderstandings backfires.
What's HDR here ? The scene or the display ?
The image only encodes a scene-referred light emission with 0 and 1.
That scene-referred light emission has infinite dynamic range, with a
more
be delegated
> individually.
> @Aurélien - considering your name, I'm assuming you're a native French
> speaker - if the work is divided beforehand and it's easier for you,
> you could provide info in French to me as well.
> Best regards,
> Isabelle
>
> On Sun, Aug
Hi,
This is my video on filmic RGB, explaining how it works and how to do it
in real-life cases:
https://www.youtube.com/watch?v=zbPj_TqTF88=youtu.be I hope it
resolves most of the misunderstandings and trial-errors sessions that
always end-up in frustration.
A shorter addendum is on the way to
Filmic RGB works exactly the same as the old one, the changes are merely
cosmetic.
What does not work ?
Le 30/11/2019 à 03:46, David Vincent-Jones a écrit :
>
> It is unfortunate that the new 'filmic rgb' appears to act quite
> differently from the original 'filmic' and I have now lost the
business to
wire their state to user input, then their state to CSS rules.
Le 15/11/2019 à 21:33, Aurélien Pierre a écrit :
>
> Will have a look in the next few days.
>
> Le 15/11/2019 à 21:10, Nicolas Auffray a écrit :
>> Timur, see here for issue posted :
>> https://github.com
-to-day basis on darktable, and we are already swamped.
Le 18/11/2019 à 17:55, Julian Rickards a écrit :
> My apologies
>
> On Mon, Nov 18, 2019 at 10:58 AM Aurélien Pierre
> mailto:rese...@aurelienpierre.com>> wrote:
>
> Forget about segfaults and crashes, our first prior
Forget about segfaults and crashes, our first priority is now to make
every native English speaker feel respected in his difference and
identity, offering fully differentiated support of every English dialect
: en_GB, en_AU, en_US, en_ZA, en_CA, en_NZ, en_FJ…
Meanwhile, people speaking languages
darktable also lacks a board of investors, a CTO, a head of UX, a
project management, a panel of test users, a famous photographer as a
brand ambassador, many tracking features to collect statistics on usage
"to improve the performance", an annual coding sprint in the Bahamas and
a couple of
Hi,
the gamma module does not do what it says anymore. It's a leftover of dt
0.x before the output colour profile was added.
It has always been there but didn't appear in the history before. It
still doesn't appear in UI. I don't remember why we made every module
appear in the history now
Will have a look in the next few days.
Le 15/11/2019 à 21:10, Nicolas Auffray a écrit :
> Timur, see here for issue posted :
> https://github.com/darktable-org/darktable/issues/3445
>
> I'm now waiting for someone with GTK/Cairo skills.
>
>
> Le 15/11/2019 à 20:55, Nicolas Auffray a écrit :
>> I
Hi,
we never touch the raw files to avoid any risk of data corruption. There
exist precedents of exif edits permanently damaging raw files on saving,
possibly in DigiKam (you would have to ask Roman Lebedev about that, I
don't remember the specifics).
Aurélien.
Le 15/11/2019 à 21:26, Christian
Here : https://youtu.be/3FFU-Ltvm0I
Le 12/11/2019 à 14:46, Julian Rickards a écrit :
> This is great Aurélien, thanks
>
> On Mon, Nov 11, 2019 at 4:35 PM Aurélien Pierre
> mailto:rese...@aurelienpierre.com>> wrote:
>
> Every module advertises its input, output and wor
Every module advertises its input, output and working colour spaces to
the pixelpipe and conversion are done on-the-fly when needed. Don't
bother about it.
Yet, you still need to ensure you do the right pixel operation at the
right time. Details :
Hi,
atrous (contrast equalizer) is quite heavy on hardware and needs a lot
of memory to store the intermediate wavelets scales. I remember having
the same issue on my previous laptop (GPU Nvidia 635M, 2 GB too) with
certain updates of the driver.
Maybe you could try to decrease the memory
Hi,
filmic RGB works in a native RGB space, while the previous filmic worked
in a native Lab space and did the RGB conversion internally.
The difference is in the blending and masking options : old filmic had
(non-linear) Lab blending parameters, while filmic RGB has (linear) RGB
blending
Hi,
I have a PR waiting with a possible fix :
https://github.com/darktable-org/darktable/pull/3068
I have tested dt 3.0rc0 on Mac OS (temporary access to a MacBook) and
fixed the oversizing with dpi set to 80 too. But I reproduced. Same way,
the fonts in tone-equalizer are oversized.
But I have
Hi,
presets are just that : presets. It's hard to have them truly universal.
If you like other presets better, just save them.
Filmic RGB uses a different spline interpolation method that behaves
differently, closer to the densitometric curves of actual film emulsion.
But the previous presets
asecurve turned OFF)
>
> Christian
>
>
> Am 12.10.2019 um 22:29 schrieb Aurélien Pierre:
>> 2. if it expects gamma encoding, enable the "unbreak color profile"
>> module (mode set to "gamma", linear set to 0, gamma set to
>>
filters in one tool) and it brakes the one
> tool-one function philosophy, but IMHO it's a great help from a
> usability point of view. I missed it a lot when switched from
> AftershotPro to darktable.
>
> On Thu, Oct 10, 2019 at 10:06 PM Aurélien Pierre
> mailto:rese...@aureli
Hi,
1. Vibrance is supposed to be *{ RGB } = Y + saturation * ( { RGB } - Y
)^vibrance*, where Y is the luminance channel from XYZ space, and { RGB
} a pixel vector. This way, you perform both operations at once. Also,
using (R + G + B) / 3 instead of Y is generally not a good idea since it
has
Ok, let's go for a "sharpness score" + focus peaking feature. That way,
users will have a way to check which area is in focus, and compare
images between them with a score.
It won't made it to next release, but maybe first minor update.
Le 06/10/2019 à 17:05, Robert Krawitz a écrit :
> On Sun, 6
argh. Tales of over-engineering…
Just overlay the euclidean norm of the 2D laplacian on top of the
pictures (some cameras call that focus-peaking), and let the
photographer eyeball them. That will do for subjects at large aperture,
when the subject is supposed to pop out of the background. For
Hi,
We support GCC 8 and 9. GCC 6 is quite old already.
The commit you refer to affects only CLang.
Cheers,
Aurélien.
Le 06/10/2019 à 15:26, Marco Tedaldi a écrit :
> Hi Everyone
> After a long time away from this list (but still regularly working
> with git master) I'm back here...
>
>
>
That can be easily done by computing the L2 norm of the laplacian of the
pictures, or the L2 norm of the first level of wavelets decomposition
(which is used in the focus preview), and taking the maximum.
As usual, it will be more work to wire the UI to the functionality than
writing the core
Hi,
Image processing filters on raw pictures (even more now, with 24-52 Mpx
images) are really demanding on computational power (especially the
nicest ones, unsurprisingly), and darktable uses 32 bits floating point
arithmetic to perform them, in order to avoid most numerical issues you
would get
Hi,
for last 2.6 version, it took me a full-time week to write the doc for 3
modules, trying to accurately describe how they worked in a vulgarized
way, in my 3rd language. Instead, will it be helpful if I recorded
videos showing what's new and how it works (possibly in a
disorganized/non-linear
Hi,
someone needs to add preserve_colors in the dt_omp_firstprivate(…) in
the next line, to please GCC 9.
Cheers,
Aurélien.
Le 25/07/2019 à 11:48, Terry Duell a écrit :
> Hello,
> Attempting to do an rpmbuild of current master (e31d89cbff35b) on
> Fedora 30, fails with the following message...
e to
> another, there are some modules missing (input and output) and also,
> the "off" modules aren't included in the possible modules to copy over.
>
> On Thu, Jun 13, 2019 at 5:30 AM <mailto:dt-l...@stefan-klinger.de>> wrote:
>
> Aurélien Pier
general.
Le 13/06/2019 à 08:36, para...@paraf.in a écrit :
>
>
> On 12 Jun 2019, at 20:21, Aurélien Pierre <mailto:rese...@aurelienpierre.com>> wrote:
>
>> Hi,
>>
>> I'm the author of the lighttable's compress history button. White
>> balance and highli
Hi,
I'm the author of the lighttable's compress history button. White
balance and highlight reconstruction should never be turned off, so what
would be the purpose of having them disabled in the first place ? Then,
we can discuss what the history compression should do/avoid/prevent.
Aurélien.
The point of collapsing the histogram is to spare some room. Adding a
GUI control to do it is equivalent to using more space to save some
space. How does that solve anything ?
Remember keyboard shortcuts are user-configurable.
Le 31/05/2019 à 04:26, Patrick Shanahan a écrit :
> * David
It's coming in v 2.8 next Christmas.
Le 03/06/2019 à 14:32, Wiktor Nowak a écrit :
> When it's posible to have tone curve separated for L, A, B channels why
> it's not possible with RGB? I'm actually more familliar to think in RGB
> therms so it would be convenient to have an option aside that
ktable is important, to gain new users. If
> by default, without digging in the mailing list, you can't know what
> settings are wrong, you will have a bad first experience with DT.
>
> Just my two cents, it would be a pity to lose users because of this.
>
> François
>
ecurve off) vs filmic (basecurve off).
>
> So, filmic is better but I could not completely get rid
> of the green tint.
>
> Chris
>
>
>
> Am 28.05.2019 um 09:33 schrieb Aurélien Pierre:
>> For the last time :
>>
>> *BASE CURVES ARE EVIL, CRAP, GARBAGE, NO
> Film like response vs more creative curve editing, with its
> disadvantages) and one of the strong advantage of Darktable is
> allowing all these use cases. Starting a war about this won't get
> us anywhere in the issue at hand here.
>
>
> Le mar
For the last time :
*BASE CURVES ARE EVIL, CRAP, GARBAGE, NO-GO, DON'T TOUCH, BIO
HAZARD, KEEP AWAY, HUN HUN, SURVIVORS WILL BE SHOT AGAIN.*
I wouldn't have taken 2 months of my life to develop filmic if base
curves had worked as expected. Base curves are a broken design and will
always
darktable handles the matrices all the same way. It's simple linear
algebra, if it works for some matrices, it will work for all matrices.
But if the coefficients of the matrice are wrong, nothing magical will
happen.
Le 25/05/2019 à 21:11, Christian a écrit :
> Hi,
> I re-did the test with the
So the input color profile (camera RGB -> XYZ transformation matrice) is
wrong in darktable. Can you export an ICC input profile from whatever
software the good picture comes from ?
Aurélien.
Le 24/05/2019 à 20:40, William Ferguson a écrit :
> Perhaps a better check for color accuracy is
Hi,
that's the problem I got with filmic. Once the wall of the non-linearity
is crossed, there is no coming back, so all you can do is move your
module to the right place in the pipe.
Basically every filter dealing with physical phenomenons (diffusion,
refraction) should be put in the linear
Hi,
please don't do a deconvolution in the Lab color model. Natural blur is
a phenomenon happening to photons and described by a convolution
product. If you want to revert it, you need to use a physically
meaningful color space, e.g. a linear one as close as possible to the
spectral space.
That
Hi,
there are lots of visual artifacts that can result from
background/foreground contrast and the surround lightness adaptation.
Please note that :
* darktable UI is currently under clean-up to wire every color and
font-size to the CSS sylesheet :
Hi,
I have deleted by accident a bug report on Redmine, by Martin Straeten
(IIRC). Is there any way to restore it ?
My apologies, I thought the "delete" option applied to the (spam)
comment, not to the whole issue. It's not clear when there is only one
comment on the issue.
Aurélien.
Hi everyone,
I was advised to watch this presentation regarding color transform for
HDR displays from the Society of Motion Picture Engineers :
https://www.youtube.com/watch?v=Z0DS7cnAYPk=youtu.be
It applies to HDR images processing as well and sums up pretty much all
my work around Filmic
On a side note, I would suggest to reach out developers from other
projects. While developing filmic, I worked with Troy Sobotka (Blender),
now Andrea Ferrero (Photoflow) is working with us on implementing the
same feature for his soft, so we share results and algos. Ingo Weyrich
(Rawtherapee) has
Hi,
there is a less sexy project that would unlock a lot of others,
regarding the rewriting of the metadata handling. Currently, EXIFs are
handled by a C++ class (exiv2) manipulated inside C wrappers functions
(instead of private methods), which actually mixes the drawbacks of both
functional and
Hi everyone,
I have noticed several people have reported bugs in darktable 2.6 rc0
and rc1 by replying to other messages on the mailing list, sometimes
unrelated. This makes it difficult to sort the bugs, assign them to the
right developer and track their fixing state.
Please use
Hi,
exposure comes before filmic in the pipe. That means everytime you
change the exposure, you wrong filmic settings (black, grey and white
levels). You should always follow this order:
1. disable base curves,
2. adjust the white balance,
3. fix the exposure (avoid clipping in blacks and in
Le 24/11/2018 à 04:51, David Houlder a écrit :
> On 24/11/18 3:22 am, Aurélien Pierre wrote:
>>
>> Hi everyone,
>>
>> my darktable is installed on Ubuntu Budgie (fork of Gnome 3), but it
>> was the same when I used Gnome Shell. I have a custom screen ICC
&g
Hi everyone,
my darktable is installed on Ubuntu Budgie (fork of Gnome 3), but it was
the same when I used Gnome Shell. I have a custom screen ICC profile
installed in gnome-color-manager, and loaded in darktable through colord.
When I change the ICC profile on Gnome with darktable open, the
Hi,
having Redmine bug tracker and Github PR apart makes it unnecessarly
complicated to follow/reference bugs and PR/fixes, or to ping people.
Wouldn't it be better to switch to Github issues tracker, wiki and such ?
Cheers,
Aurélien.
My bad. I'm on that. Sorry.
Le 04/11/2018 à 14:12, Ulrich Pegelow a écrit :
> Same here. With and without OpenCL.
>
> Am 04.11.18 um 19:58 schrieb Alexander Rabtchevich:
>> Current git produces corrupted image if export settings require
>> downsampling. Mint 19 x64 Mate. Memory is enough.
>>
>>
ave gamma and cbrt().
>
> Cheers
> Jo
>
> On Sat, 3 Nov 2018, 10:05 Andreas Schneider, <mailto:a...@cryptomilk.org>> wrote:
>
> On Saturday, 3 November 2018 09:59:23 CET Andreas Schneider wrote:
> > On Friday, 2 November 2018 21:10:33
of the pipeline in gui mode can take place here. it's
> certainly not applying gamma. i suppose we could delete these old
> gamma lut table lines of code and just round directly in process().
>
> cheers,
> jo
> On Thu, Nov 1, 2018 at 3:52 PM Aurélien Pierre
> wrote:
>> Hi
Hi,
there is in dt an hidden IOP named gamma.c that is the last one in the
pixelpipe. Looking at the code, it is useful to display the masks and
convert the pixels to uint8 values.
However, it does a gamma conversion too, with a linear and gamma
parameters. First of all, this conversion seems
Hallo Heiko !
Very pleased to hear that (not the bug part, though).
Did you try with smaller pictures ? Usually, darktable falls back to CPU
when there is not enough ressource available on the GPU.
You can try :
1. the command *nvidia-smi* to see how the GPU RAM is used (if there is
not
ypted.pcode.nl/blog/2010/06/28/darktable-camera-color-profiling/>,
and never ever use the default base curves.
> I am just wondering how having a default base curve fits in with your
> editing paradigm?
>
> Sincerely,
> Jason
Thanks for your input,
Aurélien.
> On 2018-10-25 08:28 PM, A
have any questions or do you need someone for proof reading, do not
> hesitate to ask.
>
> Pierre
>
> Am Donnerstag, 18. Oktober 2018, 23:46:50 CEST schrieb Aurélien Pierre:
>> Hi everyone,
>>
>> My 2 pull requests have been merged into master, I'm very happy about
Hi everyone,
My 2 pull requests have been merged into master, I'm very happy about
it. These tools are very powerfull but certainly not intuitive and need
a proper tutorial.
Could I get access to darktable.org blog so I can write a full tuto in
English ?
Thanks,
Aurélien.
Le 10/10/2018 à 00:14, William Ferguson a écrit :
> On Tue, Oct 9, 2018 at 7:18 PM Aurélien Pierre
> mailto:rese...@aurelienpierre.com>> wrote:
>
> What I call "signal-processing" here are all the module intended
> to clean the data and turn an (al
What I call "signal-processing" here are all the module intended to
clean the data and turn an (always) damaged picture into what it is
supposed to look like in theory. That is :
1. reconstructing missing parts (clipped highlights)
2. recovering the dynamic range (tonemapping)
3.
But even if we keep the actual disposition, don't you think it's weird
that :
* in/out color profiles are stored in the color tabs, whereas they are
"basic" in the sense they are needed from technical requirements and
always on,
* signal-processing modules are mixed with creative ones
have to
set following rules (signal normalization and restoration) and the ones
you are free to use as you wish.
Le 08/10/2018 à 02:53, Andreas Schneider a écrit :
> On Monday, 8 October 2018 03:06:34 CEST Aurélien Pierre wrote:
>> Hi everyone !
> Hi Aurélien,
>
>> I
Le 08/10/2018 à 00:42, Jochen Keil a écrit :
> Hi,
>
> On Mon, Oct 8, 2018 at 5:39 AM Aurélien Pierre
> wrote:
>> The real question here is : could you get past the change and benefit from
>> it ?
>>
>> I'm biased here, since I developed repetitive strain
ting do I even consider
> spending time on noise reduction and lens correction as there is not
> much point on noise reduction in the bad images.
>
> Personally, I have found after a couple months it's easy to remember
> where all the modules are and changing it would only make it wors
Hi everyone !
I would like to propose a lifting for the UI in the darkroom.
*Problem**
*
Currently, the modules are separated in 5 tabs :
* base
* tones
* colors
* enhancements
* effects
But :
* some modules in the color group affect the tones as well
/1734
If someone wants to finish the color wheels, you just have to map the
radius to what is passed to the current saturation slider, and the angle
to what is passed to the current hue slider. The maths are ready and
working.
Have a nice day,
Aurélien.
Le 21/09/2018 à 20:32, Aurélien Pierre
results for color-grading with this module, it's always
too harsh. I don't know if it is because of the color space of the
lift/gamma/gain transfer function.
Le 21/09/2018 à 21:11, Per Inge Oestmoen a écrit :
> Aurélien Pierre wrote:
>
>> On another note, is it mandatory to make the adjuste
ncouraging. 660EUR for a bounty that shouldn't
> take you more than your sunday afternoon to fix sounds like a good
> deal. now we'll also have to work on the conditions of our daytime
> jobs to free up time. this should be possible.
>
> cheers,
> jo
> On Mon, Sep 10, 2018 at 7:5
Thanks Jo !
so now I'm working on the OpenCL port. I have this function in the IOP :
#ifdef HAVE_OPENCL int process_cl(struct dt_iop_module_t *self,
dt_dev_pixelpipe_iop_t *piece, cl_mem dev_in, cl_mem dev_out,
const dt_iop_roi_t *const roi_in, const dt_iop_roi_t
*const roi_out) {
hat C is hard to learn, so congratulations Aurélien! :-)
Thanks ! I have posted the first results :
https://discuss.pixls.us/t/solving-dynamic-range-problems-in-a-linear-way/9006
>
> rawfiner
>
>
> Le mer. 12 sept. 2018 à 14:46, Aurélien Pierre
> mailto:rese...@aurelienpierre.com&
Hi everyone,
when working with color profiles, the main historic issue was the
non-linearity of the sensors/films. Now, it is rather that the color
profile is performed on a chart having 6-7 EV of dynamic range while
modern cameras have 12-15 EV. Simple gamma corrections (invented for CRT
Hi everyone !
Doing some cleanup on Redmine, I see bugs and feature requests are
sorted by categories, which are the place where they occur (lighttable,
darkroom, Lua, masks).
I would like to propose an additional taxinomy, for example as tags, to
narrow the field of expertise they require :
h. somehow the
> core issue seems to be senior dev time to me.
>
> cheers,
> jo
>
> On Sat, Sep 8, 2018 at 7:24 AM Aurélien Pierre
> wrote:
>> Hi everyone,
>>
>> looking at the Redmine feature requests, it seems that a lot of legitimate
>> requests are left
Do the (hard)core devs need more help reviewing merge requests ? How
could we solve that issue ?
Le 08/09/2018 à 05:02, Andreas Schneider a écrit :
> On Saturday, 8 September 2018 07:24:51 CEST Aurélien Pierre wrote:
>> Hi everyone,
> Hi Aurélien,
>
>> Shouldn't w
Hi everyone,
looking at the Redmine feature requests, it seems that a lot of
legitimate requests are left idle, and some have been so for several
years, generating duplicates. Most of these features are cosmetic User
Interface improvements or making variables writable, such as :
* delete some
Hi,
I'm using a 3D (6 axes) mouse in dt on Ubuntu to zoom and set the size
of the drawn masks. On my system, I'm not using the natural scrolling,
meaning that the scrolling moves the view, not the content.
In dt, I have to scroll to the bottom to increase the masks size (and
scroll to the top to
Hi,
I don't think threaded jobs would be of much use here, since the image
processing is already parallelized at the array level. The OpenCL
interface should already use all the available cores of your GPUs on one
single image at the time. What you suggest would, I think, degrade the
overall
Also, a thing I have thought about for a while would be the ability to
give names/titles to modules and especially their instances. Checking
online, it's been on for 2 years :
https://redmine.darktable.org/issues/10935
Le 29/07/2018 à 10:32, Marek Jędrzejewski a écrit :
> I think it would be
-zero values
> only for pixels that are detected as noise both by TV and Laplacian.
> Is there a particular reason for multiplying (or did I misunderstood
> something?), or could we take the maximum value among TV and Laplacian
> for each pixel instead?
>
> Thanks again
>
>
%20Variation%20masking.ipynb
Performance benchmarks are at the end.
Cheers,
Aurélien.
Le 17/06/2018 à 15:03, rawfiner a écrit :
>
>
> Le dimanche 17 juin 2018, Aurélien Pierre <mailto:rese...@aurelienpierre.com>> a écrit :
>
>
>
> Le 13/06/2018 à 17:31, rawf
Le 13/06/2018 à 17:31, rawfiner a écrit :
>
>
> Le mercredi 13 juin 2018, Aurélien Pierre <mailto:rese...@aurelienpierre.com>> a écrit :
>
>
>>
>> On Thu, Jun 14, 2018 at 12:23 AM, Aurélien Pierre
>> > <mailto:res
>
>
> also, i usually use some blending to add the input buffer back on top
> of the output. this essentially leaves the grain alone but tones it
> down.
>
>
> I do the same ;-)
Me too
>
>
>
> cheers,
> jo
>
>
> On Thu, Jun 14, 2018 a
Hi,
The problem of a 2-passes denoising method involving 2 differents
algorithms, the later applied where the former failed, could be the
grain structure (the shape of the noise) would be different along the
picture, thus very unpleasing.
I thought maybe we could instead create some sort of
hal-01342111/
*
https://joandurangrimalt.wordpress.com/research/novel-tv-based-regularization/
--
*Aurélien PIERRE*
aurelienpierre.com <http://aurelienpierre.com>
_
Am Dienstag, 2. Januar 2018, 19:29:54 CET schrieb Aurélien PIERRE:
>> because I'm able to deconvolve it :-P
> I'd like to challenge that claim. Please deconvolve this image:
>
> https://houz.org/tmp/img_0001.pfm
Never challenge the power of my algorithms :
https://photo.aureli
because I'm able to deconvolve it :-P
*Aurélien PIERRE*
aurelienpierre.com <http://aurelienpierre.com>
Le 2018-01-02 à 12:44, Pascal Obry a écrit :
> Le mardi 02 janvier 2018 à 12:38 -0200, Jefferson Ferreira a écr
cal target. I had to adjust them
individually, using the absolute target color, which is not what you
want to do on 48 patches.
I wonder if there is any ways to prevent darktable-chart from generating
tone curves and force it to only adjust the LUT ?
Thank you !
--
*Aurélien PIERRE*
aurelien
?
Thanks,
--
*Aurélien PIERRE*
aurelienpierre.com <http://aurelienpierre.com>
signature.asc
Description: OpenPGP digital signature
1 - 100 of 141 matches
Mail list logo
