That’s a good idea, I should probably do that.
Maybe I can even make it remember them per focal length for zoom lenses and try to fit the corrections or something…
That would be wonderful! As for the focal length and zooms, that would probably be a good idea, but maybe a bit over the top? For me this would be most useful for manual/vintage lenses where there is no exif or lensfun profile to select. And sometimes I also like to add the occasional vignette to an image…Anyhow, great work, this app really fills a gap in raw editing on linux (and other platforms too I imagine).
Updated 2021-10-29: v0.11.2rc5
A relatively major change: I reordered the pipeline to fix white balance once and for all. Turns out not quite “for all”, since Libraw won’t give one of the matrices I need for the Sigma fp and fp L… I’ll have to deal with that.
Anyway, the old white balance would totally break for Fuji 26mp cameras in extremely warm lighting with AWB. Additionally, adjusting white balance away from the default would lose highlight dynamic range. Now both of those are fixed.
This does, however, mean that you might need to tweak white balance and exposure compensation on your previously imported photos.
With the reordering also comes a few changes to the ordering of the tools, and new tools.
First off there is a new alternate-demosaic switch which lets you switch to LMMSE and xtransfast demosaicing for Bayer and X-Trans raws respectively. LMMSE used to be bundled with noise reduction, but now it’s split off. Interestingly, the required noise reduction settings vary dramatically depending on what demosaicing was used, especially in high noise situations. LMMSE needs higher luminance NR than Amaze, but it gives much better results at those higher values. Fuji with the Markesteijn algorithm turns into a total blur really quickly at surprisingly low luminance NR settings, while the xtransfast algorithm seems to be almost completely unaffected by the nonlocal means luminance NR. Weird.
NR interacts more favorably with lens corrections; it now occurs before Lensfun, so distortion correction doesn’t interfere with how sharp the noise is.
Using NR might result in an increased memory footprint now. I have some ideas planned for having intermediate levels of memory saving versus caching, but that is not ready yet.
Additionally, at least on 0.11.2rc4, there was a bug in which cropping or leveling and making no changes would cause the program to loop continuously, manifesting as all the histograms flickering. This bug has been fixed.
2 Likes
Just thinking out load (so probably wrong 
)… if the NR is applies before lens correction , that means that vignetting correction isn’t applied yet.
Wouldn’t this have the effect that the corners of an image get more of a total exposure boost eventually, and bring the noise more forward… Requiring more NR in the corners ?
The darker the image that’s fed into the noise reduction algorithm, the stronger the NR at any given setting, so this is in fact the right way to do it.
Updated 2021-11-10: v0.11.2rc6
This fixes a bug where changing Lensfun lens corrections and image rotation would erroneously summon up the first image you processed.
It also improves performance by reducing redundant computation.
Additionally, it has significantly improved noise reduction in extreme white balance situations, mildly improved otherwise.
2 Likes
When I install the .exe, I get two missing DLL.
Updated 2021-11-12: v0.11.2rc7 for Windows only
I’ve added the two missing DLLs (someone else told me which ones their computer asked for); if it asks for more could you tell me what they are?
Thanks for the new build. Filmulator now appears to crash during startup. Running WIndows 10.
I am seeing the same issue in W10 for the 0.11.2rc7 build. Installs fine, but when started, nothing happens. I monitored the task manager and there’s not even a process started for the program. I’m not sure if it opens first then crashes for you but for me it’s a total failure to launch. I tried running in admin mode as well.
I booted up my Windows machine to try it and the same happened to me.
I’ll have to do some investigating…
Yes, I see nothing happen in task manager, but it may happen so fast it never gets updated to the screen.
This happened to me a while ago with some qt software I was building for work. It was missing some plugins (so dll files not included but without windows yelling that something is missing ).
-
there was an utility with qt to copy a bunch of files to make a redistributable package. Are you using it ? Might at least give a hint about what might be missing
-
there were debug environment variables you could set before launching the app to get more insight in the qt start procedure and where it might be failing . For the live of me I can’t remember.
Still struggling with the Windows build, but my friend has made an Arm64 build for Mac…
Filmulator_v0.11.2rc7_arm64.dmg (49.4 MB)
note: may only run on MacOS 12? Not sure.
Great! But it doesn’t run…
Termination Reason: Namespace DYLD, Code 1 Library missing
Library not loaded: @rpath/libraw_r.22.dylib
Referenced from: /Applications/Filmulator.app/Contents/MacOS/filmulator
Reason: tried: '/usr/local/lib/libraw_r.22.dylib' (no such file), '/usr/local/lib/libraw_r.22.dylib' (no such file), '/usr/local/lib/libraw_r.22.dylib' (no such file), '/usr/lib/libraw_r.22.dylib' (no such file)
(terminated at launch; ignore backtrace)
I will try to reinstall libraw, but perhaps your friend is more capable… I’m on macOS 12.0.1, iMac M1.
Update: Installing libraw fails (I’m not doing it right, I guess). I hope your friend can figure out what goes wrong, @CarVac! I’d really like to try Filmulator.
Another update: perhaps the libraw version is wrong in the Filmulator code? I can install libraw using macPorts in /opt/local/lib/libraw_r.20.dylib but that’s ‘20’, not ‘22’. Also the path is different (but I tried to remedy that with an alias/symbolic link).
Update 3: After tricking the system by adding libraw_r.20.dylib manually to /usr/local/lib and changing the version number to ‘22’, it now crashed saying:
Termination Reason: Namespace DYLD, Code 1 Library missing
Library not loaded: liblensfun.2.dylib
Referenced from: /Applications/Filmulator.app/Contents/MacOS/filmulator
Reason: tried: 'liblensfun.2.dylib' (no such file), '/usr/local/lib/liblensfun.2.dylib' (no such file), '/usr/lib/liblensfun.2.dylib' (no such file), '/Applications/Filmulator.app/Contents/MacOS/liblensfun.2.dylib' (no such file), '/usr/local/lib/liblensfun.2.dylib' (no such file), '/usr/lib/liblensfun.2.dylib' (no such file)
(terminated at launch; ignore backtrace)
So probably more dependencies are broken/missing. Also, it seems that on M1 they should be in different locations than before…
@CarVac If your prefer, I can communicate with your friend directly.
Update 4: Launch now proceeds until librtprocess is loaded; I don’t have it and I don’t know how to install it. The other dependencies may or may not be working now; I fiddled with the filenames. Giving up now… back to my photos. Hoping we will see a working macOS version soon!
Filmulator_v0.11.2rc7_2_arm64.dmg (44.9 MB)
Here’s another attempt; it should include LibRaw in the bundle.
Thanks to you and your friend for not giving up! Still crashes on launch… note that I fiddled with dependencies, adding dylib files to different locations, and so on, so I’m not sure which dependencies are now missing in the bundle, but now launch crashes at librtprocess loading. All the dependencies should be in the bundle (lensfun, libomp, librtprocess, maybe others), because M1 Macs put those in strange new locations, and for non-coders like me, installing librtprocess is already too high a hurdle.
It shouldn’t be doing that but I think it’s an artifact of him testing it on the same machine that he’s building it on.
Is there anything I can do to help? From tomorrow on I’ll be away from my M1 for a few days, but tonight (6PM here) I could test any new builds. Again, I think all the dependencies should be in the bundle, or it won’t run on M1.