The main difference in what you will see in the UI is shown here…the math is done differently wrt saturation…as you will see no more curve for it and midtone saturation is now replaced with a slider to tweak extreme luma saturation…
Where do I look to see option for v3 v4 v5 v6?
Ok I spotted it in color science!
Many thx
Options…where you change the norms…and it you have never used those well you are in for a surprise…changing them changes the whole output…added as an edit in my first reply
Set the norm to be the same and then toggle v5 and v6 to look for any differences…
Original post edited, thanks
Thanks
Keeping in mind Kofa’s comments about the normal process of setting up a build and updating it using git pull…you might want to consider removing this paragraph. I think it could be confusing esp to new users, an audience that your post would be targeting… Just a thought…
Are these steps safe to follow without uninstalling current dt master (from opensuse repository)? Ie. keeping current install as is?
Do the steps to build sigmoid work for current master from opensuse (therefore can skip steps 1.1>1.13)? And if so, can similar steps be worked for new filmic v6?
@Soupy , I know nothing about opensuse I’m afraid, someone else will have to answer.
Re. your second point, current master includes filmic V6, if that helps.
Many thanks for these instructions. I found them very helpful in going back a few versions because of an issue.
1 Like
Personally I would just follow 4.0…simple to do. Pick a directory different from you currently installed version…
If you want to reset the master its easy to do…removing sigmoid for future builds…
Basically the same as described by @phweyland
chhil.pdf (114.5 KB)
I’m following 4. @phweyland way but after typing git submodule update, it hangs on
Cloning into ‘/home/tim/darktable/src/tests/integration’…
Any ideas?
Has it hung, or just taking a while? The test data is big, takes a while, best to do the suppression command.
Not sure. I gave it half an hour. Cloning into the submodules before it only took a few minutes max, so I assumed something was up. No idea what the suppression command is. Is the test data essential or can I carry on without it?
You don’t need the test data, I think it’s what the devs use for testing. The command is 1.9 in my process.
1 Like
Back at it today and a new error:
tim@timmint:~/darktable/build$ cmake -DCMAKE_INSTALL_PREFIX=/opt/DT/
CMake Warning:
No source or binary directory provided. Both will be assumed to be the
same as the current working directory, but note that this warning will
become a fatal error in future CMake releases.
CMake Error: The source directory “/home/tim/darktable/build” does not appear to contain CMakeLists.txt.
…Checking my folders, I notice CMakeLists.txt has been created in /home/tim/darktable. I have no idea why it is there instead of in /home/tim/darktable/build… Indeed the /build folder is empty. I simply followed @phweyland instructions exactly, only adding in git config submodule.src/tests/integration.update none (which worked) as discussed above.
How to proceed?
Normally, I use cmake <options> ..
note the “…” at the end, which tells cmake to look in the parent directory for the source/instructions.
It’s also what @RawConvert uses in his instructions (actually, he uses “…/.” should be equivalent to “…”)
Thanks! A silly mistake, I thought those dots represented a folder within a folder. Now it is working. However, is there a trick to get sigmoid? In darkroom I cannot find it in modules: all, nor by typing in search bar.
Also, there is a crash. In collections module, if I go from a tag. Eg. ‘2020’, to film roll, it crashes. Can report that in github if need be.
Also, my old dt (3.8.1 from opensuse repository) no longer opens. Because the library had to be updated for this version? I did back up .config if I need to revert back.
It was these that got me going initially, but I didn’t follow exactly, because I didn’t want loads of files in HOME, so I did it all within a folder under HOME. You have to be careful about the build folder, I also had it wrong to begin with.
No, it should appear using the search, so it looks like the build hasn’t worked. One thing about phweyland’s process is that it does an intensive build step twice, whereas I think only once is necessary. I’d suggest you try my process, that should work, unless @jandren 's branch and/or Master have changed for the worse, I haven’t built sigmoid since 10 April.
I suggest don’t report until you’ve successfully built sigmoid, then re-check. If still crashing, PM Jakob with the detail. I got slightly in hot water for reporting in the usual place because sigmoid is not in Master yet.
I guess you’ve overwritten it using folder “darktable” under HOME? I believe my method avoids such problems by using separate folders for the building and especially where the executable lives.
1 Like
Thanks for your help. I’ve decided just to revert back to the build I was on before… much rather things working correctly! Was good to have a little play with filmic v6 anyhow. Hopefully Jandren can get sigmoid officially merged before next release.