<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Aurora HDR 2019 Review: HDR image editing and processing software for Windows	</title>
	<atom:link href="https://reviews.thewindowsclub.com/aurora-hdr-review/feed/" rel="self" type="application/rss+xml" />
	<link>https://reviews.thewindowsclub.com/aurora-hdr-review/</link>
	<description>Software, Services &#38; Hardware Reviews by TheWindowsClub</description>
	<lastBuildDate>Fri, 14 Dec 2018 10:33:23 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.1</generator>
	<item>
		<title>
		By: Casey Fry		</title>
		<link>https://reviews.thewindowsclub.com/aurora-hdr-review/#comment-76</link>

		<dc:creator><![CDATA[Casey Fry]]></dc:creator>
		<pubDate>Sat, 06 Oct 2018 16:47:00 +0000</pubDate>
		<guid isPermaLink="false">https://reviews.thewindowsclub.com/?p=1895#comment-76</guid>

					<description><![CDATA[If you rely on batch processing, look elsewhere, at least for now. I Just downloaded and tried 2019 in hopes that the batch processing may have improved from 2018, but it almost seems worse... of course, this would be a non-issue if we could bypass the auto-grouping and specify batches by multiples instead, or at least have the option to adjust/modify the auto &quot;grouping&quot;...

I&#039;m shooting with a D750 and a D600, both in aperture priority, auto bracketing 3 frames at 2 stops apart.
For example, I tried to test batch a job with 282 images; in Oloneo and Photomatix, this yielded the expected 94 hdr images (282/3=94). However, in Aurora 2019, it yielded 50. Not only did some images not get &quot;grouped&quot;, some groups contained 2, 3, 6, 8 and 9 images!

Obviously, this is unacceptable, so I&#039;m not really seeing the point of the batch feature in its current state, unless I&#039;m missing a setting to specify multiples, or a way to adjust the auto groups... I tried manually dragging the images to their correct groups, which it allowed me to do, but it didn&#039;t change anything, as but the results remained the same.

While the automatic grouping feature is an neat idea, it really doesn&#039;t offer any advantages over the tried and true multiples method, but instead has critical disadvantages.]]></description>
			<content:encoded><![CDATA[<p>If you rely on batch processing, look elsewhere, at least for now. I Just downloaded and tried 2019 in hopes that the batch processing may have improved from 2018, but it almost seems worse&#8230; of course, this would be a non-issue if we could bypass the auto-grouping and specify batches by multiples instead, or at least have the option to adjust/modify the auto &#8220;grouping&#8221;&#8230;</p>
<p>I&#8217;m shooting with a D750 and a D600, both in aperture priority, auto bracketing 3 frames at 2 stops apart.<br />
For example, I tried to test batch a job with 282 images; in Oloneo and Photomatix, this yielded the expected 94 hdr images (282/3=94). However, in Aurora 2019, it yielded 50. Not only did some images not get &#8220;grouped&#8221;, some groups contained 2, 3, 6, 8 and 9 images!</p>
<p>Obviously, this is unacceptable, so I&#8217;m not really seeing the point of the batch feature in its current state, unless I&#8217;m missing a setting to specify multiples, or a way to adjust the auto groups&#8230; I tried manually dragging the images to their correct groups, which it allowed me to do, but it didn&#8217;t change anything, as but the results remained the same.</p>
<p>While the automatic grouping feature is an neat idea, it really doesn&#8217;t offer any advantages over the tried and true multiples method, but instead has critical disadvantages.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
