![]() ![]() ![]() Why these microscopical changes in luminance level? It takes hundreds of passes to get to the right level. So what am i not using correctly now?Ĭould you please answer the questions i raised in my original post: All issues i mentioned in my original post remains the same. Third: I have now re-edited my keyframes and set clarity, blacks, whites and dehaze to 0. ![]() The whole image is the meaningful reference area. Second: The images is the moon against a black background. Atmospheric interference causes exposures to differ slightly from image to image, thus causing flicker. You have explained earlier to me that the holy grail wizard is not usable when using automatic exposure. There is no way i can be on site and manually adjust exposure. Temperature during this 5 hour shoot was -20☌. It was shot with a Pentax K-3 and sky-watcher 200PDS Newtonian telescope. Of course i want help, but it's not easy to stay calm after wasting so many hours trying to get a decent output from deflicker.įirst thing: I'm working on a timelapse of the lunar eclipse. I hope that you don't take it personally. I have reported several bugs that i found, that should be helpful to you.īut when something doesn't work I'll complain. Let me know why you think you can't use the holy grail wizard. This is described here: īottomline for visual deflicker as will most tools: you need to know them and use the correctly then they will deliver the results that you expect. Often it helps trendously to use the tone curve instead of the whites/blacks to do the editing. The bigger the differences in luminosity in the images, the more contrast changes LR will introduce with some tools like Dehaze, Clarity, Whites, Blacks. If you use a reference area, then you will be deflickering for that part, but in fact introducing flicker to other parts because the contrast changes. If you have changes in Contrast, you can deflicker as long as you want, you'll never get rid of it although you might have a smooth curve. Third: Deflicker will only work with Luminance, not Contrast. So make sure to find a suited reference area which shows the flicker effect only. If you have huge contrast images this might not be the best way. ![]() Otherwise, LRT will only see the whole image as one number and try to equilize this number across the sequence. Second: You need to set a meaningful reference area for deflicker, as explained in my deflicker tutorial. I think there might be a way, so let me know, why you can't use it. Because it speeds things up, which makes Deflicker more efficient. You can trust me that visual deflicker in LRT is the best you can get, for a reason it's the leading technology to deflicker on a raw file basis.įirst thing: there is also a reason, why there is a "Holy Grail Wizard". On a 6 core Intel i7 with 32GB RAM.Īre you only here to complain, or do you want help? If so please calm down a bit and let me help you. Approx 1s per image times 1300 images times 150 passes of deflickering. Java is a memory hog, adobe dng converter is eating CPU. The ramping is good, but if i cant get rid of the flicker, it's pointless.Īs it works now, it would be faster if i had the option to type in the luminance level manually.Īnd performance. 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? This run it starts by undoing previous refinements, so that the end result is worse than before you run the last passes!!! AAAAARGH!!! To actually get it to work again, you have to select another set of images, then back again. Right now it says i have run 250 passes of deflicker, in reality, it has run 150. this time it does nothing, except increases the counter how many passes you have run. 100% CPU usage but levels still not within the green line. 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. Since i cant shoot in holy grail mode, i rely heavily on visual deflicker.īut there must be some serious faults with the computing algorithms. This post was last modified:, 12:01 by lage. ![]()
0 Comments
Leave a Reply. |