Can Lightroom HDR/Panorama merges save to a different folder instead of the source folder?
Asked 9/22/2016
4 views
2 answers
0
In Lightroom 6.7, I’m testing the built-in HDR and Panorama merge features. My photo library is stored on a read-only filesystem for safety, which has worked fine for normal non-destructive editing.
However, Lightroom’s HDR merge fails because it tries to create the merged file in the same folder as the source images. I assume Panorama merge works the same way.
Is there any way to tell Lightroom to save the intermediate or merged HDR/Panorama output to a different writable folder instead of next to the originals? I’d prefer not to make the source filesystem writable unless that’s the only option.
Originally by Photography Stack Exchange contributor. Source · Licensed CC BY-SA 4.0
Photography Stack Exchange contributor
9y ago
2 Answers
1
I think the short answer is "no" if you are doing a direct lightroom merge to HDR. You can use an edit-in and choose "merge .. in Photoshop" and do the merge there, and from Photoshop you can save-as, though this is not quite the same thing as letting LR do it.
I think the more broad answer is having the drive/folder as read-only is not compatible with a number of lightroom features. When you edit in an external program (most plugins, or even photoshop) the normal behavior is to export a file (usually a TIFF) into the same folder as the original image, and operate on that file. Subsequent edits are usually done by editing that same TIFF (or occasionally producing yet another one). And clearly direct modification such as convert to DNG requires write access, as does writing metadata (for some file types), and updating capture date/time.
While it is perfectly true that Lightroom is "non-destructive" and so should not need to write to the original file for most usage, many of its features assume it can write to the folder on which the file resides, and a very few to the file itself. While there are some workarounds, it may be worth asking if you can put the protections at a file, not folder level, to protect your originals.
Originally by user28109. Source · Licensed CC BY-SA 4.0
user28109
9y ago
0
Generated from our catalog & community — verify before relying on it.
No—Lightroom’s built-in HDR and Panorama merge creates the new merged file alongside the source images, so it needs write access to that folder. There isn’t a setting to redirect that merge output to a different folder.
This limitation also applies to several other Lightroom workflows that generate new files, such as editing in Photoshop or plugins, which typically create a TIFF or similar file next to the original. Some features also require write access for metadata or file conversion tasks.
If you want to keep the originals on a read-only volume, your practical options are:
- temporarily make that folder/volume writable for the merge, or
- use an external editor such as Photoshop via Edit In / Merge, then use Save As to place the result somewhere writable.
So if you want to use Lightroom’s native HDR/Panorama merge, the source folder must be writable.
Recommended products
UniqueBot
AI9y ago
Your Answer
Related Questions
Can Lightroom queue panorama or HDR merges to run later?
Why does Lightroom Classic show Photoshop-edited TIFFs in a different folder after Edit In?
How can I apply a Smart Filter like Unsharp Mask to multiple layers in Photoshop CS5?
Can Lightroom export to a mirrored folder name in a different parent directory?
Why does a stitched panorama TIFF become much larger than the original JPEGs?