<?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/">
	<channel>
		<title><![CDATA[LRTimelapse Forum - All Forums]]></title>
		<link>https://forum.lrtimelapse.com/</link>
		<description><![CDATA[LRTimelapse Forum - https://forum.lrtimelapse.com]]></description>
		<pubDate>Sat, 21 Nov 2026 07:06:03 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[LRTimelapse 7.5.6 beta 5]]></title>
			<link>https://forum.lrtimelapse.com/Thread-lrtimelapse-7-5-6-beta-5</link>
			<pubDate>Fri, 20 Nov 2026 19:36:32 +0100</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.lrtimelapse.com/member.php?action=profile&uid=2">Gunther</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.lrtimelapse.com/Thread-lrtimelapse-7-5-6-beta-5</guid>
			<description><![CDATA[This beta lets Motion Blur work together with a crop animation, and the download and installation are smaller. It also covers visual previews and their colors on wide gamut Macs, folders on network drives and removable drives. Many other smaller fixes are included as well.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">New Features</span><ul class="mycode_list"><li>Motion Blur now works together with a crop animation.<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">Improvements</span><ul class="mycode_list"><li>Smaller download and installation. Unused libraries are no longer included.<br />
</li>
<li>Dialog buttons show their shortcut key underlined. Buttons with the same first letter now each have their own key.<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">Fixes</span><ul class="mycode_list"><li>Mac: With color management on, visual previews showed shifted colors on wide gamut displays. Color management is now handled by macOS. Visual Deflicker now measures these previews in their own colors, so results can differ slightly from before.<br />
</li>
<li>Visual previews could show black or outdated frames, or stop loading.<br />
</li>
<li>Folder tree: A network drive that did not respond could freeze the window. Cards, drives, new folders and image counts did not always show up.<br />
</li>
<li>Folders with many JPGs on a network drive took very long to load, and switching to another folder could freeze the window for minutes.<br />
</li>
<li>When the open folder was deleted or its drive ejected, it stayed open and saving failed. When the drive came back, a click did not load the folder, and changes could be lost.<br />
</li>
<li>Settings could get lost, for example on a full disk.<br />
</li>
<li>Opening a folder during a batch Multi-Pass Deflicker could overwrite its results.<br />
</li>
<li>Rename with Date Prefix could overwrite images or separate an image from its XMP file.<br />
</li>
<li>A render could start with a wrong color space or orientation.<br />
</li>
<li>Rendering with crop animations could skip frames.<br />
</li>
<li>Initializing a saved sequence shot in portrait orientation turned the images to landscape.<br />
</li>
<li>A rotation set in Lightroom could get lost.<br />
</li>
</ul>
<br />
Update should kick in automatically via auto updater, otherwise you can download the latest version at any time via the <a href="https://lrtimelapse.com/download/beta" target="_blank" rel="noopener" class="mycode_url">beta download page</a>.<br />
<br />
If you experience any issues, please let me know <a href="https://forum.lrtimelapse.com/" target="_blank" rel="noopener" class="mycode_url">in the forum</a>!]]></description>
			<content:encoded><![CDATA[This beta lets Motion Blur work together with a crop animation, and the download and installation are smaller. It also covers visual previews and their colors on wide gamut Macs, folders on network drives and removable drives. Many other smaller fixes are included as well.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">New Features</span><ul class="mycode_list"><li>Motion Blur now works together with a crop animation.<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">Improvements</span><ul class="mycode_list"><li>Smaller download and installation. Unused libraries are no longer included.<br />
</li>
<li>Dialog buttons show their shortcut key underlined. Buttons with the same first letter now each have their own key.<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">Fixes</span><ul class="mycode_list"><li>Mac: With color management on, visual previews showed shifted colors on wide gamut displays. Color management is now handled by macOS. Visual Deflicker now measures these previews in their own colors, so results can differ slightly from before.<br />
</li>
<li>Visual previews could show black or outdated frames, or stop loading.<br />
</li>
<li>Folder tree: A network drive that did not respond could freeze the window. Cards, drives, new folders and image counts did not always show up.<br />
</li>
<li>Folders with many JPGs on a network drive took very long to load, and switching to another folder could freeze the window for minutes.<br />
</li>
<li>When the open folder was deleted or its drive ejected, it stayed open and saving failed. When the drive came back, a click did not load the folder, and changes could be lost.<br />
</li>
<li>Settings could get lost, for example on a full disk.<br />
</li>
<li>Opening a folder during a batch Multi-Pass Deflicker could overwrite its results.<br />
</li>
<li>Rename with Date Prefix could overwrite images or separate an image from its XMP file.<br />
</li>
<li>A render could start with a wrong color space or orientation.<br />
</li>
<li>Rendering with crop animations could skip frames.<br />
</li>
<li>Initializing a saved sequence shot in portrait orientation turned the images to landscape.<br />
</li>
<li>A rotation set in Lightroom could get lost.<br />
</li>
</ul>
<br />
Update should kick in automatically via auto updater, otherwise you can download the latest version at any time via the <a href="https://lrtimelapse.com/download/beta" target="_blank" rel="noopener" class="mycode_url">beta download page</a>.<br />
<br />
If you experience any issues, please let me know <a href="https://forum.lrtimelapse.com/" target="_blank" rel="noopener" class="mycode_url">in the forum</a>!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Singer Island Skies - Storms]]></title>
			<link>https://forum.lrtimelapse.com/Thread-singer-island-skies-storms</link>
			<pubDate>Wed, 18 Nov 2026 12:58:46 +0100</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.lrtimelapse.com/member.php?action=profile&uid=101281">johnbedwards</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.lrtimelapse.com/Thread-singer-island-skies-storms</guid>
			<description><![CDATA[I hope you enjoy a few moments of evening and nighttime storms moving across the ocean off Singer Island, Florida. <br />
<br />
For more than 10 years, I’ve shot thousands of timelapse sequences from the balcony of my home. Only a small number have made the final cut, representing my favorite moments in this collection of short timelapse videos. <br />
<br />
It may be obvious, but best if watched in 4K with sound, even though image quality on YouTube is rather limited. <br />
<br />
John<br />
<br />
<a href="https://youtu.be/8dKm43TMuu0" target="_blank" rel="noopener" class="mycode_url">https://youtu.be/8dKm43TMuu0</a>]]></description>
			<content:encoded><![CDATA[I hope you enjoy a few moments of evening and nighttime storms moving across the ocean off Singer Island, Florida. <br />
<br />
For more than 10 years, I’ve shot thousands of timelapse sequences from the balcony of my home. Only a small number have made the final cut, representing my favorite moments in this collection of short timelapse videos. <br />
<br />
It may be obvious, but best if watched in 4K with sound, even though image quality on YouTube is rather limited. <br />
<br />
John<br />
<br />
<a href="https://youtu.be/8dKm43TMuu0" target="_blank" rel="noopener" class="mycode_url">https://youtu.be/8dKm43TMuu0</a>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Using Images of a timelapse for stills (different and separate editing)]]></title>
			<link>https://forum.lrtimelapse.com/Thread-using-images-of-a-timelapse-for-stills-different-and-separate-editing</link>
			<pubDate>Mon, 16 Nov 2026 19:10:15 +0100</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.lrtimelapse.com/member.php?action=profile&uid=113318">juanmacab</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.lrtimelapse.com/Thread-using-images-of-a-timelapse-for-stills-different-and-separate-editing</guid>
			<description><![CDATA[Hello, my name is Juanma, from Spain. Just starting with LRTimelapse these days, and I have a question, which is kind of two- or three-fold:<br />
<br />
First of all, I'll let you know something I do before starting creating the timelapse, and I will appreciate if anyone can please confirm if I am doing this right or not: when I come home with... say 1000 photos for a timelapse, and first of all I want to edit one or two of them for posting on Instagram, ...am I right to think that then I cannot use that sequence anymore for a timelapse, as one or two of the shots are already edited?<br />
Right or wrong, until now I have considered that I cannot do it, so what I am doing is I'm copying the whole sequence to a different folder (via Windows folders, not with Lightroom), and then I will import that second, unedited sequence into Lightroom later during the LRTimelapse processing.<br />
But this creates a problem: I now have the same sequence of 1000 pictures in two different folders, thus occupying twice the room in my hard drive!<br />
How do I manage this so I don't have this space problem in my hard drive? I could just work with the original sequence, by first removing it from Lightroom and then importing/adding it again during the processing of the timelapse, but in this case I loose the history of the processed images, right? How is all this managed, please?<br />
<br />
The second thing: once I have created the timelapse there is the original sequence of RAW files, plus a new folder with all the intermediate JPGs or TIFFs: if I delete this folder, where am I if I want to render a new video with a different setting (resolution, speed, etc...)? Do I have to start the whole process again if I want to render a new video?<br />
<br />
Last: after having created the timelapse, the folder with the original RAW images now has all of its images edited; if I want to use one of them for a different editing, how does that affect the future rendering of new videos from that already edited sequence?<br />
<br />
I don't know if I can quite make myself understood or not, as I may still lack the technical language in all this; sorry if that's the case. If anything is not quite clear, please let me know and I'll try to explain it better or in a different way.<br />
<br />
Thanks in advance!]]></description>
			<content:encoded><![CDATA[Hello, my name is Juanma, from Spain. Just starting with LRTimelapse these days, and I have a question, which is kind of two- or three-fold:<br />
<br />
First of all, I'll let you know something I do before starting creating the timelapse, and I will appreciate if anyone can please confirm if I am doing this right or not: when I come home with... say 1000 photos for a timelapse, and first of all I want to edit one or two of them for posting on Instagram, ...am I right to think that then I cannot use that sequence anymore for a timelapse, as one or two of the shots are already edited?<br />
Right or wrong, until now I have considered that I cannot do it, so what I am doing is I'm copying the whole sequence to a different folder (via Windows folders, not with Lightroom), and then I will import that second, unedited sequence into Lightroom later during the LRTimelapse processing.<br />
But this creates a problem: I now have the same sequence of 1000 pictures in two different folders, thus occupying twice the room in my hard drive!<br />
How do I manage this so I don't have this space problem in my hard drive? I could just work with the original sequence, by first removing it from Lightroom and then importing/adding it again during the processing of the timelapse, but in this case I loose the history of the processed images, right? How is all this managed, please?<br />
<br />
The second thing: once I have created the timelapse there is the original sequence of RAW files, plus a new folder with all the intermediate JPGs or TIFFs: if I delete this folder, where am I if I want to render a new video with a different setting (resolution, speed, etc...)? Do I have to start the whole process again if I want to render a new video?<br />
<br />
Last: after having created the timelapse, the folder with the original RAW images now has all of its images edited; if I want to use one of them for a different editing, how does that affect the future rendering of new videos from that already edited sequence?<br />
<br />
I don't know if I can quite make myself understood or not, as I may still lack the technical language in all this; sorry if that's the case. If anything is not quite clear, please let me know and I'll try to explain it better or in a different way.<br />
<br />
Thanks in advance!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[LRTimelapse 7.5.6 beta 4, 3, 2 and 1]]></title>
			<link>https://forum.lrtimelapse.com/Thread-lrtimelapse-7-5-6-beta-4-3-2-and-1</link>
			<pubDate>Fri, 13 Nov 2026 14:38:04 +0100</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.lrtimelapse.com/member.php?action=profile&uid=2">Gunther</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.lrtimelapse.com/Thread-lrtimelapse-7-5-6-beta-4-3-2-and-1</guid>
			<description><![CDATA[These Betas contain a lot of fixes and stability improvements. Please use the latest in your daily workflow and let me know if you encounter any issues. Thank you!<br />
<br />
<span style="font-weight: bold;" class="mycode_b">7.5.6 beta 4</span><ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Fix:</span> An installed license no longer disappears after a restart when an invalid license file had been chosen before.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Visual previews no longer stall forever when the Adobe DNG Converter hangs. A converter process that does not finish within five minutes is ended. After three such processes in a row LRTimelapse turns the visual previews off and says why. The log names the file and the converter version, and reports when the previews make no progress for two minutes.<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">7.5.6 beta 3</span><ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Improvement:</span> Batch operations list the subfolders in the order of the folder tree and process them in that order.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Improvement:</span> Waiting compositions show their folder in the batch queue.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Batch deflicker processes sequences in capture time order, like the main window.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Deflicker: Very bright or very dark outlier frames are corrected in the right direction.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Applying the Simple Deflicker again replaces all previous values.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Deflickering a selection uses the same smoothing strength as the whole sequence.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> The saved defaults for Increase Rating and Mark as Finished are restored correctly.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Changing Ignore Blacks/Whites in the batch deflicker dialog no longer affects the open sequence.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> A single click on a slider name in the editor no longer resets the value. A double click resets it.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> The value popup accepts both comma and point as decimal separator and no longer cuts off decimals.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Editing a 5-star keyframe in the editor keeps it a 5-star keyframe.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Sync in the editor always transfers the edits, and Shift+Click on Sync back transfers them to all previous keyframes.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Batch Deflicker writes the preview video into the render folder of the processed sequence, not into the one of the sequence open in the main window.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Batch operations on a parent folder no longer process the subfolder that is loaded in the main window. It is shown in red in the list of subfolders.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Batch Auto Transition can no longer be applied to the folder loaded in the main window, like the other batch operations.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Exporting several folders with LRTExport no longer removes the existing intermediate frames when not all images are selected.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> When the internal export cannot export some images, a message now says so instead of the render silently not starting.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Images that fail during the internal export are reliably retried in the second attempt.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Internal export: Images for which the DNG Converter reported success without writing a file are retried instead of silently missing in the video. A damaged JPG is now reported in the log.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> The sync scripts keep the Holy Grail and deflicker masks of every keyframe, also when a keyframe was reset or a mask was deleted in Lightroom.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> An installed license no longer disappears after a restart when an invalid license file had been chosen before.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> A deleted LRT mask keeps its place, so mask settings stay with the right mask across the sequence.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Cancelling the output folder selection in the render dialog keeps the folder and the render settings of the sequence.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> A locked crop offset is kept for all sequences.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Rendering with "Source resolution" right after choosing a sequence, or several sequences at once, uses the size of each sequence, not the one loaded before.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Cancelling the output folder selection while the render dialog is open and another folder is loaded switches the dialog properly back to Render.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Composition: "Remove frames" always takes the frames from the start and the end of the sequence, also with "Invert".<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Composition: The last stripe shows the last image of the sequence.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Composition: When you create compositions for several folders, a short folder no longer lowers the number of stripes for the following ones.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Composition: A folder without images in a multiple selection no longer stops the compositions of the other folders.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Composition: Compositions carry the color profile of the sequence again, and JPG compositions are no longer reported as failed.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Composition: A very short folder still gets a composition when "Remove frames" would leave no image.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Composition: A composition never carries the color profile of the folder loaded before.<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">7.5.6 beta 2</span><ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Rendering could fail when a folder name contained a percent sign.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Portrait sequences rendered from Lightroom or in batch mode could be rendered larger than the selected resolution and were then named OriRes.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Auto Transition keeps the camera profile and other String parameters, even when the first image is not a keyframe.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Eased transitions over very short selections no longer produce invalid values.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Batch transition is not tied anymore to the column selection in the table.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Manual transitions with a single keyframe also apply its crop to all images.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Keyframes and edits made while previews are still loading are saved, and LRTimelapse asks about them before closing.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Cleared values are reliably removed from the metadata when saving.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Exposure and other values saved with a decimal comma are read correctly.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Reference boxes stay on the right images after switching between folders with different sort orders.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> JPG and TIFF sequences edited in Lightroom keep their white balance when opened for the first time.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> The default 16:9 crop fits frames wider than 16:9.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Importer: Importing without DNG conversion keeps DNG files that are already in the destination.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Importer: When the DNG conversion produces no file, the imported original is kept.<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">7.5.6 beta 1</span><ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Fix:</span> HDR Jpgs from Google Pixel Phones could not be saved.<br />
</li>
</ul>
]]></description>
			<content:encoded><![CDATA[These Betas contain a lot of fixes and stability improvements. Please use the latest in your daily workflow and let me know if you encounter any issues. Thank you!<br />
<br />
<span style="font-weight: bold;" class="mycode_b">7.5.6 beta 4</span><ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Fix:</span> An installed license no longer disappears after a restart when an invalid license file had been chosen before.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Visual previews no longer stall forever when the Adobe DNG Converter hangs. A converter process that does not finish within five minutes is ended. After three such processes in a row LRTimelapse turns the visual previews off and says why. The log names the file and the converter version, and reports when the previews make no progress for two minutes.<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">7.5.6 beta 3</span><ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Improvement:</span> Batch operations list the subfolders in the order of the folder tree and process them in that order.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Improvement:</span> Waiting compositions show their folder in the batch queue.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Batch deflicker processes sequences in capture time order, like the main window.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Deflicker: Very bright or very dark outlier frames are corrected in the right direction.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Applying the Simple Deflicker again replaces all previous values.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Deflickering a selection uses the same smoothing strength as the whole sequence.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> The saved defaults for Increase Rating and Mark as Finished are restored correctly.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Changing Ignore Blacks/Whites in the batch deflicker dialog no longer affects the open sequence.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> A single click on a slider name in the editor no longer resets the value. A double click resets it.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> The value popup accepts both comma and point as decimal separator and no longer cuts off decimals.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Editing a 5-star keyframe in the editor keeps it a 5-star keyframe.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Sync in the editor always transfers the edits, and Shift+Click on Sync back transfers them to all previous keyframes.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Batch Deflicker writes the preview video into the render folder of the processed sequence, not into the one of the sequence open in the main window.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Batch operations on a parent folder no longer process the subfolder that is loaded in the main window. It is shown in red in the list of subfolders.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Batch Auto Transition can no longer be applied to the folder loaded in the main window, like the other batch operations.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Exporting several folders with LRTExport no longer removes the existing intermediate frames when not all images are selected.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> When the internal export cannot export some images, a message now says so instead of the render silently not starting.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Images that fail during the internal export are reliably retried in the second attempt.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Internal export: Images for which the DNG Converter reported success without writing a file are retried instead of silently missing in the video. A damaged JPG is now reported in the log.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> The sync scripts keep the Holy Grail and deflicker masks of every keyframe, also when a keyframe was reset or a mask was deleted in Lightroom.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> An installed license no longer disappears after a restart when an invalid license file had been chosen before.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> A deleted LRT mask keeps its place, so mask settings stay with the right mask across the sequence.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Cancelling the output folder selection in the render dialog keeps the folder and the render settings of the sequence.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> A locked crop offset is kept for all sequences.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Rendering with "Source resolution" right after choosing a sequence, or several sequences at once, uses the size of each sequence, not the one loaded before.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Cancelling the output folder selection while the render dialog is open and another folder is loaded switches the dialog properly back to Render.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Composition: "Remove frames" always takes the frames from the start and the end of the sequence, also with "Invert".<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Composition: The last stripe shows the last image of the sequence.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Composition: When you create compositions for several folders, a short folder no longer lowers the number of stripes for the following ones.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Composition: A folder without images in a multiple selection no longer stops the compositions of the other folders.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Composition: Compositions carry the color profile of the sequence again, and JPG compositions are no longer reported as failed.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Composition: A very short folder still gets a composition when "Remove frames" would leave no image.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Composition: A composition never carries the color profile of the folder loaded before.<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">7.5.6 beta 2</span><ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Rendering could fail when a folder name contained a percent sign.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Portrait sequences rendered from Lightroom or in batch mode could be rendered larger than the selected resolution and were then named OriRes.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Auto Transition keeps the camera profile and other String parameters, even when the first image is not a keyframe.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Eased transitions over very short selections no longer produce invalid values.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Batch transition is not tied anymore to the column selection in the table.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Manual transitions with a single keyframe also apply its crop to all images.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Keyframes and edits made while previews are still loading are saved, and LRTimelapse asks about them before closing.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Cleared values are reliably removed from the metadata when saving.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Exposure and other values saved with a decimal comma are read correctly.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Reference boxes stay on the right images after switching between folders with different sort orders.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> JPG and TIFF sequences edited in Lightroom keep their white balance when opened for the first time.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> The default 16:9 crop fits frames wider than 16:9.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Importer: Importing without DNG conversion keeps DNG files that are already in the destination.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Fix:</span> Importer: When the DNG conversion produces no file, the imported original is kept.<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">7.5.6 beta 1</span><ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Fix:</span> HDR Jpgs from Google Pixel Phones could not be saved.<br />
</li>
</ul>
]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[LRT marked as NOT LICENSED]]></title>
			<link>https://forum.lrtimelapse.com/Thread-lrt-marked-as-not-licensed</link>
			<pubDate>Thu, 05 Nov 2026 22:37:19 +0100</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.lrtimelapse.com/member.php?action=profile&uid=112932">southcitycamera</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.lrtimelapse.com/Thread-lrt-marked-as-not-licensed</guid>
			<description><![CDATA[I had to reset my computer and it wiped out everything ... when I reloaded LRT it comes up NOT LICENSED How do I get my PROFESSIONAL LICENSE back.<br />
I tried to have it resent but did not work   please advise ... jimmy]]></description>
			<content:encoded><![CDATA[I had to reset my computer and it wiped out everything ... when I reloaded LRT it comes up NOT LICENSED How do I get my PROFESSIONAL LICENSE back.<br />
I tried to have it resent but did not work   please advise ... jimmy]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[A bug in LR TL - per Claude debugging.]]></title>
			<link>https://forum.lrtimelapse.com/Thread-a-bug-in-lr-tl-per-claude-debugging</link>
			<pubDate>Wed, 04 Nov 2026 22:31:32 +0100</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.lrtimelapse.com/member.php?action=profile&uid=100052">slabkoff</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.lrtimelapse.com/Thread-a-bug-in-lr-tl-per-claude-debugging</guid>
			<description><![CDATA[The last few times I used LR TL (LRTimelapse 7.5.5 (2026-09-14) build 1059) - a strange thing cropped up. <br />
<br />
System: Mac Studio M2 Ultra, 128 GB RAM, 2 TB SSD. Running MacOS 26.6.2 (Tahoe).<br />
<br />
My intervals that were coming into use were taking every 8th frame of the stack coming from the camera and getting the XMP data wrong. The sequence was shot on a Nikon Z6ii using the internal intervalometer with a 3s interval with a constant set of settings (camera on manual).  Every 8th frame had the file name and shoot time wrong in LR TL. THis was causing every 8th frame to be out of order.<br />
<br />
When I exported the stack by sorting by acquisition time (exif data) from Lightroom, that corrected the issue.  In talking to Claude about the issue, it thought that there may be an issue during import - specifically around parallel processing of frames. as every 8th frame was incorrectly labeled. <br />
<br />
The full Claude discussion is here - it wanted me to share the files w/ you but I don't see a way to do that easily.  Please reach out to me privately and I can set up a Google Drive w/ the data for you to review.<br />
<br />
****<br />
From Claude:<br />
<br />
I found it: the camera is fine. The bad timestamps are in the XMP sidecar files, and LRTimelapse wrote those files.<br />
<br />
I checked DSC_5690 through DSC_5839 (150 frames).<br />
<br />
The NEFs (and JPGs) are perfect. Every raw file’s capture time is exactly 3.00 seconds after the one before (±0.01 s), with no gaps or reversals. Your Z6 II and its intervalometer did their job, and Interval priority isn’t involved.<br />
<br />
The XMPs are wrong on exactly every 8th frame. In this stretch, DSC_5690, 5698, 5706, 5714, 5722, 5730, 5738 and so on each have a DateTimeOriginal in the .xmp that doesn’t match the NEF. The wrong value isn’t random. It’s the correct capture time of a different frame from that same every-8th group. For example:<br />
<br />
File	True time (NEF)	Time in XMP	Whose time that really is<br />
DSC_5714	14:37:42.01	14:38:06.02	DSC_5722<br />
DSC_5722	14:38:06.02	14:36:54.01	DSC_5698<br />
DSC_5738	14:38:54.01	14:37:42.01	DSC_5714<br />
DSC_5754 onward			the frame 8 earlier<br />
<br />
That’s what produced your “27.0 / neg” and “neg / 1'15" pairs. The 7 frames in between are all correct.<br />
<br />
Who wrote it: every XMP lists “LRTimelapse Pro 7.5.5 (Mac/ARM)” as the creator tool, with a metadata date of today at 4:15 PM, right around your screenshot. So these times came from LRTimelapse’s own metadata reading and writing, not from Lightroom or the camera.<br />
<br />
My best guess at why: an error that repeats on a fixed 8-frame cycle looks like a bug in parallel processing. If LRTimelapse reads metadata in batches of 8 (one per worker thread), one result per batch landing on the wrong file would produce exactly this pattern. That’s my inference, not something I can confirm, but it also fits the Fayerweather moonrise problem. Sorting by capture time in Lightroom worked there because Lightroom was using the correct times from the raw files.<br />
<br />
What I’d do:<br />
<br />
Report it to Gunther on the LRTimelapse forum or by email. Mention version 7.5.5 Mac/ARM, the every-8th-frame pattern, and that the NEF times are correct while the XMP times are wrong. Include 3 or 4 NEF/XMP pairs, such as DSC_5713, 5714, 5715 and 5722.<br />
Fix this sequence’s XMPs by copying the correct capture time from each NEF into its XMP. ExifTool can do this in one pass, and it leaves your LRT and Lightroom edits alone. I can do it for the whole folder, backing up the XMPs first. Just say so.<br />
<br />
One side note: every XMP I looked at also says RawFileName="DSC_5357.NEF" (your first frame) and has the same DocumentID. That may just be how LRTimelapse copies settings across a sequence, but it’s worth mentioning to Gunther too.]]></description>
			<content:encoded><![CDATA[The last few times I used LR TL (LRTimelapse 7.5.5 (2026-09-14) build 1059) - a strange thing cropped up. <br />
<br />
System: Mac Studio M2 Ultra, 128 GB RAM, 2 TB SSD. Running MacOS 26.6.2 (Tahoe).<br />
<br />
My intervals that were coming into use were taking every 8th frame of the stack coming from the camera and getting the XMP data wrong. The sequence was shot on a Nikon Z6ii using the internal intervalometer with a 3s interval with a constant set of settings (camera on manual).  Every 8th frame had the file name and shoot time wrong in LR TL. THis was causing every 8th frame to be out of order.<br />
<br />
When I exported the stack by sorting by acquisition time (exif data) from Lightroom, that corrected the issue.  In talking to Claude about the issue, it thought that there may be an issue during import - specifically around parallel processing of frames. as every 8th frame was incorrectly labeled. <br />
<br />
The full Claude discussion is here - it wanted me to share the files w/ you but I don't see a way to do that easily.  Please reach out to me privately and I can set up a Google Drive w/ the data for you to review.<br />
<br />
****<br />
From Claude:<br />
<br />
I found it: the camera is fine. The bad timestamps are in the XMP sidecar files, and LRTimelapse wrote those files.<br />
<br />
I checked DSC_5690 through DSC_5839 (150 frames).<br />
<br />
The NEFs (and JPGs) are perfect. Every raw file’s capture time is exactly 3.00 seconds after the one before (±0.01 s), with no gaps or reversals. Your Z6 II and its intervalometer did their job, and Interval priority isn’t involved.<br />
<br />
The XMPs are wrong on exactly every 8th frame. In this stretch, DSC_5690, 5698, 5706, 5714, 5722, 5730, 5738 and so on each have a DateTimeOriginal in the .xmp that doesn’t match the NEF. The wrong value isn’t random. It’s the correct capture time of a different frame from that same every-8th group. For example:<br />
<br />
File	True time (NEF)	Time in XMP	Whose time that really is<br />
DSC_5714	14:37:42.01	14:38:06.02	DSC_5722<br />
DSC_5722	14:38:06.02	14:36:54.01	DSC_5698<br />
DSC_5738	14:38:54.01	14:37:42.01	DSC_5714<br />
DSC_5754 onward			the frame 8 earlier<br />
<br />
That’s what produced your “27.0 / neg” and “neg / 1'15" pairs. The 7 frames in between are all correct.<br />
<br />
Who wrote it: every XMP lists “LRTimelapse Pro 7.5.5 (Mac/ARM)” as the creator tool, with a metadata date of today at 4:15 PM, right around your screenshot. So these times came from LRTimelapse’s own metadata reading and writing, not from Lightroom or the camera.<br />
<br />
My best guess at why: an error that repeats on a fixed 8-frame cycle looks like a bug in parallel processing. If LRTimelapse reads metadata in batches of 8 (one per worker thread), one result per batch landing on the wrong file would produce exactly this pattern. That’s my inference, not something I can confirm, but it also fits the Fayerweather moonrise problem. Sorting by capture time in Lightroom worked there because Lightroom was using the correct times from the raw files.<br />
<br />
What I’d do:<br />
<br />
Report it to Gunther on the LRTimelapse forum or by email. Mention version 7.5.5 Mac/ARM, the every-8th-frame pattern, and that the NEF times are correct while the XMP times are wrong. Include 3 or 4 NEF/XMP pairs, such as DSC_5713, 5714, 5715 and 5722.<br />
Fix this sequence’s XMPs by copying the correct capture time from each NEF into its XMP. ExifTool can do this in one pass, and it leaves your LRT and Lightroom edits alone. I can do it for the whole folder, backing up the XMPs first. Just say so.<br />
<br />
One side note: every XMP I looked at also says RawFileName="DSC_5357.NEF" (your first frame) and has the same DocumentID. That may just be how LRTimelapse copies settings across a sequence, but it’s worth mentioning to Gunther too.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Issue with Filter for Long Term Timelapse]]></title>
			<link>https://forum.lrtimelapse.com/Thread-issue-with-filter-for-long-term-timelapse</link>
			<pubDate>Mon, 02 Nov 2026 18:33:33 +0100</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.lrtimelapse.com/member.php?action=profile&uid=88710">Olivia</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.lrtimelapse.com/Thread-issue-with-filter-for-long-term-timelapse</guid>
			<description><![CDATA[Hi,<br />
Wondering if theres a bug in the Filter. I use it all the time for longterm timelapse, but recently have been having issues where I will select images, or use the time/day filter and it removes the images you want to keep, rather than the ones you've highlighted. <br />
<br />
Screenshot attached. <br />
<br />
LOG of recent filter where I selected/highlighted 176 images and tried to remove them, but it removed the 15186 images I wanted to keep. <br />
<br />
2026-11-03 06:26:47 [DEB] Showing Message Dialog: Remove Images<br />
2026-11-03 06:26:54 [DEB] dialog closed with Yes / Ok<br />
2026-11-03 06:26:54 [DEB] Creating folder: /Volumes/PS-T9/T9 WIP /1. ALL JPEGs FOR SELECTION_REMOVED<br />
2026-11-03 06:26:55 [DEB] Overflow Watch event on sun.nio.fs.AbstractWatchKey&#36;Event@6019e2d3<br />
2026-11-03 06:26:56 [DEB] Overflow Watch event on sun.nio.fs.AbstractWatchKey&#36;Event@454db692<br />
2026-11-03 06:26:57 [DEB] Overflow Watch event on sun.nio.fs.AbstractWatchKey&#36;Event@6421bdab<br />
2026-11-03 06:26:57 [DEB] Moved 15186 image files to /Volumes/PS-T9/T9 WIP /1. ALL JPEGs FOR SELECTION_REMOVED<br />
2026-11-03 06:26:58 [DEB] Overflow Watch event on sun.nio.fs.AbstractWatchKey&#36;Event@298d3fc4<br />
2026-11-03 06:26:59 [DEB] Overflow Watch event on sun.nio.fs.AbstractWatchKey&#36;Event@6ad4f5c<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3989" target="_blank" title="">Screenshot 2026-11-03 at 6.26.46 AM.png</a> (Size: 419.04 KB / Downloads: 8)
<!-- end: postbit_attachments_attachment --><br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3990" target="_blank" title="">Screenshot 2026-11-03 at 6.27.10 AM.png</a> (Size: 15.61 KB / Downloads: 3)
<!-- end: postbit_attachments_attachment --><br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3991" target="_blank" title="">Screenshot 2026-11-03 at 6.26.52 AM.png</a> (Size: 261.22 KB / Downloads: 3)
<!-- end: postbit_attachments_attachment -->]]></description>
			<content:encoded><![CDATA[Hi,<br />
Wondering if theres a bug in the Filter. I use it all the time for longterm timelapse, but recently have been having issues where I will select images, or use the time/day filter and it removes the images you want to keep, rather than the ones you've highlighted. <br />
<br />
Screenshot attached. <br />
<br />
LOG of recent filter where I selected/highlighted 176 images and tried to remove them, but it removed the 15186 images I wanted to keep. <br />
<br />
2026-11-03 06:26:47 [DEB] Showing Message Dialog: Remove Images<br />
2026-11-03 06:26:54 [DEB] dialog closed with Yes / Ok<br />
2026-11-03 06:26:54 [DEB] Creating folder: /Volumes/PS-T9/T9 WIP /1. ALL JPEGs FOR SELECTION_REMOVED<br />
2026-11-03 06:26:55 [DEB] Overflow Watch event on sun.nio.fs.AbstractWatchKey&#36;Event@6019e2d3<br />
2026-11-03 06:26:56 [DEB] Overflow Watch event on sun.nio.fs.AbstractWatchKey&#36;Event@454db692<br />
2026-11-03 06:26:57 [DEB] Overflow Watch event on sun.nio.fs.AbstractWatchKey&#36;Event@6421bdab<br />
2026-11-03 06:26:57 [DEB] Moved 15186 image files to /Volumes/PS-T9/T9 WIP /1. ALL JPEGs FOR SELECTION_REMOVED<br />
2026-11-03 06:26:58 [DEB] Overflow Watch event on sun.nio.fs.AbstractWatchKey&#36;Event@298d3fc4<br />
2026-11-03 06:26:59 [DEB] Overflow Watch event on sun.nio.fs.AbstractWatchKey&#36;Event@6ad4f5c<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3989" target="_blank" title="">Screenshot 2026-11-03 at 6.26.46 AM.png</a> (Size: 419.04 KB / Downloads: 8)
<!-- end: postbit_attachments_attachment --><br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3990" target="_blank" title="">Screenshot 2026-11-03 at 6.27.10 AM.png</a> (Size: 15.61 KB / Downloads: 3)
<!-- end: postbit_attachments_attachment --><br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3991" target="_blank" title="">Screenshot 2026-11-03 at 6.26.52 AM.png</a> (Size: 261.22 KB / Downloads: 3)
<!-- end: postbit_attachments_attachment -->]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Apple Silicon discussion]]></title>
			<link>https://forum.lrtimelapse.com/Thread-apple-silicon-discussion</link>
			<pubDate>Mon, 02 Nov 2026 10:13:47 +0100</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.lrtimelapse.com/member.php?action=profile&uid=113305">mayerto</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.lrtimelapse.com/Thread-apple-silicon-discussion</guid>
			<description><![CDATA[Hi,<br />
I'm looking to replace my MacBook Air and Mac Studio with a MacBook Pro. <br />
I just wanted to check if the statement from 2022 in the M1 discussion still holds up: Only CPU matters, GPU is not used in LRT and it doesn't need more than 32GB RAM? <br />
The current M5 pretty much restricts CPU cores outside a Mac Studio to 18 cores anyways, the questions is pretty much if there is (or maybe ever will be) a benefit going for the 40 core GPU (instead of 32) or more than the 36GB RAM. <br />
I do use RAWs from the A7R series, so up to 140MB per image and sometimes up to a couple thousand (biggest I had was 3000) images per timelapse, if that matters at all. <br />
<br />
LRT is pretty much the only use I have that maxes out my PC, so I want to make sure to give it as much power as possible to get the jobs done as quickly as possible. <br />
<br />
Thanks! <img src="https://forum.lrtimelapse.com/images/smilies/smile.gif" alt="Smile" title="Smile" class="smilie smilie_1" /><br />
Torben]]></description>
			<content:encoded><![CDATA[Hi,<br />
I'm looking to replace my MacBook Air and Mac Studio with a MacBook Pro. <br />
I just wanted to check if the statement from 2022 in the M1 discussion still holds up: Only CPU matters, GPU is not used in LRT and it doesn't need more than 32GB RAM? <br />
The current M5 pretty much restricts CPU cores outside a Mac Studio to 18 cores anyways, the questions is pretty much if there is (or maybe ever will be) a benefit going for the 40 core GPU (instead of 32) or more than the 36GB RAM. <br />
I do use RAWs from the A7R series, so up to 140MB per image and sometimes up to a couple thousand (biggest I had was 3000) images per timelapse, if that matters at all. <br />
<br />
LRT is pretty much the only use I have that maxes out my PC, so I want to make sure to give it as much power as possible to get the jobs done as quickly as possible. <br />
<br />
Thanks! <img src="https://forum.lrtimelapse.com/images/smilies/smile.gif" alt="Smile" title="Smile" class="smilie smilie_1" /><br />
Torben]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[LR edits only applying to keyframe after auto transition]]></title>
			<link>https://forum.lrtimelapse.com/Thread-lr-edits-only-applying-to-keyframe-after-auto-transition</link>
			<pubDate>Sun, 01 Nov 2026 20:59:42 +0100</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.lrtimelapse.com/member.php?action=profile&uid=98487">Slugger Media</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.lrtimelapse.com/Thread-lr-edits-only-applying-to-keyframe-after-auto-transition</guid>
			<description><![CDATA[I have seen threads similar to this subject but not quite with my exact scenario. I will admit that this sequence is quite Under exposed, however I have brought much worse sequences to life in the past.<br />
I'm having something strange happen. Im working on a HG sequence that goes into a astro milky way scene. Only the keyframe edits only show in LR Timelapse after the usual workflow, not the frames in between. As you can see from the screenshots, there are spikes where the keyframe edits are and the unedited frames in between. I have tried numerous different visual luminance reference areas.<br />
I have watched the expert tips #5 video and tried to troubleshoot with those suggestions with no success. I have one by one gone through disabling each setting one by one still with no luck. I am using camera standard as a profile. As you can see from the screenshots my edits are quite minimal, I feel something else is happening.<br />
<br />
I also have a separate issue involving masks. Gunther I know you're not a big fan of this but I am adding to one of your masks with the add sky feature. It worked fine on my keyframes but after auto transition in LRT I see your original top mask gradient (#4) at the top of my frame and not to the rest of the mask that added to mask #4. I have read all the posts about this and have had success with it in the past. (with static shots) When adding to the mask I synced in LR to the rest of the sequence before applying any editing.<br />
<br />
I've spent days trying different things with no success. Here are my specs:<br />
Mac Golden Gate 27.0.1<br />
LRT Pro License 7.5.5<br />
Lightroom Classic 15.6<br />
Adobe DNG 18.7<br />
<br />
Gunther I have also sent you the log for this.<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3986" target="_blank" title="">Screenshot 2026-10-14 at 3.21.03 PM.png</a> (Size: 449.4 KB / Downloads: 6)
<!-- end: postbit_attachments_attachment --><br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3987" target="_blank" title="">Screenshot 1.png</a> (Size: 456.96 KB / Downloads: 6)
<!-- end: postbit_attachments_attachment --><br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3988" target="_blank" title="">Screenshot 2.png</a> (Size: 467.66 KB / Downloads: 3)
<!-- end: postbit_attachments_attachment -->]]></description>
			<content:encoded><![CDATA[I have seen threads similar to this subject but not quite with my exact scenario. I will admit that this sequence is quite Under exposed, however I have brought much worse sequences to life in the past.<br />
I'm having something strange happen. Im working on a HG sequence that goes into a astro milky way scene. Only the keyframe edits only show in LR Timelapse after the usual workflow, not the frames in between. As you can see from the screenshots, there are spikes where the keyframe edits are and the unedited frames in between. I have tried numerous different visual luminance reference areas.<br />
I have watched the expert tips #5 video and tried to troubleshoot with those suggestions with no success. I have one by one gone through disabling each setting one by one still with no luck. I am using camera standard as a profile. As you can see from the screenshots my edits are quite minimal, I feel something else is happening.<br />
<br />
I also have a separate issue involving masks. Gunther I know you're not a big fan of this but I am adding to one of your masks with the add sky feature. It worked fine on my keyframes but after auto transition in LRT I see your original top mask gradient (#4) at the top of my frame and not to the rest of the mask that added to mask #4. I have read all the posts about this and have had success with it in the past. (with static shots) When adding to the mask I synced in LR to the rest of the sequence before applying any editing.<br />
<br />
I've spent days trying different things with no success. Here are my specs:<br />
Mac Golden Gate 27.0.1<br />
LRT Pro License 7.5.5<br />
Lightroom Classic 15.6<br />
Adobe DNG 18.7<br />
<br />
Gunther I have also sent you the log for this.<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3986" target="_blank" title="">Screenshot 2026-10-14 at 3.21.03 PM.png</a> (Size: 449.4 KB / Downloads: 6)
<!-- end: postbit_attachments_attachment --><br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3987" target="_blank" title="">Screenshot 1.png</a> (Size: 456.96 KB / Downloads: 6)
<!-- end: postbit_attachments_attachment --><br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3988" target="_blank" title="">Screenshot 2.png</a> (Size: 467.66 KB / Downloads: 3)
<!-- end: postbit_attachments_attachment -->]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Keyframes not importing to Lightroom and Visual Preview stuck at 1%]]></title>
			<link>https://forum.lrtimelapse.com/Thread-keyframes-not-importing-to-lightroom-and-visual-preview-stuck-at-1</link>
			<pubDate>Wed, 28 Oct 2026 21:17:13 +0100</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.lrtimelapse.com/member.php?action=profile&uid=113301">Richie</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.lrtimelapse.com/Thread-keyframes-not-importing-to-lightroom-and-visual-preview-stuck-at-1</guid>
			<description><![CDATA[Hello Gunther,<br />
First, let me say that I have been using LRTimelapse professionally for many years now and it is an absolutely essential part of my workflow.  I am so grateful for all of the time and care that you put into this product and your obvious love for timelapse is infectious.  I've used your program on thousands of timelapses over the years and it makes all the difference.  Bravo!<br />
<br />
I am running into a problem that I have never encountered before that has me scratching my head.  I've dug through the FAQs and tried a number of things, but still having issues.  <br />
<br />
My first problem is that Lightroom isn't reading the keyframes I set in LRT.  I read this post: <a href="https://forum.lrtimelapse.com/Thread-keyframes-metadata-editing-from-lrtimelapse-not-visible-in-lightroom-or-vise-versa" target="_blank" rel="noopener" class="mycode_url">https://forum.lrtimelapse.com/Thread-key...vise-versa</a> and tried all of that, but it didn't fix the problem.  I tried to bypass this by adding my own keyframes on the first and last frames in Lightroom, then saved the metadata and returned to LRT.  The changes appear in LRT, so I run the AutoTransition, and it adds all of the changes through the sequence.  I didn't mention until now that this is a 9000 frame sequence.  I do a lot of construction timelapse, and LRT has handled this many photos with ease in the past.  After applying the Autotransition, I hit the Visual Preview button, but it gets stuck at 1%.  I've waited hours, but no movement beyond 1%.  <br />
<br />
There was one corrupt file in the sequence, so I removed it, and deleted the folder from Lightroom, and attempted to re-import it.  Still no keyframes.  I tried this a second time and still getting no keyframes.  I'm running the latest versions of Lightroom, LRT, and the DNG converter.  I just did a timelapse last week with no problems, and changed no system settings before this issue started.   As a test, I just tried with a shorter sequence- only 625 frames- and also no keyframe recognition after import.  Ughh...<br />
<br />
I'm at a loss of what to do next... any ideas?<br />
<br />
Thanks!<br />
Richie]]></description>
			<content:encoded><![CDATA[Hello Gunther,<br />
First, let me say that I have been using LRTimelapse professionally for many years now and it is an absolutely essential part of my workflow.  I am so grateful for all of the time and care that you put into this product and your obvious love for timelapse is infectious.  I've used your program on thousands of timelapses over the years and it makes all the difference.  Bravo!<br />
<br />
I am running into a problem that I have never encountered before that has me scratching my head.  I've dug through the FAQs and tried a number of things, but still having issues.  <br />
<br />
My first problem is that Lightroom isn't reading the keyframes I set in LRT.  I read this post: <a href="https://forum.lrtimelapse.com/Thread-keyframes-metadata-editing-from-lrtimelapse-not-visible-in-lightroom-or-vise-versa" target="_blank" rel="noopener" class="mycode_url">https://forum.lrtimelapse.com/Thread-key...vise-versa</a> and tried all of that, but it didn't fix the problem.  I tried to bypass this by adding my own keyframes on the first and last frames in Lightroom, then saved the metadata and returned to LRT.  The changes appear in LRT, so I run the AutoTransition, and it adds all of the changes through the sequence.  I didn't mention until now that this is a 9000 frame sequence.  I do a lot of construction timelapse, and LRT has handled this many photos with ease in the past.  After applying the Autotransition, I hit the Visual Preview button, but it gets stuck at 1%.  I've waited hours, but no movement beyond 1%.  <br />
<br />
There was one corrupt file in the sequence, so I removed it, and deleted the folder from Lightroom, and attempted to re-import it.  Still no keyframes.  I tried this a second time and still getting no keyframes.  I'm running the latest versions of Lightroom, LRT, and the DNG converter.  I just did a timelapse last week with no problems, and changed no system settings before this issue started.   As a test, I just tried with a shorter sequence- only 625 frames- and also no keyframe recognition after import.  Ughh...<br />
<br />
I'm at a loss of what to do next... any ideas?<br />
<br />
Thanks!<br />
Richie]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[LRTimelapse and LightCraft: Could Compatibility Be Possible?]]></title>
			<link>https://forum.lrtimelapse.com/Thread-lrtimelapse-and-lightcraft-could-compatibility-be-possible</link>
			<pubDate>Fri, 23 Oct 2026 14:47:18 +0200</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.lrtimelapse.com/member.php?action=profile&uid=100390">Bernard Dery</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.lrtimelapse.com/Thread-lrtimelapse-and-lightcraft-could-compatibility-be-possible</guid>
			<description><![CDATA[I'd like to raise a question that may be of interest to several photographers and timelapse creators in this community.<br />
<br />
For years, we've relied on a particularly effective combination to get the most out of our timelapse sequences: LRTimelapse and Adobe Lightroom Classic. Their complementary features have become an integral part of our workflow, particularly when it comes to RAW image processing, managing transitions, and correcting flicker.<br />
<br />
Recently, however, a developer used artificial intelligence to recreate software from the Adobe suite, including Lightroom. This new application, called LightCraft, aims to offer an alternative to Lightroom.<br />
<br />
I'm well aware that the legality of this process is likely to spark considerable debate, both online and potentially in court. However, that is not the subject of my question.<br />
<br />
What I'd like to know is whether it might be possible, in the foreseeable future, for LRTimelapse to become compatible with LightCraft.<br />
<br />
For photographers who create timelapses, could such compatibility be an interesting option, particularly for those who want to explore alternatives to the Adobe ecosystem?<br />
<br />
I'd be very interested to hear Gunther's thoughts, as well as those of the community.<br />
<br />
PS: LightCraft is Open-Source<br />
<br />
Thank you!]]></description>
			<content:encoded><![CDATA[I'd like to raise a question that may be of interest to several photographers and timelapse creators in this community.<br />
<br />
For years, we've relied on a particularly effective combination to get the most out of our timelapse sequences: LRTimelapse and Adobe Lightroom Classic. Their complementary features have become an integral part of our workflow, particularly when it comes to RAW image processing, managing transitions, and correcting flicker.<br />
<br />
Recently, however, a developer used artificial intelligence to recreate software from the Adobe suite, including Lightroom. This new application, called LightCraft, aims to offer an alternative to Lightroom.<br />
<br />
I'm well aware that the legality of this process is likely to spark considerable debate, both online and potentially in court. However, that is not the subject of my question.<br />
<br />
What I'd like to know is whether it might be possible, in the foreseeable future, for LRTimelapse to become compatible with LightCraft.<br />
<br />
For photographers who create timelapses, could such compatibility be an interesting option, particularly for those who want to explore alternatives to the Adobe ecosystem?<br />
<br />
I'd be very interested to hear Gunther's thoughts, as well as those of the community.<br />
<br />
PS: LightCraft is Open-Source<br />
<br />
Thank you!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Singer Island Skies- Daytime Colors]]></title>
			<link>https://forum.lrtimelapse.com/Thread-singer-island-skies-daytime-colors</link>
			<pubDate>Sat, 17 Oct 2026 12:29:26 +0200</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.lrtimelapse.com/member.php?action=profile&uid=101281">johnbedwards</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.lrtimelapse.com/Thread-singer-island-skies-daytime-colors</guid>
			<description><![CDATA[I hope you enjoy a few moments beneath the beautiful skies over Singer Island, Florida. For more than 10 years, I’ve shot thousands of timelapse sequences from the balcony of my home. Only a small number have made the final cut, representing my favorite moments in this collection of short timelapse videos. <br />
<br />
In this video I highlight the range of colors of the ocean and sky throughout the day.<br />
<br />
It may be obvious, but best if watched in 4K with sound, even though image quality on YouTube is rather limited. <br />
<br />
John<br />
<br />
<a href="https://youtu.be/HgdNXH-5nZ8" target="_blank" rel="noopener" class="mycode_url">https://youtu.be/HgdNXH-5nZ8</a>]]></description>
			<content:encoded><![CDATA[I hope you enjoy a few moments beneath the beautiful skies over Singer Island, Florida. For more than 10 years, I’ve shot thousands of timelapse sequences from the balcony of my home. Only a small number have made the final cut, representing my favorite moments in this collection of short timelapse videos. <br />
<br />
In this video I highlight the range of colors of the ocean and sky throughout the day.<br />
<br />
It may be obvious, but best if watched in 4K with sound, even though image quality on YouTube is rather limited. <br />
<br />
John<br />
<br />
<a href="https://youtu.be/HgdNXH-5nZ8" target="_blank" rel="noopener" class="mycode_url">https://youtu.be/HgdNXH-5nZ8</a>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Replacing the LRTimelapse Pro Timer 2.5 battery]]></title>
			<link>https://forum.lrtimelapse.com/Thread-replacing-the-lrtimelapse-pro-timer-2-5-battery</link>
			<pubDate>Fri, 09 Oct 2026 13:43:43 +0200</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.lrtimelapse.com/member.php?action=profile&uid=100969">ruery</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.lrtimelapse.com/Thread-replacing-the-lrtimelapse-pro-timer-2-5-battery</guid>
			<description><![CDATA[First of all, I would like to express my sincere gratitude to Gunther Wegner for inventing this excellent product; as a time-lapse photographer, I use it frequently.<br />
<br />
The clock battery needs to be replaced every two years. I have been using the lrtimelapse pro timer 2.5 for 5 years. This time, I also replaced the LP503035 battery because it was no longer holding a charge well. I upgraded to a 503048 800mAh battery, which should last for many years to come.<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="JPG Image" border="0" alt=".jpg" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3981" target="_blank" title="">微信图片_20261009193516_6_4964.jpg</a> (Size: 185.42 KB / Downloads: 8)
<!-- end: postbit_attachments_attachment --><br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="JPG Image" border="0" alt=".jpg" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3982" target="_blank" title="">微信图片_20261009193517_7_4964.jpg</a> (Size: 281.15 KB / Downloads: 6)
<!-- end: postbit_attachments_attachment --><br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="JPG Image" border="0" alt=".jpg" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3983" target="_blank" title="">微信图片_20261009193518_8_4964.jpg</a> (Size: 385.09 KB / Downloads: 6)
<!-- end: postbit_attachments_attachment --><br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="JPG Image" border="0" alt=".jpg" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3984" target="_blank" title="">微信图片_20261009193519_9_4964.jpg</a> (Size: 258.9 KB / Downloads: 7)
<!-- end: postbit_attachments_attachment --><br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3985" target="_blank" title="">da9c5610-c862-4b87-9f2f-667cf0e76dd6.png</a> (Size: 285.73 KB / Downloads: 12)
<!-- end: postbit_attachments_attachment -->]]></description>
			<content:encoded><![CDATA[First of all, I would like to express my sincere gratitude to Gunther Wegner for inventing this excellent product; as a time-lapse photographer, I use it frequently.<br />
<br />
The clock battery needs to be replaced every two years. I have been using the lrtimelapse pro timer 2.5 for 5 years. This time, I also replaced the LP503035 battery because it was no longer holding a charge well. I upgraded to a 503048 800mAh battery, which should last for many years to come.<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="JPG Image" border="0" alt=".jpg" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3981" target="_blank" title="">微信图片_20261009193516_6_4964.jpg</a> (Size: 185.42 KB / Downloads: 8)
<!-- end: postbit_attachments_attachment --><br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="JPG Image" border="0" alt=".jpg" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3982" target="_blank" title="">微信图片_20261009193517_7_4964.jpg</a> (Size: 281.15 KB / Downloads: 6)
<!-- end: postbit_attachments_attachment --><br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="JPG Image" border="0" alt=".jpg" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3983" target="_blank" title="">微信图片_20261009193518_8_4964.jpg</a> (Size: 385.09 KB / Downloads: 6)
<!-- end: postbit_attachments_attachment --><br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="JPG Image" border="0" alt=".jpg" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3984" target="_blank" title="">微信图片_20261009193519_9_4964.jpg</a> (Size: 258.9 KB / Downloads: 7)
<!-- end: postbit_attachments_attachment --><br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.lrtimelapse.com/images/attachtypes/image.gif" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=3985" target="_blank" title="">da9c5610-c862-4b87-9f2f-667cf0e76dd6.png</a> (Size: 285.73 KB / Downloads: 12)
<!-- end: postbit_attachments_attachment -->]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[The Starry Timelapse Airplane Remover v0.12.0 has just been released!]]></title>
			<link>https://forum.lrtimelapse.com/Thread-the-starry-timelapse-airplane-remover-v0-12-0-has-just-been-released</link>
			<pubDate>Mon, 05 Oct 2026 04:31:47 +0200</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.lrtimelapse.com/member.php?action=profile&uid=105813">brian_in_the_cloud</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.lrtimelapse.com/Thread-the-starry-timelapse-airplane-remover-v0-12-0-has-just-been-released</guid>
			<description><![CDATA[Star 0.12.0: remove airplane and satellite trails from nighttime timelapses<br />
<br />
Star is a free tool that automatically finds and removes airplane, satellite streaks and car headlights from nighttime timelapse image sequences. It aligns the frames to the stars and merges them, so the trails drop out without damaging the sky. It also has a review step where you can fix anything it got wrong.<br />
<br />
New in 0.12.0: a beta desktop app for Linux and Windows, so the graphical interface is no longer macOS-only, and GPU acceleration on Macs, which can speed up processing on the latest hardware. Alignment of moving-camera timelapses also works much better.<br />
<br />
Download: <a href="https://brianm998.github.io/starry_timelapse_airplane_remover/" target="_blank" rel="noopener" class="mycode_url">https://brianm998.github.io/starry_timel...e_remover/</a>]]></description>
			<content:encoded><![CDATA[Star 0.12.0: remove airplane and satellite trails from nighttime timelapses<br />
<br />
Star is a free tool that automatically finds and removes airplane, satellite streaks and car headlights from nighttime timelapse image sequences. It aligns the frames to the stars and merges them, so the trails drop out without damaging the sky. It also has a review step where you can fix anything it got wrong.<br />
<br />
New in 0.12.0: a beta desktop app for Linux and Windows, so the graphical interface is no longer macOS-only, and GPU acceleration on Macs, which can speed up processing on the latest hardware. Alignment of moving-camera timelapses also works much better.<br />
<br />
Download: <a href="https://brianm998.github.io/starry_timelapse_airplane_remover/" target="_blank" rel="noopener" class="mycode_url">https://brianm998.github.io/starry_timel...e_remover/</a>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Firmware 39 beta 5 and 4 for LRT PRO Timer 3.x and 2.5]]></title>
			<link>https://forum.lrtimelapse.com/Thread-firmware-39-beta-5-and-4-for-lrt-pro-timer-3-x-and-2-5</link>
			<pubDate>Sun, 04 Oct 2026 13:07:44 +0200</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.lrtimelapse.com/member.php?action=profile&uid=2">Gunther</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.lrtimelapse.com/Thread-firmware-39-beta-5-and-4-for-lrt-pro-timer-3-x-and-2-5</guid>
			<description><![CDATA[Beta 4 addresses a behavior in Single/Bulb mode where a short click during a running exposure brought up the "Decoupling..." screen again. It also makes the status pages follow the rotary encoder without delay. <br />
<br />
Beta 5 enables the brown-out protection on all PRO Timer devices: if the supply voltage drops below about 2.8 V, the timer restarts. Until now, only devices with the LRTimelapse bootloader 1.2.3 (3.5) had this protection. With this update, you don't need to update the bootloader anymore.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Improvements</span><ul class="mycode_list"><li>Brown-out protection on all devices: if the supply voltage drops below about 2.8 V, the timer now restarts cleanly instead of running on unstably. Until now only devices with the LRTimelapse bootloader 1.2.3 had this.<br />
</li>
<li>The second status page shows the cause of the last restart (e.g. power-on, brown-out) and the brown-out level (B39 = active at about 2.8 V).<br />
</li>
<li>The status pages react immediately to the rotary encoder (removed a fixed 250 ms wait after each refresh).<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">Fixes</span><ul class="mycode_list"><li>Single/Bulb mode: a short click during a running exposure showed "Decoupling..." again; it is now ignored until the exposure has ended.<br />
</li>
</ul>
<br />
The easiest way to install the beta is the new browser based updater at <a href="https://lrtimelapse.com/lrtpt-updater/" target="_blank" rel="noopener" class="mycode_url">lrtimelapse.com/lrtpt-updater</a> (Chrome or Edge, no drive mounting needed). Let me know your experiences with the new updater below!]]></description>
			<content:encoded><![CDATA[Beta 4 addresses a behavior in Single/Bulb mode where a short click during a running exposure brought up the "Decoupling..." screen again. It also makes the status pages follow the rotary encoder without delay. <br />
<br />
Beta 5 enables the brown-out protection on all PRO Timer devices: if the supply voltage drops below about 2.8 V, the timer restarts. Until now, only devices with the LRTimelapse bootloader 1.2.3 (3.5) had this protection. With this update, you don't need to update the bootloader anymore.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Improvements</span><ul class="mycode_list"><li>Brown-out protection on all devices: if the supply voltage drops below about 2.8 V, the timer now restarts cleanly instead of running on unstably. Until now only devices with the LRTimelapse bootloader 1.2.3 had this.<br />
</li>
<li>The second status page shows the cause of the last restart (e.g. power-on, brown-out) and the brown-out level (B39 = active at about 2.8 V).<br />
</li>
<li>The status pages react immediately to the rotary encoder (removed a fixed 250 ms wait after each refresh).<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">Fixes</span><ul class="mycode_list"><li>Single/Bulb mode: a short click during a running exposure showed "Decoupling..." again; it is now ignored until the exposure has ended.<br />
</li>
</ul>
<br />
The easiest way to install the beta is the new browser based updater at <a href="https://lrtimelapse.com/lrtpt-updater/" target="_blank" rel="noopener" class="mycode_url">lrtimelapse.com/lrtpt-updater</a> (Chrome or Edge, no drive mounting needed). Let me know your experiences with the new updater below!]]></content:encoded>
		</item>
	</channel>
</rss>