The processing step visual deflicker is defective in my case - Printable Version +- LRTimelapse Forum (https://forum.lrtimelapse.com) +-- Forum: LRTimelapse 6 (https://forum.lrtimelapse.com/Forum-lrtimelapse-6) +--- Forum: LRTimelapse 6 - General Questions (https://forum.lrtimelapse.com/Forum-lrtimelapse-6-general-questions) +--- Thread: The processing step visual deflicker is defective in my case (/Thread-the-processing-step-visual-deflicker-is-defective-in-my-case) |
The processing step visual deflicker is defective in my case - rony - 2022-02-13 Hello, I wanted to run the RC1 version for a small test. Up to the step of the visual deflicker, everything worked fine for me. When I wanted to tackle this step, I set the smoothing of the curve, as well as the runs (4). The process started - the CPU power went up, the bar progressed. However, somehow nothing changed - both in the preview window the image stayed the same and the visual luminance value stayed the same - then when the second pass started, exactly the same thing happened - there was no change. I aborted the process and closed the software. After restarting the software and selecting the folder, all states were initially loaded. However, the visual deflicker process "somehow" automatically started again. The button flickers in a 2 second rhythm and images are "processed" seemingly at random. There is no process bar which progresses nor can I stop the process. The CPU load is close to 100%, which indicates that something is being executed. However, again - nothing changes in the state of the visual luminance. :/ I am using the Windows version. RE: The processing step visual deflicker is defective in my case - Gunther - 2022-02-13 Could you try to do "Metadata / Initialize" on that sequence then "Save". Now try the workflow again. If this happens again, please send or post the log file (info menu). RE: The processing step visual deflicker is defective in my case - rony - 2022-02-14 Thanks for your quick reply I have initialised the metadata and then saved it. After that, the development settings were reset - which is ok I then started the visual deflicker without any changes to the images - both passes calculated eagerly, but didn't change anything in the images :/ I hope I did everything right - the extract from the log is attached. Code: 2022-02-13 22:29:01 [DEB] Created Log file: C:\Users\rony\Documents\LRTimelapse RE: The processing step visual deflicker is defective in my case - Gunther - 2022-02-14 You are using an outdated version of Adobe DNG Converter and LRTimelapse should have notified you of that. That version is not compatible with the latest Lightroom Classic, which I assume you are using because you set your "Masks Version" to 2.0 in the settings. So: please make sure to have installed the latest Lightroom and Adobe DNG Converter. Should you be using a Lightroom Classic older than 11 and not be able to upgrade, you'd need to set the Masks to 1.0. RE: The processing step visual deflicker is defective in my case - rony - 2022-02-14 Thank you, I have now manually downloaded the latest version (14.2). Unfortunately, I had not received any notification on my computer as well as on my laptop. Unfortunately, I can't remember the message - but is it possible that I clicked "never show again"? I seem to remember that I could only click it away, but it would appear again the next time I opened the software. Actually, I always updated as soon as the message came up because I was hoping that it might have a positive effect on the processing speed. After updating, I opened LRT again - now the button for the visual deflicker flickered again. I'll delete the META data and see if it still occurs. And whether I can now perform the visual deflicker RE: The processing step visual deflicker is defective in my case - Gunther - 2022-02-14 You can reset your settings by clicking on "Reset Settings" on the bottom left of the settings dialog. This will also reset any "never show again" settings. Let me know if everything works now. RE: The processing step visual deflicker is defective in my case - rony - 2022-02-15 So the error I originally raised was not one, and could be fixed by updating to the new version of the DNG Converter. I had deliberately installed the old version on my computer - but I don't get the message for an update there :/ If it was not found, there is a message, and of course if there is an update for LRT, there is a message. funny ... I will keep a closer eye on the DNG converter in future. |