HDR batch processing for Lightroom Classic CC
Vložit
- čas přidán 7. 09. 2024
- I wrote a small script to automate the creation of HDR raw files from bracketed sets for Lightroom Classic CC. It is not faster than doing it manually, but at least you can let your PC do it alone.
Run the script enter number of exposures, number of HDR pictures and then and left click on the first image you want to process...
All you need is the scripting application AutoIT: www.autoitscri... (full Installation (free))
and
the script: maps4me.net/too... (please unzip before use)
For users of Lightroom Classic V7 here is a faster script which does not need the captions of the preview window and makes usage of the CTRL+SHIFT+h shortcut: maps4me.net/too... (please unzip before use)
Hey Sockeye404, i want to shake your hands because this is what i search the whole time. I am very very happy! Many many thx to you and i wonder that Adobe doesn´t did the same. The LR HDR is my absolute favorite because of the style... no more clicking... wowowow!!!
Thank you for finding this helpful, if you run into any issues, please let me know
Brawa dla Ciebie! Bardzo pomogłeś mi tym skryptem. Dziękuję! :)
@sockeye404 Sometimes the script chooses 2 photos instead of 3. Is there a solution?
Danke
Hello. I couldn't access the script. Is it possible to send it?
Hi!
Thank you for sharing your Idea!
Could this same process potentially be used with Camera Raw?
In principle AutoIT can be used to automate any user interaction with Windows software. But as Adobe has implemented a function in LR to group and HDR-process them automatically, I did not follow this solution any more, as a workaround is always the 2nd option :-)
Thank you very much for the good work with the script, as well as sharing it here with us. I have few questions: I'm having issues while running it.
1. At the beginning it had issues of NOT bringing the newly created DNG file into lightroom.
2. At some point it was running the script on only 2 images instead of on 3 (it runs on 3 at the beginning of every run, but then switch to only 2).
3. Then another issue happened - instead of taking 3 original images, it takes 2 original + 1 DNG, and then of course lightroom pops up an error of not being able to merge.
At all 3 situations I thought it had something to do with the length of process. So I checked and rechecked, and then changed and rechanged the timing of the miliseconds to be longer.
When running manually per set - the process takes my computer 34 seconds. So I tried to use 17000 ms, then 18000 ms, then 20000 ms, and still it creates those 3 issues.
Any ideas why it happens and what should be done in order to prevent it from the issues? Thanks! Ori.
Hi Ori, yes there is a challenge with this approach. Lightroom HDR processing times increase with each iteration. If the HDR processing takes longer than the time set in the script, it breaks. As Lightroom now has this automatic grouping and batch-processing built in, I did not follow up on my script. A possibility would be to automatically add some waiting time in the script for each loop to cope with Lightroom slow down.
@@Sockeye404 Thanks I'll try that and keep you posted... Is there a need to change the pause time(s) at all anywhere? I saw them as 100ms and 50 ms... And wondering if changing those (one or both or all of them) would help with anything? Or is it just the ms of the HDR processing time?
@@orikuper4433 I would add a variable in the beginning of the script for the slow down compensation e.g.: "Global $IntSlowDownComp = 100" Then in the final loop which starts with "for $i= 1 to $IntNumRuns" add a new line before the expression "Sleep($IntMsPerSequence)" and put in "$IntMsPerSequence = $IntMsPerSequence + $IntSlowDownComp"
This will slow down (increase the waiting time) for each cycle for the amount of milliseconds you set for $IntSlowDownComp. Im my example 100ms. This means after every 10 loops (10 sets) it will give Lightroom 1 more second to process.
@@Sockeye404 perfect thanks. I was just wondering yesterday about the possibility of adding an n+1 thing to the script... So your reply here is exactly that. During the night I left it with 30000ms to process 455 sets... it worked fine, but my HDD got full and stopped. So now I'm emptying some room and will let it keep running with the 30k ms - and see if it can make it to the end. If not - I'll definitely add your added code here. Thanks again and I'll keep y'all posted ☺️
@@Sockeye404 Update: I ended up transferring the whole process from my (16GB Ram) laptop to my (32GB Ram) desktop, AND embedded your additional code into it, and it works like a charm there. One thing maybe to change in your added code: since "IntMsPerSequence" already existed, I entered the new one as "$IntMsPerSequenceDelayed". That way the original can (when need) to use the original one for the calculations. Viel Dank!!! (sorry if the spelling is wrong) :-)
Thank you!
It seems that I have followed all your tuto and it runs perfectly but for only one merge and it stops... Can you help me ?
Are you sure you always have the focus on Lightroom and do not click somewhere else? The script applies the keyboard shortcuts only to the topmost application.
Hello! I'm trying to use it but first problem is that lightroom asking me do i want to delete file. as i see in your clip is doing it automatically. Hows that? And second question. when i run this script can i touch any other app or keyboard or i need to leave it alone? This think got a potential! you are great! thanks :)
Hi Markowicz, the script just sends keyboard commands. In this case to remove the selected set of merged originals from the library: ALT + BACKSPACE. This keyboard command removes selected images from the library (not deleting the file) without asking. Could you please check if your version of Lightroom reacts this way, by typing ALT + BACKSPACE? If no, which keyboard command do you use?
And yes the script just sends keyboard commands (to the currently topmost application) and therefore you need to leave it alone.
I tried manually and alt+backspace removes the photo without a dialogue. But through the script, it asks for a confirmation. Any clues? (I tried replacing ! by ALT)