Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Program loosing adjustments!

Roman Makhmutov
This is a very serious problem.

I have 4 folders:
00 Unnecessary files
01 Wedding preparations
02 Wedding ceremony
03 Wedding portraits
04 Wedding portraits on the walk

Today, 8.nov.2011 i've adjustem all of them, one-by-one and sended them to batch.

All of them have been processed correctly without problems.

Then i've closed program, restart computer, and opened these folders again one-by-one.

01 - No adjustments
02 - No adjustments
03 - Half of the adjustments have been erased
04 - Everything is OK
00 - Adjustments have been erased for earlier files

Then i've checked .cos files in the folders.

.cos files without adjustments have been modified at 4.nov.2011, i suppose it was date when i previously opened them.

Lucky me i'm already converted these raws to jpgs!

***

This has happened with me SECOND TIME. First time it happened when i'm sended files to batch, them deleted them and restarted program.

This looks likes very serious problem for me. How can i use program if it can ruin my job in just one moment?
0

Comments

26 comments

Date Votes
  • Coach2
    Did you happen to move the files into folders after processing them? Or, did you rename the files after processing? Moving or renaming the files outside of C1 will not copy their adjustment files to the proper location.
    0
  • Roman Makhmutov
    I just restarted the program, nothing else.
    0
  • Permanently deleted user
    Happens to me all the time. Support says it is my computer not their software. They also say it is just me this is happening to.
    0
  • Coach2
    I think it would help if dan122 and Roman8 were to compare notes about system configurations and workflows then both of them should file a support case. In the mean time, I would back up the .cos files before exiting the program. I certainly wouldn't just keep using Capture One if it were happening "all the time." Maybe using a previous version until a solution is found. You also might want to create a new session file (delete or rename *.col50 in My Documents, My Pictures) to start up with a clean C1 configuration. This is an old fix for many C1 ailments.
    0
  • Paul Steunebrink
    Gents, are we using internal disks or external/additional disks as well?
    0
  • Keith Reeder
    [quote="dan122" wrote:
    They also say it is just me this is happening to.

    Well if nobody else has raised a support case about it, then technically they're right.
    0
  • Roman Makhmutov
    This failure happens on Windows 7 Ultimate, 8GB Ram, Core 2 Duo 1.8 @ 1.8. I have internal SATA disk (second failure files was here) and external USB disk (first time this had happened here).

    I suppose this starts after installation of lates 6.3.3 version.

    Sometimes i've recieving "database error" message but in never caused such problems before.

    Now i will use these advices:

    1. Create new session file
    2. Always backup all modified cos files after adjustments
    3. Immidiatly convert RAW to JPG after done with current folder
    0
  • Keith Reeder
    Here's some more advice, Roman.

    Raise a support case.
    0
  • Permanently deleted user
    Been happening for a while, support has been less than helpful. The unfortunate part for me is that I have been using C1 since ver 1 so my workflow is built around C1. Have tried other software and if I could find the same workflow and quality I would not be using this software.

    I have been having this issue since 9/10. Here is their answer:

    Dan,
    I apoligize for your disappointment and if we could be of further assistance we would not hesitate. However, in your specific case we have described behavior which cannot be verified, reproduced or evaluated. Again, I apologize that this unique issue is not something we can assist with. We have worked hard to try and identify the issue but without being able to see it occur or have log information showing it occuring it is impossible to account for. We certainly care about the issue and would be happy to help you resolve the issue but as this is the only report of this occuring it is seen as an isolated incident on your system. Again, I cannot apologize enough for your trouble if you can think of anything we havn't tried yet to help you identify and resolve your issue we would would welcome the suggestion, currently we are just plum out of ideas to fix this anomaly.

    Kind Regards,
    Phase One Support

    So please put in a support case, maybe it will help but I doubt it.
    0
  • Jim MSP
    [quote="dan122" wrote:
    Been happening for a while, support has been less than helpful. ...

    I have been having this issue since 9/10.
    .


    Dan - very strange.
    Could you detail your pc and software for us?
    Where (drive) is your CO program resident?
    What drive are your photos on?

    If you drop everything (program & photos) back to the C drive, does this problem still exist?
    0
  • Permanently deleted user
    I am running Win 7 Enterprise 64 bit, i7 2.8GHz processor with 8GB RAM. Running as administrator so should not be any permission issues.

    Everything runs off my C drive, raws are stored and processed there. C1 is installed in default location.

    I have actually seen this on more than one PC as I upgraded computers last year. I personally believe it is either a memory leak issue or just bad programming. I normally do not see it if I simply open a folder of images, process them and close C1. When it seems more likely to happen is when I am working on a folder of images then send them to the prcessing queue then go open another folder of images work on them, send them to process queue etc. Somedays I might process 1,500-2,000 images and that is when I see this happen more.

    Phase One looked at a log file and said "We don't see anything, this can't happen, must be your computer". I pointed out that I have seen it on multiple PCs then they said, sorry we can't help.
    0
  • Jim MSP
    [quote="dan122" wrote:
    ...
    .... personally believe it is either a memory leak issue .... I normally do not see it if I simply open a folder of images, process them and close C1.
    When it seems more likely to happen is when I am working on a folder of images then send them to the processing queue then go open another folder of images work on them, send them to process queue etc. Somedays I might process 1,500-2,000 images and that is when I see this happen more.
    ......


    I certainly cannot relate to such a large number of files processed at once.

    However, I agree with your memory leak assessment.
    When v6.0 first came out, I had a number of crashes while processing a much smaller number of files (100-200) at a time.
    I continuously monitored the memory used by CO with Win Task manager, and once it reached about 1.2G, I quit CO and restarted. This avoided the crashes I'd get when the memory got closer to 1.3G .

    The newest version for me seems to plateau out about 1.4G on a few hundred images, and remain stable. But this is without sending them into the process que.

    I'd be curious to see what Task Manager says about your memory usage when you have so many images stacked up for processing.
    0
  • Permanently deleted user
    It usually hangs out around 2GB or RAM usage. C1 gets to a point where it just uses memory then it sits there, don't think it is really changed much due to volume as it only processes one at a time. The queue is just a list of files so it not using much memory.
    0
  • Jim MSP
    [quote="dan122" wrote:
    It usually hangs out around 2GB or RAM usage. C1 gets to a point where it just uses memory then it sits there, don't think it is really changed much due to volume as it only processes one at a time. The queue is just a list of files so it not using much memory.

    It is a bit more than that, including file location. You don't by any chance try to look at some of the processed files (in their new folder?) before it is done processing all the files in the queue?
    If so, CO can probably process a file faster than it generates a new proxie when it comes upon a new file. My system seems to take for ever in proxie generation for my 60D files.
    You might get getting some conflict in the proxie handler when it is trying to read and write at the same time.
    0
  • Permanently deleted user
    The files all process correctly, that isn't the issue. The problem is when you go back in to the folder and all your corrections are gone.

    If C1 works correctly when you adjust a file all changes are supposed to be saved when you change off that image to the next one. THat is why P1 claims it isn't their software since it is supposed to work that way. Problem is for some reason it stops saving adjustments.

    Very possible that there is some bad code that is executed when you open a different folder of images, this is actually where I think the problem is. This is a problem for me when I have to process 6-8 folders of images in one day, the program is just not reliable enough.

    The other issue, to me, is that if there is a problem writing adjustments to the file there should be an error generated but C1, if it sees the error does nothting with it and igmores it. That's bad programming.
    0
  • Coach2
    [quote="dan122" wrote:
    This is a problem for me when I have to process 6-8 folders of images in one day, the program is just not reliable enough.


    I find that I have less problems if I only work on one folder at a time. After processing one folder, I will click on an empty folder, "parking" there so when I restart the program doesn't start generating any proxies. I then exit the program. When I restart and begin working on a new folder the program is working fresh.

    It almost sounds like there is a write-delay problem going on with your files. There are settings for your hard drive to turn off write-delay but it may slow your system down a bit.
    0
  • Drew Altdo
    Coach,
    Are you saying that you have the same issue as described but Dan?
    Dan has created a support case with us but we cannot find any reason for the behavior he has reported. It would be of great help to us, and Dan, if you could create a support case and get us specifics of your issue if it is the same as what Dan has reported in this thread.
    0
  • Coach2
    No, I'm not having the same problem as Dan. I'm just offering general suggestions for him based on experience with C1 as well as other programs. I occasionally will have a problem where the program tells me I need to restart, but I've minimized those problems by restarting with each new folder, one at a time.
    0
  • Roman Makhmutov
    This weird thing is just happened to me again. And looks likes i've found the core of the problem.

    1st time i've opened RAW files on my Mac, and proxies was generated on Mac. All of them marked as "hidden files".

    Then i've opening these files at Windows, and made an adjustments, but they are never saving after program re-start.

    Then i've unmarked settings files from "hidden".

    Problem was solved.

    Solution: make sure your settings files are NOT hidden. They ARE hidden if you firts time open them on Mac.
    0
  • Paul Steunebrink
    Great you found the cause.

    Although I frequently swap image folders around from Mac to Win and back to Mac, I did not had this issue. I know however, that the Mac 'dot' files are hidden by default on Windows. These are not the real files but contain information for displaying them on the Mac. When you have the Windows system to show hidden files, applications might see them for real.

    Either delete the ._ dot files on Windows after copy from Mac or set the Windows Explorer to not showing hidden files.

    There seems to be a Mac tweak for not copying the 'dot' files to Windows through a network share, but I was not successful in implementing this in the past.
    0
  • Drew Altdo
    [quote="Roman8" wrote:
    ...looks likes i've found the core of the problem.
    1st time i've opened RAW files on my Mac, and proxies was generated on Mac. All of them marked as "hidden files"...


    Although I understand the steps you have taken, this would not relate to settings/adjustments as the 'Proxie' files do not carry any of this information. The settings and adjustments are saved in the 'COS' (Capture One Settings) files.
    0
  • Roman Makhmutov
    By "proxies" i mean .cos file as well.
    0
  • Drew Altdo
    [quote="Roman8" wrote:
    By "proxies" i mean .cos file as well.


    OK, just to be clear the .COS files are NOT Proxie files. There is a separate .COP file which is referred to as the Proxie (Capture One Proxie).
    0
  • NN126882UL6
    Every time i'm opening RAW files on Mac, settings files became "hidden".

    Then i should "reveal" them on Windows (unmark "hidden" attribute) to be sure problem will not cause again.
    0
  • Michael4711
    I'm getting this problem as well. Has there been any new data on this issue or possible solutions.

    This just happened to me a second time today. The first time it was a seemingly random loss of settings - maybe retained about 20% of my settings - and today I think it only saved the settings for a dozen or so at the beginning out of hundreds. Unlike the original poster, I didn't actually convert to JPEG before restarting the program so I just lost hours of RAW edits.

    I checked my settings files and none of them are hidden (I didn't move any of them between computers). However, when I sorted them in Windows (Windows 7 x64) by date modified, the newest ones are all the original file names (i.e. IMG_0323) and the oldest ones are the new batch-renamed file names (i.e. EMCH-001). It almost seems like the settings got applied to settings files under old file names even though they were edited after the batch rename took place. However, the mask files are using the new file names and are some of the newer files.

    I'm going to try restoring the RAW files from a backup containing the original file names and see if it will read any of the settings files...

    I hope this problem gets solved soon. For the next project I'm going to try batch renaming then restarting the program before I apply any editing to see if that helps.

    Michael
    0
  • Michael4711
    OK, it looks like I fixed my problem. I was right about my theory of how it was applying the edit settings to the old file names. I fixed the problem by loading all of the original files onto my system with the old file names, made a new session for this directory and copied the COS files from the old project into the Settings50 directory of the new session and Capture One loaded the settings just fine.

    I'm pretty sure I renamed the files before I did the RAW edits first time, but either way, it's either not copying/renaming the settings files during the batch rename, or it's not changing to the new naming convention for the COS files when I edit directly after a batch rename.

    I think my best bet for now will be to rename the files in another program before I load them into Capture One the first time until this issue is addressed.

    I hope this helps others who have this problem and I especially hope it helps Phase One apply a patch to prevent this from happening in the future.

    Michael
    0

Post is closed for comments.