<?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: LRTimelapse 4: Improved workflows and better performances	</title>
	<atom:link href="https://timelapsenetwork.com/products/software-and-apps/lrtimelapse-4-improved-workflows-performances/feed/" rel="self" type="application/rss+xml" />
	<link>https://timelapsenetwork.com/products/software-and-apps/lrtimelapse-4-improved-workflows-performances/</link>
	<description>The Worldwide community dedicated to time-lapse photography. Learn the technique, share your experiences and master it watching the best videos for free!</description>
	<lastBuildDate>Tue, 28 Apr 2015 17:35:00 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: Marco Famà		</title>
		<link>https://timelapsenetwork.com/products/software-and-apps/lrtimelapse-4-improved-workflows-performances/#comment-199</link>

		<dc:creator><![CDATA[Marco Famà]]></dc:creator>
		<pubDate>Tue, 28 Apr 2015 17:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://timelapsenetwork.com/?p=13827#comment-199</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://timelapsenetwork.com/products/software-and-apps/lrtimelapse-4-improved-workflows-performances/#comment-198&quot;&gt;Aaron Priest&lt;/a&gt;.

Fantastic feedback Aaron, glad you loved it and thanks for your note about the Ramper Pro together with LRTimelapse 4!]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://timelapsenetwork.com/products/software-and-apps/lrtimelapse-4-improved-workflows-performances/#comment-198">Aaron Priest</a>.</p>
<p>Fantastic feedback Aaron, glad you loved it and thanks for your note about the Ramper Pro together with LRTimelapse 4!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Aaron Priest		</title>
		<link>https://timelapsenetwork.com/products/software-and-apps/lrtimelapse-4-improved-workflows-performances/#comment-198</link>

		<dc:creator><![CDATA[Aaron Priest]]></dc:creator>
		<pubDate>Tue, 28 Apr 2015 16:26:00 +0000</pubDate>
		<guid isPermaLink="false">http://timelapsenetwork.com/?p=13827#comment-198</guid>

					<description><![CDATA[I beta tested this for Gunther with the Ramper Pro, and it handles the deflickered .xmp files of the Ramper Pro beautifully by copying the tiny exposure changes to a hidden gradient mask and column in LRT, allowing you to initialize the Exposure 2012 column back to zeros and edit the exposure of your keyframes for creative taste, but still preserve the Ramper Pro&#039;s deflickering. Before, we had to create gradient masks over the entire image with an exposure adjustment on the keyframes, but the gradients would sometimes get ruined by Lightroom when copying/pasting metadata. Gunther added a new script for Lightroom to sync this data so it won&#039;t get destroyed by Lightroom. This is a major improvement for anyone shooting with a Ramper Pro!]]></description>
			<content:encoded><![CDATA[<p>I beta tested this for Gunther with the Ramper Pro, and it handles the deflickered .xmp files of the Ramper Pro beautifully by copying the tiny exposure changes to a hidden gradient mask and column in LRT, allowing you to initialize the Exposure 2012 column back to zeros and edit the exposure of your keyframes for creative taste, but still preserve the Ramper Pro&#8217;s deflickering. Before, we had to create gradient masks over the entire image with an exposure adjustment on the keyframes, but the gradients would sometimes get ruined by Lightroom when copying/pasting metadata. Gunther added a new script for Lightroom to sync this data so it won&#8217;t get destroyed by Lightroom. This is a major improvement for anyone shooting with a Ramper Pro!</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
