Zum Hauptinhalt gehen

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

CO don't crash but won't work opening specific folders

frieri
I can't understand why CO 8.1 stop working when I try to open specific folders, always the same.
It loads 3 or 4 images and after few seconds it freezes and I have to manually force it down.
Could anyone suggest a solution?
Many thanks in advance.

This is the hardware and software I'm using:
MacBook Air 13" (mid 2011)
OS X Yosemite 10.10.1
1,7 GHz Intel Core i5
4 GB 144 MHz DDR3
Intel HD Graphics 3000 384 MB
0

Kommentare

8 Kommentare

Datum Stimmen
  • SFA
    Are you using sessions or catalogues?

    If Catalog have you tried running the repair process?

    If Sessions does this happen with a new session?

    If you have not already tried a new session to read the folders it may be useful to do so. I can't be sure that it will work but it would mostly eliminate the possibility that there is a problem with the session's internal file references to the files in those folders.

    Also. Do the folders have any unusual files in them that C1 might not be able to work with?

    The answers to these questions may help to work out what is going on.

    HTH.


    Grant
    0
  • frieri
    Hi Grant, thank you for your answer.

    [quote="SFA" wrote:
    Are you using sessions or catalogues?

    No sessions or catalogues; I edit my image files from the CO Library.

    [quote="SFA" wrote:
    Do the folders have any unusual files in them that C1 might not be able to work with?

    No, only DNG Raw files.
    0
  • Keith Reeder
    [quote="frieri" wrote:
    No sessions or catalogues; I edit my image files from the CO Library.

    So in fact you're probably using the "default" session then, Roberto. You must use either a session or a catalogue - that's how Capture One works - but using the default session is "invisible" in practical terms.

    I wonder if the problem is a corrupt image file? The fact that it's always failing at more or less the same point suggests that it's a particular file that's causing the problem.
    0
  • frieri
    [quote="Keith Reeder" wrote:

    So in fact you're probably using the "default" session then, Roberto...
    I wonder if the problem is a corrupt image file? The fact that it's always failing at more or less the same point suggests that it's a particular file that's causing the problem.

    Well, I'we already tried to rename or delete or move the files and the CO directories without result.
    0
  • SFA
    Roberto,

    Try a new Session. Just create a new one - give it any name you like - and then using the library explorer, go to a folder that gives problems and try to read the files in it to see if it gives the same result that you usually get - CO hanging.


    As a second test using the new session (or even a third session to keep things "clean" for testing) try to Import the images in a problem folder and see what happens to the import process.

    Have any of the DNG files been edited using other software?

    If the files are direct from a camera it might be useful to know which type of camera if the problem continues.



    HTH.


    Grant
    0
  • Paul Steunebrink
    As suggested, create a new session and browse to the folder in your Library tool. Using the same session for a longer period - typical for users who say they don't use sessions - are prone for this kind of errors.

    Another tip is to repair permissions with your OSX Disk Utility tool.
    0
  • frieri
    Solved!

    [quote="SFA" wrote:
    Roberto, try a new Session. Just create a new one ...

    Thank you very much Grant for your help.
    As you suggested me, I created a new CO session, which works perfectly with all the folders in my library.
    So I replaced the old, evidently corrupted, .cosessiondb file with the new one.

    [quote="Paul_Steunebrink" wrote:
    ...Using the same session for a longer period - typical for users who say they don't use sessions - are prone for this kind of errors. Another tip is to repair permissions with your OSX Disk Utility tool.

    Thank you Paul for your confirmation.
    I've executed the permissions repair yesterday, but the problem persist.
    0
  • SFA
    Hi Roberto,

    I use Windows not Mac but just once I have seen a similar problem. Somehow an internal reference to a single edit file had become corrupt and that resulted in some very strange effects but something similar to what was happening for you.

    By chance I noticed a corrupt thumbnail which would not repair when recreated. I deleted the edit file for that file and all was good. I made a new edit and all was still good. So it was just something that happens in computers from time to time. Or so it seemed.

    That was about 2 years ago using V7. I have not seen such a problem since and I have tried several times to recreate the problem by doing things I might have been doing around the time it first occurred.

    I think you can be confident that you are unlikely to see the problem again any time soon.


    Grant
    0

Post ist für Kommentare geschlossen.