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

Catalog Nightmare !!! Please help!

ettore.causa
I use Capture One 7.1.6 on Mac OSX 10.9.1
everything is being functioning really fine the last months but
suddenly yesterday CO won't manage to lunch and it crushed every single time i tried
so at the end I performed a full reset as read on the Phase One site (Trashing the app.Preference,etc)
Now CO lunches fine and opens a new empty catalog but as soon as i tried to open my old one it crushes again!!!!

I did verify this catalog multiple times and it says that its ok
Don't know what to do any longer

Thanks for your help

Ettore
0

Kommentare

8 Kommentare

Datum Stimmen
  • Steven48
    Have you tried repairing permissions through Disk Utility? Don't know if it has anything to do with it, but it couldn't hurt.
    0
  • ettore.causa
    yep,...i did ☹️
    0
  • mli20
    I too have serious problems with a catalog, a problem which I handed over to technical support 3 weeks ago. I have yet to receive anything meaningful from them as to reasons and resoultion. Mind you, I am running COP7 on Windows, but I believe the catalog design to be flawed, hence this heads-up.

    You might wish to see this thread;


    Not much by way of help, but you are not the only one with a catalog nightmare. Good luck.

    Cheers,
    Mogens
    0
  • Christian Gruner
    Please create a case with our Support team and attach the catalog.db file and the crash-report as well.

    By creating a support case it's much easier to help you reach a solution.

    Thanks!
    0
  • ettore.causa
    Thanks i just did!
    0
  • HansB
    2 weeks ago I ran into a similar, maybe the same, problem. It occurred after removing referenced images from a large (20GB) catalog. I coincidentally found a way to fix my problem.

    I trashed the catalog (to use a backup copy, losing all recent changes).
    The next day I pulled the catalog back into place from trash (to give it just one more chance).
    It worked!

    And this was somewhat reproducible. After removing some other images from the catalog the problem was back.
    Trashed it, pulled it back a little later (with C1 closed and re-opened - don't know if that matters), and it worked again. No further hiccups since then, but I didn't remove any other images from that catalog recently.

    I had the combination with C1 dying at startup, too. After reverting to the backup catalog I noticed that C1 loaded that catalog automatically at startup. So the defective catalog caused the C1 startup crashes.


    Best regards,
    Hans-B.
    0
  • mli20
    [quote="NNN635022403475152212" wrote:
    Thanks i just did!


    Please report back here of any progress with technical report on this issue.

    As I have written I too have problems with a COP7 catalog. After 14 days of silence technical support yesterday came back...to ask for a screenshot. Yes, it took them 14 days to come up with that idea.

    To me, for all practical purposes technical support, on catalog issues, is unacceptable. And mind you, it's not that an solution is not immediately available that annoys me, it's the silence.

    I wish you a different experience. Good luck.

    Cheers,
    Mogens
    0
  • NN206299UL
    I think this is where the treasured, but so often overlooked XMP files comes in to good use - if you are likely to be royally screwed by a corrupt catalogue then make sure you check the box in the preferences to enable sidecar XMP. Lightroom users know this as they do not have the luxury of all those folders containing the independent proxy and settings files. Lots of people don't like it because it looks 'messy' but there you go. The other advantage is that you can chuck the RAW and XMP files in to another raw converter and it will read the settings (though not necessarily show on the sliders).

    Just out of interest - I had a similar problem with adobe creative cloud, wondering if your user account is also going 'off keel' the solution was a OSX user account in order to make any adobe software work.
    0

Post ist für Kommentare geschlossen.