lmnr files and ignoring the flakiness of the Luminar database, what is so different about the way Luminar stores edits when compared to Lr, ON1, DxO etc. lmnr files back again.Д«randt whilst I understand that you want.

The squeeky wheel gets the grease so I recommend anyone wanting/needing similar functionality make it known to Skylum that you want. I know there are others with the same concerns as I have as I have caught brief snippets of their thoughts. For me, i am fine with saving standalone files (some of which I choose to retain for future re-editing, and some I can blow away), and using export to pass my edited image back to my main catalog, but to save my edits, I need the ability to save. Capture One makes a new copy in its catalogue of the tiff that it passes to Luminar - but there is no place in Luminar to save my edits and history other than their catalogue so that doesnt really help, and it doesnt recognize Capture One to send the image back, and apparently the Plugin approach does not allow you to save your edits for future reworking.

I started to try to Flex and the plugin route, as I want to skip the whole Luminar DAM, since I use Capture One which actually has a great well thought out DAM in which multiple copies can be created and opened from multiple locations etc. Not sure if that is really a sustainable solution, and locate image isnt even documented, so I have no clear idea how it works etc. However, you might try moving your Catalog and photos to another device, and then trying to Locate Folders.' Luminar support says they 'Currently, we do not recommend such workflow. People with large amounts of images tend to use a more hierarchical arrangement, whereby less frequently edited stuff is migrated over to other media, not trying to keep everything for example in the Pictures directory of their limited desktop storage.

Neofinder dam