V10 extremely slow - support not answering
I have had it now several times that support cases get not answered for weeks and if someone finally takes care the delay is excused with understaffing. Sometimes I get a couple of questions, most of them had already been answered with the initial opening of the support case. In other cases I get an response which is completely missing the point and claiming that issue .... had been fixed in 10.01 or 02 but the answer is completely missing the point, i.e. not related to my support case at all. Unfortunately PhaseOne also closes the case and I have to open a new one - same behaviour.
This is very frustrating with V10.02 still not being usable (too slow) even 3 months after the initial release and two "bug fixes".
Is there any other way to communicate with Capture One support (or even better management) besides through support cases? I tried calling the support team but this did not help either
This is very frustrating with V10.02 still not being usable (too slow) even 3 months after the initial release and two "bug fixes".
Is there any other way to communicate with Capture One support (or even better management) besides through support cases? I tried calling the support team but this did not help either
1
-
Is there any other way to communicate with Capture One support (or even better management) besides through support cases? [quote][/quote]
Absolutely! With your Wallet.1 -
Unfortunately that does not solve my current issues as I have already paid for the software and upgrade to V10. 1 -
What is your Support case number ? 0 -
244596 is the best starting point but there are several other cases as I had the previous ones had been closed.
If needed I could provide contact details via PN or email and explain it in a call.
Frank0 -
Frank,
We are working on this case together with R&D.
Case 244596 has been replied to.
Please check your "Support Cases" under "My Pages".-1 -
[quote="SebastianS" wrote:
[.....]
We are working on this case together with R&D.
[.....]
Thanks Sebastian,
This is a very good news !!
Cheers,
Robert0 -
Crossing my fingers! I really, really hope you guys can get this sorted out! Make C1P the best program on earth and take no prisoners! 😊 0 -
That sounds very positive.
Lets hope we will never see these single threaded processes beach balling in CO ever again!0 -
V10.1 is slightly better than V10.0 but still much slower compared to V9.3. Again most of the time when opening larger catalogs Activity Monitor is reporting "not responding" for Capture One and there is neither a high CPU or disk load.
Frank0 -
[quote="FL" wrote:
V10.1 is slightly better than V10.0 but still much slower compared to V9.3. Again most of the time when opening larger catalogs Activity Monitor is reporting "not responding" for Capture One and there is neither a high CPU or disk load.
Frank
Look in the system logs for something named "Autosave" and look at how many ms it take to do its work.
It should be a few ms only. When I suffered from that Not Responding bug it took at least 25000 ms to save something when launched and as it was a single threaded process doing it - everything else halted.0 -
Similar issue I posted on yesterday. Takes 3 minutes to open up an Aperture library imported in v 9. I too would love for C1 to work as well as it could. When it does open catalogs finally, I do like it and agree that it is as good as Aperture, but if takes minutes to open a catalog....
Adding some testing i have done to help us all out...
The Autosave log shows short times, et 30 ms.
I regenerated all the previews overnight and it still takes 3 minutes to open the catalog. I suspect it may be because they Aperture import only references the files (to use Aperture parlance) and does not copy them to the C10 Catalog.
Using C10.1, iMac 27 inch 5k retina 40 GB of RAM, upgraded CPU and graphics processor and Thunderbolt 2 connections to the external catalog on RAID discs. In other words, the system should be more than fast enough to do this in seconds as opposed to minutes.
Checking the C10 catalog for errors yielded no problems either...
The drives on which the library/catalogs reside is working fine, no errors on Disk Utility or Tech tool pro. Aperture and photos apps can open their libraries in about 5 seconds and they are the same size as the one that C10 has problems with.
Even though the program appears to hang, with the infamous beach ball, Activity Monitor shows varying CPU loads (usually very low school as 2-5 %) then it shoots up to something more logical, such as 80% just before it opens the catalog completely at about 3 minutes.
I have checked memory usage and this does not seem to explain the slow process especially with 40 GB of installed RAM!0 -
Atenolol,
what did you do to stop the autosave bug? I have been asking support many times in several support cases what kind of process this is and how to stop it - unfortunately I never got any answer.
Best
Frank0 -
To Atenolol,
The autosave bug never showed long times in my console log. I am not sure if I never had it, or never noticed it because I never looked at that until I completed both steps below - verification of catalog and regenerating previews.
To verify, use the option in the FILE Menu and select Verify catalog or session, and only after that did I check the console logs for autosave.
Regenerating all the previews may have also fixed the bug as I did that before ever checking the console logs. Same menu as above, command is just below Verify, but first go to the ALL IMAGES LISTING at the top left of the program window, than select ALL the photos you want to regenerate previews for..
Hope this helps.0
Post is closed for comments.
Comments
13 comments