I suppose you could just set auto for CC to be inactive, AGX or Sigmoid to be inactive and WB to as shot and then you would be there with scene blend modes I think and you could activate the other components as needed…I guess you would then have to revert the wb to as shot to reference…
I guess the utility in all that would be weighed by how often you want that to be the default starting point…
Yeah, I use ‘none’ workflow default and only noticed this recently too. Easy to cause problems because some blend modes in display blending clip anything above display 100%.
Now I’m wondering if a ‘tonemapper off’ preset would be a better idea for me, I always start with CC default anyway. Have to use a key shortcut for ‘reset’ on CC because it doesn’t initialise properly as a preset. Same with white balance for different cameras because presets don’t save the ‘camera reference’ button, only the primary coefficients. Exposure is always a custom amount but that black level correction also gets baked in
Here’s another issue I’ve wondered about for many years, even though I feel the answer should be obvious: how to easily reuse (copy) a drawn mask but one that isn’t linked to the original.
It seems there are at least 4 ways to reuse a drawn mask:
1- “Add existing shape” dropdown option
2- “Use same shape as” dropdown option
3- use a raster mask (not technically the same)
4- use the Mask Manager to duplicate shapes
The first three options are linked to the original shape, so changes made to it will affect the original mask in the original module.
So, as far as I can tell, the only way to reuse an existing shape, not linked to the original mask and module, is to use the Mask Manager. You have to find the shape in the list at the bottom, right-click and choose “duplicate shape”. Then in the module you want to reuse the shape, you can then choose the “Add existing shape” option to choose the duplicate.
Am I missing some more obvious way of doing this? I feel like there should be a way of doing this within a module or using copy/paste, without using the Mask Manager.
Is this a bug or a feature? Every time I change images, the history panel gets under the preview and I need to scroll it up again. It’s starting to be extremely annoying, any config to deal with this? Such as auto scroll the panel up when opening a new image, or similar
Is there an easy way to define a shortcut to create a new instance of a module and apply a specific preset to that instance? Or will I have to lua-script that?
Depends on what you’re doing. If you’re using it for white balance (with a mask), both should be the same as the first instance. In all other cases illuminant should be D50, while the adaptation can be whatever makes sense, since it affects all the other tabs as well. All the monochrome presets use XYZ, for example.
The default order is optimised for “normal” photos, so negative inversion may well need to have some modules moved. More generally, the order is such that the scene-linear relationship is preserved for as long as possible and, if you work bottom-up, you will always get predictable results with a minimum of back and forth.
Andy Hutchinson has a good video on this:
And Erik Lenz has some that are also very good:
I haven’t looked into it, but I imagine this has something to do with the different color spaces used. CC RGB uses darktable-UCS, but that is unlikely to perfectly match whatever the vector scope uses.
That’s not how it works. If you shoot raw, you don’t get the camera JPEG look and will have to process the photo yourself. Doesn’t matter what kind of look you want. The RawTherapee documentation has a good explanation: Editor - RawPedia
Shouldn’t snapshots be above that…its working fine for me on Win11 ie I dont’ see that behaviour…have you made any css or other UI changes that could introduce that??
i wanted to expand on this to reflect what ive learned thanks to this thread and realized that even tho i understand better now, i lack the words to explain it properly. but heres a try:
the vectorscope RYB space is not uniform across colors, and that makes that when making changes in CB RGB working space, which i belive is uniform, to reflect a non uniform transform in the vectorscope.