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

Editing changes not saved upon exiting C1

Charles O'Hara
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.
0

Comments

72 comments

Date Votes
  • CSwinton
    [quote="SFA" wrote:
    [quote="CSwinton" wrote:
    [quote="SFA" wrote:

    ...
    It's beta in terms of it being a developer release (to be used with caution) not an end user release - unless you are an end user masquerading as a developer to get the latest and greatest as early as possible.
    ...
    Grant


    My Windows machine automatically updated to 1709 this past week as part of regular updates. I did not run off to get the "latest and greatest". As far as I can tell, it began a staged public roll-out as of 10/17.


    Did you have the previous Creators Update installed?


    If I did it wasn't intentional.. 😂
    0
  • SFA
    [quote="CSwinton" wrote:
    [quote="SFA" wrote:
    [quote="CSwinton" wrote:


    My Windows machine automatically updated to 1709 this past week as part of regular updates. I did not run off to get the "latest and greatest". As far as I can tell, it began a staged public roll-out as of 10/17.


    Did you have the previous Creators Update installed?


    If I did it wasn't intentional.. 😂


    😂

    One of the reasons I have stayed with Win 7 is that it is now quite easy to avoid any undesirable updates!

    😉


    ETA: A short research session discovered this article.

    http://www.zdnet.com/article/windows-10 ... grade-now/

    Not necessarily authoritative of course but it has some interesting comments.

    The Previous Creators Update back in March/April had a theoretically restricted initial update target and started to roll out "the public" in July. So a 3 to 4 month gap whilst they bedded things down after the development beta's original finalisation.

    I have seen a headline that suggested the roll out is being pushed much sooner this time but of course that does not mean it is certain to be problem free (or even problem lite!)

    As the writer mentions at the top of the referenced article, businesses (and anyone else who has no desperate need to adopt a significant update so soon after release) would be wise to wait longer if given the opportunity.



    Grant
    0
  • xplatinum
    [quote="SFA" wrote:

    😂

    One of the reasons I have stayed with Win 7 is that it is now quite easy to avoid any undesirable updates!

    😉

    Windows 7 will refuse to install on the newer Kaby lake cpus. Same with 8.1.

    https://cdn.images.express.co.uk/img/dynamic/59/590x/secondary/Windows-10-Block-900122.jpg
    0
  • Charles O'Hara
    [quote="SFA" wrote:


    The Previous Creators Update back in March/April had a theoretically restricted initial update target and started to roll out "the public" in July. So a 3 to 4 month gap whilst they bedded things down after the development beta's original finalisation.

    I have seen a headline that suggested the roll out is being pushed much sooner this time but of course that does not mean it is certain to be problem free (or even problem lite!)

    As the writer mentions at the top of the referenced article, businesses (and anyone else who has no desperate need to adopt a significant update so soon after release) would be wise to wait longer if given the opportunity.

    Grant


    As far as I know, every mid-year update of Windows, once RTM (as compared to less stable beta or release candidates Insider builds), is to be pushed out at different intervals, depending on which update ring you apply to. Those settings can be manually changed in the Windows Update menu in Windows 10. The fastest "stable" ring is the "Semi-annual Channel (Targeted)", is not selected by default for evey user: only a few targeted users should fall into this category - this allows Microsoft to test some features and iron out bugs before the wider rollout a few months later on the slowest release ring, simply labeled "Semi-annual Channel". This is the recommended channel for businesses. This Fall Creator Update should follow those principles too, I guess.

    Here is a table showing the different release cycles for the stable builds (from an article I posted earlier on this thread).
    https://images2.imgbox.com/98/7f/j6Ugd0Qt_o.jpg
    0
  • xplatinum
    [quote="SFA" wrote:
    As the writer mentions at the top of the referenced article, businesses (and anyone else who has no desperate need to adopt a significant update so soon after release) would be wise to wait longer if given the opportunity.

    The only way to postpone it is to modify the default update settings to the ones below. That's how you stay off 1709 for a good while or until you decide you are ready. The vast majority will have the update pushed to them without being given a choice or an heads-up.

    https://i.imgur.com/FSMps0U.png
    0
  • SFA
    @xplatinum

    All interesting stuff, thanks.

    From what I can gather the "targeted" roll out for the Fall release seems (to watchers) to be somewhat less targeted than for the previous 6 monthly release and is being pushed somewhat faster.

    For a new machine I would expect to use Win 10 if that is what it comes with and I have no particular qualms (other than bugs and stability and potential lack of easy roll back - or any roll back) about taking Windows 10 now it has been around for a while.

    However if the releases have constraints that people may need to be aware of they constraints should be managed and the users advised. It should not be beyond the budget and abilities of a company like Microsoft (nor Apple who seem to have set the model trend in this area) to at least find a way to warn people about the sorts of issues that might rather than expecting (so it seems) their clients to work things out for themselves - through discussions like this. Interesting thought they are so many people waste so much time chasing something that really ought to be covered in the development planning risk assessments.

    And "fixed" one way or another.


    Grant
    0
  • Charles O'Hara
    [quote="xplatinum" wrote:
    [quote="SFA" wrote:
    As the writer mentions at the top of the referenced article, businesses (and anyone else who has no desperate need to adopt a significant update so soon after release) would be wise to wait longer if given the opportunity.

    The only way to postpone it is to modify the default update settings to the ones below. That's how you stay off 1709 for a good while or until you decide you are ready. The vast majority will have the update pushed to them without being given a choice or an heads-up.

    https://i.imgur.com/FSMps0U.png


    Yes, that is the correct settings menu. However, "Current Branch for Business" was renamed to "Semi-annual Channel" earlier this summer.

    This is all explained in this article:
    https://rcpmag.com/articles/2017/07/28/ ... model.aspx
    0
  • Christian Gruner
    This issue is now fixed with the introduction of Capture One 10.2.1: viewtopic.php?f=69&t=26920
    0
  • xplatinum
    [quote="NNN635796750580192506" wrote:
    Yes, that is the correct settings menu. However, "Current Branch for Business" was renamed to "Semi-annual Channel" earlier this summer.

    It has been renamed in 1709 😉
    0
  • WPNL
    [quote="Christian Gruner" wrote:
    This issue is now fixed with the introduction of Capture One 10.2.1: https://forum.phaseone.com/En/viewtopic ... 69&t=26920


    Thanks! 😊
    0
  • Permanently deleted user
    I have managed to confirm the already obvious and superseded point that the "Semi-annual Channel" does not allow for a downgrade to 'Current Branch for Business'; compared to me being fairly sure that 'Current Branch for Business' allowed for a few months ago in the previous update situation.

    Damn Microsoft. 😡
    0
  • PhaseoneUser13961
    Now that 10.2.1 has been released, what should be done with sessions worked on using 10.2.0 post Windows Fall Update?

    All the TMP files in the Settings100 folder are still there. Should these be deleted?

    I can reproduce a setting not saving in 10.2.1 for a session that was worked on using 10.2.0 post Windows Fall Update. My support case, started 22-10-2017, has been updated with the workflow and new logs.

    I have a session with 19 Canon CR2 files. A clone is made (F7). A crop is added to the clone. Capture One is closed and reopened. The clone with crop has saved. (This would not have saved with 10.2.0.) The clone is deleted. Capture One is closed and reopened. The deletion of the clone has not saved. Delete the clone again. Close and reopen Capture One. This time the clone deletion has saved. This is 100% reproducible for this session.

    A fresh session was created in 10.2.1 and the 19 CR2 files imported from the previous session's Capture folder without bringing the adjustments across. When initially repeating the workflow for this fresh session, the clone deletions had saved properly a number of times. Repeating the test later in the day, the did not have deletions saving. ❓

    Regards,

    MikeB
    0

Post is closed for comments.