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

Session wrongly changes .cos files modified date (although no edits were made)

BeO
  • Edited
Top Commenter

Can someone please confirm this new bug?

 

Steps to reproduce:
1. WIth an open session navigate in the library tool to a system folder where image files are located and show the imagers in the C1 Browser
2. close C1
3. open Windows Explorer and locate the directory CaptureOne/Settings15.3
4. note the Date Modified in Explorer for the .cos files
5. start C1 again, navigate to the folder as in step1
6. note the Date Modified in Explorer for the .cos filesn has changed.

The impact of this bug is quite severe, because all backup solutions or synchronize between computers solutions for session edits (the .cos files) are mislead.

It could be that an old edit on computer 1 gets a newer timestanp (date modified) than a newer edit on computer 2, and subsequently the user would overwrite the newer adjustement file with the older one, it he attempts to synchronize image adjustments between the computers.

Windows10, C1 version 15.4.2.10 (and 15.4.1.19).
It did work correctly with 15.1 / 15.2

0

Comments

2 comments

Date Votes
  • BeO
    Top Commenter

    C1 support quickly provided me a link to 15.2.1.9 for Windows and I can confirm that this bug which was introduced in 15.3 or 15.4 does not exist.

    The bug might also still exist in version 16, which I did not test.

    0
  • BeO
    Top Commenter

    Meanwhile I have some refined information for this defect.

    In 15.4, it seems that .cos files for images in the Capture folder of the specific session are not affected (and presumably the selects folder and trash), but any other system folder.

    And even in 15.2, if you create a new session and browse to a system folder with images (which already contain CaptureOne folder), the .cos files Date Modified is updated. This occurs only once per session (whereas in 15.4 it occurs every time with all sessions, existing or new, after a restart of C1). 

    I actually consider even the 15.2 behaviour as a defect, a session should never ever change the file modified date if it does not change the file (its content). And the content is not changed, I double checked this.

    Hard to say if this caused any loss of edits, in the case I edited images on more than one computer in between syncronzisation days.

    0

Post is closed for comments.