Capture One 12 Crashing

Commentaires

19 commentaires

  • diver1
    I don't know what the problem you got but why...
    ...you have expectations on the day one of the release somebody able to respond on your report?
    ...if you use C1 (and any other product) for commercial use why do you going to install the update immediately?I was in Beta testing for the 12 (for Mac and Win) without any issues but would not install in the production until 12.01 at least...
    0
    Actions pour les commentaires Permalien
  • Emile Gregoire
    [quote="OldRadioGuy" wrote:
    Disappointed that I haven't had a chance to use the release version in C1-12. The reason: The app crashes every time I attempt to choose a folder in Import or add a folder in Libraries. I didn't experience this behavior in the betas, nor have I ever had this happen in previous new-version releases.

    I completed the auto-bug report generated upon crash three times, and I opened a service ticket. Running macOS Mojave, Version 10.14.1 here on an iMac Retina 5K, 27-inch, 2017; 4.2 Ghz Intel Core i7; 32 GB memory; Radeon Pro 580 8192 MB.

    Am I the only one to have this happen?


    Sorry to hear about your problem! Can't help you, I have no problems with the release version of 12, just like the betas worked smoothly. Maybe someone else can chime in in a positive way 😉
    0
    Actions pour les commentaires Permalien
  • Oliver Waletzko
    [quote="OldRadioGuy" wrote:
    The app crashes every time I attempt to choose a folder in Import or add a folder in Libraries.

    Sorry for you to hear that. I cannot reproduce your problem - but in case I'd be concerned my workaround (in addition to advice from the PO support team of course) would be as follows:

    I'd backup the folder /user/Library/Application Support/Capture One/ - then completely erase the C1 12 Application following the instructions on and re-install C1 12 - and see if that solved your problem.

    If you should be missing customizations you had previously made you've got the option to selectively copy back folders oder folder content from your backup (see above).

    Hope that helps...
    0
    Actions pour les commentaires Permalien
  • NNN636917267337929836
    if co1 pro crashing?solution,just overclock a little bit your cpu voltage.its work for me
    0
    Actions pour les commentaires Permalien
  • Robert Whetton
    [quote="NNN636917267337929836" wrote:
    if co1 pro crashing?solution,just overclock a little bit your cpu voltage.its work for me

    OC a Mac 😂 🙄
    0
    Actions pour les commentaires Permalien
  • Twan Dieltjes
    I have this problem too this tuesday morning. For me it happend when my NAS wasn't online yet.
    C1 reported correctly that the pictures where offline. I did some small changes to some pictures and close C1.
    When the NAS got online, I started C1 12 again and directly when i click on a folder in the library, the application crashes.

    I did the full bug report and on request of support, I created and uploaded a movie which shows the behaviour.

    In a mail from support, they recommended me also to do a full de-install and install again but I haven't done it. If they ask me to test something, I can but I don't want to wait long. Support did not responded yet.

    I'm just a hobby photographer but this should not happen. At least… it never happend when I used LR 6.14.
    Because I did not liked the adobe subscriptions, I switched. Hopefully this was not a bad choice.

    Any new information about how to solve this?
    0
    Actions pour les commentaires Permalien
  • Paul Steunebrink
    I would start doing verification of your catalog first (File menu, Verify). Start Capture One with the Shift or Alt key (whether on Windows or Mac) and open the file menu. By the way, if Capture One does not crash when you open it without catalog, it is probably not the program and reinstallation won't help you much, is my idea.

    Is your catalog on your local disk or on the NAS? Better have it on your local drive.

    If this does not help or the verification fails without successful repair, do you have a recent backup made from within Capture One to restore?
    0
    Actions pour les commentaires Permalien
  • Twan Dieltjes
    If seems to be an issue with the database.
    I have a single catalog made for testing and it does not crash.
    In fortunately I don’t have a backup with seems to work. C1 did create a local backup but with it c1 crashes too.
    So I agree fully uninstall does not sound as the solution.

    The catalog is on the local harddrive of my MacBook.

    I’am afraid I have to create new catalogs and lost the editing information.
    My trust in C1 is a bit damaged now.....
    0
    Actions pour les commentaires Permalien
  • Paul Steunebrink
    I understand the verify/repair process was not successful as well?

    What you could do, is create a new catalog and import the damaged catalog into the new catalog. This sometimes helps if the damaged catalog is still good enough to transfer the image data, and that is all you need!

    I think it is worth a try.

    And, please set in Preferences that you make a backup everyday/always. It is your only fallback scenario. And do regular the verification process, as a kind of maintenance, in particular after an import.
    0
    Actions pour les commentaires Permalien
  • Twan Dieltjes
    I'm still in contact with support.
    Creating a new catalog and import from the previous did not work. C1 was showing a messagebox but no progress was shown for a long time. So i stopped it and started to create a new catalog and import the files manually.

    Unfortunately, I've lost the edits i did this way. Very annoying. But I also discovered something.

    I can browse to my Synology NAS from my macbook in 2 ways. I can use the "location" link in finder or a mapping to my NAS which I create with the "Connect to server" menu option before I start C1. There seems to be a different for C1 between do's 2. When I browse and import via the "location" link, after the import, capture one shows 2 times the same Volume name of my NAS but when I hover over it, it shows a …-1 as name. So C1 seems to duplicate the Volume name and add's -1 to the name as it should be a different location. One of the names is also shown with a warning sign as being Offline. Very weird.

    When I import via the "Connect to Server" mapping, everything seems ok and more stable.
    Why? I don't have any idea. Anyone?
    0
    Actions pour les commentaires Permalien
  • Paul Steunebrink
    [quote="NNN636737621499121270" wrote:
    ...
    When I import via the "Connect to Server" mapping, everything seems ok and more stable.
    Why? I don't have any idea. Anyone?

    Unless you configured your NAS for File Services, both SMB and AFP are enabled. The two ways of connecting refer to both protocols. This is confusing for applications.

    The solution is simple, disable one of the two protocols, disconnect any connection and connect again.
    0
    Actions pour les commentaires Permalien
  • Twan Dieltjes
    I had AFP and SMB both enable so I disabled AFP.
    I had good hope because it looked like C1 even got a bit faster....

    Imported new pictures again et voila....
    again C1 crashes when I click on the folder or want to open a picture.....
    0
    Actions pour les commentaires Permalien
  • Paul Steunebrink
    [quote="NNN636737621499121270" wrote:
    I had AFP and SMB both enable so I disabled AFP.
    I had good hope because it looked like C1 even got a bit faster....

    Imported new pictures again et voila....
    again C1 crashes when I click on the folder or want to open a picture.....

    I suggest to create a new catalog for testing again, on your local drive and import some images (referenced) from your NAS and start working with it.

    If that works fine, the issue is probably with your other catalog. If it crashes like the before, it is something with your setup.

    By the way, I would verify the catalog after every crash.
    0
    Actions pour les commentaires Permalien
  • Twan Dieltjes
    I already created a new one and imported pictures from my NAs.
    It worked fine for 1 day. This evening C1 crashed again after the import of a new folder with pictures.

    Very frustrating. My C1 is useless at the moment

    Are there issues known with the latest Mac OS?
    I bought the latest 16 inch MacBook Pro last month
    0
    Actions pour les commentaires Permalien
  • Ian Wilson
    [quote="NNN636737621499121270" wrote:
    I already created a new one and imported pictures from my NAs.
    It worked fine for 1 day. This evening C1 crashed again after the import of a new folder with pictures.

    Very frustrating. My C1 is useless at the moment

    Are there issues known with the latest Mac OS?
    I bought the latest 16 inch MacBook Pro last month

    It’s not clear to me whether the new catalog you created is all on the internal storage, or whether it still references images stored on the NAS. If the NAS is still involved, it might be worth creating a new small test catalog wholly on the computer, to see whether you still have the problem or whether the NAS is the problem.

    Ian
    0
    Actions pour les commentaires Permalien
  • Twan Dieltjes
    The catalog itself is on the SSD of my latest Macbook 16inch (Catalina) and yes, the pictures are on the NAS.
    Yes, it's a good test to create everything local on the SSD but not the final solution of course.

    So what if C1 one then works as expected? My macbook 16 inch is just a month old.
    I did not had these kind of issues with my 2013 macbook. (with the same NAS and on the same network)
    I even bought a USB to Ethernet adapter to check if Wifi was the issue but I have the same issues with both
    0
    Actions pour les commentaires Permalien
  • Paul Steunebrink
    [quote="NNN636737621499121270" wrote:
    The catalog itself is on the SSD of my latest Macbook 16inch (Catalina) and yes, the pictures are on the NAS.
    Yes, it's a good test to create everything local on the SSD but not the final solution of course.

    We try to help you in establishing what causes the issues you are having. Once that becomes more clear, we can work towards a final solution. Test setup are not final solutions. There are a way to differentiate.
    [quote="NNN636737621499121270" wrote:
    So what if C1 one then works as expected? My macbook 16 inch is just a month old.
    I did not had these kind of issues with my 2013 macbook. (with the same NAS and on the same network)
    I even bought a USB to Ethernet adapter to check if Wifi was the issue but I have the same issues with both

    Valuable information. First, make sure your new Macbook 16 is *not* using hardware acceleration (Prererences, Genral tab). Set for both display and processing the setting to Never.

    Regarding your NAS, your new computer uses an adapter for Ethernet connection. Possible suspect.

    And, which network protocol is your NAS set to communicate? Defaults are AFP and SMB. It is better to stick to one protocol only.

    Before you open a catalog in Capture One, make a connection to your NAS with Finder first. This wakes up the NAS and establishes a 'full connection'.

    You see, quite some variables in the equation.
    0
    Actions pour les commentaires Permalien
  • Twan Dieltjes
    I disabled AFP so the NAS now only connects via SMB.
    Synology analysed the logfiles from my NAS and there was no disconnect or signs to a lost connection.

    Today, I discovered also something. Via facebook somebody asked me, if I was running version 12.1.5.
    I was running 12.1.4 but when I used the "Check for update" option in the software, capture one only reports the new 20 version. Strange but maybe they prefer people to upgrade (and get some money) to 20.

    So I went to the website, downloaded the latest version and discovered it was 12.1.5.8.
    I've installed it yet but had to leave so I haven't test it yet.

    I have to issue via Wifi also so the Ethernet adapter is not the issue.
    0
    Actions pour les commentaires Permalien
  • Twan Dieltjes
    Seems like 12.1.5 is stable again. I'm now importing all my pictures in new databases.....
    Fingers crossed
    0
    Actions pour les commentaires Permalien

Vous devez vous connecter pour laisser un commentaire.