V 9.1 is crash prone
Downloaded 9.1 und tried to change some keyboard shortcuts. Crashes all the time, can´t switch the viewer off and on. Thank you very much. You should consider staying with v. 9.0.x until the new version is mature and stabil.
0
-
The above was what was the best workaround for me.
Started 9.1, oh no its fucked. Realised I didn't have a backup which included the massive shoot I was working on and the catalogue was already upgraded so can't use it in 9.0.x. So I did this:
1) reverted back to 9.0.x
2) created a new catalogue
3) ENSURED I WAS VIEWING ALL IMAGES IN THE LIBRARY TAB (this was the main thing - do not be viewing an individual album or the library tool disappears in the upgrade, make sure the "all images" folder is selected)
4) Closed 9.0.x
5) Upgraded to 9.1
6) Opened 9.1 and upgraded the catalogue
7) New catalogue in 9.1 should open WITH the library tool intact.
😎 Import your old catalogue to the new one.
Obviously if you backed up before upgrading this is all moot, just downgrade and use a backup catalogue.
Im totally blown away by the apparent lack of action from C1/P1. Most users of C1 are professionals and this kind of software issue can cause massive issues. When Adobe screw up, they roll back within hours. Why can't C1 do the same? At least make a tool for us to be able to downgrade our upgraded catalogues.0 -
The situation is quite simple. Apparently I haven't been able to explain it properly:
Yup, seems clear now. Well, as I said, I would try importing the old one or as EnderWiggins mentioned, try to fix the converted one. But it sounds like the converted one got shot, so I'm not sure how well the repair works, never tried that before. - Good luck!I now backup every time I quit C1.
Same here. After reading about all the issues people were having with their catalogs, that's the only responsible thing to do.0 -
[quote="funkcanna" wrote:
Im totally blown away by the apparent lack of action from C1/P1. Most users of C1 are professionals and this kind of software issue can cause massive issues. When Adobe screw up, they roll back within hours. Why can't C1 do the same?
At some point people will have to start to realise what they are dealing with here.
Adobe Systems has about 12.000 employees.
Phase One in Denmark is so small in comparison, that they are able to show their whole workforce in a small headshot collage on their about page
And just 20 of them are working on C1, that's one row of pictures in the collage.
Considering all that, I'm amazed about what quality product this David is able to release facing the Goliath from Mountain View.0 -
[quote="EnderWiggins" wrote:
[quote="funkcanna" wrote:
Im totally blown away by the apparent lack of action from C1/P1. Most users of C1 are professionals and this kind of software issue can cause massive issues. When Adobe screw up, they roll back within hours. Why can't C1 do the same?
At some point people will have to start to realise what they are dealing with here.
Adobe Systems has about 12.000 employees.
Phase One in Denmark is so small in comparison, that they are able to show their whole workforce in a small headshot collage on their about page
And just 20 of them are working on C1, that's one row of pictures in the collage.
Considering all that, I'm amazed about what quality product this David is able to release facing the Goliath from Mountain View.
Quite so Ender.
In fact with C1 there is always the option to go back to a previous release.
I tend to install alongside a previous release just in case there are problems. However when a catalogue or session need to be updated direct roll back is rarely an option. That's why C1 always creates a copy of the pre-update catalogue or session as part of its conversion process. If anything goes wrong then revert to the previous known good release and rename the saved catalogue or session and carry on as before. You have control over the roll back - indeed the update too!
Sure it's frustrating if a problem only becomes obvious AFTER some time editing but in this case it seems that those having problems have seem them quite early. They have certainly been widely noted here in the forum.
I note that the most significant problems reported seem to apply to Mac users only. I'm on Windows and all seems well with the problem areas discussed here although I suspect that some of the problem features are not available in the Windows version.
Grant0 -
Whist I can reliably make Catalogs on my Mac version of COP since v9.0.x, I still prefer to use Sessions. I catalog in MediaPro. 0 -
[quote="EnderWiggins" wrote:
At some point people will have to start to realise what they are dealing with here.
Adobe Systems has about 12.000 employees.
Whilst I appreciate the differences in employee size, when I pay almost 300euro for an application, the number of employees they have is not my concern.
I may have missed it but I'm yet to see any action from C1 on this issue and 9.1 has been out for a while now.0 -
While we do not publish day-to-day updates on what we are working on, a lot of things are going on internally. I cannot say when, but we are of course aware that some users are experiencing stability-issues with 9.1.0.
However, we are also noticing that other parts of the application seems to be working better than ever (like the totally reworked Canon tethering engine). So while some users are experiencing instability, many other users have it working perfectly to their needs.
We are actively working to resolve the outstanding issues. We hope for your understanding, as this is not a day-to-day task.0 -
Christian,
I thank you for your updates here on the forum.
This communication with the day-to-day users is very important as it provides us with confirmation that something is happening.
I would still like to have the functionality that is in Photoshop Channel Mixer. I have been putting Support Cases in for the last 18 months. This is, in my view, one of two weakness in CaptureOne Pro, the other is the lack of a freely available SDK so users can build interfaces and plugins into image processing pipeline.0 -
Christian,
May I ask why it isn't a day-to-day task? Every forum and blog points out bugs and performance deficiency of catalogs in Capture One. These are from serious users. Non-users don't comment on it because they don't experience it. There should be sufficient factual evidence of severe and repeated problems. Shouldn't it be a priority, indeed, task #1?0
Post ist für Kommentare geschlossen.
Kommentare
39 Kommentare