Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

1H to rename 1500 pictures!

Comments

12 comments

  • Jim R
    I've never used this function before so I gave it a try. It took 2 mins 43 seconds to rename 207 images (.NEF files). If that holds, then it would take about 18 mins to rename 1500 images. I was using a MacBook Pro, which is not as fast as my Mac Pro. Your one hour time seems ridiculous to me.
    0
  • Edward Caruso
    was this on an external drive or over a network?
    also what version of capture one? - I forgot which but there was an update that improved batch renaming.
    0
  • Dimitri Lowette
    Hi,
    It's alway like that with me.
    Last version of C1, running on a Big fat mac pro with OS X 10.6.6.
    Renaming +-1500 .CR2 to jpeg 100% (70 quality)
    The files are already open for an hour in C1 and are on one of the hard drive in the mac pro ( in the same file)
    !?
    Dim
    0
  • Paul Steunebrink
    [quote="dimitri" wrote:
    ...
    Renaming +-1500 .CR2 to jpeg 100% (70 quality)

    Renaming or processing? Sounds more like processing.
    0
  • Dimitri Lowette
    renaming!!
    0
  • Edward Caruso
    just as Paul said:
    you wrote - "Renaming +-1500 .CR2 to jpeg 100% (70 quality)"
    That sounds like processing which might take an hour or more if its that many files.
    Are you selecting the thumbnail images and then choosing batch rename from the right click contextual menu?
    V6 improved batch rename finally and it shouldn't take that long.
    0
  • Dimitri Lowette
    😊 yes sorry, it's renaming, I don't know why I wrote "to jpeg 100% (70 quality)" to tired maybe!!
    D.
    0
  • Drew Altdo
    Took me 25 Minutes on a lesser machine to rename 1,500 images from a G12.
    By contrast it took roughly 3 minutes with a Program designed specifically for renaming (ABFR)

    The only thing I would point out is that when you rename through Capture One, although in your case the time seems exorbitant, it is not simply renaming one file... it is renaming 4 (maybe 5) for each RAW file you want to rename. So, in a worst case scenario the same action in a specialized software would take 18-20 minutes as appose to our 25 minutes. In addition to the renaming of files you may not notice (Settings, Proxie, Focus Mask, XMP) we are also replacing information in the Session file that references your images. All in all, we do alright but it's not as good as a specialized software.
    In the case of it taking 1 Hour, I would create a support case so we can figure out where the hang up is on your system.
    0
  • Daniel Goldwasser
    Drew,
    The slow renaming has always been one of my biggest frustrations with Capture One. I understand that it is renaming 4 or 5 files for each image, but the time really adds up on a high volume shoot i.e 2500+ images per day over 20+ shot folders.
    Do you think this an area where we're likely to see any significant improvements in the future, or is this just one of the trade offs of this design of the program.

    Thanks,
    Daniel
    0
  • Coach2
    You can avoid having to rename "4 (maybe 5) for each RAW file" if you use a third-party program to rename just the raw files before starting Capture One, thus avoiding having to rename it's previews and adjustment files. You can also use a third-party program such as FastStone Image Viewer (free, yes I made a donation), to delete your obvious non-keepers beforehand to speed up CO's preview generation. FastStone has supported many RAW formats, including G12, for some time now.
    0
  • Daniel Goldwasser
    Agreed, there are several work arounds, but depending on the nature of the shoot these are not always possible. Advertising, catalog, lifestyle, etc, shooting tethered, CF card, or both. Clients changing the names at the end of the day... Bottom line is when I want to batch rename in capture one, it just takes a while.
    0
  • Coach2
    You're right it isn't always possible. Because of sensor dust I had to rely on CO to rename the occasional associated LCC files from my recent trip. Though I didn't have a speed issue, renaming in CO did seem to cause several lockups. Still, my workflow helps to speed up most of my processing time.
    0

Post is closed for comments.