impossible d'ouvrir CAPTURE ONE
Bonjour,
je viens de télécharger la mise a jour 16.3.5.1929.exe et je ne parviens plus à ouvrir capture one. Dés l''ouverture, un message "capture one s'est arrété de façon inattendue.
Que faire ? j'ai besoin d'accéder rapidement à mon travail.
Merci
-
Same to me on IMAC.
C1 V16.3.5.10 crashes on IMAC I7 macOS 14.3 after loading the library. Downgraded to 16.3.4.
C1 V16.3.4 runs satisfactorily.
Knitted again with hot needle !Helmut
0 -
Merci pour cette réponse rapide. je viens également de revenir à la version précédente en attendant la résolution du problème.
Je n'avais pas précisé que je suis sous Windows 11.
Bonne soirée
0 -
Well, I have this latest version installed and running on 2 PCs under Windows 11 without any problems. Can you find any hints for causes in the Windows event logs or any entries in the Capture One logs (in the path C:\Users\Your_User_Name\AppData\Local\CaptureOne\Logs) which note faults?
-1 -
16.3.5.10 Mac version is crashing upon opening on both my MacBook Pro M2 and Mac Mini M1. Annoying, since it introduced the support for the new NEFX Nikon files...
I hope they will fix it soon
0 -
Same here => back to 16.3.4 (BTW, this version already adresses NEFX files from ZF and Z8 if I'm reading well : "Capture One Pro (16.3.4) is a service release that includes Nikon Zf and Nikon Z8 .NEFX support"
Filed a bug to C1 team about the 16.3.5.10 issue. They took it in account and it is opened now.
Other similar issues may be in the works : https://support.captureone.com/hc/en-us/community/posts/16636766979613-Mac-Windows-crashes-when-trying-to-open-denoised-Nikon-Z8-DNG
My own findings are it's affecting all Z8 and ZF DNG files, whether it is from stitching panorama, merging HDR or in above case so, denoised ones.
0 -
Okular : en suivant le chemin que vous indiquez, je trouve plusieurs fichiers et je n'y connais rien. Quel est celui qui correspond au journal ?
0 -
@guillaume-leveque Brice Vous pouvez trouver les logs en suivent ce tuto : https://support.captureone.com/hc/en-us/articles/360002405257-How-do-I-retrieve-logs
Je cite :
"les fichiers les plus importants à inclure sont :
Application (pour tout problème)
CaptureCore (pour les problèmes de session de prise de vue directe - tether)
ImgCore (pour les problèmes d'édition de photo)
ImgCoreOCL (pour les problèmes d'accélération matérielle)"0 -
Merci, je vais les transmettre à l'équipe.
0 -
@guillaume-leveque Brice
If you're going to open a support case they will for sure ask you for the logs as mentioned by Pierre. You can try yourself to check the file Application.log for any entries which look for failures (maybe lines with warnings, faults or critical mentions). When C1 crashes it also creates a Crashdump.log which can contain any hints.What else you can do is to start C1 with holding down the Shift key, then opens a menu which let's you choose to open another catalog or session or create a new session/catalog. So you could prove if a corrupt catalog/session is the cause.
0 -
Okular : I already filed a bug report. It's probably not a problem with catalog corruption.
Version 16.3.4 is working ok with ZF and Z8 DNG files while version 16.3.5 crashes with the same catalog.
0 -
Pierre Lagarde
My hint was adressed to @guillame-leveque Brice, he didn't mention about ZF + Z8 files. So his problem might be a different one than yours.0 -
Okular Might be but still, his problem can't be a catalog corruption as he said he went back to version 16.3.4 and it seems that this solved his problem for the moment.
Anyway, 16.3.5 crashes for many here and it's not because of catalog corruption. It's because of the version being buggy ;) .
0 -
Bonjour,
Effectivement, en revenant à la version précédente, j'ai pu ouvrir Capture one sans problème. Par ailleurs, c'est sur une session et non sur un catalogue que le problème s'est produit. je ne sais pas si cela fait une différence.
Merci à tous pour vos partages d'expérience.
0
Please sign in to leave a comment.
Comments
13 comments