What is the difference ...
I am a relatively new CaptureOne user and, until now, had been using simple Sessions for my work. Those sessions did not require importing as I just browsed to the location of the images and began working on them.
I now realize that there are more complex Sessions that involve importing images into the Sessions but don't know what the difference is between those Sessions with importing and Catalogs, which require importing. It seems to me that both require importing, both keep track of changes to the images and both create a folder structure to control all of that information. Can someone please tell me why one would use a Catalog instead of a Session (or the other way around)?
Thank you.
I now realize that there are more complex Sessions that involve importing images into the Sessions but don't know what the difference is between those Sessions with importing and Catalogs, which require importing. It seems to me that both require importing, both keep track of changes to the images and both create a folder structure to control all of that information. Can someone please tell me why one would use a Catalog instead of a Session (or the other way around)?
Thank you.
0
-
Catalogs require import, for sessions it is optional.
There is so much to tell about the choice between sessions and catalogs. Actually, this is one of the main reasons I created a separate site on the web to tell you all about it. As a coincidence, the latest blog in the serie on catalogs was just published today. I would be happy to take any question you might have after reading.
Main page: http://imagealchemist.net
All blogs about sessions: http://imagealchemist.net/tag/session/
All blogs about catalogs: http://imagealchemist.net/tag/catalog/0 -
Thank you again. I have read the blogs and I now believe that I understand the difference between catalogs and sessions. I do not need the overhead of a catalog but using a session with an import requires that I use up twice the amount of space since it is apparently not designed for images that reside on local discs, and using a session without an import means that the software will not be able to do any automatic adjustments. Given all of that I have started to use catalogs so I an use the already existing images on my local discs without duplication.
Your help has been greatly appreciated and would have helped me finish my work faster except that C1 8.2 has now stopped working properly on my system and crashes with every import attempt. No action on my part (rebooting, shutting down and restarting, re-installing) seems to have any effect and I will probably try to drop back to 7.2.3 which was working properly. I expect that your session/catalog information is also valid for that. Thank you again.0 -
Hi, glad I could help in understanding about sessions and catalogs. It is also valid for CO7. Sorry to hear that CO8.2 does not work properly. Would CO 8.1.1 perhaps be better?
Of course you could ask Phase One support for help. In particular preventing crashing has a number one priority. So if I may encourage you to file a support case...
http://www.phaseone.com/SupportMain.aspx
Up to you.0 -
I have worked out what the problem was and how to fix it so the crashing is now a thing of the past.
What had apparently happened was that there was a corrupt image in the folder that I was importing. C1 crashed when trying to import it and, when I started it again the import dialog box still contained the path to the folder containing the bad image. It automatically tried to do the import again and, again, crashed. This repeated every time I tried to do any kind of import and it seems to me that the idea of keeping that dialog box populated and automatically trying to import when the dialog box opens is an open invitation to this kind of issue. Since it automatically started to import when the dialog box opened I had no chance to change the import path and the only thing I could do was to rename the import folder. Then, of course, it could not find the folder to import and stopped crashing.
I had notified support of the problem and I notified them again that I had found the problem and had addressed it.
Thanks to your blog I am much more knowledgeable about catalogs and sessions but I do have one question. I have been using catalogs with the images being "imported" to their current locations so I don't have to use up any more disc space than I have to. However I have noticed that when I create a new catalog it does not have any value populated in the Output Location -> Store Files entry in the Basics Tab under the Process Recipe. Sessions allow you to select the image folder as the output location which is convenient since I then set the subfolder to C1 and don't have to worry about resetting it if I create a new session. But catalogs do not allow the use of the Image Folder and I don't understand why.
I don't know if it is an oversight or intentional. I had the same question when I tried to set up keyboard shortcuts for both the Edit With and Open With commands. The Edit With entry showed up in the keyboard shortcut menu but the Open With did not and I had to send a question to the support team to ask them if the omission was intentional or not. They replied they did not know but would create a feature request for it. I have the same question about the use of the Output location in the Basic Tab of the Process Recipe section (now that was a mouthful).0 -
I don't use catalogs, but upon checking i think i've found you set the image folder in the File tab of the output recipe. 0 -
[quote="HCS" wrote:
I don't use catalogs, but upon checking i think i've found you set the image folder in the File tab of the output recipe.
I am not sure what you are saying here.
In my catalogs I set the Root Folder in the File Tab to the Image Folder and the SubFolder to C1. This allows me to send my output jpgs to the C1 subfolder of the folder containing the raw images. I have been doing this since version 7 with no problem and it is now working (again) with 8.2.
My problem turned out to be that there was a single corrupt raw image in the folder I was importing and C1P choked on it and crashed. When I restarted C1 and opened the import dialog to change the folder C1 crashed again because it began to import the same files, including the corrupt one, as soon as the dialog box appeared and before I could change the setting.
This seems to be a bug to me. If C1 crashes when importing from a folder the software ought to either disable automatic importing the next time the dialog box appears or reset the import setting to something else. The import begins immediately well before the user has a chance to reset it - the average time between my pressing the import button and the crash was probably about 1/4 seconds - and this happens even if a new catalog (or session) is used. The only way out of this cycle for me was to rename the import folder so C1 could not automatically begin the import. I am actually surprised that the software does not have a try-catch (or equivalent) around the import section to prevent a complete software crash when an exception occurs.
This is what was causing my problem, not the setting of the Root Folder in the File Tab, and isolating the single corrupt image solved the whole problem.
If I am misunderstanding your post please let me know.0 -
[quote="MikeFromMesa" wrote:
[quote="HCS" wrote:
I don't use catalogs, but upon checking i think i've found you set the image folder in the File tab of the output recipe.
I am not sure what you are saying here.
In my catalogs I set the Root Folder in the File Tab to the Image Folder and the SubFolder to C1. This allows me to send my output jpgs to the C1 subfolder of the folder containing the raw images. I have been doing this since version 7 with no problem and it is now working (again) with 8.2.
My problem turned out to be that there was a single corrupt raw image in the folder I was importing and C1P choked on it and crashed. When I restarted C1 and opened the import dialog to change the folder C1 crashed again because it began to import the same files, including the corrupt one, as soon as the dialog box appeared and before I could change the setting.
This seems to be a bug to me. If C1 crashes when importing from a folder the software ought to either disable automatic importing the next time the dialog box appears or reset the import setting to something else. The import begins immediately well before the user has a chance to reset it - the average time between my pressing the import button and the crash was probably about 1/4 seconds - and this happens even if a new catalog (or session) is used. The only way out of this cycle for me was to rename the import folder so C1 could not automatically begin the import. I am actually surprised that the software does not have a try-catch (or equivalent) around the import section to prevent a complete software crash when an exception occurs.
This is what was causing my problem, not the setting of the Root Folder in the File Tab, and isolating the single corrupt image solved the whole problem.
If I am misunderstanding your post please let me know.
I was under the impression that i was replying to below question in your previous thread. I may have misunderstood you in that post. I do agree CO shouldn't go on importing a file that it has found to be corrupt before. I do actually think it shouldn't trip over a corrupt file, it should put it aside and continue, but alas ... we seem to agree then 😄[quote="MikeFromMesa" wrote:
... However I have noticed that when I create a new catalog it does not have any value populated in the Output Location -> Store Files entry in the Basics Tab under the Process Recipe. Sessions allow you to select the image folder as the output location which is convenient since I then set the subfolder to C1 and don't have to worry about resetting it if I create a new session. But catalogs do not allow the use of the Image Folder and I don't understand why. ...0
Post is closed for comments.
Comments
7 comments