Upgrading version 11 catalog
I have a licensed copy of version 11 and have been trialing version 12. I recently processed some images in version 11 using a session and a favorites folder and decided to open the version 11 session with 12 and do some additional processing. Of course I was asked if C1 should upgrade the session and I replied Yes.
When the upgrade was complete I was shown my images, but many some of my edits are gone, layers are missing and my ratings have disappeared (of the 25 or 30 rated images only one still shows as rated). Is this a known issue when upgrading sessions? I am completely puzzled.
Fortunately I saved the complete folder structure for my version 11 session and I can go back and use it, but what happened here?
When the upgrade was complete I was shown my images, but many some of my edits are gone, layers are missing and my ratings have disappeared (of the 25 or 30 rated images only one still shows as rated). Is this a known issue when upgrading sessions? I am completely puzzled.
Fortunately I saved the complete folder structure for my version 11 session and I can go back and use it, but what happened here?
0
-
Yes, when you upgrade from version N-1 to version N, you can't go back, and the (N-1) catalogs and sessions can't be opened any longer with version N, i.e. you lose most of your adjustments.
It is strongly suggested to backup your catalogs and/or sessions folders before upgrading, just in case.0 -
[quote="tenmangu81" wrote:
Yes, when you upgrade from version N-1 to version N, you can't go back, and the (N-1) catalogs and sessions can't be opened any longer with version N, i.e. you lose most of your adjustments.
I think that perhaps there is a typo in your post.
You say that when you upgrade a catalog or session from N-1 to N it can not be opened in N. I think you mean it can no longer be opened in N-1. I understand the process of upgrading changes the catalog/session so it no longer can be understood by N-1. If the process of upgrading from N-1 to N produces a catalog or session that can not be understood by N, what is the reason for upgrading the catalog or session.
What I tried to say is that the upgraded session did not contain the information that was in the previous session so the edits made in version 11 no longer showed up in version 12. If upgrading a session from version 11 to 12 produces information that can not be read properly by version 12, I don't see the purpose of upgrading. The result of this is that I can not use version 12 to continue editing my version 11 photos, even after upgrading the session to version 12 and that just does not make any sense to me. As I understand it, the purpose of upgrading a session from version 11 to version 12 is so that you can continue editing in version 12.[quote="tenmangu81" wrote:
It is strongly suggested to backup your catalogs and/or sessions folders before upgrading, just in case.
Yes. I did that, and I still have the version 11 catalog which still works with version 11.0 -
Mike,
No a session upgrade should not lose the edit information you mentioned from a V11 Session.
Were your using the V 12.0.2 release? Or an earlier one?
Either way it may be worth checking the release notes for the 3 V12 releases to date to see if anything listed underchanges - especially software fixes for 12.0.1 and 12.0.2 seem like they might relate to what you are seeing.
When there IS a major change to the underlying processing C1 make this clear in the announcements and the release notes. It's not something that is undertaken lightly an usually the effect is at the image level for processing.
It sounds like you have something else going on here.
With a session one would expect to see separate folders for both the V11 and the v12 edits sidecar files in the sub folder(s) below the folders in which the source images are stored. The first check would be to see if those subfolders still exist.
HTH.
Grant0 -
[quote="SFA" wrote:
Mike,
No a session upgrade should not lose the edit information you mentioned from a V11 Session.
Were your using the V 12.0.2 release? Or an earlier one?
The About dialog box says 12.0.2 and, as far as I know, that is the latest release.[quote="SFA" wrote:
With a session one would expect to see separate folders for both the V11 and the v12 edits sidecar files in the sub folder(s) below the folders in which the source images are stored. The first check would be to see if those subfolders still exist.
There are Settings110 and Settings120 folders which I assume refer to versions 11 and 12. Both still exist, but the contents are quite different. For example the version 11 folder contains 10 comask files corresponding to the 10 images with masks and layers. The version 12 folder contains only 4, and even those 4 do not show the same number of layers as in version 11. That is, if I only look at the images that have layers in both versions, the ones with 2 layers in version 11 only show one layer in version 12.
I guess I should file a bug report about this, although I am a bit surprised that no one else has seen this. Before I do that I guess I should check the release notes and see if there is anything about this listed.
This is really quite disappointing. As a general rule CaptureOne has been very stable and I have seen very few, if any, issues that affected me, so I did not expect this sort of thing. Perhaps they did not test the upgrade functionality very well.0 -
I checked the release notes but saw nothing about this so I filed a bug report. 0 -
[quote="MikeFromMesa" wrote:
[quote="tenmangu81" wrote:
Yes, when you upgrade from version N-1 to version N, you can't go back, and the (N-1) catalogs and sessions can't be opened any longer with version N, i.e. you lose most of your adjustments.
I think that perhaps there is a typo in your post.
Yes, you are right !! Of course I meant N-1 instead of N !!0 -
Mike,
What were the missing layers doing (in edit terms)?
All doing the same sort of adjustment work or are they just randomly mislaid?
I can think of some ways to investigate but it's probably better to wait for the Support Team to come back to you.
Plus I don't have any useful amount of time I could be certain to be available to progress my possible suggestions until next week.
Grant0 -
[quote="SFA" wrote:
What were the missing layers doing (in edit terms)?
It actually turned out to be pretty interesting to compare the adjustments between versions, and the results are not what I would have expected. Here are some comparisons:
Image 1
version 11 - 2 layers, Layer 1 is a gradient mask of the sky, Layer 2 is a brush mask of the ground
version 12 - 1 Layer, Layer 1 is a luminosity mask of the sky.
Image 2
version 11 - same layers as Image 1, although the adjustments are different
version 12 - same layer as Image 1
Image 3
version 11 - same layers as Image 1, although the adjustments are different
version 12 - no layers
Image 4
version 11 - Layer 1 is a sky gradient
version 12 - Layer 1 is a luminosity mask of the sky
Image 5
version 11 - 2 Layers, Layer 1 is a gradient of the sky, Layer 2 is a gradient of the ground
version 12 - no layers
So it almost seems consistent. It only seems to consider one layer beyond the background and the gradients seem to change into luminosity masks. However it breaks down when you consider that some masks don't get translated at all as in Images 3 and 5. I am going to do a bit more comparing and see if I can narrow this down. It might be helpful for the support people to know what is happening beyond "Hey. My layers are disappearing".0 -
That does sound a little odd Mike - I assume you updated the process engine for the images to V12?
The Luminosity adjustments for masks are of course new but it seems odd that they have appeared and apparently replaced a previous V11 mask. Of some sort.
The Gradient mask tools has been re-engineered for V12 so it is perhaps not a surprise that something may have happened there in some form of "translation" from 11 to 12 BUT I would hope that you were offered an opportunity to retain the V11 edits as they were rather than the upgrade making an assumption that the edits should be upgraded to V12.
Certainly I did not see any problems testing but I am a Windows user and, as ever, technical things may be different with Macs.
Grant0 -
[quote="SFA" wrote:
That does sound a little odd Mike - I assume you updated the process engine for the images to V12?
That was automatically set when I opened version 12 after the session upgrade.[quote="SFA" wrote:
The Luminosity adjustments for masks are of course new but it seems odd that they have appeared and apparently replaced a previous V11 mask. Of some sort.
The Gradient mask tools has been re-engineered for V12 so it is perhaps not a surprise that something may have happened there in some form of "translation" from 11 to 12 BUT I would hope that you were offered an opportunity to retain the V11 edits as they were rather than the upgrade making an assumption that the edits should be upgraded to V12.
It seems to me that there are several problems with the session upgrades involving (1) the type of replacement layer, (2) whether or not layers even got replicated, (3) layer names were lost and (4) almost all of my image ratings were lost. I need to do a bit more testing to see if I can track down what might be causing this, just out of curiosity.
In some ways it is not all that important. I can process this batch of images with 11 and then just use 12 on new sessions but it is annoying that there is such an issue when converting sessions and it could be a big issue in the future if I need to go back and reprocess old version sessions. I do not know if the same issue even exists for either catalogs or sessions where the images are actually imported. In this case I am just using a "favorites" folder with the session.0 -
[quote="MikeFromMesa" wrote:
[quote="SFA" wrote:
That does sound a little odd Mike - I assume you updated the process engine for the images to V12?
That was automatically set when I opened version 12 after the session upgrade.
I would have thought an automatic change of processing engine would be unusual.
I mainly use sessions. There is no automatic processing engine upgrade for the session as a result of opening the session from an earlier version in V12 although one can choose to make that change if preferred.
The COSESSIONDB file is of course updated and a copy of the previous session file is saved. But the Image processing engine is left as it is. (Very old versions of C1 are not covered here but that has been the case for a while).
I can then leave the image with its original edit and processing engine, create a variant, change the engine of the variant to V12 and see what happens. I see a warning of some part of the existing edit (i.e. of a cloned variant) is in some way not directly compatible.
It may be worth repeating the process and verifying the session in V11 before opening it in V12.
Grant0 -
For what it is worth -
I filed this as a bug report with support. They have asked for, and I have sent, a ton of additional information including a screen recording showing the version 11 images, the conversion and the version 12 images showing the missing adjustment layers, the log files, an EIP package, whatever that is, and this is still on on-going issue.
I would guess that the screen recording was meant as proof that this really was an issue.0
投稿コメントは受け付けていません。
コメント
12件のコメント