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. ⚠️

File Naming / Numbering

matt antrobus
If I use Capture One Pro V3.7.3 to import P25 files from a CF card and utilize the Rename capture facility then the following happens:

file on CF Card \"CF011134\" is renamed as \"test-001134\" which is great apart from dropping the \"ten thousand\" & replacing the \"one\" with a \"zero\".

The previous file shot tethered into the same capture folder is \"test-011133\".

This is a real pain when later sorting files, & I would hope that every file would be having a distinct number until I reach \"999999\".

Anyone know why this is happening & whether i can make capture one rename using the same file number???

thanks

Matt
0

Comments

6 comments

Date Votes
  • Anonymous
    Matt,

    If you decline the offer of Phase One Media Reader to import images from your CF card, then the filenames will remain exactly as the camera named them when transferred to hard disk.

    Using the Batch Rename tool in Capture One, you should be able to set names how you want them.
    http://support.phaseone.com/KB/Home/Sea ... nguageID=1

    Regards,
    k c
    0
  • matt antrobus
    hi Keith

    Thing is I do want to accept the offer of Phase One importing the images, & renaming them. I just dont understand why it almost but not quite uses the original number when I ask it to.

    ie - file on CF Card \"CF011134\" is renamed as \"test-001134\" this is not my typo - the number part of the renaming is changing from 011134 to 001134.

    Any idea why & what i can do about it - otherwise it's perfect & doing what I want it to do.

    Matt
    0
  • Anonymous
    Matt,

    I agree, I like the naming upon import too and I use it on Windows platform.
    On my Mac, because the Batch Rename feature is a bit better, you should be able to set:
    > Name Prefix
    > Start Count at the number exactly where you want to
    > Set the number of digits in the name

    I don't have a Pback with as many captures as you do to make a Real Test, but I still believe you can acomplish what you're after in the Batch Rename.

    With some files in a Session I have, I started at your # of test-011133
    and I got consecutive numbering on up.

    Please test and let us know, or if I'm misunderstanding your needs.

    Regards,
    k c
    0
  • matt antrobus
    Hi Keith

    Yes, I think you have misunderstood, or I haven't made myself clear enough.

    Here's the whole picture. At the start of a shoot I will create a new session, called for example \"pink\" & often I will start shooting tethered & shots will go into the capture folder being named pink-011039 and so on, using the six digit counter on the back.

    Then I may well continue shooting direct to a CF card. The next file will be numbered \"CF011040\" using the same six digit counter. However if I then chose to import this file (and of course others) into the same capture folder using the auto import & rename, then the file is renamed \"pink-001040\", everything is working as expected apart from the six digit number changing from 011040 to 001040.

    My need, for various reasons, is for every file shot to have is unique six digit camera counter unchanged during the import process, & I really can't understand why or what is making this happen.

    Hope this makes it clearer.

    Matt
    0
  • Anonymous
    Matt,

    Sorry, I should have clarified up front.
    I saw your Support Case exchanges with Eric and knew he would handle this in depth. I was offering a workaround to help you work through this. I see it has been reported as a Bug and now R&D and Developers will handle it from here. Therefore, I hope that my suggestion helps in some way to get the file names you need to have in your workflow.

    Regards,
    k c
    0
  • matt antrobus
    hi Keith

    Thanks I appreciated your help & left it on the forum too, as I thought others may benefit, or be able to help.

    it's quite a nasty bug & i hope it's resolved soon.

    Matt
    0

Post is closed for comments.