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. ⚠️

Warning: 4.5 corrupted previously good files

Matt 1
We have been using the new 4.5 since it came out, and experiencing all of the same extremely annoying yet manageable bugs that others have already documented. Today, however, 2/3 of the way through the day it crashed hard, and upon restarting the computer, discovered to our horror that more than half of the files in the session had been destroyed by the program. All of the files were perfectly fine prior to the incident.

Quite terrifying that the program is capable not only of corrupting incoming files, but also of destroying the other files in the session.

I have no anger left to vent towards Phase for this atrocious product; the purpose of this post is to warn others to back up the session files periodically during the day--don't wait until the end of the day!

good luck to all with this POS program,
matt
0

Comments

5 comments

Date Votes
  • Henry1
    That is bad, really bad. I feel your pain.

    Just out of curiosity, is that V4.5 or V4.5.2?
    0
  • Paul Steunebrink
    And in addition to Henry's sympathy: are you working tethered?
    0
  • Joachim Neumann
    Hello,

    I am working with version 4.5 for Windows and two times I had some destroyed files. I am not working tethered.
    I had no idea where this destruction did come from. Now it seems so as if CO 4.5 did that.
    I had some luck because I did save the files before.
    0
  • derek hillier
    Sorry about the crash but this is a Mac forum you should post in the pc part


    Derek
    0
  • Jonathan Gilbert
    Matt,

    If you think Capture One has corrupted files, please create a support case and provide us with all the details... What version of Capture One is use, what were you doing when the crash occurred? How were the files captured? what do the corrupted files look like? Where the corrupted files moved at all when working in Capture One? etc...

    For the record Capture One itself has never had the ability to corrupt files. This is because Raw files are handled as read-only. All cases related to 0kb files after a crash were due to the fact that the Mac OS was writing data to Cache rather than to the hard disk. In 4.5.2 we made a provision for this that specifically requires the OS to right to disk immediately and return verification that the file has been written to disk so that files are not lost during a crash.
    0

Post is closed for comments.