Aperture Catalog Import - Version Name and Caption
Hello,
I am evaluating Capture One 10.1 as a replacement for Aperture 3.6. I am a long time user of Aperture but just beginning to explore Capture One.
I use Aperture's Version Name field to provide titles to my images. I also often use the Caption field for more info on the image.
When importing an Aperture Library into Capture One, the Version Name and Caption fields are ignored.
I think I can use an AppleScript to copy the Version Name into the IPTC Object Name field before the import. But what about the Caption - usually some long text?
In Aperture I sometimes like sorting the image Browser by Version Name. In Capture One I see that I can sort the Browser by Name - is this the IPTC Object Name field or the File Name? I'd prefer to see the Name field in the Viewer instead of the File Name - is there a preference for this?
I apologize for these newbie questions, but I am going through a lot of anguish during the transition from Aperture to Application X.
Cheers.
I am evaluating Capture One 10.1 as a replacement for Aperture 3.6. I am a long time user of Aperture but just beginning to explore Capture One.
I use Aperture's Version Name field to provide titles to my images. I also often use the Caption field for more info on the image.
When importing an Aperture Library into Capture One, the Version Name and Caption fields are ignored.
I think I can use an AppleScript to copy the Version Name into the IPTC Object Name field before the import. But what about the Caption - usually some long text?
In Aperture I sometimes like sorting the image Browser by Version Name. In Capture One I see that I can sort the Browser by Name - is this the IPTC Object Name field or the File Name? I'd prefer to see the Name field in the Viewer instead of the File Name - is there a preference for this?
I apologize for these newbie questions, but I am going through a lot of anguish during the transition from Aperture to Application X.
Cheers.
0
-
[quote="designwallah" wrote:
Hello,
I am evaluating Capture One 10.1 as a replacement for Aperture 3.6. I am a long time user of Aperture but just beginning to explore Capture One.
I use Aperture's Version Name field to provide titles to my images. I also often use the Caption field for more info on the image.
When importing an Aperture Library into Capture One, the Version Name and Caption fields are ignored.
I think I can use an AppleScript to copy the Version Name into the IPTC Object Name field before the import. But what about the Caption - usually some long text?
I had a similar problem, and Applescript can indeed be used to copy information into the IPTC fields, both in Aperture and in Capture One Pro. I can share some Applescripts if you would like.
The IPTC "Description" Field is generally specified as a free text field of up to 2000 characters, and so might be a good place for your Aperture Caption Info (although I don't know how many characters COP will support. Perhaps not 2000)
There is an IPTC "Headline" field specified as "A brief synopsis of the caption. Headline is not the same as Title" which is typically up to 256 characters.
There is also the IPTC "Title" Field which is specified as "A shorthand reference for the digital image. Title provides a short human readable name which can be a text and/or numeric reference. It is not the same as Headline." This is typically up to 64 Characters
In Aperture I sometimes like sorting the image Browser by Version Name. In Capture One I see that I can sort the Browser by Name - is this the IPTC Object Name field or the File Name? I'd prefer to see the Name field in the Viewer instead of the File Name - is there a preference for this?
I apologize for these newbie questions, but I am going through a lot of anguish during the transition from Aperture to Application X.
Cheers.
One thing I ran into is that if there are >10,000 images in a folder (e.g "All Images"), and each image has a unique value in a particular metadata field ( so that in one metadata field, you have 10,000 or more unique strings") this is handled rather inefficiently by the Filters tool in Capture One Pro, leading to very slow performance when the image browser is showing a folder with more than 10000 images (such as the All Images folder). It works fine in folders of 2000 images, above 4000 I start to see a slight slowdown, at 7000 it's an annoyance and at 15000 images it's unusable.
The problem arises if the Filters tool is visible, even if the metadata field with the "problem" data is not shown.
The work around is to remove the the "Filters Tool" from the "Libarary" tool tab (so that it's never visible). I make a custom tab for the "Filters" tool only, and only use if in smaller folders. When I need to sort and select images, I use the advanced search window/function, which doen't have this problem.
Compared to Aperture, the COP browser handles large catalogs more slowly, and is more likely to beachball.0 -
Eric,
Thanks very much for your detailed response.
Unfortunately, while it appears I can use AppleScript to set IPTC values, these IPTC fields are not shown in the browser.
For example, if I set some IPTC field to be the title for my images, and I have a group of images of numbers (e.g. 12, 3, 45, 4...), I won't be able to sort the images by their title - the number (e.g. 3, 4, 12, 45...).0 -
[quote="designwallah" wrote:
Eric,
Thanks very much for your detailed response.
Unfortunately, while it appears I can use AppleScript to set IPTC values, these IPTC fields are not shown in the browser.
For example, if I set some IPTC field to be the title for my images, and I have a group of images of numbers (e.g. 12, 3, 45, 4...), I won't be able to sort the images by their title - the number (e.g. 3, 4, 12, 45...).
True. Aperture, the tool that you and I just came, from can't sort by the IPTC fields either.
However, if you use the COP advanced search menu, you can select images based on the the IPTC fields.
The filter tool can also be made to use any of the IPTC fields.0 -
Eric,
May I ask you your opinion of Capture One, as a former Aperture user? Did you have to make many compromises?
I have a feeling I won't be happy. I am not a professional, so I suppose I am concerned about things that professionals are not - image titles and captions, GPS, smart albums, sorting, speed...
I had to update my Mac OS so I could install Capture One, which, unfortunately caused Aperture to behave oddly - it's slowly going off the rails. I'll have to switch to something else very soon.
Regards.0 -
[quote="Francesco Mariani" wrote:
Whatever you switch to from Aperture will cause compromises. Even moving to App,le Photos will reult in compromises.
Eric,
May I ask you your opinion of Capture One, as a former Aperture user? Did you have to make many compromises?
I finally feel that with Capture One 10.1 I don't have to make too many compromises, and Capture one has some good features that Aperture does not have.
Capture One browsing speed with a large catalog is finally reasonable, and hierarchical keywords work, and these two were the biggest problems for me.
One feature I still miss is stacks, but I have a usable work around now.
Nor am I a professional, but my priorities are (of course) not exactly the same as yours.
I have a feeling I won't be happy. I am not a professional, so I suppose I am concerned about things that professionals are not - image titles and captions, GPS, smart albums, sorting, speed...
Over half the items you mention are supported by Capture One, but they work differently than Aperture.
I think that GPS is not well supported by Capture One, however I never attach GPS coordinates to my images, so it doesn't matter to me.
There are other good applications out there, they will all have compromises in some areas compared to Aperture (and really to COP as well) - one need to pick a tool where the compromises are acceptable.
Other SW that I ahve heard people dicussing here are Lightroom, ON1, PhotoSupreme, Myllio, Affinity, - they each have their compromises.
I had to update my Mac OS so I could install Capture One, which, unfortunately caused Aperture to behave oddly - it's slowly going off the rails. I'll have to switch to something else very soon.
Regards.0 -
I had a similar problem, and Applescript can indeed be used to copy information into the IPTC fields, both in Aperture and in Capture One Pro. I can share some Applescripts if you would like.
Eric, I would truly appreciate you sharing your Applescripts with me. I think I'll take the plunge and import my Aperture catalog to Capture One and learn how to use it.
Thanks,0 -
[quote="Francesco Mariani" wrote:
I had a similar problem, and Applescript can indeed be used to copy information into the IPTC fields, both in Aperture and in Capture One Pro. I can share some Applescripts if you would like.
Eric, I would truly appreciate you sharing your Applescripts with me. I think I'll take the plunge and import my Aperture catalog to Capture One and learn how to use it.
Thanks,
Sure, I see that I've got 53 Applescripts intended for use with Aperture to prepare for the migration to Capture One Pro - most of them are a little informal - they fall into 3 different types.
1) Scripts used to manipilate the names of imagaes. Capture One has less felxibility than Aperture which can handle a version name and a file name being completely separate. In making this migration I decided to kake the fiel names the same as my version names, and to update my version naming system so that there was a unifrom strategy for naming images. for example image number 289 from my Olympus E-M1 in 2017 would be called "EM1-17_00289" and the file name will be "EM1-17_00289.RW2". Then variations for images from many soyurces arranged in a sequence, images given to me, images manipulated by other SW and images from scanners. It was quite a bit of work to manipulate images with 4 or 5 different older naming systems into one unified whole. I have a bunch of scripts to manipulate image names, finding a set of characters and repalcing them with another. You will probably want to edit the scripts to work into your system.
Here is an example-- Change the Aperture Version Name from "V" to "G1" and fix the format
tell application "Aperture"
set selectedImages to (get selection)
end tell
if selectedImages is {} then
error "No images selected - select one or more images"
else
repeat with i from 1 to count of selectedImages
set thisImage to item i of selectedImages
tell application "Aperture"
tell library 1
tell thisImage
set versionName to (get value of other tag "VersionName") as string
try
set imageDate to value of EXIF tag "ImageDate"
set exifAccessFlag to true
on error errText number errNum
log "Access to " & versionName & " failed with error number " & errNum
end try
end tell
end tell
end tell
set newInitials to "G1"
if exifAccessFlag = false then
log versionName & " unchanged due to bad exif data; error number " & errNum
else
set nameLength to count of versionName
if nameLength < 10 then
log versionName & " unchanged due to name too short: " & nameLength
else
set char1Detect to (get character 1 of versionName) as string
set char7Detect to (get character 7 of versionName) as string
if char1Detect ≠"V" or char7Detect ≠"_" then
log versionName & " unchanged due to unsuitable format"
else
set imageYear to (the year of imageDate) as string
set shortYear to (get characters 3 thru 4 of imageYear) as string
set newYYseq to "-" & shortYear & "_"
set counterString to (get characters 8 thru 10 of versionName) as string
set versionNameNew to newInitials & newYYseq & "0" & counterString
tell application "Aperture"
tell library 1
log "From " & versionName & " To " & versionNameNew
set name of thisImage to versionNameNew
end tell
end tell
end if
end if
end if
end repeat
end if
on replace_text(this_text, search_string, replacement_string)
set AppleScript's text item delimiters to the search_string
set the item_list to every text item of this_text
set AppleScript's text item delimiters to the replacement_string
set this_text to the item_list as string
set AppleScript's text item delimiters to {""}
return this_text
end replace_text
2. Images to take Metadata from one place and put it info another. For example to take the Aperture Original Import Date, and put it into an IPTC field:-- Copy ImportSession to IPTC "Source" from "JobID" fields, eliminate blanks
tell application "Aperture"
set selectedImages to (get selection)
end tell
if selectedImages is {} then
error "No images selected - select one or more images"
else
tell application "Aperture"
tell library 1
repeat with i from 1 to count of selectedImages
set thisImage to item i of selectedImages
tell thisImage
set fileName to (get value of other tag "FileName") as string
set versionName to (get value of other tag "VersionName") as string
if exists IPTC tag "Source" then
set OldSource to (get value of IPTC tag "Source") as string
if length of OldSource > 29 then
set lengthOldSource to length of OldSource
set NewSourceP1 to rich text 1 thru 13 of OldSource
set NewSourceP2 to rich text (lengthOldSource - 12) thru lengthOldSource of OldSource
set value of IPTC tag "Source" to NewSourceP1 & "..." & NewSourceP2
log "Version: " & versionName & " Source is too long - shortened"
end if
if exists IPTC tag "OriginalTransmissionReference" then
log "Version " & versionName & " already has Job Identification field, did not move Source"
log "Source: " & OldSource
log "JobID: " & OldSource & value of IPTC tag "OriginalTransmissionReference"
else
make new IPTC tag with properties {name:"OriginalTransmissionReference", value:OldSource}
set value of IPTC tag "Source" to ""
log "Version: " & versionName & " JobID: " & "Empty" & "--> " & OldSource
end if
end if
end tell
end repeat
end tell
end tell
end if
3) Capture One Pro does not support Stacks, but Aperture supports this very useful feature. In Aperture I copied each stack into an album like {S1, S2, S3}, and these are inside a folder called "Stacking". I then wrote an Applescript that starts with an image selected in one of the albums, navigates upwards to the folder that holds all the albums, then in each album searches for the counter in each version name, and then renames the Album using the highest and lowest counter values to something like "S_0015-0023" (for an album containing images 0015 to 0023)tell application "Aperture"
set imageSel to (get selection)
if imageSel is {} then
error "Please select an image."
else
tell (item 1 of imageSel) to set parent_folder to parent of parent
set album_list to every album of parent_folder
repeat with this_album in album_list
set parent_obj to this_album
set parent_obj_name_char to rich text 1 of (get name of parent_obj)
set imageSel to every image version of parent_obj
if length of imageSel > 0 then
set found_ctr to false
repeat with i from 1 to count of imageSel
tell (item i of imageSel) to set image_name to get name
set found_nums to false
set image_ctr_str to ""
set valid_nums to false
set dash_found to false
repeat with char_ctr1 from 1 to length of image_name
set image_name_char to rich text char_ctr1 of image_name
if image_name_char = "-" then
set dash_found to true
exit repeat
end if
end repeat
set underscore_found to false
repeat with char_ctr2 from char_ctr1 + 1 to char_ctr1 + 4
set image_name_char to rich text char_ctr2 of image_name
if image_name_char = "_" then
set underscore_found to true
exit repeat
end if
end repeat
repeat with char_ctr3 from char_ctr2 + 1 to length of image_name
set image_name_char to rich text char_ctr3 of image_name
if "0123456789" contains image_name_char then
set image_ctr_str to image_ctr_str & image_name_char
set found_nums to true
else if found_nums and "_- " contains image_name_char then
exit repeat
end if
end repeat
if dash_found and underscore_found and found_nums then
if 2 < length of image_ctr_str then set valid_nums to true
end if
if valid_nums then
set image_ctr to image_ctr_str as integer
if not found_ctr then
copy image_ctr to parent_ctr_min
copy image_ctr_str to short_ctr_str_min
copy image_ctr to parent_ctr_max
copy image_ctr_str to short_ctr_str_max
set found_ctr to true
else if parent_ctr_min > image_ctr then
copy image_ctr to parent_ctr_min
copy image_ctr_str to short_ctr_str_min
else if parent_ctr_max < image_ctr then
copy image_ctr to parent_ctr_max
copy image_ctr_str to short_ctr_str_max
end if
end if
end repeat
if found_ctr then
set name of parent_obj to (parent_obj_name_char & "_" & short_ctr_str_min & "-" & short_ctr_str_max)
--log "Renamed as: " & parent_obj_name_char & "_" & short_ctr_str_min & "-" & short_ctr_str_max
else
log "Did not rename " & (get name of parent_obj) & " did not find counter"
end if
else
log "No images found in: " & (get name of parent_obj) & " did not rename"
end if
end repeat
end if
end tell
My post migration Applescripts for manipulating Capture One Pro are posted in the Scripting Forum here.0 -
I've noticed there isn't much discussion on transitioning from Aperture to Capture One. I've dug around on the web and have found a few articles discussing successful Aperture to Capture One imports, but no one seems to have mentioned one of the things that bugs me: Version Name. After importing images into Aperture, the File Name and Version Name match. For example, I import three images, named _DSC9311.NEF, _DSC9312.NEF and _DSC9314.NEF. The Version names are set to '_DSC9311', '_DSC9312' and '_DSC9314'. For the Aperture Grid View, I have selected to show Version Name. The images are pictures of fruit, so one of the first things I do is change the Version Names to 'Cantaloupe', 'Apple" and 'Banana' respectively. Now I can resort the project files by Version Name so that my fruit pictures are in alphabetical order - I see an intelligent name in the Grid View, instead of a camera-generated name.
I am not a professional making money from my photography, but I am wise enough to want a better tool than Apple Photos. I don't know what a professional's workflow is, but I don't understand why, for example, a portrait photographer wouldn't want to apply metadata to their images - naming the subject, instead of only seeing a camera-generated name in the Capture One browser.
As an ex-Aperture user, Eric has provided me quite a bit of valuable information, are there any other ex-Aperture users out there?
Cheers,0 -
[quote="Francesco Mariani" wrote:
I've noticed there isn't much discussion on transitioning from Aperture to Capture One. I've dug around on the web and have found a few articles discussing successful Aperture to Capture One imports, but no one seems to have mentioned one of the things that bugs me: Version Name. After importing images into Aperture, the File Name and Version Name match. For example, I import three images, named _DSC9311.NEF, _DSC9312.NEF and _DSC9314.NEF. The Version names are set to '_DSC9311', '_DSC9312' and '_DSC9314'. For the Aperture Grid View, I have selected to show Version Name. The images are pictures of fruit, so one of the first things I do is change the Version Names to 'Cantaloupe', 'Apple" and 'Banana' respectively. Now I can resort the project files by Version Name so that my fruit pictures are in alphabetical order - I see an intelligent name in the Grid View, instead of a camera-generated name.
I am not a professional making money from my photography, but I am wise enough to want a better tool than Apple Photos. I don't know what a professional's workflow is, but I don't understand why, for example, a portrait photographer wouldn't want to apply metadata to their images - naming the subject, instead of only seeing a camera-generated name in the Capture One browser.
As an ex-Aperture user, Eric has provided me quite a bit of valuable information, are there any other ex-Aperture users out there?
Cheers,
Hi Francesco
I hardly want to be seen as a promoter of Aperture - that product is a done deal, an unsupported orphan now, and I'm moving on. Capture One is much more active in improving its tools than Apple ever was.
In Capture One Pro, I think much of what you desire can be done:- Upon import, if you do not select "Store in Catalog" or "Store in Current Location" you can set a new file name in quite a versatile manner.
- You can also choose to enter text in the Description field, which ends up in the IPTC Content Description field.
- The IPTC Content Description field can can be viewed and changed later in the Metadata Tool, which is normally on the the Metadata Tool Tab.
- You can set a MetaData preset with a custom IPTC Content Description field and apply to all selected images
- By typing in the box under the Image in the browser, the file name can be changed. (This one actually scares me a little - there's no OK dialog - a couple of random key strokes and you may have trouble finding your image back ...)
- Right Click on a set of selected images, and you can do a batch rename of the file names
- The Filters tool can also be made to use the IPTC Content Description field (although I would be cautious in doing so if there are many values)
- The Advanced Search tool can search according to the IPTC Content Description field.
- The IPTC Content Description field (and others too) can be used to name the output file.
It would be convenient to display the IPTC Content Description in the Viewer or Browser, below the image, but for the rest I would say that Capture One has got a lot flexibility and power here.0 -
Eric, do you think I can use the Object Name field instead of the Content Description field?
Thanks,0 -
[quote="Francesco Mariani" wrote:
Eric, do you think I can use the Object Name field instead of the Content Description field?
Thanks,
Hi Franceso
I observe that in the import process window, the only field that can be written is the Content Description field.
On output, any IPTC field can be used in file naming.
My experience so far is that after import one can write any text string in any IPTC Metadata field.
The supported text length for the two fields may differ.
Acording to this website, which PhaseOne may or may not follow, , the supported text length for the Content Description field is 2000 characters.
For Object Name it is 64 characters.
I don't know how Phase One designers observe these restrictions and what limits (such as length) are inherent in their design. You might find out something info by asking Phase One (raise a ticket), and a little hands on testing might prove fruitfull as well.
Also important is how they test it. For example, if they say internally the maximum supported size is 64 characters, then they hopefully test with 64 characters to make sure the function is correct. However, from obervations through this frum, they don't test everything. But now if you put 100 or 1000 characters in a field where the designer expected 32, strange and undesireable things may happen.
I check these things by creating a dummy catalog with a large number of referenced images. If it gets completely corrupted, no worries. When done, erase it.
Try putting a long character string (the longest you think you will ever need, and then add a few characaters) into the description field of one image, and then into all images. Try search, edit, and export functions
Now try it in the Object Name field.
Hre is a an Applescript for Capture One that you could modify. It searches all the user collections and clears one of the IPTC fields. But you can easily change it to write an IPTC field as well.:
-- Written this way because in the current 10.1 version of COP retreiving a very large number of images from the "all Images" collection (collection 1) causes my iMac to hang
global debug
set debug to true
global maxSearchLevel
set maxSearchLevel to 100
tell application "Capture One 10"
tell document 1
set everyCollection to get every collection
set countColls to count of everyCollection
if countColls = 1 then -- If there are no user collections, there is only the "All Images" collection.
display notification "No User Collections to Search"
error "No User Collections to Search"
end if
set searchLevel to 0
set nextSearchLevel to searchLevel + 1
if nextSearchLevel ≤ maxSearchLevel then
repeat with c_Counter from 1 to countColls
set searchCollName to (get name of collection c_Counter) as text
if searchCollName ≠"All Images" then
my search_collection((collection c_Counter), nextSearchLevel)
end if
end repeat
end if
end tell
end tell
--Handlers -------------------
on search_collection(thisCollection, searchLevel)
-- recursive handler to search a collection and it's subcollections
-- if successful, returns a list of paths each as a text string
global debug
global maxSearchLevel
set nextSearchLevel to searchLevel + 1
tell application "Capture One 10"
tell document 1
tell thisCollection
set thisCollName to (get name) as text
set thisCollKind to (get kind) as text
set subCollections to get every collection
set everyVarList to get every variant
set v_counter to 0
set v_change_Ctr to 0
repeat with thisVariant in everyVarList
if (get status job identifier of thisVariant) ≠"" then
set v_counter to v_counter + 1
tell thisVariant
set v_change_Ctr to v_change_Ctr + 1
set status job identifier to ""
end tell
end if
end repeat
log "Done " & thisCollKind & " " & thisCollName & " " & {v_counter, v_change_Ctr}
set nextSearchLevel to searchLevel + 1
if nextSearchLevel ≤ maxSearchLevel then
repeat with searchCollection in subCollections
my search_collection(searchCollection, nextSearchLevel)
end repeat
end if
end tell
end tell
end tell
return
end search_collection
One thing to be aware of. If you have a catalog with 10,000 or more images, and you have loaded one of the IPTC Metedata fields with a value that is present and unique for ever item, the Filter tool becomes very slow to refresh. More than that, any time the Filter Tool is present (i.e. on the slected Tool Tab) , many screen refresh operations and keysroke responses become excrutiatingly slow in any view where all the images are present in the browser.
This does not affect the Fllter tool in a smaller folder, with a few 100 images or less.
So the users choice is are: use this kind of Metadata, and move the Filter tool to another tab or delete it altogther OR use this kind of Metadata and do not use all images with Library Tool Tab OR Do not use this kind of MetaData
I haave chosen option 1, move the Filters tool to a custom tab.0 -
[quote="Francesco Mariani" wrote:
Eric,
May I ask you your opinion of Capture One, as a former Aperture user? Did you have to make many compromises?
I have a feeling I won't be happy. I am not a professional, so I suppose I am concerned about things that professionals are not - image titles and captions, GPS, smart albums, sorting, speed...
I had to update my Mac OS so I could install Capture One, which, unfortunately caused Aperture to behave oddly - it's slowly going off the rails. I'll have to switch to something else very soon.
Regards.
Eric, I just wrapped up my trial of CP1X and as a professional Aperture user, Capture One misses the mark for me and my workflow, mainly in its implementation of brushes. If you were a keyboard power user and remapped your keys to use brushes fast you'll know what I mean.
In Aperture I can call up any brush with a single keyboard key and immediately start working without even using the mouse, menu or sliders.. I hit “S†I get my sharpen brush, “D†I get my Dodge; “T†Skin Soften; “B†Burn, etc.. they are all keyboard mappable and completely limitless (Unlimited # of layers, multiple “Dodge†layers if desired too); I don’t need to access a certain menu or any sliders in order to start working, in-fact a brush HUD automatically appears and disappears when the brush is called or dismissed. So basically were talking 1 step (or no step depending on how you look at it).
Compare that to Capture One, which from my understanding, is limited to an “add layer†system in which (Step 1) is to go to the Local Adjustments tool inspector where each layer must be added; (step 2) name layer; (step 3) determine/make a brush, heal or clone layer; (step 4) adjust sliders for desired layer/brush (step 6) hit “B†on the keyboard or select tool with mouse to apply brush.. and/or (step 7) right click to bring up HUD and adjust brush. (And I can’t even make “add layer†keyboard mappable which would at least speed up the process).
WOW.. that’s 6-7 steps PER BRUSH, vs. Aperture’s 0-1 step process.
Now if you don't use brushes much then I think Capture One will work out fine as a replacement to Aperture, there are still some oddities in the human interface area, but all manageable really.0 -
Hi Francesco
I definitely don'yt see mtslf as a power user, photograghy is one of my hobbies, and I have a more than full time job. Regarding the keyboard mapping of brushes, I don't have enough usage of any tool to fix the mapping in my mind.
I wonder if it is possible for you to use an Applescript or Automator action to eliminate some of those keystrokes.
Best of luck fin your search; I only know of perhps one othe tools that might meet your requirements.0 -
[quote="Eric Nepean" wrote:
- By typing in the box under the Image in the browser, the file name can be changed. (This one actually scares me a little - there's no OK dialog - a couple of random key strokes and you may have trouble finding your image back ...)
- Right Click on a set of selected images, and you can do a batch rename of the file names
as a former database developer, I don't favour using 'meaningful' file names for any of my images. the file names should be used as a form of identification, and shouldn't be changed once entered into the db. a separate field "variant name" should be used instead if available. all of my images are renamed "yyyymmdd_hhmmss -- camera make -- camera model -- " before import into Photos (using A Better Finder Renamer). I then use CO to 'import' the images from the Photos db leaving them physically where they are. I can then use both DAM products to access the photos as needed.
the first point you brought up is actually rather serious when we're are cataloging images from another DAM db. being able to change the file name on a whim or accidentally when it is part of another DAM could cause the other DAM to 'lose' the image file. not good. I just tested this. even though the image was in the Photos db, clicking on the file name in the CO browser allowed me to change the file name. perhaps the CO developers should change this behaviour? especially for non-local image files.
I used Aperture for several years, had a very hard time finding a 'suitable' substitute. same as you, I found CO10 to be the best substitute I could find. but a Stacks feature with associated 'stack and album picks' would certainly be nice 😊
and a Smugmug plugin -- LOL!
I'm getting very used to working with levels and curves now, and so I now shoot with the intention to get as much colour information as possible at the time of shoot rather than getting the 'balanced' photo. I'm hoping Canon releases an upgrade to my 1D Mark III soon, one with even better sensors, a higher dynamic range, and preferably an in-viewfinder histogram LOL!
cheers all.0 -
[quote="Gregory_" wrote:
I do something similar - after trying a few options, I decided that the month and day could just as well be replaced by a sequence number, and I didn't need thee make if I had the model. So: {camera_model:5}-YY_{sequence:5}[quote="Eric Nepean" wrote:
as a former database developer, I don't favour using 'meaningful' file names for any of my images. the file names should be used as a form of identification, and shouldn't be changed once entered into the db. a separate field "variant name" should be used instead if available. all of my images are renamed "yyyymmdd_hhmmss -- camera make -- camera model -- " before import into Photos (using A Better Finder Renamer).- By typing in the box under the Image in the browser, the file name can be changed. (This one actually scares me a little - there's no OK dialog - a couple of random key strokes and you may have trouble finding your image back ...)
- Right Click on a set of selected images, and you can do a batch rename of the file names
I then use CO to 'import' the images from the Photos db leaving them physically where they are. I can then use both DAM products to access the photos as needed.
Does that leave them in the Photos DB, or as referenced images in the OSX filesystem?
I'm working on an Applescript that would provide a similar feature to stacks in Capture One.
the first point you brought up is actually rather serious when we're are cataloging images from another DAM db. being able to change the file name on a whim or accidentally when it is part of another DAM could cause the other DAM to 'lose' the image file. not good. I just tested this. even though the image was in the Photos db, clicking on the file name in the CO browser allowed me to change the file name. perhaps the CO developers should change this behaviour? especially for non-local image files.
I used Aperture for several years, had a very hard time finding a 'suitable' substitute. same as you, I found CO10 to be the best substitute I could find. but a Stacks feature with associated 'stack and album picks' would certainly be nice 😊
There is a stack like feature in CO for images from Phase One cameras, but it's not available for images from other cameras. I wonder if this will be more generally available in the next release of Capture One.
and a Smugmug plugin -- LOL!
I'm getting very used to working with levels and curves now, and so I now shoot with the intention to get as much colour information as possible at the time of shoot rather than getting the 'balanced' photo. I'm hoping Canon releases an upgrade to my 1D Mark III soon, one with even better sensors, a higher dynamic range, and preferably an in-viewfinder histogram LOL!
cheers all.
I have the in viewer histogram on my E-M1 and GX7 quite useful0 -
[quote="Eric Nepean" wrote:
Does that leave them in the Photos DB, or as referenced images in the OSX filesystem?
I import the images into Photos which moves them into the Photos "Masters" folder. when I import them into CO, I leave them where they are. CO just references them.[quote="Eric Nepean" wrote:
I have the in viewer histogram on my E-M1 and GX7 quite useful
I'm not a full time photographer and sometimes forget how to adjust the exposure for the photo I'm taking. during my recent trip to Japan, I found myself constantly checking the histogram after taking each photo just to make sure I hadn't clipped important data. an in-viewer histogram would definitely be helpful, but this would probably require a mirror-less camera and an LED viewfinder? I'd definitely want a really high-def viewfinder if I went this route.0 -
[quote="NNN636179069410610679"] wrote:
[quote="Francesco Mariani"] wrote:
Eric,
... (And I can’t even make “add layer†keyboard mappable which would at least speed up the process).
/quote]
You can add a new layer with a keyboard shortcut. It creates a new layers with a default name (you don't have to name it). Now, you still would need to go to the layers tool tab if you want to change anything else than exposure, and you do have to select the tool (brush/gradient), but it's kind of OK.
But you're right, it's far from "fully customisable keyboard shortcuts".
OTOH, what I didn't like about the brushes in Aperture was the fact that a mask was associated with a single brick. Need to adjust exposure and highlights? 2 bricks, 2 masks (unless I missed something). Anyway, AP is history, and we can only hope that Phase One "borrows" the good things from other applications.
Cheers,
Peter.0
Post ist für Kommentare geschlossen.
Kommentare
17 Kommentare