In Lightroom they have a long time offered the users a compromise with four or five different setup options, some creating a lot smaller previews, to be able to cull faster but the price to pay for that will have to be payed when opening the “Developer” module because than Lightroom have to create previews with much higher resolution and that costs there too.
Lightroom has exactly the same problem by design and it is due to the fact that it’s integrated like Photolab PhotoLibrary now is with the RAW-converter and the need that has for high resolution previews. When I worked with FotoWare (enterprise DAM) that system was rigged to automatically create new folders when they reached 1000 files just of that reason.Īnother important thing to understand. I accept that the keyword functionality I wish for (equal to Lightroom Classic) does not simply fall under “improvement” (as many don’t need what I do), improved performance and ease of use, with a sprinkling of new capabilities, should, I think, be high on the priority list.
If they were to see serious improvement (and there are many suggestions in these forums for what that means) I think it makes PhotoLab into a much better product. I personally believe if they are removed PhotoLab will be a far less compelling product. Either they should all be removed or some effort should be expended to make them better. It has the same basic features that its competitors have. PhotoLab, for better or worse, has a DAM. Same story for keywords that I frequently take issue with and for which others suggest Photo Mechanic or similar. The function is part of PhotoLab but has issues. I wonder what else the pick and reject functions as well as the star ratings are for if not for culling images? PS: I consider this a performance bug of sorts, hence the bug tag. While doing that, I also noticed that moving right at the end of a line (13 thumbnails in a line) to jump the first image of the next line also took longer than usual.Īnyways, maybe this could be improved in future versions. I resorted to not filtering out the rejected images and instead do the tedious reject + cursor right method instead. Sometimes 1 or 2 seconds, in at least one instance I even got the spinning rainbow mouse pointer. However, today there was a very noticeable delay between rejecting the image (by hitting 9) and the image disappearing from view. I have my filter set so that rejected images get filtered out, so that as soon as I reject them, they disappear from the image browser. Usually I end up with a few hundred photos in a single folder only and hadn’t noticed any issues before (I think the biggest folder before today had between 600 and 700 photos). I had to cull through 1273 photos today (I shoot wildlife and today was particularly good ).
0 kommentar(er)
