Catalogue regularly crashes

Comments

3 comments

  • Paul Steunebrink
    Start Capture One with the Alt-key pressed to prevent it from loading a session or catalog. Next, verify your catalog that crashes.

    I understand the images for your catalog are on the Synology NAS, but is the catalog on your internal disk or on NAS too? I prefer to have it on the internal disk to prevent latency issues from the network connection.
    0
    Comment actions Permalink
  • SFA
    I have a Windows 7 PC and a Synology NAS. The NAS connection is via Wi-Fi network.

    I mostly use sessions but have two or three catalogues I sometimes use for testing.

    I often leave a session or sessions and catalog open for days or weeks at a time. Often the system will hibernate during this period but usually everything will start up again where I left it on leaving hibernation.

    However there are some situations with the NAS when it too hibernates, not always connected to the PC hibernating, and does not restart when an application neds data from its drives. This, working with a catalogue but not really seen with a session as far as I recall, can lead to a crash as C1 times out. Or at least that is how it seems.

    I can work around it by forcing the NAS to come out of hibernation using Windows Explorer before attempting and Ci catalogue activity that requires access to the NAS. Once it has "woken up" things seems to work OK, just not as fast as a local (to the PC) drive.

    Could you be seeing something similar?


    Grant
    0
    Comment actions Permalink
  • Gert Klaus
    [quote="Paul_Steunebrink" wrote:
    Start Capture One with the Alt-key pressed to prevent it from loading a session or catalog. Next, verify your catalog that crashes.

    I understand the images for your catalog are on the Synology NAS, but is the catalog on your internal disk or on NAS too? I prefer to have it on the internal disk to prevent latency issues from the network connection.


    Bedankt Paul for your reply!
    I´ll try your way, though I'm not understanding, why a software can completely crashes the computer. The C1 window stays until I force quit the MAC. And obviously I'm not the only one, who experiences this problem.
    I think ill stop trying and searching for a solution and go on using "Media Pro"
    Nobody understands why they bought this pretty cool software and then doing their own solution...
    0
    Comment actions Permalink

Please sign in to leave a comment.