fatal crashes
I've just had CO10 freeze. After waiting a while and then forcing quit, I can no longer connect with the database:
----
Failed to connect with database
/Capture One Catalog/2016-07-29 18.04.17/Capture One Catalog.cocatalogdb
Database connection FAILED
The requested document type is not recognized.
The provided database is of an unknown type.
----
I've always resorted to a previous backup in the past, but this happens far too often for my liking. Anybody else have the same experience?
----
Failed to connect with database
/Capture One Catalog/2016-07-29 18.04.17/Capture One Catalog.cocatalogdb
Database connection FAILED
The requested document type is not recognized.
The provided database is of an unknown type.
----
I've always resorted to a previous backup in the past, but this happens far too often for my liking. Anybody else have the same experience?
0
-
Please contact our Support Team. 0 -
I had the same issue 😕 I tried to repair the catalog but I always got the same message. I finally deleted the catalog. It was so frustrating cause I was in the middle of making a full transition from LR to C1. It seems that C1 still have some problems with large catalogs ☹️. I wished they would find a quick solution for it. 0 -
If Phase One would stabilize and improve C1P for large catalogs, they would rule the world! They have done an amazing job on everything else, but solid DAM is sorely needed. It’s the only thing that keeps the majority of my colleagues from switching to C1P. 0 -
Exactly.
I would suggest PhaseOne to spend the next 6 mouths to fix/optimise C1P10.
It's not very "funny" but it's very useful
[quote="Moryan" wrote:
I've just had CO10 freeze. After waiting a while and then forcing quit, I can no longer connect with the database:
----
Failed to connect with database
/Capture One Catalog/2016-07-29 18.04.17/Capture One Catalog.cocatalogdb
Database connection FAILED
The requested document type is not recognized.
The provided database is of an unknown type.
----
I've always resorted to a previous backup in the past, but this happens far too often for my liking. Anybody else have the same experience?
Yes, I've had this 3-4 times in the first week trialling C1 pro 10.
C1 has alwasy been a bit fragile IMO but this type of crash is terminal to the Catalog in question. Not happy!0 -
Maybe PhaseOne offers us an update as Xmas present 😊 0 -
C1 catalogs are terribly unreliable. I've been a c1 user since v7, and ever since v9, it is so unreliable that I'm now bouncing between it and back to lightroom. I upgraded to c1 v10 with the hope that reliability might be better, but its not. In fact the databases are worse. I've now apparently lost several years and variations of catalogs - the upgrade operation to c1 v 10 fails for all the large ones and at least two now show no files after they've been upgraded.
The only way to get this damn thing to work is to use locally hosted sessions with every new shoot. They seem reasonably stable.
It is such a shame, as the actual meat of the tool is great. The editor tools are the best out there. But the brain dead file management catalog scheme is just too unreliable to be trusted for anything important. I'm beaten down and sick of spending hours and hours trying to recover and open catalogs. I'm going back to Lightroom after 5+ years as a C1 user.
And yes, I've tried a bunch of things recommended by support, including a sledgehammer uninstall/reinstall.
Sad sad sad0 -
Same issues...... Phase One please listen to these users..... You have a major issue with this software!!!!!!!
I have been using Phase One cameras/backs for about 15 years since i bought the H101 in 2002. I have since gone through the various version of Capture One and backs. P30,P30+,IQ250.
The software is by far the best to process Raw files. I used Aperture as a DAM to manage my library until they ceased development. This forced me to seek other software for this purpose. I used to use Media Pro and was one of there beta testers back in 2000 before it was bought by Microsoft and again ceased proper development. I tried Lightroom but just don't like the interface and how it handles Raw files. I am again looking to migrate 15,000 image into a DAM. I have now tried using Capture One ..... and it's a mess. I imported these images in to version 9 and a day later got : Database connection FAILED. Nothing i did could fix it so i upgraded to Version 10 of Capture One hoping they had fixed issues. I spent the day importing and before it had even finished building the thumbnails it crashed and again i got the : Database connection FAILED message.
Phase One bought Media Pro to use as some sort of asset management..... there has been no new development of this software for almost 15 years..... it is exactly the same. Phase One should make a proper DAM software that can handle large amounts of images. They are the best at producing RAW processing software. But they need to look at why no one is using it properly as a DAM software. Lightroom is really out there on it's own for this..... proper mobile integration etc. I want to use CO as a Dam and Raw process software. Why are they not developing it for this as well?
Please can anyone let me know how to recover a : Database connection FAILED issue. As i don't want to go through this yet again only to be locked out. Lightroom has never crashed and lost it's whole database...... I am aware you need to back up and i take this very seriously but when the catalog crashes before it hasn't even finished it's building of the thumbnails this does work......
Phase One need to fix this issue before they add even more bells and whistles to the software. They could clean up if they get this right.
Any ideas?
Many Thanks
Ollie0 -
[quote="NN635420785644361250UL" wrote:
C1 catalogs are terribly unreliable. I've been a c1 user since v7, and ever since v9, it is so unreliable that I'm now bouncing between it and back to lightroom. I upgraded to c1 v10 with the hope that reliability might be better, but its not. In fact the databases are worse. I've now apparently lost several years and variations of catalogs - the upgrade operation to c1 v 10 fails for all the large ones and at least two now show no files after they've been upgraded.
The only way to get this damn thing to work is to use locally hosted sessions with every new shoot. They seem reasonably stable.
It is such a shame, as the actual meat of the tool is great. The editor tools are the best out there. But the brain dead file management catalog scheme is just too unreliable to be trusted for anything important. I'm beaten down and sick of spending hours and hours trying to recover and open catalogs. I'm going back to Lightroom after 5+ years as a C1 user.
And yes, I've tried a bunch of things recommended by support, including a sledgehammer uninstall/reinstall.
Sad sad sad
You lost several years worth of catalogs? How so? With a backup nothing would be lost.
Given that C1 catalogs are seemingly so fragile, here's a list of things I've been doing to protect me against any potential catalog failures;- use referenced catalogs (originals are not kept inside the catalog)
- keep catalogs small (various reports of issues with catalogs point to sizes going beyond 10k)
- don't use the keywording "feature" (it's apparently so broken still that it manages to corrupt catalogs)
- don't upgrade catalogs when a new (major) version of C1 is released. Instead, create a new catalog with the new version and import the old catalog. If beneficial, update images with the new processing engine.
- create a backup/optimize every time C1 is closed
- create an automated backup every hour to an external drive (i.e. Time Machine)
- create an automated backup every hour to cloud storage (i.e. CrashPlan)
This has worked out great for me so far (knock on wood), I have never had any catalog issues (other than the known performance/usability issues). You might want to give this a try...0 -
[quote="oliver11" wrote:
Same issues...... Phase One please listen to these users..... You have a major issue with this software!!!!!!!
I have been using Phase One cameras/backs for about 15 years since i bought the H101 in 2002. I have since gone through the various version of Capture One and backs. P30,P30+,IQ250.
The software is by far the best to process Raw files. I used Aperture as a DAM to manage my library until they ceased development. This forced me to seek other software for this purpose. I used to use Media Pro and was one of there beta testers back in 2000 before it was bought by Microsoft and again ceased proper development. I tried Lightroom but just don't like the interface and how it handles Raw files. I am again looking to migrate 15,000 image into a DAM. I have now tried using Capture One ..... and it's a mess. I imported these images in to version 9 and a day later got : Database connection FAILED. Nothing i did could fix it so i upgraded to Version 10 of Capture One hoping they had fixed issues. I spent the day importing and before it had even finished building the thumbnails it crashed and again i got the : Database connection FAILED message.
Phase One bought Media Pro to use as some sort of asset management..... there has been no new development of this software for almost 15 years..... it is exactly the same. Phase One should make a proper DAM software that can handle large amounts of images. They are the best at producing RAW processing software. But they need to look at why no one is using it properly as a DAM software. Lightroom is really out there on it's own for this..... proper mobile integration etc. I want to use CO as a Dam and Raw process software. Why are they not developing it for this as well?
Please can anyone let me know how to recover a : Database connection FAILED issue. As i don't want to go through this yet again only to be locked out. Lightroom has never crashed and lost it's whole database...... I am aware you need to back up and i take this very seriously but when the catalog crashes before it hasn't even finished it's building of the thumbnails this does work......
Phase One need to fix this issue before they add even more bells and whistles to the software. They could clean up if they get this right.
Any ideas?
Many Thanks
Ollie
Take a look at some of the steps I listed in my preceding post, maybe that will work for you getting your images migrated.0 -
dredlew
What you are basically saying is don't use Capture One :
here are my thoughts to your statements.
It is not meant as an rant but in informed discussion that hopefully Capture One will listen to......
use referenced catalogs (originals are not kept inside the catalog)
.......I use referenced but it should be able to cope with both managed and referenced...... it is a paid software after 15 years of development. i only use referenced as i want to keep the catalog size small hoping that it will be less like to corrupt this way.
keep catalogs small (various reports of issues with catalogs point to sizes going beyond 10k)
......I shoot approx 1500 images/day.... i don't want them all catalogued and will use sessions for every day work. but surely DAM software should be able to cope with more than 10k images.
don't use the keywording "feature" (it's apparently so broken still that it manages to corrupt catalogs)
......Why included it if it doesn't work......and surely it's a basic feature (even though i don't really use it)
don't upgrade catalogs when a new (major) version of C1 is released. Instead, create a new catalog with the new version and import the old catalog. If beneficial, update images with the new processing engine.
....... Betas test software before you release it... even Apple figures this out.
create a backup/optimize every time C1 is closed
...... if a catalog crashes before the thumbnails are even built then become unusable then this is not possible
create an automated backup every hour to an external drive (i.e. Time Machine)
....... i agree but have never had to do this with any other DAM software..... in 2017 is this really needed..... what other software do you do this every hour....... ? At the end of a day but not every hour..... that means you are very nervous about how it behaves.
create an automated backup every hour to cloud storage (i.e. CrashPlan)
..... see above. I back up at the end of every shot when i work...... a catalog should be more stable as it contains day/weeks/years of work. I used Aperture for many year and never once had a corrupt database...... Lightroom for 2 years with nothing going wrong.....
Capture One has by far the best RAW processing and interface but they need to fix everything else relating to catalogs or just remove them until they are ready for prime time.
Thanks
Ollie
www.oliverpearce.com0 -
I too have been frustrated with the slowness of the Catalog performance and imports.
With a recent batch of troubleshooting and Library cleanups, I have found that on import COP will try to do importing and preview generation and possibly metadata resolution all at once - that's when it becomes non-responsive. If however, the user is clever, then COP can be encouraged to do these in sequence, andit's a much better behaved application. This shouldn't be up to the user, this should be designed in.
Observations:
Originally I would import my Aperture Library into an empty catalog with no further actions. The active folder is all images. COP first starts importing, and shortly after starts preview generation for all the images, and then is not responsive for a considerable time.
I have found that if I select (click on) the Group containing the import (where no images are visible) then preview generation stops, and COP remains responsive through the entire import. Not surprisingly, the import completes faster than if COP tries to do preview generation at the same time. After import is complete, then I select "All Images", and COP completes the preview generation without becoming non-responsive.
I note that hierarchical keywords can be imported into COP by formatting them as "Level1|Level2|Level3" or as "Level1 | Level2 | Level3". Eventually COP seems to reformat all the hierarchical keywords as "Level1|Level2|Level3" - I have seen it change after import is completed, during preview generation. In my Aperture Library I have changed the format to "Level1|Level2|Level3" so that reformatting isn't needed upon import.
I observe that the XMP format for IPTC Metadata fields is length limited - most keywords are limited to 32 text characters, with the exception of Headline, Description, Title, Instructions and Copyright notice - which are longer, and a few which are shorter and have formatting restrictions (Intellectual Genre and a few Code type fields). COP doesn't seem to enforce any length or format restrictions in any IPTC field, this may act in unexpected ways when exchanging IPTC Metadata with embedded XMP or sidecar XMP. I've just observed that having data in the "Job Identification" and "Source" fields causes an unexpected slow down. Both are nominally 32 character fields. I also note another user who had issues when the (c) appeared in the Title field - I found the same issue. I wonder how thoroughly COP has been tested with data in these fields. I don't seem to have any problem with data in the "Special Instructions" field or the "Copy right Notice" field - including the (c) symbol in Copyright Notice.0 -
[quote="oliver11" wrote:
dredlew
What you are basically saying is don't use Capture One :
That's not what I'm saying. What I'm saying is that these steps work for me and I believe that I have not had issues because of them. Since you do have issues, maybe you need to change your workflow. Clearly, C1 is not Aperture, nor Lightroom. And these underlying issues are not going to be fixed anytime soon if history is any indication. So you have to find ways around the shortcomings if you want to use C1. Everyone has different deal-breakers, so it depends on you what you are willing to accept or change.0 -
That's not what I'm saying. What I'm saying is that these steps work for me and I believe that I have not had issues because of them. Since you do have issues, maybe you need to change your workflow. Clearly, C1 is not Aperture, nor Lightroom. And these underlying issues are not going to be fixed anytime soon if history is any indication. So you have to find ways around the shortcomings if you want to use C1. Everyone has different deal-breakers, so it depends on you what you are willing to accept or change.
Profitional means Profitional ❗️
If they demand so much money for it, must also do for it 💡
we hope Phase one find a better solution .0 -
[quote="CAPTURE NIKON D700" wrote:
That's not what I'm saying. What I'm saying is that these steps work for me and I believe that I have not had issues because of them. Since you do have issues, maybe you need to change your workflow. Clearly, C1 is not Aperture, nor Lightroom. And these underlying issues are not going to be fixed anytime soon if history is any indication. So you have to find ways around the shortcomings if you want to use C1. Everyone has different deal-breakers, so it depends on you what you are willing to accept or change.
Profitional means Profitional ❗️
If they demand so much money for it, must also do for it 💡
we hope Phase one find a better solution .
I guess you mean "professional".
If you think the price tag for CO is too high, go have a look at "real professional" DAM systems. Then come back and let me know whether you think that the roughly 200 Euro price tag is still too high. Those other DAM systems don't even deliver the raw conversion quality like CO.
Full disclosure: i'm also not using CO for asset management, i also think it is not mature enough in both stability and functionality area.0 -
I guess you mean "professional".
If you think the price tag for CO is too high, go have a look at "real professional" DAM systems. Then come back and let me know whether you think that the roughly 200 Euro price tag is still too high. Those other DAM systems don't even deliver the raw conversion quality like CO.
Full disclosure: i'm also not using CO for asset management, i also think it is not mature enough in both stability and functionality area.
are you a photographer with a high end company level ? if yes
😉
you should look for a server + DAM solution
DAM dont need to bee professional high end like you thing, its need only a data storage place where to save and find
i agree that C1 a good RAW Converter.
but the very old Aperture still works, and do better as the professional.
this way my disappointment.
how like it should tray it . 😁
I do not want to raise someone here
when somthing not worth to use.
Developer needs feedback. Capture one start to bee stronger as bevor. upgrades should bee better..0 -
DAM software ideally should be deeply integrated with a Raw Processing facility. This saves time and keeps the workflow simple.
Aperture is very good software but has had no development for almost 4 years. It no longer supports the newer cameras and is dated it its architecture so Apple Photos shows..... but this is aperture software that doesn't offer the professional what is needed.
Apple has left Professional Photographers behind when they ceased development of Aperture.
Lightroom took over the main bulk of the switchers.
CO is the best Raw processor but needs serious development to offer a DAM solution.0 -
[quote="oliver11" wrote:
DAM software ideally should be deeply integrated with a Raw Processing facility. This saves time and keeps the workflow simple.
Aperture is very good software but has had no development for almost 4 years. It no longer supports the newer cameras and is dated it its architecture so Apple Photos shows..... but this is aperture software that doesn't offer the professional what is needed.
Apple has left Professional Photographers behind when they ceased development of Aperture.
Lightroom took over the main bulk of the switchers.
CO is the best Raw processor but needs serious development to offer a DAM solution.
If you intend integrated to mean the same software, then i sincerely disagree.
I do agree on the integration part, but that should mean being able to open raw converter from dam solution and showing the edits in the dam solution after raw editing (rather not having to render the edits). I use photo supreme for DAM and it's rather mature (i use the PostgreSQL version). It allows to integrate rather nicely with CO sessions and it does somewhat show CO edits (only the very rough ones, like BW etc.). I believe DAM is a profession on its own, as is RAW conversion.
Having both in the same software, locks you into the raw converter and cataloguing other types of files becomes more difficult (think of PSD docs, Word docs, etc.). I routinely use more than one raw converter, even though CO is my bread and butter converter.0 -
I prefer the DAM software like Aperture (Managed and Referenced) and Lightroom (Referenced) where you can catalog and keyword and edit images and it this is reflected in the previews. A one stop shop. CO is meant to be this but it doesn't work and keeps crashing on small libraries. 10 images is very small for a DAM software.
I you use Lightroom as a DAM and try to roundtrip into CO it won't show the edit without processing as a TIFF or jpg. There is no need if it is in the same program. You make your edits and this is reflected in the preview which is all that is needed until an export of the high res. If you use two programs , one as DAM one as Process then you always have to export a high res to view in the DAM software..... exporting and importing just to view changes. A waste of time and space.
I dont see the benefit of using two pieces of software.......0 -
[quote="oliver11" wrote:
I prefer the DAM software like Aperture (Managed and Referenced) and Lightroom (Referenced) where you can catalog and keyword and edit images and it this is reflected in the previews. A one stop shop. CO is meant to be this but it doesn't work and keeps crashing on small libraries. 10 images is very small for a DAM software.
I you use Lightroom as a DAM and try to roundtrip into CO it won't show the edit without processing as a TIFF or jpg. There is no need if it is in the same program. You make your edits and this is reflected in the preview which is all that is needed until an export of the high res. If you use two programs , one as DAM one as Process then you always have to export a high res to view in the DAM software..... exporting and importing just to view changes. A waste of time and space.
I dont see the benefit of using two pieces of software.......
I'm not denying that edits should be reflected, at least on a basic level (but preferably all edits). However, that doesn't necessitate having them in one software. Also, it doesn't necessitate rendering to TIFF of JPEG from the converter program. It does, indeed, necessitate that the DAM software recognizes the edits in the converter program.
That is why i mentioned photo supreme, because it does this for CO, DXO and Photo Ninja. Also, there are some open source DAM programs that do this. It's called Raw Recipe Reflection (3R). It does give the benefits you're after, as well as the other benefits like i mentioned in my other post.
Of course, if you only work with one converter and don't catalogue other file types than your images, you'd be fine with an all-in-one dam/converter. And i agree that CO at this moment is not very strong in the dam department.
YMMV.0 -
Digital Asset Management implies a system to manage many types of digital assets - all types of files and documents potentially.
What seems to be under discussion is a PAM - Photo Asset Management ... although for many that may stray into image areas beyond just photography.
So where does the functionality have to extend to to make a PAM suitable as a complete Asset Management tool for the collective of posters here?
Grant0 -
I think most people consider DAM to be for images..... but you are right we probably should be discussing PAM - Photo Asset Management. CO is resigned for still images not moving or really any other type of file. Final Cut Pro for example for moving image. Lightroom can handle video footage but it's not designed primarily for this and is not the best way to edit moving footage. I think CO is the best at processing still RAW images just needs to up it's game on the storage and retrieval of still images in a catalog library situation. 0 -
PAM - Photo Asset Management.
here you go ..thanks 💡
fair and well paid upgrades also ❗️0 -
[quote="oliver11" wrote:
I think most people consider DAM to be for images..... but you are right we probably should be discussing PAM - Photo Asset Management. CO is resigned for still images not moving or really any other type of file. Final Cut Pro for example for moving image. Lightroom can handle video footage but it's not designed primarily for this and is not the best way to edit moving footage. I think CO is the best at processing still RAW images just needs to up it's game on the storage and retrieval of still images in a catalog library situation.
But a full DAM system will involve just about every sort of file type one might think of.
PDF, Word (and similar), TXT, ..... whatever.
Anything that might be classed as a potentially readable document.
(In my view that make video very marginal historically .... but maybe not for the future.
And as soon as you allow video you have have to allow music (if you did not already) and all types of sound files.
All are Digital Assets that need to be Managed.
Of course the majority of people do not need this level of Management nor do they use it if they have it available - even when they KNOW they have it available.
With the exception of genuine need cases - mostly corporate bodies who probably collectively perhaps don't even realise they have a need at all - I strongly suspect that most DAM system are really solutions being hawked around looking for a problem that is spread widely enough for them to try to increase their user count by justifying the "need" that they claim to address.0 -
[quote="dredlew" wrote:
Given that C1 catalogs are seemingly so fragile, here's a list of things I've been doing to protect me against any potential catalog failures;
Don't you find it odd that you must be so careful in what you do and don't do in an expensive, professional-grade piece of software? Don't use keywords; don't use managed; don't add more than 1000 images; use sessions; etc.
Would you find it acceptable when you buy a car (popular analogy) and be told that you cannot open all doors at once so your passengers must get in one by one; that the speed drops by 2 when there a more than 2 people inside; that the seats cannot be adjusted without breaking the car? But hey, at least the engine is terrific!
And it's not that these are new issues; there are so many posts complaining about the poor performance; about regression… since at least v8. It's disheartening that there's been so little progress in these areas.
I'm not willing to give up on C1 because of it's editing capabilities. But I haven't upgraded yet to v10. I'll see how it evolves and what 11 brings. Maybe I'll keep using C1 as a raw convertor and use something else (LR, Aperture, Photos, digiKam, …) as a DAM. I have bought Luminar to play around a bit; interesting, especially for a v1.
Cheers,
Peter.0 -
[quote="peter.f" wrote:
[quote="dredlew" wrote:
Given that C1 catalogs are seemingly so fragile, here's a list of things I've been doing to protect me against any potential catalog failures;
Don't you find it odd that you must be so careful in what you do and don't do in an expensive, professional-grade piece of software? Don't use keywords; don't use managed; don't add more than 1000 images; use sessions; etc.
Would you find it acceptable when you buy a car (popular analogy) and be told that you cannot open all doors at once so your passengers must get in one by one; that the speed drops by 2 when there a more than 2 people inside; that the seats cannot be adjusted without breaking the car? But hey, at least the engine is terrific!
And it's not that these are new issues; there are so many posts complaining about the poor performance; about regression… since at least v8. It's disheartening that there's been so little progress in these areas.
I'm not willing to give up on C1 because of it's editing capabilities. But I haven't upgraded yet to v10. I'll see how it evolves and what 11 brings. Maybe I'll keep using C1 as a raw convertor and use something else (LR, Aperture, Photos, digiKam, …) as a DAM. I have bought Luminar to play around a bit; interesting, especially for a v1.
Cheers,
Peter.
It really doesn't matter what I find odd or what x-car analogy is. We all know that C1 has great Raw conversion and crap DAM. It's been like this for years and after a gazillion support tickets, not much has changed. PhaseOne does not care enough for that to change anytime soon. Maybe in another decade you'll see a respectable DAM part inside C1, just don't hold your breath. - I've given it several tries over the past years and only with v9 did it finally become usable to me. Still with lots of issues, but usable. V10 did not change much either, gained one new feature I can actually use, which is output sharpening. Issues luckily have not increased by much either (for me).
Given that you know what the situation is with this application, you either wait it out until it becomes usable for you or you start using it and work around the issues to make it work for you. - Is this how it's supposed to be? I don't think so but there's really nothing you can do about it.
Luminar is a nice start but still a few versions away from becoming an alternative. Same with Affinity Photo, which is supposed to get a DAM as well. However, once these two get up to speed, it could be the only driving force to have PhaseOne invest more resources into the app. We shall see...0 -
Luminar is a nice start but still a few versions away from becoming an alternative. Same with Affinity Photo, which is supposed to get a DAM as well. However, once these two get up to speed, it could be the only driving force to have PhaseOne invest more resources into the app. We shall see...
just wait !
Affinity and Luminar promised there customer what the do !0
Post is closed for comments.
Comments
27 comments