Skip to main content

Working version any time soon ?

Comments

5 comments

  • John Friend
    Top Commenter

    As this is not an issue for most customers, the mechanism to get help is for you to file a support request with log files and engage with them 1 on 1 on your particular issue.

    1
  • SFA
    Top Commenter

    Nicolas, 

    I once had a problem like that with a newly created session. From memory it was either V6 or V7 of C1.

    The session would regualrly crash about every 10th or 11th image as I worked through about 3000 images.

    Eventually I spotted an image with a slightly imperfect preview presentation. The Preview would not refresh. I deleted the file and re-imported it.  I good preview appeared and the crashing stopped.

    I think what had happened was that somehow, somewhere in the process of writing the file fragments to disk, a fragment had been allocated a bad numeric "name". I found a name of a fragment "file" related to that particular image that ended with a lot of zeros.

    There was potential for that file to be incorrectly selected for use with other images. If the data in the file happened to fall in a place where the system was expecting numeric data for a data field but was presented with alpha data (or, potentially, vice versa in some cases) the system would crash. There would be no practical way to stop it.

    I suspect that the original error was something to do with Windows (7 at the time as I recall) and was simply a glitch. The problem never recurred.

    If it might be the case that you have something similar happening, there is no way a distant support desk would be likely to deliver a "fix" other than by luck or by having complete access to the problem system and allocating a huge amount of time trying guess what might be going on and creating processes or searches to test their theories.

    I was lucky, in some ways, in that I eventually reached the image with the problem preview and stumbled across a solution. The same sort of data issue could exist somewhere in the data fragment files that would not provide any visual evidence at all.

    I'm not trying to say that the problem I had is in any way the same as the problem that you have. Just that if you do have a similar type of deep technical problem waiting for a fix is unlikely to deliver a satisfactory result. Some other approach may be better.

    If you are working with a catalog - are all catalogs/sessions affected?

    If so it certainly a very different problem compared to mine BUT might simply be the same sort of thing in a different part of the system's files.

    0
  • Nicolas Det

    Thanks for your tips.

     

    Unfortunately, it does not match my issue. The issue happens on 3 differents machines, on different sessions and catalogs. Even on local SSD.

    "As this is not an issue for most customers, the mechanism to get help is for you to file a support request with log files and engage with them 1 on 1 on your particular issue."

    Already done, they logged the issue.

    However, even if only 5% are affected, it would maes 5% less income...

    Regards

    0
  • Ian Wilson
    Moderator
    Top Commenter

    Nicolas Det - you haven't said whether you are on Mac or Windows, and which version of MacOS or of Windows you are using. Have you checked that your OS version is supported for your version of Capture One?

    Ian

    0
  • SFA
    Top Commenter

    Nicolas, I don't recall whether you are a Mac or Windows user.

    Clearly if the issue cannot be related to a specific catalog or sessions or machine it may well be unrelated to a specific file (although in theory that is not an impossibility if you have common files and images copied across multiple sessions, catalogs and devices.)

    Do you also share other C1 files across the machines. Or, perhaps, run other software that might sometimes interfere somehow with how C1 runs?

    Anything that is normally stored in userconfig or plist files might well be shared across several machines and the particular data involved (assuming there might be some sort of "data corruption" issue in play) would therefore come to exist on all machines.

    Likewise resources like Keyword libraries, although the nature of any file anomaly would probably need to be something different to my "data type" example.

    These are just examples. There are very likely many many more possibilities.

    All that I can suggest in that respect is that one looks for commonality to connect the problems as they arise.

    Especially if it is the sort of problem that is very rare.

     

    Where did you get the "only 5% affected" number from?

     

    0

Please sign in to leave a comment.