Batch Processing Showing Vastly Different Results
Hi,
I am a new user of Aurora'19 and have been toying with it just over the past 2 days. Results are good, until I decided to do batch processing.
From my understanding (correct me if I'm wrong), batch processing allows me to process multiple images using the exact same settings (aka "Look"). This is important for me because I like shooting multi-image panoramas, and would like to process them before stitching. However, I noticed that images processed using batch processing ends up looking vastly different from those processed using "Open image..." button. In fact, they look closer to my out-of-camera-jpeg than anything.
I noticed this for my collection of 6 images for a panorama. They are shot as single images, not bracketed.
What I did was this
- Loaded an image within the series which is representative of the overall panorama exposure.
- Started by selecting a preset look. In this case, I chose Landscape > Better sunrise.
- Tweaked the settings on the right. I did a few adjustments, the most primary one being the exposure, others were relatively minor.
- Saved the Look by clicking on "Save as Aurora HDR Look...". I coose the image name of the reference image as the Look name, in this case "0419".
- I also saved the file via File > Save As..., just in case. For comparison, I exported an image here.
- Then I opened batch processing, selected all 6 images in the series, chose "Single image" instead of "Bracketed HDR", and clicked Process. I changed to User Aurora HDR Look, and selected the "0419" preset created earlier. Slider set to 100.
- Clicked process and wait.
What I noticed is that the image obtained from step 7 (batch processing) looks entirely different from the one at step 5 (export). Even if I were to select a single image (instead of multiple) during step 6, the result is still the same. See image below. 1: out-of-camera JPG (note that I used RAW for Aurora HDR). 2: batch. 3: exported.
This behaviour is also observed when using built-in presets instead of user looks.
Do I have the wrong understanding of the working mechanism of batch processing or am I doing something wrong here?
Any guidance will be much appreciated here.
Thanks a million.
Yeo
-
HI Yeo,
Thank you for your detailed explanation!
You should definitely be getting the same results form opening/editing and single image as you would with the same setting in batch processing. Would you mind sending us the source files to support@skylum.com so we can try to replicate it on our end?
If the files are too large to email you can use WeTransfer.com and then include the shared link in your email.
A screenshot (cmd-shft-3) of the export dialog when exporting a single image, as well as a screenshot of your batch settings would also be quite helpful.Thanks in advance!
-
Hi Yeo,
Exporting with different color profiles can indeed cause a difference in the appearance of the export, depending on the app you're using to view the results, and the color profiles in use by your computer/display. However, if you've ensured that the exports - both for a single image and batch - were the same, then there is something else amiss. Our techs will look into the files you send over and will be in touch via email.
-
Good to know that I'm not alone!
Another question - A19 does automatic processing every time we open an image. I imagine this processing to differ from image to image. Since I am capturing images with the intention of stitching them into a panorama, does (or is it possible to make) batch processing apply identical processing to all of the images, so that the output files, even though being separate images, have matching exposure, white balance, DR, etc? Assuming of course that I kept my camera's settings between shots.
-
Hi Yeo! At the moment, the algorithms of the Quantum engine work like this. The Tone mapping or the merging of brackets can be analyzed differently due to certain circumstances. The tone mapping is automatic, nevertheless, we are gathering feedback from our users to consider making it an optional feature.
-
Hi Yeo,
If the images are captured with consistent settings then the results from batch processing should also be consistent across those image.
In running a set like that through batch processing, have you had an issue where the results were inconsistent with each other? I know that you mentioned the batch results and single image processing results differed (which we are looking into), but if you batch the whole set, are there significant differences in the set? -
Outside of the inconsistent results, not having the ability to apply lens corrections via batch processing makes the product unusable for Olympus users. Images have darkened corners when run through batch processing. I can import the same images one set at a time and apply lens corrections, or export from lightroom and it works fine. Makes the product unusable.
-
Hi, Damian. regarding the batch algorithms, I have replied to you in another thread here: https://community.skylum.com/hc/en-us/community/posts/360002804072-Batch-Processing-Aurora-2018-not-working-correctly
We're improving them in each update as well as the lens corrections issues mentioned by Jeff. We will keep you posted, since currently, we don't have ETA for the next update of Aurora HDR 2019.
-
For those wanting lens correction within batch processing it’s simple. Just make a new pre-set that has the lens corrections included in the reset itself. You can use your own custom settings one batch processing. I typically open up the first set from a location and adjust the settings for the job. Then I save a preset. Then I can batch process using my own preset on several different shots. I hope that helps.
-
Also, in the batch process window, you can easily adjust any images that didn’t auto group correctly. Just drag them into the correct group before you start the job. There are several factors that can affect us. If some of the brackets have little to no detail auto group thing can be difficult. Additionally if the brackets were shot manually and the timestamps are far apart, the software may not be able to detect the brackets. This is why you can easily drag him come by to check the job before you submit it.
Please sign in to leave a comment.
Comments
21 comments