Exporting image from DxO PL4 to CO20 destroyed my large session
Greetings,
I tried using DxO PL4 DeepPrime to reduce noise for an image shot at a very high ISO. I then made the mistake of exporting to CO rather than to disk. I now find that all of my edit history has been lost - i.e. cropped images are not showing the greyed out original dimensions when I select crop and my tools are all showing neutral values.
Unfortunately, the session contained more than 3,000 images. Even worse, I was almost done editing (down to my last 100 or so images) when I made this mistake. I really don't want to do all of this work over!
My feeling is that DxO PL4 overwrote all of its edits onto my CO20 edits for all of the images rather than just the one I was trying to work on - but I'm simply guessing. Does anyone know what might have happened and what I should do now?
I quit CO20 because the hard drive was spinning continuously and the cosessiondb file has already swelled to more than twice the size of the cosessiondb.backup, which is dated 11/13/20 (the day I updated from CO12 to CO20/21). I suppose I could go back to that session but I'd still lose a lot of time that I've spent working on this in the last two weeks.
Any help would be appreciated.
Thanks,
Bruce
-
You don't have a Time Machine back from before you did the work using DxO PL4?
Ian
0 -
Sadly no. I use Time Machine to backup my internal SSD but my external photo drive is too large so I only back this up intermittently.
Bruce
0 -
Perhaps, I should say that the Settings131 .cos files, Settings120 .cos files, and Thumbnails .cot files are all intact as of course are the original RAW files. Is there a way to recreate the database using the constituent files?
0 -
The settings files describe the changes capture one will apply to your original, unchanged image files to get your desired result. If DxO PL4 replaced the original image files I think you are out of luck.
0 -
If you have the original RAW files and all of the edits (from both versions) you should be able to resurrect things - unless DxO overwrote the RAW and you have no back up availability anywhere.
If that had happened I would be very surprised.
However there is a reason why C1 never replaces a "source" or "previously exported" file and this story may a kind of example for that rationale.
0 -
Bruce,
AS far as I know, DPL doesn't overwrite the initial RAW. What I have tried is to use DeepPrime in DPL4 and export the result as a (linear) DNG with only optics correction and noise reduction. In that case, and if your native RAW is not DNG, you would keep your original RAW intact. The only thing I was disappointed about is that the exported image has a reduced colour space (Display P3) with respect to the usual and very large Capture One workspace.
The way I proceeded was to open my RAW images (which are DNG in my case) with DPL4, save the noise and optics corrected linear DNG on my desktop, and then import it in my Capture One session. Please note that, anyway, the new corrected DNG image is saved under an other name, and accordingly should not erase your original RAW.
You should be able to retrieve your adjustments using your C1 settings.
0 -
Thank you all for your help and insights. Indeed the original RAW file (ORF) is unchanged. I still have no idea what happened to my cosessiondb file, but I when I pasted a new empty ****.cosession.db file into the original session folder then reimported the RAW files - all was restored. I cannot explain why the original ***.cosession.db became corrupted in the strange way that it did.
I will try using a linear DNG export. In my experimentation so far I've only used tiff and DNG outputs, and the DNG colors were hideously shifted to a yellowish/green tint. Maybe my mistake there was not using linear DNG.
While I appreciate many of the features of Capture One, noise reduction for high ISO images using DxO PL4 DeepPrime is in a totally different league than what I can accomplish using Capture One. I'd be interested in how they accomplish this or whether my eyes simply don't see the tradeoffs that keep CO from choosing to match this feature.
This was the first time that I requested any help from this forum or PhaseOne and I am really impressed at how helpful the community is! Thank you, again.
Bruce
0 -
check out: https://blog.dxo.com/denoising-technology/
there are for sure tradeoffs but the results are so incredible good that they probably don't matter much in comparison. the biggest issue is processing time but faster Macs are on the way and dxo is for sure working on it too, so at some point this will also not be an issues. ai will help getting better images and the groundwork is laid out now by companies like dxo or adobe , co is probably simply not able to develop something similar in a foreseeable timeframe to compete with them, as it seems far more complex than what is used today.
0
Post is closed for comments.
Comments
8 comments