Yes, that makes me happy .
BTW: I can test a exiv2 implementation in Photoshop if it is still needed.
Yes, that makes me happy .
Update 2021-02-14: v0.1.11rc9
The pre-Filmulation and post-Filmulation histograms now correspond only to the area of the crop (though Filmulation still runs on the full image to make make cropping more responsive).
I can’t do this nearly as simply for the raw histogram, though, because of the presence of distortion correction…
Additionally, you can now hit the Esc key to cancel the dropdown box for lens selection; this is nice if you search for a lens but can’t find it.
New white balance features are fantastic; thanks!
Update 2021-04-07: v0.11.2rc1
I took a bit of a break, and now I’m back.
I added a Help button that causes applicable tooltips to show instantaneously instead of with a delay, which should help users explore the in-application documentation more easily.
Additionally, I enabled directory import to follow symlinks (and added a 20-deep recursion limit), as well as enabling it to open file symlinks (which is needed to work with git-annex.
Thanks for sharing all your hard work on this with us. I thought I would start to play around with Filmulator and I have one question is there a way to compare the original image with the state of the current edit…essentially a preview vs original toggle?? Thx
Not at the moment.
At some point I may add the ability to save multiple edits of the same file but I haven’t worked out a good UI for it.
Thx…Ya even a way to add a global opacity slider or something maybe not sure…it would just be nice to be able to toggle to the original to see visually where you have gone with the image…
Update 2021-06-24: v0.11.2rc2
Lotsa changes here:
Noise reduction is the big one. Turning on the switch reveals new controls.
- Noise Reduction itself additionally enables LMMSE demosaicing.
- NR Strength controls nonlocal means demosaicing which does chroma and luma NR together.
- NR Gradients is something you should increase if you get posterization. This is at the expense of making it slower.
- Speckle NR is the impulse denoise from RawTherapee. Nonlocal means sometimes adds speckles, and this will help take those out.
- Chroma NR is also from RawTherapee. Going too high causes some color shifts (not quite sure where they’re coming from) and a bit of smearing, but I usually find it’s not necessary.
The noise reduction settings are not saved between processing sessions, because they’re not finalized yet; I think there may yet be some more tweaking I can do. When I do rev up the database and have them save, then I’ll call that version 1.0.0.
Also, it is memory hungry. When doing noise reduction to 60 megapixel A7r4 files, memory usage balloons to over 19 gigabytes. Beware. I might be able to shrink this in the future though…
- Black levels on Panasonic cameras is fixed…? Not 100% sure this is finalized, but it’s a big improvement.
- When beginning cropping, if you’re fit zoomed, the view zooms out so all crop handles are visible.
- The intro text when no image is selected now tells the user that you can zoom and pan around.
- Sampling a custom white balance no longer automatically saves it.
- If no matching lenses are found when searching for a lens, the user is prompted to download lens corrections.
- Fixed a bug where switching images by keyboard would block rating changes.
- Fixed a bug where tooltips would run off the bottom of the window and get cut off.
- Make sliders on the Settings tab reset to their defaults instead of to what they were when the program was launched.
- Made a Reset All button for settings to rescue the user from accidentally making it 400% scaled.
- A tooltip for all continuous sliders now tells the user how to get to the precise input dial.
- The tooltip on the Help button always shows up instantly even when not in Help mode.
Update 2021-06-27: v0.11.2rc3
I fixed a horrendous memory leak in noise reduction. A7r4 files now take 11 gigabytes peak in my testing.
I also reduced memory usage overall, with 8.8 gigs peak for A7r4 files when not using noise reduction.
Trying out the noise reduction features with some images from my Fuji X-T4. Just wanted to ask about the LMMSE demosaicing, are you aware of any issues with this with x-trans CFA’s?
Also a suggestion to be able to preview noise reduction settings on a selected rectangle in stead of the full image. And to be able to do some “before/after” flipping back and forth which is really helpful to judge the effects of noise reduction.
The sliders are also not quite so intuitive to use and the max value of the first slider leaves the image in a pretty unusuable smeared state. Why the need to pull it so far beyond realistically usable levels? Also the sliders could use some tooltips, and some reasonable default values based on the ISO of the image being edited.
In the discussion leading up to this build I kept reading that you didn’t want to use any kind of luminance noise reduction, only chroma. Yet the first slider is both luma+chroma. Did you change your mind?
Don’t get me wrong I really appreciate this new feature and your continued work on Filmulator. I really like it, even compared to Capture One which I also use.
Thanks for the feedback, this is exactly what I was hoping for.
I should clarify the wording in the tooltips, LMMSE is only used on Bayer raws.
Previewing on a small region is going to be… challenging to implement, but I agree it’s probably necessary. I’ll probably need to make some sort of bypass to the Filmulation algorithm, which won’t work reasonably on small crops.
Because high values may be useful for extremely high ISO images like this one: Hockey game under lights: 20k ISO on m4/3
Everything has tooltips, it’s on the name of the tool so that the tooltips don’t bother you while you’re manipulating the slider. Try pressing the Help button in the top right to make tooltips appear instantly.
Instead of guessing at reasonable defaults, I might actually make Filmulator keep a moving average of your NR settings for each ISO for each camera… does that sound good?
I didn’t use RawTherapee’s luma noise reduction that was built into the same code as their chroma NR. The luma+chroma noise reduction currently in Filmulator is an independently developed nonlocal means implementation.
I was originally going to use nonlocal means for just luminance NR, but it proved better for very high ISO images to use both luminance and color from nonlocal means, then feed that output into the chroma NR from RawTherapee.
And every time I encounter software that doesn’t let me pull it far enough I think “why?!?!?” :).
Images are always different and you never know what someone is trying to achieve.
I (used to) use filmulator for mapping tiff files from scans that needed exposure fixing, and contain quite some DR. (high dynamic range negative scans that have all the signal ‘squished’ in 16bit tiff files). Filmulator was awesome in what it did out of the Box by just raising an exposure slider… But the noise and grain in old 1600 iso film negatives is nothing compared to iso 64000 iso modern digital files :).
Well I guess there are use cases for massive levels of noise reduction after all
I suppose if we wanted to be really advanced the slider range should scale by ISO, so that it has “more range” for high ISO images and “less range” for smaller ISO values. But then again it might be overengineering. I’m just looking for a way to make these tools easier to use for the end user.
Something I’ve seen in luminar (or affinity, don’t know anymore) is an ‘extreme’ checkbox that ups the slider range.
Default it’s conservative, a click of the checkbox and you can go nuts if you think you need it.
You don’t need any iso scaling (which differs per camera, or files don’t have Metadata) and it’s easy to program.
A halfway decent Noise estimator, like sampling flat patches at several intensities, could be helpful for auto-setting at least a conservative initial denoise. That would avoid noise-profiling all cameras and has the potential to be more robust than the average-denoise-used on similar images from the same camera+lens+iso combo.
I like the idea of the ‘extreme’ checkbox/toggle. Reminds me of the ‘overdrive’ setting. A ‘denoise-overdrive’ toggle would tie into the same concept used for the filmulation stage.
The reason I use Drama+Overdrive is because I imagine newbies maxing out Drama and not noticing the negative effects it can have. (also because of implementation details)
But I can’t imagine anyone not noticing the negative effects of overly strong noise reduction, so I don’t know how necessary a precision toggle is. After all, if you want fine control then you can use the precise input dial (by right clicking on the slider name).
And the NR sensitivity to fine adjustments in the 20-30 range is low enough that I never find it needing fine-tuning in my experience.
Everything has tooltips
Yes and I had forgotten about that - sorry for not remembering about that. I would suggest a few phrasing changes though. For NR Strength it says “when set to zero this is disabled. This may cause speckles” - I think a newline might be missing in there. Also the Chroma NR strength tooltip says that chroma noise reduction is disabled when the slider is at 0. But this contradicts the tooltip from “NR Strength” which says it enables both Luma+Chroma nr. So which is it, when the Chroma NR slider is 0?
might actually make Filmulator keep a moving average of your NR settings for each ISO for each camera… does that sound good?
A moving average sounds overengineered to me. I think that simply starting out with the same values (all sliders) that were used on a previous image with the same ISO? Or rounded “down” to the nearest ISO that was processed (so if you open an ISO 3200 image, and Filmulator knows only values for previous photos up to ISO 2500, then use those values).
Overall I think the new NR is quite effective but it does still lag behind in terms of what the best noise reduction technology can offer. It’s good for many shots, but I would probably continue to export in TIFF format and use software like Neat Image afterwards. NI is by no means the newest or best but it is faster than Filmulator and gives better results - IMO.
Perhaps this is a good opportunity to incorporate some AI technology in Filmulator, and get the hype going
These last few builds seem to make my D700 NEFs no longer work; they show up as black frames!
Confirmed. D200 NEF also show up as black frames.
Double clicking them though opens them fine…
Since which build?
I’m chasing down an issue with white balance on Fuji cams…