Posts: 42
Threads: 23
Joined: Feb 2018
Since i cant shoot in holy grail mode, i rely heavily on visual deflicker.
But there must be some serious faults with the computing algorithms.
Running 1 pass is pointless. The changes in the computed luminance levels are so microscopical, that running 50 passes isn't enough to get the levels within the green line.
Then you run 50 passes of refinement. 100% CPU usage but levels still not within the green line.
Then you run another 50 passes. this time it does nothing , except increases the counter how many passes you have run. Right now it says i have run 250 passes of deflicker, in reality, it has run 150. It's still flickering.
To actually get it to work again, you have to select another set of images, then back again.
Then you run a set of refinements again. This run it starts by undoing previous refinements, so that the end result is worse than before you run the last passes!!! AAAAARGH!!!
Why these microscopical changes in luminance level? There must be an estimated level (green line) you want to get to? Why not set that level in the first pass, and then fine tune the level if necessary?
Something has to be done. Right now LRTimelapse is useless for me. The ramping is good, but if i cant get rid of the flicker, it's pointless.
As it works now, it would be faster if i had the option to type in the luminance level manually.
And performance. Java is a memory hog, adobe dng converter is eating CPU. Approx 1s per image times 1300 images times 150 passes of deflickering. Thats 54 hours. On a 6 core Intel i7 with 32GB RAM...
BR,
Lage