Now the user can decide, if he wants to use the external corrections, or LRTimelapse’s Holy Grail Wizard. Both usually provide very similar results. In that case, the external corrections would be overwritten by LRTimelapse’s Holy Grail wizard. Improved support for external rampers like Timelapse View or RamperProĪdded a dialog when external xmp corrections from one of those devices exist and the user tries to invoke the holy grail wizard. Increased the number of possible threads to 24. Users with a private License can now control the number of threads used when creating the visual previews, like pro users. Using systems temp folder for preview conversions now, this might speed up visual preview generation when working on slow drives like network drives. But this is the only way to get the regular previews for such images like Cinema DNG (visual previews have always worked!). The raw files have to be demosaiced for this, so it’s slower as the normal preview extraction. Fixed: On the very first start of LRT on a computer, the log file dialog was shown too small.Ĭonsiderably sped up preview loading for several cameras (for example canon, fuji etc.)Īdded preview support for (Cinema)-DNG files, that do not have any camera previews embedded. (Thanks to forum user Teemu76 for reporting these two issues). Fixed: Under the same precondition like the last issue, the Keyframes Wizard was not activated after a reinitialization of the sequence. Fixed: When “Clear Metadata” was used (normally not something you’d need to do) a subsequent initialization of the metadata didn’t respect the “Set 16:9 crop when initializing” setting. Auto Transition will then take over the values from the keyframes (either from camera or modified by the user) and set them to “Custom” in order to make the transitions. You can then start editing with the White balance that the camera provided as default value on the keyframes. The White Balance information from the camera will now be preserved when bringing the sequence to Lightroom. This makes it easier to keep it always updated in order to ensure support for the latest camera models. Added version check for Adobe DNG Converter. With an UI Scaling of 2.0, the Keyframes Wizard was cut at the bottom, fixed. Creating a new folder from the import dialog did not refresh the folder tree, fixed. Sometimes LRTimelapse did not start with the folder tree at the position where it was closed. Increased the range for the Rotate slider in the Holy Grail Wizard. Please note, that you might have to use quotation marks, like LRTimelapse "C:\temp", depending on your platform and starting method. You can also pass multiple parameters: for example to have LRTimelapse launch at the top left corner of your screen, regardless on how you left off, just use LRTimelapse screenposx1=0 screenposx2=0. To have define a certain start path for example, you could launch LRTimelapse with Any parameter of the LRTimelapse user.props file can now be passed as commandline parameter. Added a “Delete Holy Grail adjustments” button to the toolbar above the table next to “Delete Deflicker” to delete the holy grail adjustments, if necessary. Added Alt-Q as additional shortcut to exit the application. Redesigned the plus/minus buttons next to the slider controls. The button will only appear for sequences shot in A-Mode. However, there seem to be cameras that do not smooth in A-Mode, therefore I’ve added a Button to the Keyframes-Wizard which will allow to force the Holy Grail Keyframe creation. In such cases the HG-Wizard would do more harm than good, because it would calculate compensations for “steps” that are not there. Normally, for sequences shot in A-Mode, the Holy Grail Wizard is deactivated, because such sequences normally come rather smooth from the camera (most cameras do smoothing in A-Mode, but still write discrete values into EXIF). Improved visibility for the visual-preview-creationstatus bar (below the visual previews) on high-dpi displays. The keyframes are now being displayed more opaque, just like in the camera previews mode. In “Visual Preview” mode the keyframe indicators in the preview sometimes were hardly visible. dat index files which for example the Nikon Z7 and Z6 create instead of putting them into a “MISC” folder.
0 Comments
Leave a Reply. |