Then I went back to the regular git version of darktable, but it won’t start. I get:
[defaults] found a 64-bit system with 32822120 kb ram and 6 cores (0 atom based)
[defaults] setting very high quality defaults
[dt_ioppr_check_so_iop_order] missing iop_order for module negadoctor
[dt_ioppr_check_so_iop_order] missing iop_order for module doctor
And that’s it. I did remove my .config/darktable directory, but to no avail.
I think you have to discard history for the images you edited with negadoctor
You’re trying to show/edit images with a module that isn’t in master (yet)
If you can’t start DT, rename all xmp files you edited with negadr to something like .xmp.old
Thanks for the hint. Unfortunately, it did not help. Strange. (This annoys me it’s a linux system, I should be able to fix it. I grepped through the whole filesystem, and the string negad does not occur in the xmp files. I removed the complete .config/darktable and .cache/darktable directory. I checked-out a clean copy and installed it. So why is it complaining?) My original 3.0 from the arch repository still starts up though.
@anon41087856 For some images, after I set the color film base, when I click on the DR picker, the image gets very dark, even if I redraw the square to leave the unexposed film part outside. Screenshots and raw file below:
A darkening Dmax, which values goes through the roof, usually arises when you have dust on the film, so the measure is completely wrong. You need to select a clean bright part to measure the Dmax. Otherwise, simply setup the Dmax manuallly to make it look good.
Hum, I think you’ve mentioned that on your video.
Even if we read tfm/see tfv, we still forget things. With the lack of the underlying knowledge, it’s as if we really don’t connect things and end up relegating some important details to oblivion.
That would be great, but the way negative inversion works now is already awesome.
I wonder if the dust&scratches future code could also be used for slides, since they’re both subject to the same diseases (dust, scratches, but also fungus). Then maybe it would fit better inside imagedoctor, isn’t it?
My research documented in Scanned image scratch removal with “ICE” shows that you need some pretty advanced inpainting techniques to get reasonable results. Even the dedicated code from vuescan does not do a good job here, only patch based algorithms lead to acceptable results so far IIRC. That’s probably not to far from the healing/cloning in retouch module, but the difference is that a manual source patch is selected there.
A sample image is available at the end of the thread above, and I’ll update the original post soon to include some more samples. Only dust and scratches, as this is detected by an infrared scan, unfortunately, fungus is not and requires manual work to recover.
Wow, coming back to pixls.us after two weeks, I had 54 posts and one 20 minute video to catch up in this thread… Thanks a lot, @anon41087856, for your work on this and on darktable in general.
In case there are some people following this thread who have missed it so far, I’d like to point out that you might want to consider supporting @anon41087856’s work: aurelienpierre's profile - Liberapay
Personally, I’m sitting on 3900 scanned negatives and still have a few thousand to scan. Currently, I’m using some scripts to batch process them, which is great to get a preview and to ensure that the scans are okay, but so far I have still been missing a way to manually editing single important pictures. I am really happy that this is changing and hope to find time to play around with it soon!
Well, aren’t we all lucky you’ve got such a useful sense of humor? I’m pleased as punch with it and have been using it exclusively to process my negatives. I have a feeling it’s only gonna get better and am over the moon that I now have a reliable workflow for my film post processing. Nicely done!
Is there a Windows build where I can try out the new neg module? I moved away from darktable because of problems with the old negative module, so this is of huge interest to me.