Slow batch rename
Hello.
After importing a bunch of new photos I run a batch rename for each day in the session. Usually I don't attend the process (*), since I do as soon as I'm back home and I have other things to do; but recently I noticed it's very slow: roughly 12 minutes for 1000 files (MBPro 16", macOS 11.6.5). Even considering that multiple files for each photo (e.g. caches) have to be renamed and an operation in the database is involved, it looks to me slower than necessary.
Honestly it's not a big issue, but is it possible to do something to mitigate it?
Thanks.
(*) I see there is an old comment (twelve years ago), so perhaps it's really an old issue.
-
Do you really mean a session and not a catalog? In my experience, batch rename is much faster in sessions than in catalogs.
Ian
0 -
Hi, I haven't seen your post. Just posted same issue yesterday. Seems like, for this process you need lots of RAM in Capture One. My maxed out Mac mini 2018 with 64MB beats a MacBook M1 2021 with 16MB. I also have to complain about the speed for a simple batch rename process. Using Capture One marketing phrase "Reimagine your workflow“ – I do it now like in old times (if I don't have time), import and rename the files before on my Mac before importimg them to Capture One 22 with a handy little app called "A Better Finder Rename". If you want to speed up your workflow even more use Photo Mechanic. What a pity, we can't do it that fast in Capture One yet.
0 -
@Ian Yes in Sessions, it's much, much faster, like I would rename via Mac Finder and how it should be.
Seems like the catalog’s database forcing it to slow down. Maybe I will change my workflow for shootings and use sessions.
But still got the problem to do "Digital Asset Management" with many pictures with catalog.
0 -
Sorry for the late response, but I didn't see the notification.
Yes, as Phrank says, I'm working with the catalog.
0 -
I too am seeing this issue. There are two issues with Batch renaming.
1) As others have said, it is far too slow for what its doing.
2) The UX is *very* slow to respond. This is what makes it the most painful part of the experience.
An easy resolution is to tear it off as an asynchronous process (and modify the UX to accommodate). For what its worth, my images are stored on a Synology DS1817+. My MacBook Pro, an M1 Max w/64GB RAM is connected via Hardware Ethernet to my Synology (not using WiFi).
0 -
Just a reminder that it works MUCH faster in a session. (I was surprised at first when people complained it was slow, as it had always been fast for me, but I had previously only done it in sessions, and when I came to do it in a catalog I did find it a lot slower.)
Ian
0
投稿コメントは受け付けていません。
コメント
6件のコメント