Luminar 3 Windows: 'Save' operation missing
Just noticed this when trying to save an edit.
Where has the 'Save' gone? How can I save an edit into a lmnr file?
Perhaps there is some other way to save now?
Luminar 3:
Luminar 2018:
-
I'm sorry but I can't say I appreciated this move.
I use Luminar on my laptop, which I use as a temporary photo editing environment before moving the originals along with the edited files AND lmnr projects to different NASes.
If I'm not able to save a project file and my laptop fails I'm screwed, I don't have any copy of what's in the database. Besides databases are not meant to be stored on a cloud drive if they're not cloud-based, so there's no actual redundancy policy applyable to this model. Besides I can't save a single photo project in case I want to later edit that single image (because months after deleting it from the database someone tells me I have to slightly edit it) so I have to either keep all my images on my laptop "just in case" or I lose the chance to continue where I had left off.
I don't like to bring up other software's features but since someone did and, in my opinion, didn't tell the whole story I'm forced to point out that Lightroom behaves a little different from catalog-only: yes, it uses a catalog to store previews, advanced previews and edits; yes, it's true that you can't export a single file containing the original photo along with the editing history and/or the current editing settings; BUT you DO have the chance to export the original plus an xmp file which contains what I did on that file.
I know new software aims to simplify (in order to get more users as well) but we should never give up control for that, that's not what professionals do.
I'd like to have back the chance to save single .lmnr files.
Thanks
Antonio
-
OK, so still learning this Luminar 3 SW, and I am finding that it is family with a lot of other modern design SW. What do I mean by that ? It is going down the path of taking control away from the user, and making "assumptions" about what the user wants to do. I'm sorry but that is stupid idiotic nonsense. Why not just start with a blank screen and hope the user can figure out what to do. So for this particular topic.... WHAT I cannot save a project in a file dedicated to my picture ? Are you folks insane ? Hiding everything in some kind of a catalog database somewhere on my computer !! That is the type of nonsense I expect from Apple or MS windoz these days. Not being able to control what I save and where is absolutely stupid. Who came up with that idea ? Oh yeah,,, modern SW design. Please put basic user control functionality back in ASAP or I may have to write off my purchase cost of Luminar # and just go back to GIMP. (Which is pretty darn good BTW). I was hoping for a more advanced editing capability, not a "modern" SW experience.
-
Kate,
QUOTE This won’t save layers but your filter settings will be saved. As a bonus, you’ll be able to instantly apply the settings you used for a certain project to other projects. END QUOTE
That isn't any sort of bonus ! If we want to do that then that can be done simply be creating a new preset (why on earth you dispense with conventional terminology and call them 'looks' is beyond comprehension).
In return what we've lost is multiple layers and possibly hours of work with local edits. That's inane. Imagine if an editor calls and asks for certain changes and that file/edits no longer exists per se. because of a change in equipment or location.
You guys really need to sort that out ASAP. No wonder there is a lot of anger/frustration out there.
-
I believe it is in the Luminar development roadmap, for a future release.
The problem with the current 'catalog based' way of saving the edits is that when the catalog is corrupted you lose all the edits for all your files. This has happened many time to me so far, due to a bug in the way it handles images after editing (see the black picture problem, which still persists with the current upgrade).
It is very important to be able to save an image edit stack into a separate file. It is too easy to corrupt the catalog.
-
I agree Geoff Swan. I'm also concerned that they will go the way of Luminar 2 or Aurora and create a GIANT file that contains the original plus all of the change data. A side car like ON1 uses would be far more preferable as it's easy to use, back up, restore, move to another system, and doesn't take up a huge amount of space.
Also, if it ever does corrupt, you lose only one set of image edits.
-
In my opinion it was a very bad idea to remove the possiblity to save edits in "lmnr" file format! Because it means one cannot move any edits from one computer to another. One also cannot backup edits to an external disc / memory and so on.
To me, this is an essential feature which was removed without need (e.g. one could have left the "save" option in addition to the Luniar Catalog). Every other program I used at least gave the possibility to copy / backup sidecar files (which contain the edits) together with the original picture files.
I hope Skylum plans to return the "save" function or introduce sidecar files which can be copied and backed up!
-
Have to agree with the 'save' comments here - This is a reason I got Luminar instead of LR in the first place. I can save my full edit stack as a .lmnr file and move it between computers and storage devices, knowing I can easily make minor edits any time - Without having to rely on a Catalogue that is linked to an external SSD.
Luminar - The 'save' feature was useful and a bonus. If LR users didn't like it, don't use it, but don't take it away from those that appreciated it. That for me is big mistake.
-
Hi Robert, less than 1% of users were using the native luminar project file format The decision was made to automatically capture edits in the catalog and Stead allowing people to avoid loss of data from crashing or forgetting to save. If you’d like to see the other functionality restored, please file a future request. Then it can be considered by the team. Thank you for the feedback
-
Richard,
It's simple, I'm used to being able to control what gets saved to my storage device and the format it gets saved. This typically gets done via the typical save commands. Sounds like I'm not missing any functionality, just an unorthodox method of saving data that I don't know how to control yet. What I really regret is the 30 minutes I spent last night trying to figure out before giving up. So, can you send me a link that explains how data is saved, where, and how to specify a format?
Thank you. -
Seems to have attracted some interest.
Anyhow, back to the original observations.
I don't use any Adobe products. They are blacklisted here.
Sometimes I need to open and edit an image that is not in a catalog, nor do I require it to be (may have come from a third party). I see that it now appears in "Quick Edits", which is useful, and contains the edit stack so I can go back and readjust. This effectively replaces the lmnr file. Thanks for clearing this up.
The second problem is that now all I see are black images (since the quick edit) in the catalog. For all folders and albums. This is a bug. Previously restarting L3 cleared this problem for a while, however now it is persistent so I cannot see any images in any part of the catalog. Not really much use any more.
-
This looks mostly like a change management issue. A big change to the mode of operation should be accompanied with support documentation on how to deal with the change. Just dropping Save from the menu is jarring.
So, I gather that Luminar 3 replaces separate project files with a unified catalog that records all adjustments to all files in the catalog. Adjustments to files not in the catalog are stored under Quick Edits. You must move or rename catalogued files using Luminar, not Windows Explorer, to keep the association between the original file and the adjustments. If this is correct, please add it to the user guide. Thanks.
Please sign in to leave a comment.
Comments
40 comments