Hard to add new archives to the DB on Windows #700
-
0.8.6 Windows Currently in LR, to "properly" add a new archive to the database (i.e. adding it to a category, adding tags etc.) I need to go through two major steps:
Only after going through these two excruciating steps (which depending on the situation can take minutes) can you actually get to see the new archive and edit it. This is very much not enjoyable when you're adding multiple archives to the database while reading along. Now, some may ask "But why not use the 'Add Archives' tab built into LR and just drag&drop? Two reasons. Mainly, the "add archives" thing doesn't function very well when you're adding many archives or archives with a large file size - I attempted to add around 6 archives that ranges from ~200MB to 600MB size into the database with the "add archives" function, and LR got stuck processing that task for an hour - while a copy&paste in the windows explorer takes less than 30 seconds. Then there's the fact that "Add archives" drops the added archives straight into the root content folder directory. Personally I prefer having the content folder contain several different child folders by category in the windows explorer so I can view&manage them more easily when I check the explorer locally. LR just sticks everything I add into the root folder, which can be bothersome in this situation. Basically, trying to add a new archive to the database currently is quite a pain in the arse, at least for me. If there are any optimizations that can be done in the future to speed up this process or make it less painful, it would be greatly appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
👋 Converted this to a discussion as it's more of an external issue with the windows port than a fixable bug; Have you tried simply restarting the server instead of triggering a full rescan? |
Beta Was this translation helpful? Give feedback.
👋 Converted this to a discussion as it's more of an external issue with the windows port than a fixable bug;
Have you tried simply restarting the server instead of triggering a full rescan?
I know the filewatcher can be busted on windows depending on a ton of external factors I don't have control over, but after a server restart it usually works long enough to figure out what files were added.