Copy and paste the history stack. See darktable user manual - history stack
If you’re not happy with it, just make your own preset.
I like the idea, and it seems to do a good job (at a quick glance). What I don’t like is having to follow the tree of manufacturer/family/model.
I think I solved my own problem. I exported my camera style to a file. I changed the name of the file, but reimporting it only gave an exists-already message.
Looking at the file contents, I changed
<name>_l10n_darktable camera styles|Sony|ILCE...|ILCE-7M4</name>
to
<name>Sony-A7iv</name>
And now it is sitting as a single item in the styles list. I hope I haven’t done anything technically wrong with my ignorant small hack?
Don’t know how much I’ll use it, though: I really like darktable+Sigmoid’s starting point. But it seems like a good tool to have in the box.
You can also select a style, click Edit, check the duplicate check box, edit the name, then click save.
1 Like
In 5.0 also don’t miss the new feature, you can select multiple images on the filmstrip and while editing an image just press Ctrl+x to synchronize the last module edited to all selected images.
2 Likes
If you can do better on most images, you can certainly contribute a new style. Just post on GitHub the style and some examples to show us why it is better.
1 Like
Thank you, I missed/misunderstood that.
No, I didn’t mean better than dt’s “like the raw file.” I meant “more to my taste.” That is to say that I prefer dt’s starting point plus a little work, to the raw file or dt’s interpretation. But it is good to have that available. 
I think this can be used to upgrade the module order to v5. But I don’t think it exists in light table (unless I am doing something wrong). It is a good feature.
Did you know you can assign shortcuts to styles? Then you don’t need to select them in the module.
- Find the style
- Double-click it
- Press the desired shortcut (key combination)
Double-click on a style name to apply that style to all selected images. A style may also be applied to all selected images by pressing a shortcut key assigned to it (see preferences > shortcuts) while in the lighttable or darkroom view.
(darktable user manual - styles)
2 Likes
I am running MacOS on M2 Ventura 13.4.1 machine. Which image I should use:
darktable-5.0.0-arm64-13.5 or darktable-5.0.0-arm64?
The styles are just an exposure tweak, local contrast, filmic and rbg colorbalance… You can apply the style to what you would consider a good test image or a colorchart and then make an adjustment in one or all of those and then save your style…there is no magic or model to tweak…its just a custom set of adjustments per camera worked out by a dev using those modules to try and give a best guess start for images from a certain camera…
2 Likes
I’m very happy! Just afraid I’m not using it right, 
I notice that there is a discrepancy between the styles for Olympus E-M1 mk 2 and mk 3, (the first one having an instance of color rgb), which immediately may appear somewhat strange since they have the same sensor. But I guess then, that this may possibly be influenced by different images used for the definition of the cameras’ styles.
1 Like
I installed the new 5.0 Windows version last night, and I gotta say that I like it.
Took a couple of edits to familiarize myself with it, as my workflow was all based on experience with the 4.x versions…so not a massive relearning curve based on what I was used to.
I’m looking forward to trying out the composite module some time soon.
@priort @Pascal_Obry Thanks both for your explanations and suggestions - I’m sorry but DT is complicated for newbies
I now understand how styles work. Looking at my particular case (Nikon Z6, I use a random image, the style applies changes 12 to 17 in the history), I can see that Filmic RGB is applied twice (same parameters with just an addition in the second one) and then Sigmoid on top of it.
Sigmoid doesn’t change anything to the photo,
then the style makes meaningful changes after the first RGB application: see photo below
(valid until 1/28/25)
but it gets too heavy (I think) when RGB is reapplied on top of it with the same parameters: photo 2
(valid until 1/28/25)
Now that I get it, I can customize the style for my taste starting from the values you give, which is great! Just not sure if this kind of issue is worth discussing with the community, and if yes where is the best place?
the official builds requires at least macos 13.5. So for 13.4.1 you can use the arm64 build from darktable 5.0.0 for older macOS versions (10.14 & 11.0). This supports all macOS versions >=11.0
You must have had a camera-default style that was applied in addition to the new defaults. Happened to me, too. In the end, you should only ever have one instance of Sigmoid/Filmic/Basecurve.
The history stack, which is in your screenshot is the order in which you applied or changed a module; it is not a count of how many instances of the module you have.
You need to look at the “power” panel on the right hand side to see how many instances you have.
2 Likes
The different cameras may have the same sensor, but that doesn’t mean they have the same firmware. Which can mean differences between the processing on the three cameras, with differences in the final jpegs.
2 Likes
Maybe/sort-of I knew. Never tried it, though. Thanks!