Hey Kevin, I just started using Capture 1. My 30 days is almost up and I'm definitely keeping it! I found your channel when looking for help and subscribed after watching 3 videos! You are providing excellent help! So far I have only been looking at your Capture 1 videos, but I'm looking forward to diving into others as well. I've had a very similar naming convention for years. The only issue I ran into is for events where I am using a rapid fire on the camera. With cameras these days capable of shooting 8-20 frames per second this naming would run into an issue with groups of images trying to have the same name. I do a lot of concert photography so this is a frequent scenario for me. I started using a sequence after the seconds, but the sequence applies to the whole group, not just where there would be multiples. This was confusing. So I ended up using GTH-YYMMDD-000x and forgetting about the time. I do like your idea about adding the "photo by..." text on export. I might start using that one!
Dude! You literally saved me SO MUCH TIME. Thank you for this video and your other one on setting up your overall Capture One workspace. You are a godsend. Seriously.
Do I? Yes. Would I? It depends. Since I use sessions for each shoot, but also have an archive catalog for all my past sessions, renaming them in the session would disassociate them in the catalog. If I rename them via the catalogue, that might still work, since sessions read images in the session folder instead of a database. I'll have to look into it. I guess the REAL QUESTION is do YOU think there is value in renaming old jobs? If I didn't have my master catalog, I would absolutely do this for any session prior to me using this naming schema.
Hey Kevin, I just started using Capture 1. My 30 days is almost up and I'm definitely keeping it!
I found your channel when looking for help and subscribed after watching 3 videos! You are providing excellent help!
So far I have only been looking at your Capture 1 videos, but I'm looking forward to diving into others as well.
I've had a very similar naming convention for years. The only issue I ran into is for events where I am using a rapid fire on the camera. With cameras these days capable of shooting 8-20 frames per second this naming would run into an issue with groups of images trying to have the same name. I do a lot of concert photography so this is a frequent scenario for me.
I started using a sequence after the seconds, but the sequence applies to the whole group, not just where there would be multiples. This was confusing.
So I ended up using GTH-YYMMDD-000x and forgetting about the time.
I do like your idea about adding the "photo by..." text on export. I might start using that one!
Dude! You literally saved me SO MUCH TIME. Thank you for this video and your other one on setting up your overall Capture One workspace. You are a godsend. Seriously.
Brilliant as always. Appreciate you taking the time to put this together.
You're very welcome!
Do you feel there is value in going back and renaming old jobs files from years past?
Do I? Yes. Would I? It depends. Since I use sessions for each shoot, but also have an archive catalog for all my past sessions, renaming them in the session would disassociate them in the catalog. If I rename them via the catalogue, that might still work, since sessions read images in the session folder instead of a database. I'll have to look into it.
I guess the REAL QUESTION is do YOU think there is value in renaming old jobs? If I didn't have my master catalog, I would absolutely do this for any session prior to me using this naming schema.