Editing changes not saved upon exiting C1
For the past few days I have been experiencing a VERY frustrating bug with Capture One: whenever I quit the program, some or all of the editing changes I made are not saved whenever I reopen the program. It's as if everything was just stored in RAM and never written to disk!
The major culprit seems to be related the local adjustments: my masks either do not get saved when reopening the app, or they completely disappear! For example, let's say I create a new layer and start drawing a mask; when I close and then reopen C1, the mask may have been incompletely saved, or it may have disappeared entierely! And if some mask is there upon restarting, upon another reopening of the program it sometimes would just vanish. So all in all, it seems completely random.
This is totally disrupting of my workflow and I feel like I am going to miss delivery deadlines... as I have to work over and over and over again only to find that my changes never register on the hard drive, or worse, what looks like it was properly saved gets trashed on the next program start! I tried moving my sesson folder to another disk, to no avail.
I just tried a complete, clean reinstall of C1. The bug is still there. My next step will be a complete Windows 10 reinstall... as I cannot find what may cause this.
Any help would be greatly appreciated, thank you.
The major culprit seems to be related the local adjustments: my masks either do not get saved when reopening the app, or they completely disappear! For example, let's say I create a new layer and start drawing a mask; when I close and then reopen C1, the mask may have been incompletely saved, or it may have disappeared entierely! And if some mask is there upon restarting, upon another reopening of the program it sometimes would just vanish. So all in all, it seems completely random.
This is totally disrupting of my workflow and I feel like I am going to miss delivery deadlines... as I have to work over and over and over again only to find that my changes never register on the hard drive, or worse, what looks like it was properly saved gets trashed on the next program start! I tried moving my sesson folder to another disk, to no avail.
I just tried a complete, clean reinstall of C1. The bug is still there. My next step will be a complete Windows 10 reinstall... as I cannot find what may cause this.
Any help would be greatly appreciated, thank you.
0
-
Which release of version 10 are you using?
Have you run a session "verify"? (From what you have written I assume you are using sessions not catalogues at this point.)
You may want to delete any cache and temporary files that relate to C1.
Also check the log files for error messages that provide clues.
If I were you I would also open a Support Case with the Capture One support team.
Grant0 -
I am using Windows version 1709. I just did a fresh install, just in case.
What exactly is a session "verify" ? The problem seems to happen in multiple sessions, by the way.
Also, I think the cache files are irrelevant, because I tried a fresh install of C1 after doing a clean uninstall. This won't matter anyway since I will be doing a completely fresh install on top of a Windows fresh install.
I posted here because the support server was hanging whenever I tried to open a ticket (to add insult to injury, haha). I'll report back when everything is done installing.
Thanks!0 -
Having exactly the same issue with sessions (not with catalogues).
Half of my edits are lost when closing and restarting CO1, certainly masks, but also exposure edits etc.
Véry, véry annoying indeed.
Since this is happening to others too, I guess I should raise a support case.
Chris0 -
OK, so I did the following:
- Complete SSD format and Windows 1709 clean install (including up to date drivers and all)
- Capture One Pro 10.2 clean install
- I cleared the cache folders in the session folders I tested
And... the bug is still there. Chris M, you are right, every kind of edit is affected. I also noticed that file managing (star and color ratings) often reverts to a previous state. Even deleted variants come back after a restart. I am completely unable to do any work in this current state of things...
Were you able to raise a support ticket? Yesterday I had no luck with the support server.0 -
I have just checked the Support Server. Logged in with no problems.
Did you get that far when you tried?
Grant0 -
[quote="NNN635796750580192506" wrote:
I am using Windows version 1709. I just did a fresh install, just in case.
What exactly is a session "verify" ? The problem seems to happen in multiple sessions, by the way.
So is that Win 10 Creators Update?
For the Verify;
Open C1 and go to the File menu.
About 1/3 of the way down the list should be "Verify Catalog or session".
Click on that and it opens a Windows browser screen that allows you to browse to the to the catalog or session file to be verified.
Note that you cannot Verify an open session.
The process does a number of internal checks on the session and will report on the results.
If the conclusion is that the session is OK then either the particular problem you are experiencing is something to do with the session file but is not something currently identified as requiring checking or - possibly more likely given you have multiple session presenting challenges - something else that may or may not be under the control of C1.
In a session your main edits are in the .cos files and masks in the .comask files. Both can be found in by right clicking on an image in the C1 browser and choosing "Show in Explorer". That takes you to the Image file. Also in that folder is a Capture One folder.
OPen the Capture One folder and then the Settings folder (you may have more than one Settings folder if the session has been processed in several versions of C1) and that should then list for you the .cos and .comask files complete with the date of last update and all the other usual Windows stuff.
The cos files are xml and sort of human readable in Wordpad - enough to work out whether things appear or disappear between edits it you monitor the file.
comask files are not generally human readable so you are left with the date of last edit as a guide.
There are also log files if you have the desire to seek to understand what they are telling. Not everyone wishes to go that deep.
HTH.
Grant0 -
[quote="SFA" wrote:
I have just checked the Support Server. Logged in with no problems.
Did you get that far when you tried?
Grant
Yes, It works now! I submited a ticket and pointed to this thread for further info.
As for the rest, I verified one of the problematic sessions and every check passed successfully.
I will now try to find out any useful information in the cos files.0 -
Some user is experiencing problem with reappearing keywords after deletion.
It looks like this problem is linked with what I'm experiencing (stuff not getting recorded on the hard drive).
viewtopic.php?f=69&t=267700 -
[quote="NNN635796750580192506" wrote:
Some user is experiencing problem with reappearing keywords after deletion.
It looks like this problem is linked with what I'm experiencing (stuff not getting recorded on the hard drive).
https://forum.phaseone.com/En/viewtopic ... 69&t=26770
Not necessarily.
There is (or was) a very specific set of circumstances that could lead to the apparent non-deletion of keywords.
It has been covered a number of times since V9.
If you don't have that problem (as they did not have the problems you are describing) then a connection is doubtful.
If the session file has verified OK then either it is something previously unidentified and so unchecked or possible an issue outside Monarch's direct control (or thought to be outside Monarch's direct control).
I think you really need some help from someone who can, as a starting point, assess the log files. The Support Team are good for that.
Grant0 -
Alright! It just seemed like a possible connection.
I am currently waiting for the support team to analyze my log files.0 -
My problems with sessions seem to have begun with installing the Windows 10 creators update preview. I don't think it's about corrupted sessions or such. I also did a fresh install with the official release of the Windows 10 autumn update, and the problem persists. So I assume that something in the new Windows 10 update is causing problems with writing the edits to disk.
Seems like a CO1 service release is the only solution...
Chris0 -
I think you are unto something ChrisM. I also started getting problems around the time I installed the Fall Creator Update. And also for me, a clean Windows install did not fix the problem. 0 -
Chris, can you check if you have multiple "TMP" files in your broken session "Settings100" folders?
I noticed a large amount of them in the sessions I tried to work on, whereas there are none of these files in sessions which I know were working previously.
Finding that out would of course not fix anything, but it may help the devs find what's going on.0 -
[quote="NNN635796750580192506" wrote:
Chris, can you check if you have multiple "TMP" files in your broken session "Settings100" folders?
I noticed a large amount of them in the sessions I tried to work on, whereas there are none of these files in sessions which I know were working previously.
Finding that out would of course not fix anything, but it may help the devs find what's going on.
Yes,
Multiple temp files are written.
Auto exposure is undone each and every closing, so are curve presets. It seems that manual edits tend to stick, but applied presets are undone. However, mixing manual edits and presets can lead to presets sticking, so I have a hard time seeing a pattern here....
Alos: the preview doés actually show the auto exposure edit, so in the preview the edits do stick, but in the viewer the edit is lost.
Clearly, working with sessions is totally impossible now, so a service update or other solution is needed fast.
Chris0 -
[quote="NNN635796750580192506" wrote:
Chris, can you check if you have multiple "TMP" files in your broken session "Settings100" folders?
I noticed a large amount of them in the sessions I tried to work on, whereas there are none of these files in sessions which I know were working previously.
Finding that out would of course not fix anything, but it may help the devs find what's going on.
I don't recall ever seeing TMP files in Settings folder before.
All sorts of applications leave temporary files lying around in the Windows designated TEMP folders, but I've never seen anything from C1 in the Settings folders.
Grant0 -
[quote="ChrisM" wrote:
[quote="NNN635796750580192506" wrote:
Chris, can you check if you have multiple "TMP" files in your broken session "Settings100" folders?
I noticed a large amount of them in the sessions I tried to work on, whereas there are none of these files in sessions which I know were working previously.
Finding that out would of course not fix anything, but it may help the devs find what's going on.
Yes,
Multiple temp files are written.
Auto exposure is undone each and every closing, so are curve presets. It seems that manual edits tend to stick, but applied presets are undone. However, mixing manual edits and presets can lead to presets sticking, so I have a hard time seeing a pattern here....
Alos: the preview doés actually show the auto exposure edit, so in the preview the edits do stick, but in the viewer the edit is lost.
Clearly, working with sessions is totally impossible now, so a service update or other solution is needed fast.
Chris
Is it possible to roll back the last Win 10 update?0 -
[quote="SFA" wrote:
[quote="NNN635796750580192506" wrote:
Chris, can you check if you have multiple "TMP" files in your broken session "Settings100" folders?
I noticed a large amount of them in the sessions I tried to work on, whereas there are none of these files in sessions which I know were working previously.
Finding that out would of course not fix anything, but it may help the devs find what's going on.
I don't recall ever seeing TMP files in Settings folder before.
All sorts of applications leave temporary files lying around in the Windows designated TEMP folders, but I've never seen anything from C1 in the Settings folders.
Grant
Yes, I never noticed that berfore either. The TMP files names are containing the original photo name, plus a string of letters and numbers. And then, some files are incorporating into their filename the filename of the previous TMP file...
For example, regarding one (proper) file named _COP3673.NEF.cos I have the following associated TMP files:
_COP3673.NEF.cos~RF177f869.TMP
_COP3673.NEF.cos~RF178b9c5.TMP
_COP3673.NEF.cos~RF178b9c5.TMP~RF1792011.TMP
_COP3673.NEF.cos~RF178b9c5.TMP~RF1792011.TMP~RF17931f3.TMP
_COP3673.NEF.cos~RF178b9c5.TMP~RF1792011.TMP~RF17931f3.TMP~RF1795579.TMP
_COP3673.NEF.cos~RF178b9c5.TMP~RF1792011.TMP~RF17931f3.TMP~RF1795579.TMP~RF1799001.TMP
_COP3673.NEF.cos~RF178b9c5.TMP~RF1792011.TMP~RF17931f3.TMP~RF1795579.TMP~RF1799001.TMP~RF17a007e.TMP
_COP3673.NEF.cos~RF178b9c5.TMP~RF1792011.TMP~RF17931f3.TMP~RF1795579.TMP~RF1799001.TMP~RF17a007e.TMP~RF17a1ed4.TMP
_COP3673.NEF.cos~RF178b9c5.TMP~RF1792011.TMP~RF17931f3.TMP~RF1795579.TMP~RF1799001.TMP~RF17a007e.TMP~RF17a1ed4.TMP~RF17a590e.TMP
_COP3673.NEF.cos~RFfcfee8.TMP
Which is a lot of junk.0 -
[quote="SFA" wrote:
[quote="ChrisM" wrote:
[quote="NNN635796750580192506" wrote:
Chris, can you check if you have multiple "TMP" files in your broken session "Settings100" folders?
I noticed a large amount of them in the sessions I tried to work on, whereas there are none of these files in sessions which I know were working previously.
Finding that out would of course not fix anything, but it may help the devs find what's going on.
Yes,
Multiple temp files are written.
Auto exposure is undone each and every closing, so are curve presets. It seems that manual edits tend to stick, but applied presets are undone. However, mixing manual edits and presets can lead to presets sticking, so I have a hard time seeing a pattern here....
Alos: the preview doés actually show the auto exposure edit, so in the preview the edits do stick, but in the viewer the edit is lost.
Clearly, working with sessions is totally impossible now, so a service update or other solution is needed fast.
Chris
Is it possible to roll back the last Win 10 update?
I was, until both ChrisM and I decided to try a clean install. Now we would have to reformat again and get an ISO of the previous Windows version, and then reinstall everything and prevent Windows Update from applying the new version. It would be quite a hassle.
Others who go through the normal process of installing the update through Windows Update without doing a clean install should be able to roll back to the previous version, though.0 -
[quote="ChrisM" wrote:
[quote="NNN635796750580192506" wrote:
Chris, can you check if you have multiple "TMP" files in your broken session "Settings100" folders?
I noticed a large amount of them in the sessions I tried to work on, whereas there are none of these files in sessions which I know were working previously.
Finding that out would of course not fix anything, but it may help the devs find what's going on.
Yes,
Multiple temp files are written.
Auto exposure is undone each and every closing, so are curve presets. It seems that manual edits tend to stick, but applied presets are undone. However, mixing manual edits and presets can lead to presets sticking, so I have a hard time seeing a pattern here....
Alos: the preview doés actually show the auto exposure edit, so in the preview the edits do stick, but in the viewer the edit is lost.
Clearly, working with sessions is totally impossible now, so a service update or other solution is needed fast.
Chris
I too tried to find a pattern. Things seem to working quite the opposite from you on my end: presets applied to photos being imported work fine and "stick"; and then furtuer edits are hit and miss when it comes to having their edits stick, with some photos completely out of luck and never recording anything at all except the first applied preset during importing.
I am also experiencing the same situation as you are regarding the thumbnails showing the proper edits. I think it's because they just show the embedded jpeg preview and do not actualize when the settings get reverted back to a previous state.
The guy working on my support case is testing the latest Windows Creator Update on his end and he is in contact with the R&D team about the issue.0 -
This morning I tried to batch rename the photos of my test session. Every single file rename failed, and then when I reopened CO every file was back to its default settings, with any previous edit that used to stick completely gone. All star ratings were gone too.
When I looked at the Settings100 folder, the cos and comask files were properly renamed; only the raw files in the Capture folder were not renamed, hence the lost editings.
CO has no problem moving the raw files around, either: I could select all the photos and move them to the trash folder, and then clear the trash without any issues. The renamed metadata files were not moved to trash, though, because their link to the raw files was broken during the failed renaming process.
So, in conclusion it looks like that:
- CO can rename metadata files, but cannot actually make any internal changes to them;
- CO cannot rename raw files, but it can move them around.0 -
where are your RAW files stored? 0 -
[quote="NNN635796750580192506" wrote:
This morning I tried to batch rename the photos of my test session. Every single file rename failed, and then when I reopened CO every file was back to its default settings, with any previous edit that used to stick completely gone. All star ratings were gone too.
When I looked at the Settings100 folder, the cos and comask files were properly renamed; only the raw files in the Capture folder were not renamed, hence the lost editings.
CO has no problem moving the raw files around, either: I could select all the photos and move them to the trash folder, and then clear the trash without any issues. The renamed metadata files were not moved to trash, though, because their link to the raw files was broken during the failed renaming process.
So, in conclusion it looks like that:
- CO can rename metadata files, but cannot actually make any internal changes to them;
- CO cannot rename raw files, but it can move them around.
If you know that you seem to have problems and there is a reasonable probability that the WIn 10 version or some aspect of its installation activity may be involved I'm not at all sure what you gain by spending time trying more things that are likely to fail without changing anything else.
As I read in a completely unrelated news article earlier today it seems that Microsoft not only fail to deliver anything like long terms support for products they have heavily invested in - like Windows Phones - they have also moved a long way into treating the user as a test guinea pig for their operating system and made it worse by taking control of the update process (at least for most users seeking an easy life.)
Apple do something similar of course, but it seems that in recent times MS have taken things somewhat further than might be wise.
Such are the "benefits" of "agile" software development.
I don't mind doing a bit of unpaid testing once in a while.
If it is to be a permanent status I would like to know where to send the invoice for the work involved.
That would be the same no matter where the problem originates and who should take the responsibility.
Grant0 -
[quote="SFA" wrote:
If you know that you seem to have problems and there is a reasonable probability that the WIn 10 version or some aspect of its installation activity may be involved I'm not at all sure what you gain by spending time trying more things that are likely to fail without changing anything else.
The thing is, this new officially stable windows version is being pushed on users, there is really no opting out. You can block Windows Update for a while, but then you cease to get security updates too, so in reality one can just postpone the new version for a while only, reasonably speaking.
While waiting for a solution, or a patch, or a fix of any kind, I have work to do. I have clients waiting to review photos so I had to try to do whatever work I could in the current state of things (exporting previews even if the originals would not get saved properly is better than nothing). I cannot just sit back and expect my bills to pay themselves! Meanwhile I decided to report what happened just so others with related problems can maybe find a clue.
Every bit of information I have gathered so far has been sent to Phase One for R&D, so I guess it was not in vain. Maybe Windows 10 did cause some funky stuff with this update, but in the end, it is Capture One that is now not working as intended anymore on an OS that should be fully supported, so I expect the devs to iron out whatever incompatibility that may have been introduced so I can continue to work with the software I paid for.0 -
I also filed a support case, and sent my system profile and CO1 log files.
They cannot reproduce the bug as yet, and advise to roll back to CO1 v10.1, but highly doubtful that that wiil work better, since it is the latest Windows update that is the culprit.
I know they were heavily pushing a Nvidia beta driver during beta stage and may have been heavily focussed on video performance or feature expanding, so an option might be to disable the video card in CO1
preferences. Will try that out when at home.
Chris0 -
[quote="NNN635796750580192506" wrote:
[quote="SFA" wrote:
If you know that you seem to have problems and there is a reasonable probability that the WIn 10 version or some aspect of its installation activity may be involved I'm not at all sure what you gain by spending time trying more things that are likely to fail without changing anything else.
The thing is, this new officially stable windows version is being pushed on users, there is really no opting out. You can block Windows Update for a while, but then you cease to get security updates too, so in reality one can just postpone the new version for a while only, reasonably speaking.
While waiting for a solution, or a patch, or a fix of any kind, I have work to do. I have clients waiting to review photos so I had to try to do whatever work I could in the current state of things (exporting previews even if the originals would not get saved properly is better than nothing). I cannot just sit back and expect my bills to pay themselves! Meanwhile I decided to report what happened just so others with related problems can maybe find a clue.
Every bit of information I have gathered so far has been sent to Phase One for R&D, so I guess it was not in vain. Maybe Windows 10 did cause some funky stuff with this update, but in the end, it is Capture One that is now not working as intended anymore on an OS that should be fully supported, so I expect the devs to iron out whatever incompatibility that may have been introduced so I can continue to work with the software I paid for.
Ah, but that lets MS (or whoever) off the hook (potentially) to throw rubbish out the door any time and instead of doing what they need to do to ensure continuance of compatibility they leave the application developers, individually and by the thousands potentially, to compromise their code and carry costs (that presumably they somehow have to pass on) in order to make what you have paid for work as it did before.
MS have form in that respect messing up the compatibility of their Office products from time to time and causing headaches for corporate system admins around the world. Then they wonder why people are reluctant to upgrade!
I seem to recall Apple doing the same thing a couple of years back, effectively breaking the work that many developers had done on the beta releases. Hundreds of applications were patched, tested and re-issued to millions of customers who then had to install, test and so on. Then Apple reverted their original patch invalidating some of the application patches once again and so the cycle and the costs repeated.
MS have done the same.
Some years ago a friend of mine was using an Adobe development tool and was surprised to find that some of his customer installations stopped working after he had updated the environment on his servers (web based applications).
It turned out after some days of puzzling about it that a new included routine had been given a very common name - I can't recall what but let's call it PRINTMAIL - a name that had not been used before in the development suite but that people had used for their own routines since is was available and an obvious choice for a particular purpose.
The newly included routine, issued with no warning documentation, effectively replaced the in application routine and so systems stopped working. It was 3 days before he stumbled across this new internal routine and a further 2 days to make the required changes to his code and deploy it. Not good for him or his customers.
In all cases a little forethought about the potential knock-on effects could have avoided an awful lot of wasted time and, potentially, lost business for many people.
Why such actions seem to be accepted, with no more than minimal whinging on mostly rather obscure (and so easily ingored) internet blogs and forums, baffles me. The risks are likely greater than the possible benefits of the Security patches - which seem to be an ever present threat anyway no matter how many patches are sent out.
With a business to run I am happy to stick with Win 7 for now. If Wini 10 ever shows signs of becoming stable I might consider it but I don't feel a desperate need at this moment to undertake free software testing for Microsoft when I don't need to. It annoys me enough that I will, one way and another, end up paying for the failures of the "big boys" one way or another and at greater cost than would have been the case if the job was done properly before release.
Surely the large and rich corporations have the cash and recruitment clout to be able to deliver that more reliably than they seem to do?
Just my personal opinion of course.
Grant0 -
Same issue here (adjustments not saving often, but not always; mess of temporary files), cropped up right after installing the Fall Creators Update, now that I've gotten that hint. Please look into this, PhaseOne, this can't be that hard to reproduce seeing as several users (and I'm sure that's just the tip of the iceberg) are complaining. 0 -
[quote="NNN635509507115078337" wrote:
Same issue here (adjustments not saving often, but not always; mess of temporary files), cropped up right after installing the Fall Creators Update, now that I've gotten that hint. Please look into this, PhaseOne, this can't be that hard to reproduce seeing as several users (and I'm sure that's just the tip of the iceberg) are complaining.
Have you created a Support Case?0 -
Yes, I brought this to Phase One during RS3 pre-release testing I also brought this up during 10.1
I asked to have R&D talk to me directly as I have special access to the OS. They closed the ticket w/o an email, w/o anything what-so-ever. The arrogance of Europeans baffles me.
I opened a 2nd one requesting they NOT close it and to reopen the first one. Still no one contacts me. We should all move to different software if they that conceited.
Sessions: I can't edit as when I delete the files, those basename pics, have to be edited again.
It feels me to a thread synchronization issue. They think the file can't be created or opened for write so they open a new one, yet they don't come back and resolve them.
J:\>del /s *.tmp
Deleted file - J:\2016_11_05_Jill's Wedding_New\Capture\_MG_2881.xmp~RF19186979.TMP
Deleted file - J:\2016_11_05_Jill's Wedding_New\Capture\05 Ceremony End\CaptureOne\Settings100\_MG_2866.CR2.cos~RF191d93bd.TMP
Deleted file - J:\2016_11_05_Jill's Wedding_New\Capture\05 Ceremony End\CaptureOne\Settings100\_MG_2866.CR2.cos~RF191d93bd.TMP~RF191e78af.TMP
Deleted file - J:\2016_11_05_Jill's Wedding_New\Capture\05 Ceremony End\CaptureOne\Settings100\_MG_2867.CR2.cos~RF1919eea2.TMP
Deleted file - J:\2016_11_05_Jill's Wedding_New\Capture\05 Ceremony End\CaptureOne\Settings100\_MG_2868.CR2.cos~RF1919b478.TMP
Deleted file - J:\2016_11_05_Jill's Wedding_New\Capture\05 Ceremony End\CaptureOne\Settings100\_MG_2868.CR2.cos~RF1919b478.TMP~RF191fa7a9.TMP
Deleted file - J:\2016_11_05_Jill's Wedding_New\Capture\05 Ceremony End\CaptureOne\Settings100\_MG_2868.CR2.cos~RF1919b478.TMP~RF191fa7a9.TMP~RF1920f3c1.TMP
Deleted file - J:\2016_11_05_Jill's Wedding_New\Capture\CaptureOne\Settings100\_MG_2881.CR2.cos~RF19186979.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\_W0A0263.xmp~RF235a396.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\_W0A0263.xmp~RF235a396.TMP~RF23ba35b.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\_W0A0263.xmp~RF235a396.TMP~RF23ba35b.TMP~RF23bba6d.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\_W0A0263.xmp~RF235a396.TMP~RF23ba35b.TMP~RF23bba6d.TMP~RF23bbf6e.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\_W0A0263.xmp~RF235a396.TMP~RF23ba35b.TMP~RF23bba6d.TMP~RF23bbf6e.TMP~RF23f68de.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\_W0A0263.xmp~RF235a396.TMP~RF23ba35b.TMP~RF23bba6d.TMP~RF23bbf6e.TMP~RF23f68de.TMP~RF2427af1.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\_W0A0263.xmp~RF235a396.TMP~RF23ba35b.TMP~RF23bba6d.TMP~RF23bbf6e.TMP~RF23f68de.TMP~RF2427af1.TMP~RF242836d.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\_W0A0263.xmp~RF235a396.TMP~RF23ba35b.TMP~RF23bba6d.TMP~RF23bbf6e.TMP~RF23f68de.TMP~RF2427af1.TMP~RF242836d.TMP~RF2428a04.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\_W0A0263.xmp~RF235a396.TMP~RF23ba35b.TMP~RF23bba6d.TMP~RF23bbf6e.TMP~RF23f68de.TMP~RF2427af1.TMP~RF242836d.TMP~RF2428a04.TMP~RF2428e98.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\_W0A0263.xmp~RF235a396.TMP~RF23ba35b.TMP~RF23bba6d.TMP~RF23bbf6e.TMP~RF23f68de.TMP~RF2427af1.TMP~RF242836d.TMP~RF2428a04.TMP~RF2428e98.TMP~RF2429be6.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\_W0A0263.xmp~RF235a396.TMP~RF23ba35b.TMP~RF23bba6d.TMP~RF23bbf6e.TMP~RF23f68de.TMP~RF2427af1.TMP~RF242836d.TMP~RF2428a04.TMP~RF2428e98.TMP~RF2429be6.TMP~RF242a0e8.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\CaptureOne\Settings100\_W0A0263.CR2.cos~RF235a3a6.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\CaptureOne\Settings100\_W0A0263.CR2.cos~RF235a3a6.TMP~RF23ba36a.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\CaptureOne\Settings100\_W0A0263.CR2.cos~RF235a3a6.TMP~RF23ba36a.TMP~RF23bba7c.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\CaptureOne\Settings100\_W0A0263.CR2.cos~RF235a3a6.TMP~RF23ba36a.TMP~RF23bba7c.TMP~RF23bbf6e.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\CaptureOne\Settings100\_W0A0263.CR2.cos~RF235a3a6.TMP~RF23ba36a.TMP~RF23bba7c.TMP~RF23bbf6e.TMP~RF23f68de.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\CaptureOne\Settings100\_W0A0263.CR2.cos~RF235a3a6.TMP~RF23ba36a.TMP~RF23bba7c.TMP~RF23bbf6e.TMP~RF23f68de.TMP~RF2427af1.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\CaptureOne\Settings100\_W0A0263.CR2.cos~RF235a3a6.TMP~RF23ba36a.TMP~RF23bba7c.TMP~RF23bbf6e.TMP~RF23f68de.TMP~RF2427af1.TMP~RF242837c.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\CaptureOne\Settings100\_W0A0263.CR2.cos~RF235a3a6.TMP~RF23ba36a.TMP~RF23bba7c.TMP~RF23bbf6e.TMP~RF23f68de.TMP~RF2427af1.TMP~RF242837c.TMP~RF2428a04.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\CaptureOne\Settings100\_W0A0263.CR2.cos~RF235a3a6.TMP~RF23ba36a.TMP~RF23bba7c.TMP~RF23bbf6e.TMP~RF23f68de.TMP~RF2427af1.TMP~RF242837c.TMP~RF2428a04.TMP~RF2428e98.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\CaptureOne\Settings100\_W0A0263.CR2.cos~RF235a3a6.TMP~RF23ba36a.TMP~RF23bba7c.TMP~RF23bbf6e.TMP~RF23f68de.TMP~RF2427af1.TMP~RF242837c.TMP~RF2428a04.TMP~RF2428e98.TMP~RF2429be6.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\CaptureOne\Settings100\_W0A0263.CR2.cos~RF235a3a6.TMP~RF23ba36a.TMP~RF23bba7c.TMP~RF23bbf6e.TMP~RF23f68de.TMP~RF2427af1.TMP~RF242837c.TMP~RF2428a04.TMP~RF2428e98.TMP~RF2429be6.TMP~RF242a0e8.TMP
Deleted file - J:\2017_09_17 Nara\Capture\01\CaptureOne\Settings100\_W0A0282.CR2.cos~RF239fc23.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0356.xmp~RF2449bec.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0356.xmp~RF2449bec.TMP~RF244ba42.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0356.xmp~RF2449bec.TMP~RF244ba42.TMP~RF244d6b3.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0356.xmp~RF2449bec.TMP~RF244ba42.TMP~RF244d6b3.TMP~RF244e9ed.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0356.xmp~RF2449bec.TMP~RF244ba42.TMP~RF244d6b3.TMP~RF244e9ed.TMP~RF244fd56.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0356.xmp~RF2449bec.TMP~RF244ba42.TMP~RF244d6b3.TMP~RF244e9ed.TMP~RF244fd56.TMP~RF245114b.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0356.xmp~RF2449bec.TMP~RF244ba42.TMP~RF244d6b3.TMP~RF244e9ed.TMP~RF244fd56.TMP~RF245114b.TMP~RF2452456.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0356.xmp~RF2449bec.TMP~RF244ba42.TMP~RF244d6b3.TMP~RF244e9ed.TMP~RF244fd56.TMP~RF245114b.TMP~RF2452456.TMP~RF24537a0.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0356.xmp~RF2449bec.TMP~RF244ba42.TMP~RF244d6b3.TMP~RF244e9ed.TMP~RF244fd56.TMP~RF245114b.TMP~RF2452456.TMP~RF24537a0.TMP~RF24547ad.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0356.xmp~RF2449bec.TMP~RF244ba42.TMP~RF244d6b3.TMP~RF244e9ed.TMP~RF244fd56.TMP~RF245114b.TMP~RF2452456.TMP~RF24537a0.TMP~RF24547ad.TMP~RF2455653.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0356.xmp~RF2449bec.TMP~RF244ba42.TMP~RF244d6b3.TMP~RF244e9ed.TMP~RF244fd56.TMP~RF245114b.TMP~RF2452456.TMP~RF24537a0.TMP~RF24547ad.TMP~RF2455653.TMP~RF24581f7.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0356.xmp~RF2449bec.TMP~RF244ba42.TMP~RF244d6b3.TMP~RF244e9ed.TMP~RF244fd56.TMP~RF245114b.TMP~RF2452456.TMP~RF24537a0.TMP~RF24547ad.TMP~RF2455653.TMP~RF24581f7.TMP~RF24598cb.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0356.xmp~RF2449bec.TMP~RF244ba42.TMP~RF244d6b3.TMP~RF244e9ed.TMP~RF244fd56.TMP~RF245114b.TMP~RF2452456.TMP~RF24537a0.TMP~RF24547ad.TMP~RF2455653.TMP~RF24581f7.TMP~RF24598cb.TMP~RF245ac91.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0361.xmp~RF243faca.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0372.xmp~RF2467ee5.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0372.xmp~RF2467ee5.TMP~RF24759f3.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0372.xmp~RF2467ee5.TMP~RF24759f3.TMP~RF249765b.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0372.xmp~RF2467ee5.TMP~RF24759f3.TMP~RF249765b.TMP~RF24986b6.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0372.xmp~RF2467ee5.TMP~RF24759f3.TMP~RF249765b.TMP~RF24986b6.TMP~RF249b623.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0372.xmp~RF2467ee5.TMP~RF24759f3.TMP~RF249765b.TMP~RF24986b6.TMP~RF249b623.TMP~RF249c5a4.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0372.xmp~RF2467ee5.TMP~RF24759f3.TMP~RF249765b.TMP~RF24986b6.TMP~RF249b623.TMP~RF249c5a4.TMP~RF249cda3.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0372.xmp~RF2467ee5.TMP~RF24759f3.TMP~RF249765b.TMP~RF24986b6.TMP~RF249b623.TMP~RF249c5a4.TMP~RF249cda3.TMP~RF249daf1.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0372.xmp~RF2467ee5.TMP~RF24759f3.TMP~RF249765b.TMP~RF24986b6.TMP~RF249b623.TMP~RF249c5a4.TMP~RF249cda3.TMP~RF249daf1.TMP~RF24ac2f0.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0372.xmp~RF2467ee5.TMP~RF24759f3.TMP~RF249765b.TMP~RF24986b6.TMP~RF249b623.TMP~RF249c5a4.TMP~RF249cda3.TMP~RF249daf1.TMP~RF24ac2f0.TMP~RF24ad203.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0372.xmp~RF2467ee5.TMP~RF24759f3.TMP~RF249765b.TMP~RF24986b6.TMP~RF249b623.TMP~RF249c5a4.TMP~RF249cda3.TMP~RF249daf1.TMP~RF24ac2f0.TMP~RF24ad203.TMP~RF24aee65.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\_W0A0372.xmp~RF2467ee5.TMP~RF24759f3.TMP~RF249765b.TMP~RF24986b6.TMP~RF249b623.TMP~RF249c5a4.TMP~RF249cda3.TMP~RF249daf1.TMP~RF24ac2f0.TMP~RF24ad203.TMP~RF24aee65.TMP~RF24b8c0c.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0356.CR2.cos~RF2449bec.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0356.CR2.cos~RF2449bec.TMP~RF244ba42.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0356.CR2.cos~RF2449bec.TMP~RF244ba42.TMP~RF244d6b3.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0356.CR2.cos~RF2449bec.TMP~RF244ba42.TMP~RF244d6b3.TMP~RF244e9ed.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0356.CR2.cos~RF2449bec.TMP~RF244ba42.TMP~RF244d6b3.TMP~RF244e9ed.TMP~RF244fd56.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0356.CR2.cos~RF2449bec.TMP~RF244ba42.TMP~RF244d6b3.TMP~RF244e9ed.TMP~RF244fd56.TMP~RF245114b.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0356.CR2.cos~RF2449bec.TMP~RF244ba42.TMP~RF244d6b3.TMP~RF244e9ed.TMP~RF244fd56.TMP~RF245114b.TMP~RF24537a0.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0356.CR2.cos~RF2449bec.TMP~RF244ba42.TMP~RF244d6b3.TMP~RF244e9ed.TMP~RF244fd56.TMP~RF245114b.TMP~RF24537a0.TMP~RF24598cb.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0356.CR2.cos~RF2449bec.TMP~RF244ba42.TMP~RF244d6b3.TMP~RF244e9ed.TMP~RF244fd56.TMP~RF245114b.TMP~RF24537a0.TMP~RF24598cb.TMP~RF245ac91.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0356.CR2.cos~RF2449bec.TMP~RF244ba42.TMP~RF244d6b3.TMP~RF244e9ed.TMP~RF244fd56.TMP~RF245114b.TMP~RF24537a0.TMP~RF24598cb.TMP~RF245ac91.TMP~RF245c029.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0361.CR2.cos~RF243faca.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0372.CR2.cos~RF2467ee5.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0372.CR2.cos~RF2467ee5.TMP~RF24759f3.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0372.CR2.cos~RF2467ee5.TMP~RF24759f3.TMP~RF249766b.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0372.CR2.cos~RF2467ee5.TMP~RF24759f3.TMP~RF249766b.TMP~RF24986b6.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0372.CR2.cos~RF2467ee5.TMP~RF24759f3.TMP~RF249766b.TMP~RF24986b6.TMP~RF249b633.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0372.CR2.cos~RF2467ee5.TMP~RF24759f3.TMP~RF249766b.TMP~RF24986b6.TMP~RF249b633.TMP~RF249c5b3.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0372.CR2.cos~RF2467ee5.TMP~RF24759f3.TMP~RF249766b.TMP~RF24986b6.TMP~RF249b633.TMP~RF249c5b3.TMP~RF249cdb2.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0372.CR2.cos~RF2467ee5.TMP~RF24759f3.TMP~RF249766b.TMP~RF24986b6.TMP~RF249b633.TMP~RF249c5b3.TMP~RF249cdb2.TMP~RF249db01.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0372.CR2.cos~RF2467ee5.TMP~RF24759f3.TMP~RF249766b.TMP~RF24986b6.TMP~RF249b633.TMP~RF249c5b3.TMP~RF249cdb2.TMP~RF249db01.TMP~RF24ad213.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0372.CR2.cos~RF2467ee5.TMP~RF24759f3.TMP~RF249766b.TMP~RF24986b6.TMP~RF249b633.TMP~RF249c5b3.TMP~RF249cdb2.TMP~RF249db01.TMP~RF24ad213.TMP~RF24aee65.TMP
Deleted file - J:\2017_09_17 Nara\Capture\03\CaptureOne\Settings100\_W0A0372.CR2.cos~RF2467ee5.TMP~RF24759f3.TMP~RF249766b.TMP~RF24986b6.TMP~RF249b633.TMP~RF249c5b3.TMP~RF249cdb2.TMP~RF249db01.TMP~RF24ad213.TMP~RF24aee65.TMP~RF24b8c1c.TMP
Deleted file - J:\2017_09_17 Nara\Capture\09\_W0A0655.xmp~RF2615939.TMP
Deleted file - J:\2017_09_17 Nara\Capture\09\_W0A0655.xmp~RF2615939.TMP~RF2617944.TMP
Deleted file - J:\2017_09_17 Nara\Capture\09\_W0A0655.xmp~RF2615939.TMP~RF2617944.TMP~RF2621bed.TMP
Deleted file - J:\2017_09_17 Nara\Capture\09\CaptureOne\Settings100\_W0A0728.CR2.cos~RF2607830.TMP
Deleted file - J:\2017_09_17 Nara\Capture\10\_W0A0799.xmp~RF2637294.TMP
Deleted file - J:\2017_09_17 Nara\Capture\10\CaptureOne\Settings100\_W0A0799.CR2.cos~RF2637294.TMP
Deleted file - J:\2017_09_17 Nara\Capture\12\CaptureOne\Settings100\_W0A0879.CR2.cos~RF2683f75.TMP
Deleted file - J:\2017_09_17 Nara\Capture\12\CaptureOne\Settings100\_W0A0887.CR2.cos~RF515e334.TMP
Deleted file - J:\2017_09_17 Nara\Capture\12\CaptureOne\Settings100\_W0A0895.CR2.cos~RF2762be9.TMP
Deleted file - J:\2017_09_17 Nara\Capture\12\CaptureOne\Settings100\_W0A0895.CR2.cos~RF2762be9.TMP~RF277c602.TMP
Deleted file - J:\2017_09_17 Nara\Capture\12\CaptureOne\Settings100\_W0A0895.CR2.cos~RF2762be9.TMP~RF277c602.TMP~RF2890606.TMP
Deleted file - J:\2017_09_17 Nara\Trash\_W0A0308.xmp~RF243a6a0.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0224.CR2.cos~RF24c7294.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0250.CR2.cos~RF246762b.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0254.CR2.cos~RF244be59.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0257.CR2.cos~RF2568ce1.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0257.CR2.cos~RF2568ce1.TMP~RF26179c1.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0270.CR2.cos~RF2585703.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0270.CR2.cos~RF2585703.TMP~RF2604a59.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0280.CR2.cos~RF263d47a.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0298.CR2.cos~RF25664e7.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0299.CR2.cos~RF260f81e.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0300.CR2.cos~RF243a48c.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0303.CR2.cos~RF2458daf.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0308.CR2.cos~RF243a6af.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0308.CR2.cos~RF243a6af.TMP~RF2577405.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0373.CR2.cos~RF2574c2a.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0373.CR2.cos~RF2574c2a.TMP~RF260a589.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0462.CR2.cos~RF27637a1.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0482.CR2.cos~RF260edbe.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0484.CR2.cos~RF256e7c3.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0484.CR2.cos~RF256e7c3.TMP~RF2611645.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0484.CR2.cos~RF256e7c3.TMP~RF2611645.TMP~RF2613e10.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0485.CR2.cos~RF2573806.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0485.CR2.cos~RF2573806.TMP~RF285fa5c.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0488.CR2.cos~RF2565130.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0491.CR2.cos~RF2570ffc.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0502.CR2.cos~RF25682b0.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0508.CR2.cos~RF256fc26.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0508.CR2.cos~RF256fc26.TMP~RF512810d.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0513.CR2.cos~RF2628e2f.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0513.CR2.cos~RF2628e2f.TMP~RF2686acb.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0520.CR2.cos~RF2615234.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0551.CR2.cos~RF260547b.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0552.CR2.cos~RF2569703.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0558.CR2.cos~RF256dd72.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0580.CR2.cos~RF256c94e.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0580.CR2.cos~RF256c94e.TMP~RF262a244.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0587.CR2.cos~RF26183c4.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0606.CR2.cos~RF2627bb1.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0613.CR2.cos~RF255ee11.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0613.CR2.cos~RF255ee11.TMP~RF256b568.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0614.CR2.cos~RF2571a2d.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0614.CR2.cos~RF2571a2d.TMP~RF2614832.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0614.CR2.cos~RF2571a2d.TMP~RF2614832.TMP~RF277da36.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0619.CR2.cos~RF257d83d.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0619.CR2.cos~RF257d83d.TMP~RF2629851.TMP
Deleted file - J:\2017_09_17 Nara\Trash\CaptureOne\Settings100\_W0A0680.CR2.cos~RF2610c13.TMP0 -
[quote="SFA" wrote:
[quote="NNN635509507115078337" wrote:
Same issue here (adjustments not saving often, but not always; mess of temporary files), cropped up right after installing the Fall Creators Update, now that I've gotten that hint. Please look into this, PhaseOne, this can't be that hard to reproduce seeing as several users (and I'm sure that's just the tip of the iceberg) are complaining.
Have you created a Support Case?
Did so now. Thumbs crossed…0 -
same issue here with the same setup (windows 10 creators fall edition + latest updates) and c1 10.2. It seems that all changes are saved into TMP files, but not copied into respective adjustment .cos file. From NNN635796750580192506 example above please shut down C1, check the latest change date of tmp file and rename that files it into respective .cos file, your adjustnemts should be restored. For instance if "_COP3673.NEF.cos~RF178b9c5.TMP~RF1792011.TMP~RF17931f3.TMP" is the latest file for all files starting with "_COP3673.NEF.cos", you should rename that "_COP3673.NEF.cos~RF178b9c5.TMP~RF1792011.TMP~RF17931f3.TMP" file into "_COP3673.NEF.cos"; start C1 and probably regenerate preview for that file to sync preview and adjustments. 0
Please sign in to leave a comment.
Comments
72 comments