Spektrafilm analog film simulation module - #21967
Conversation
|
@kofa73 this should address all the issues your bot found |
|
Is each of your commits compilable? |
|
Yes, this should be true as I manually test each one before in my PKGBUILD and do local testing |
e950b50 to
d648a87
Compare
|
This is a new module, I'll squash all commits together anyway. |
|
will do a bit of UI changes later today, then I'll collect presets |
|
Note that I did not ask the bots the compare that the processing algo matches Spektrafilm (they were told to look for generic maths issues like NaN). Let me know if you need that reviewed. |
|
Thanks, I already have a script for that myself |
83e0af5 to
0da246e
Compare
bfba93f to
74c3122
Compare
|
latest commit moves out of the way for #22042, will update once the linked PR is merged |
Ah, funny incident that we did essentially the same thing for different reasons 😁 |
|
happy to give the 42 to you ;) |
|
I hope you'll not get angry about another opencl program appearing in another PR soon 😬 |
7521079 to
d0b4e9c
Compare
now that the 42 is gone it doesn't matter anymore :D |
Ah, now I get it, sometimes it takes a while for me 😅 |
The upstream PR moved: #21534 was closed by accident and superseded by darktable-org/darktable#21967 (same piratenpanda spektrafilm branch). Two runtime changes ride along with the bump: - The data pack repo moved to the darktable.org-managed darktable-org/darktable-spektrafilm (module default SF_DEFAULT_REPOSITORY changed with it). data-pack.nix now mirrors that repo; the pack content is byte-identical (lut_hash 565f4ec4, pack_format 2, pack 0.3.3). - Packs now resolve under g_get_user_data_dir() (~/.local/share/darktable) instead of the config dir, so the runtime wrapper links the pack there. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TTw3vKZxSvgXYh2E4P6ZFE
4f2c158 to
7c97cab
Compare
43109ea to
6b6dcd6
Compare
|
Ready from my side except from a final dtdocs update and the release notes entry |
|
I have no strong opinion on it so I'll do whatever you prefer @TurboGit |
|
No strong opinion on my side either, just wanted to be sure this point was properly discussed. So if some users may use Darktable for this only, let's add a specific workflow for it. I would prefer in this PR if possible. |
562cd29 to
e75453c
Compare
|
all fine from my side, will build with 19657 tonight and test locally |
TurboGit
left a comment
There was a problem hiding this comment.
Please review all tooltip, we have:
Note the missing dot at the end. For all paragraph we need a dot. A dot is omitted only for single line title (for example the tooltip for "halation strength" is ok as a single line title).
Also not sure the -- on the middle of the text is a correct English typography? If yes, keep it otherwise we could use dot here I suppose.
Those comments apply to many tooltips.
|
@piratenpanda : This time I have tested the following scenario:
So all good, we are very close to merging. |
34f62f7 to
84a3fec
Compare
|
reworked tooltips and squashed commits |
e61bd04 to
082d5b3
Compare
082d5b3 to
0604a48
Compare
|
fixed some more stale comments |
|
Will rename function names according to #22150 |
|
I moved the coefficients into common/gaussian. I'll leave the commit for review and then I'll squash. I think the weighted Gaussian bank can be made common as well, but I think this can also happen after this is merged and I would opt to not delay this further. |
TurboGit
left a comment
There was a problem hiding this comment.
We are good I'd say now. Let's move forward and merge this for more field testing before the release. Thanks for the hard work on this new module!
|
@piratenpanda : Great job! Thank you. |
|
@piratenpanda Thanks alot! 🙏 |
|
I'd improve a bit release note for this module - explain that this module is actually a tone mapper, not just creative effects module. And maybe move it up in the list as it is the biggest feature as of now. |
|
Thanks, typical understatement me :D See #22161 |
|
Tried this just now, absolutely great! |
after my git mistake, here's another PR. Sorry for the noise. Continuing from #21534