How do I import an image from a memory card
I am in the process of transitioning from LR to C1. I am encountering a few aches and pains on the way, but generally satisfied with my progress. My latest problem, centers around importing from a CF card. I have been using LR since v1 and have become comfortable with the LR library format. My goal is to import into C1 and result in a file format the looks similar to the LR file format.
When I try to set up C1 the import instructions/options are very flexible (another way of saying complicated).
Bottom line, how do I set-up C1 to come close to looking like the LR format that I am comfortable with.
BTW, How would I go about to attaching an image to a post? When I clicked on Img, nothing seems to happen.
When I try to set up C1 the import instructions/options are very flexible (another way of saying complicated).
Bottom line, how do I set-up C1 to come close to looking like the LR format that I am comfortable with.
BTW, How would I go about to attaching an image to a post? When I clicked on Img, nothing seems to happen.
0
-
In the General section of preferences there is a check box for "Open importer when detecting card from digital camera". If you have selected that then Capture One should open the import dialog box when you insert a card into your card reader, or if there is a card already in it, when you open Capture One. If you prefer to leave that unchecked, you'd have to open the import dialog box manually with the button on the tool bar (Downwards arrow, at the top left) or by File>Import images...
C1 won't directly import images from a card in the camera.
Ian
Edited to add: you put images in a post by hosting the image somewhere (Flickr, Dropbox, etc) then putting its address between the Img tags.0 -
[quote="NNN636440347581429185" wrote:
When I try to set up C1 the import instructions/options are very flexible (another way of saying complicated).
This Phase One video has a fairly clear and prompt introduction to importing images.
https://www.youtube.com/watch?v=ZbYMv1w ... tureOnePro0 -
Thank you.
I previously got this far, but my problem is that C1 offers a myriad of "naming" options that are confusing me.
Simply stated, my goal is to get the newly imported image file format to match the file format of the thousands of old images that I previously imported from LR; I do not want to have two sets of "looks" in the C1 catalog0 -
[quote="NNN636440347581429185" wrote:
Thank you.
I previously got this far, but my problem is that C1 offers a myriad of "naming" options that are confusing me.
Simply stated, my goal is to get the newly imported image file format to match the file format of the thousands of old images that I previously imported from LR; I do not want to have two sets of "looks" in the C1 catalog
I have pretty good success using the tokens explained in the video.
Actually you don't even need to import images to rename them with tokens if you create a "Session". You can just browse to the folder, select the pictures, batch rename, compile the token structure and hit rename.0 -
This is the file structure that I am trying to achieve (it resembles the file structure that I imported from LR)
2017-11-11 (this is the folder name, the date I took the picture, from the camera) 16 (this is the image count in the folder)
I am an old dinosaur; will somebody explicitly tell me how to get to this file structure?0 -
I'm not sure I understand now.
You want the amount of images to be taken into consideration by the tokens when automatically sorting them into folders by date and write it to the name of the folder?0 -
OK, I will try to be clearer. When I first migrated my images from LR, they went into the C1 catalog as follows:
yyyy-mm-dd followed by numeric that was the number images in that file. So it looks like: 2017-11-10 (16).
When I download a set of images from my camera memory card, I do not see this file structure. Instead, I see:
Folders > In Catalog (173). Notice, there is no Year-Month-Day. And when I click on "In Catalog", I see a string of 173 images in the browser window with out any regard to the date that I took the picture. I want to see a file structure that matches my existing C1 catalog, e.g., 2017-11-12 followed by an image count. So that, when I click on 2017-11-12, I see only the images in that file.
If I were able to include a screen grab, I think my problem would be clearer.
I am getting exhausted watching videos of some guy waxing enthusiastically about how flexible (complicated) the C1 file structure is. I only want to know how to make my new down loads (from the camera memory card) resemble the thousands of images I downloaded when I bought C1 pro 10.
In my search for a solution, I actually found a video of some guy suggesting that I first load the images into LR and then send them on to C1.0 -
[quote="NNN636440347581429185" wrote:
OK, I will try to be clearer. When I first migrated my images from LR, they went into the C1 catalog as follows:
yyyy-mm-dd followed by numeric that was the number images in that file. So it looks like: 2017-11-10 (16).
When I download a set of images from my camera memory card, I do not see this file structure. Instead, I see:
Folders > In Catalog (173). Notice, there is no Year-Month-Day. And when I click on "In Catalog", I see a string of 173 images in the browser window with out any regard to the date that I took the picture. I want to see a file structure that matches my existing C1 catalog, e.g., 2017-11-12 followed by an image count. So that, when I click on 2017-11-12, I see only the images in that file.
If I were able to include a screen grab, I think my problem would be clearer.
I am getting exhausted watching videos of some guy waxing enthusiastically about how flexible (complicated) the C1 file structure is. I only want to know how to make my new down loads (from the camera memory card) resemble the thousands of images I downloaded when I bought C1 pro 10.
In my search for a solution, I actually found a video of some guy suggesting that I first load the images into LR and then send them on to C1.
Right, I think the picture is getting a little clearer.
You're probably talking about something almost completely different than "How do I import an image from a memory card".
I need to think a bit on how to explain this. Meanwhile try to post your screenshots. You can upload the image anywhere and just paste the link here.0 -
LR file format.jpg This is my LR file
C1 Files.jpg This is C10 -
Haha, I see that you are able to rename screenshots, Mr. Old Dinosaur ๐
You can use this website to upload the image to, and then send us the link given after the files went up. (make sure there is no sensitive information on your screenshot when uploading to these 3rd party services)
Nonetheless, I think that if you really want to give Capture One a run for your money, you should watch a good few hours of webinars and instructional videos on the youtube channel. Specially the ones that deal with "Catalogs vs Sessions", what catalogs are, what sessions are, and how Capture One handles the dataset for each mode.
This is a good start: https://www.youtube.com/watch?v=k6sm9bQ ... tureOnePro
David goes extensively on how most things work.
Capture One is far less daunting than it initially appears to be, but file and folder handling can be a little confusing and surely has it's quirks.
I think you're getting caught up between "referencing" your old Lightroom catalog, vs importing new files into the "managed" part of the catalog (In Catalog section).
Try having a look at this video and get back to me.
(Anybody else reading that already understands what is going on and how too tackle this issue, please dip in)
Cheers,
Gus0 -
Right, I'll preface this by saying that I am not a Catalogue user but I have investigated the concept, and I am not a Mac uder and I know there are some display differences still between Mac and Windows when using the Library tool because the operating systems offer different way to work.
Also my comments are based on observations from V9 but as far as I know will still apply.
There are 2 ways to work with catalogues.
You can store the original files INSIDE the catalogue (a MANAGED catalogue) or somewhere else (a REFERENCED catalogue).
Any catalogue can make use of files that are managed or referenced. (I'll leave any discussion of the practical differences for another thread.)
From your description you have imported the original files to a MANAGED catalogue.
Conceptually a Managed Catalogue is something that is intended to do most of the work for you.
You throw file into it and it sorts out the storage and automatically sets up various indexes that you can use for filtering the contents to show the file you seek. You can also create your own favoured grouping - by date for example - using the filter tools provided and some other methods like Albums, Smart Albums, Projects and Groups.
With a database to manage where your images are in a Managed catalogue you don't need to structure the data yourself although you can do so if you wish to via the import process - you just won't see it in the library tool.
I you use a referenced catalogue - typically used when storage needs to be distributed over several disks or when a folder of images needs to be accessed by multiple applications - you control where the images go and where the folders are to be located for the imported images.
In both situations you can create Subfolders using the Import Process and have the files stored there. The difference is that in a Managed images you will not readily see the subfolders (or any folders) in the Library tool whereas with Referenced images you will, with or without the full folder hierarchy displayed (it can be toggled on and off).
And remember a Catalogue can have a mix of Managed and Referenced images.
Using the Import function once you have selected your source of the images (Likely your CF card) the next step is the "Import to" box and choosing a destination.
Inside Catalogue will write the files into a folder that is "known" to the Managed catalogue functionality.
Alternatively you can choose any other folder (a list of previously used recently folders is provided) or create a new folder to store the new images. On the line below that you can specify that you want subfoolder created and what the rule are for naming them.
You can type in a name to be used or you can use the Token functionality to use information in the file to generate a name for the folder into which it is to be written. (Or both and indeed much more but we don't need to get too complicated here.
The Subfolders are applied to both Managed and Referenced imports. When used for Referenced images you can see the folders in the Library tool.
To replicate your existing folder naming by Date the image was taken (using date data in the file provided by the camera) you need the the following tokens.
[Image Year (yyyy)]-[Image Month (MM)]-[Image Day of Month (dd)]
which you select from the available drop down list and drag into the field box provided. You may need to adjust the default format values (YYYY, MM, dd) using the options available under the little arrow on the token.
You will need to type in the "-" between the tokens.
That should then automatically create a folder named for the date the image was taken and group all images with the same date in the same folder. Capture One will keep track of the count and will take into account any filters you might be using at the time and a few other things.
The referenced folders will be visible in the library tool when required and the full folder structure hierarchy from the system level down can be extended or contracted using the "Show Folders Hierachy" option.
My personal experience would suggest that a double level folder creation is a good idea - so a folder for year with its own subfolders for month-date. For people shooting most days it may be even better to have a folder hierarchy of Year/Month/Day but that does not sound like your existing method that you wish to match.
I hope this helps a little.
If any Mac users one to comment and correct please do dive in.
My general take on this is that there are indeed a lot of options for a very powerful solution but individual users are unlikely to need all of them in their own work flow requirements. So it is mainly a matter of working out which bits you need and setting up something that does the work for you consistently and with easy repeatability.
Grant0 -
Much thanks to everybody who is helping me sort this thing out!! I think that I am beginning to get the picture.
When I migrated to C1 from LR, my images automatically went into a catalog, which C1 named รขโฌล1 Tรขโฌ (1 T is my 1 Terabyte document SSD). And, when C1 imported the images it replicated my LR catalog file structure, yyyy-mm-dd.
When I later took a series of photographs and tried to import them into C1, I was expecting to see them go into a C1 file structure that resembled to my original import. They did not do that, instead, they went into a folder that C1 named รขโฌลIn Catalogรขโฌ. รขโฌลIn Catalogรขโฌ contained a string of images that had no separation, for example, according to the camera date.
So where do I go from here; should I continue with the รขโฌลyyyy-mm-ddรขโฌ file structure in a managed catalog or should I move to sessions as David suggested in his webinar? I have one major requirement, regardless of which way I proceed, I want to have only one file structure for both my old images and any subsequent downloads.
So, this is my revised question, do I continue with managed catalogs or do I go to sessions (or some other alternative)? And, what is the easiest way to make the file structure for my original download and my subsequent imports look alike?0 -
[quote="NNN636440347581429185" wrote:
Much thanks to everybody who is helping me sort this thing out!! I think that I am beginning to get the picture.
So, this is my revised question, do I continue with managed catalogs or do I go to sessions (or some other alternative)? And, what is the easiest way to make the file structure for my original download and my subsequent imports look alike?
When I imported a Lightroom library, CaptureOne created a referenced catalog, not a managed one. Personally, I much prefer referenced catalogs since they let me store my images on external drives and do not import the images into the actual CaptureOne catalog (only the reference to the image, plus edits, etc. are stored in the catalog file).
If you follow Grant's suggestion from an earlier message, you can automate the import of files from a memory card into disk locations with each image stored in a sub-directory with year/month/day names, just like you were doing in Lightroom.0 -
I set-up a new catalog in C1 and tried to import images into it. All I got was Error Code 516.
Is there a place I can go to obtain a list of error codes? Without knowing what 516 means, I cannot get beyond this point.0 -
[quote="NNN636440347581429185" wrote:
I set-up a new catalog in C1 and tried to import images into it. All I got was Error Code 516.
Is there a place I can go to obtain a list of error codes? Without knowing what 516 means, I cannot get beyond this point.
Is that a MAC error code?0 -
NO, it is a C1 error code 0 -
In trying to get C1 to create a catalog that I am comfortable with, I created several extra catalogs.
How can I get rid of, delete, or remove the extra/unwanted catalogs. I have listen to several "drone-on" tutorials, but I cannot find any instructions on how to get rid of unwanted catalogs. It shouldn't be that hard!!0 -
[quote="NNN636440347581429185" wrote:
In trying to get C1 to create a catalog that I am comfortable with, I created several extra catalogs.
How can I get rid of, delete, or remove the extra/unwanted catalogs. I have listen to several "drone-on" tutorials, but I cannot find any instructions on how to get rid of unwanted catalogs. It shouldn't be that hard!!
Delete them from the Finder, like you would do with any other type of file.0 -
[quote="NNN636440347581429185" wrote:
In trying to get C1 to create a catalog that I am comfortable with, I created several extra catalogs.
How can I get rid of, delete, or remove the extra/unwanted catalogs. I have listen to several "drone-on" tutorials, but I cannot find any instructions on how to get rid of unwanted catalogs. It shouldn't be that hard!!
I posted a thread asking exactly this question about two days ago. I also submitted a Support ticket with a feature request to add a 'delete catalog' action. The response was to delete using 'finder'. But, when I do that, Capture One complains then that it cannot save into the deleted catalog because it is in 'trash'. And, the warning window doesn't get displayed on the top of the Capture One window - it was buried underneath other open windows. But Capture One requires that the window be closed before it will respond to any more mouse clicks. As a result, i initially thought that the programme was frozen and nearly did a forced quit before the window became visible by accident' as I tried to get it running. Maybe if Capture one is closed when the catalog is deleted, or if some other catalog is open, it will work better.
This method eventually worked but it is inelegant and adding a 'delete' button seems like a simple fix. If you agree, maybe you should submit a Feature Request support ticket too?0 -
I absolutely agree, Capture One needs a simple delete catalog button. In fact C1 needs a whole series of simple buttons or if not a simple button, a set instructions on how to find hidden features. Everybody talks about the steep C1 learning curve; using C1 is not hard, it's finding the stealthy features that makes C1 frustrating. 0 -
[quote="nbirkett" wrote:
Maybe if Capture one is closed when the catalog is deleted, or if some other catalog is open, it will work better.
This method eventually worked but it is inelegant and adding a 'delete' button seems like a simple fix. If you agree, maybe you should submit a Feature Request support ticket too?
I'm glad you figured that part out, but I'm more surprised that the catalog file wasn't locked! That's a real issue!0 -
[quote="NNN636440347581429185" wrote:
I absolutely agree, Capture One needs a simple delete catalog button. In fact C1 needs a whole series of simple buttons or if not a simple button, a set instructions on how to find hidden features. Everybody talks about the steep C1 learning curve; using C1 is not hard, it's finding the stealthy features that makes C1 frustrating.
I honestly can't see how deleting a catalog could be any simpler than it already is. Maybe it should be a little more complicated if anything!
"Close Capture One(or just the catalog) >> Delete catalog folder >> Done"
Capture One is a professional tool that already fits within an industry and the required workflows. Making improvements? Sure. There are plenty of holes and rough edges.
Now, making something simple 'simpler' just because one click is easier than two, is a waste of time and recipe for disaster in my opinion and experience.
I mean, how often do you delete a catalog!!0 -
[quote="gusferlizi" wrote:
[quote="NNN636440347581429185" wrote:
I absolutely agree, Capture One needs a simple delete catalog button. In fact C1 needs a whole series of simple buttons or if not a simple button, a set instructions on how to find hidden features. Everybody talks about the steep C1 learning curve; using C1 is not hard, it's finding the stealthy features that makes C1 frustrating.
I honestly can't see how deleting a catalog could be any simpler than it already is. Maybe it should be a little more complicated if anything!
"Close Capture One(or just the catalog) >> Delete catalog folder >> Done"
Capture One is a professional tool that already fits within an industry and the required workflows. Making improvements? Sure. There are plenty of holes and rough edges.
Now, making something simple 'simpler' just because one click is easier than two, is a waste of time and recipe for disaster in my opinion and experience.
I mean, how often do you delete a catalog!!
My thoughts exactly.
I can't think of any likely more complicated situation, even loosely using the sessions approach, that could be realistically enhanced by an all-knowing "button".
As thing stand the only things this the button could do would be to tell the user to close the catalogue/session if it is open and then replicate the deletion method via the OS functionality.
There are other things that would place higher on my personal list of useful ideas.
(Thoughts for what they are worth.)
Grant0 -
OK, I was dumb, but now that I know how to do it (could never find it on C1 or Google), you are correct it is easy. The problem is not how hard or easy to do it, but why is C1 so stingy about sharing information.
As I was stumbling around looking for how to do things on C1, I found this article; it says it all.
The Hidden Cloning Tool in Capture One Pro
By Derrick Story on September 8, 2017
"Many photographers try to use Spot Removal instead of cloning in Capture One for a very simple reason: they can't find the cloning tool..... That's because it's tucked away in the Local Adjustments panel. Then, someone could tell you that, and you still might not find it. You'll see adjustments for just about everything else - white balance, exposure, etc. - but not cloning."
Everybody talks about the steep learning curve associated with C1. Actually C1 is intuitive and really easy to use, once you find the correct tool, the problem facing new users is, where did they hide the darn tool. C1 has great webinars and tutorials, but often, you have to watch 60 minutes of youTube to get the two minutes of information that you are searching for.
When my granddaughter was learning LR, I prepared, a "solution to a problem", based information sheet for her (it was closer to 15 pages), with references back to Martin Evening's LR book.
Open memo to the guys at C1, Esoteric writing makes frustrated newbies.0 -
[quote="SFA" wrote:
[quote="gusferlizi" wrote:
[quote="NNN636440347581429185" wrote:
I absolutely agree, Capture One needs a simple delete catalog button. In fact C1 needs a whole series of simple buttons or if not a simple button, a set instructions on how to find hidden features. Everybody talks about the steep C1 learning curve; using C1 is not hard, it's finding the stealthy features that makes C1 frustrating.
I honestly can't see how deleting a catalog could be any simpler than it already is. Maybe it should be a little more complicated if anything!
"Close Capture One(or just the catalog) >> Delete catalog folder >> Done"
Capture One is a professional tool that already fits within an industry and the required workflows. Making improvements? Sure. There are plenty of holes and rough edges.
Now, making something simple 'simpler' just because one click is easier than two, is a waste of time and recipe for disaster in my opinion and experience.
I mean, how often do you delete a catalog!!
My thoughts exactly.
I can't think of any likely more complicated situation, even loosely using the sessions approach, that could be realistically enhanced by an all-knowing "button".
As thing stand the only things this the button could do would be to tell the user to close the catalogue/session if it is open and then replicate the deletion method via the OS functionality.
There are other things that would place higher on my personal list of useful ideas.
(Thoughts for what they are worth.)
Grant
I agree that it is not a 'big issue'. But, it can be a bit more complicated than you are suggesting. First, you need to know where in your file system the catalog is located. I place catalogs in multiple locations. So, in order to find the location, Capture One support said to open the catalog and control-click on the catalog name. That gives you a link to the catalog which you click to get to it. I then just deleted the catalog using finder. That is what caused the problem. You need to add the step of returning to Capture One, closing the catalog and then returning to finder. That's a whole bunch more than two mouse clicks. And, was not mentioned by 'support'.
Nearly every software I use has a built-in 'delete' command. Adding this shouldn't be a big deal. And, might become more important if Capture One develops as a Lightroom alternative with more 'less pro' users adopting it.
I should also point out that the current process is not documented in the user manual nor help files. It is not obvious that manual deletion using finder is the recommended method to delete catalogs. In face, much software using catalogs, etc. actively discourages the use of the file system to make changes to catalogs, file locations, etc.0 -
You got to have some mystery in life ๐ 0 -
[quote="nbirkett" wrote:
I agree that it is not a 'big issue'. But, it can be a bit more complicated than you are suggesting. First, you need to know where in your file system the catalog is located. I place catalogs in multiple locations. So, in order to find the location, Capture One support said to open the catalog and control-click on the catalog name. That gives you a link to the catalog which you click to get to it. I then just deleted the catalog using finder. That is what caused the problem. You need to add the step of returning to Capture One, closing the catalog and then returning to finder. That's a whole bunch more than two mouse clicks. And, was not mentioned by 'support'.
Nearly every software I use has a built-in 'delete' command. Adding this shouldn't be a big deal. And, might become more important if Capture One develops as a Lightroom alternative with more 'less pro' users adopting it.
I should also point out that the current process is not documented in the user manual nor help files. It is not obvious that manual deletion using finder is the recommended method to delete catalogs. In face, much software using catalogs, etc. actively discourages the use of the file system to make changes to catalogs, file locations, etc.
Yeah, apparently Capture One was Session based until they implemented Catalogs, perhaps in a not by design manner.
In the way you'd typically handle Sessions, moving, renaming and deleting the database document in the filesystem is very obvious (at least to me).
I hope they don't make a 'less pro' version because they still have a lot to fix in this one!0 -
[quote="gusferlizi" wrote:
Yeah, apparently Capture One was Session based until they implemented Catalogs, perhaps in a not by design manner.
In the way you'd typically handle Sessions, moving, renaming and deleting the database document in the filesystem is very obvious (at least to me).
I hope they don't make a 'less pro' version because they still have a lot to fix in this one!
Yes -I'm not wanting a less pro version. But, even 'pros' should find some dedicated buttons useful to help work flow.0 -
Interesting comment re cloning.
I can't recall using an editor where the clone facility, whatever it offered, was not effectively part of some layer type adjustment - even if it was not referred to using that term.
Actually that's not entirely true because in the early days of digital and using jpgs, the editors were destructive anyway so layers did not come into it.
Nevertheless for something that is a specifically described feature it is usually possible to find relevant information either in the on-line Help or by downloading the PDF version of the User guide which is searchable.
Either will usually be faster than working through videos.
For techniques and tips on how to make tools do what you want with the functionality they offer the videos are likely much more useful than the written word for most people - especially those with leanings toward "visual" things, photographers for example.
In the early days of my use of C1 I often discovered other enlightening and absorbing subjects when starting out looking for something rather mundane. My personal belief is always to encourage individuals to search for their own information and solution - from as early an age as possible.
I guess it is often about what suits the individual. Despite reading a number of books and help files and article written by product experts I have never found a comfortable way to get a good handle on how to work with Photoshop (or any of it's lookalikes). I understand enough of the principles, I think, but actually using it (or its alternatives) just does not gel with me.
Ah! The wonders of individuality ....
Grant0 -
[quote="nbirkett" wrote:
Nearly every software I use has a built-in 'delete' command.
It rather depends on the software and what you are trying to delete. From within, say, Microsoft Word or Microsoft Excel, I wouldn't expect to be able to delete the document I was currently working on, or another document either. If I were working in, say, a PowerPoint or Keynote presentation, I'd expect to be able to delete a slide within the presentation (akin to deleting an image in a Capture One session or catalog) but I wouldn't expect to be able to delete that presentation, or another one, from inside the app (akin to deleting the Capture One session or catalog).
Ian0
Post is closed for comments.
Comments
31 comments