Capture One Freezing - Again!
Hello,
Once again I am experiencing great difficulty with my catalogue.
I have created a new catalogue for 2016 and have just two folders within this, both holding approximately 150 images.
I imported images today and everything went just fine with editing the images, until I wanted to re-open the catalogue.
On opening the catalogue I had far fewer images than are in the catalogue actually appear and the orange circle at the top froze without completing.
I then find that the only way to close Capture One is via the Windows Task Manager.
I then attempted to open my other folder within this catalogue only to find that no images appeared.
I opened another catalogue and checked my new 2016 catalogue to find that there was no errors.
This particular problem has been dogging me for months now.
To say that I am getting fed up with this constant problem is an under statement!
I bought a new computer to help solve this problem as my previous on wasn't up to the job and I'm still having Capture One freezing on me and failing to load catalogues.
I am paying a monthly fee for an application that keeps freezing on me and I am really angry about this situation coming back time and time again!
Am I the only person having this problem with Capture One?
Once again I am experiencing great difficulty with my catalogue.
I have created a new catalogue for 2016 and have just two folders within this, both holding approximately 150 images.
I imported images today and everything went just fine with editing the images, until I wanted to re-open the catalogue.
On opening the catalogue I had far fewer images than are in the catalogue actually appear and the orange circle at the top froze without completing.
I then find that the only way to close Capture One is via the Windows Task Manager.
I then attempted to open my other folder within this catalogue only to find that no images appeared.
I opened another catalogue and checked my new 2016 catalogue to find that there was no errors.
This particular problem has been dogging me for months now.
To say that I am getting fed up with this constant problem is an under statement!
I bought a new computer to help solve this problem as my previous on wasn't up to the job and I'm still having Capture One freezing on me and failing to load catalogues.
I am paying a monthly fee for an application that keeps freezing on me and I am really angry about this situation coming back time and time again!
Am I the only person having this problem with Capture One?
0
-
Richard,
I don't use catalogues but I do have V9.0.1 installed and I don't get any freezes in C1 that have a C1 origin.
However in the past few months I have frequently found that Windows manages to get confused about what it is doing with Windows Explorer from time to time and all operations can go AWOL for a while then work somewhat erratically until I either kill of Explorer (it will auto restart) or re-boot the machine.
I have also found that my browser - Firefox - can freeze from time to time. It usually comes back - eventually - but once such a problem has started it's best to re-start it anyway. I think the problem is connected to certain advertising sites or maybe ad campaigns. It probably does not help that I often have rather a lot of tabs open.
I'm using Windows 7 Pro.
IF what I am doing in C1 is invoking the Windows Explorer functionality, as some action do - Show in Explorer for example - then an Explorer Freeze may be induced from time to time that is likely also to effectively Freeze C1 - but that does not seem to be caused primarily by C1.
Likewise if Firefox chooses to start playing up if I have linked to the Phase web site via the C1 Help menu that is not a C1 problem either.
Both of the above mention oddnesses pre-date the installation of V9 so there seems to be no connection likely to that event.
Based on information elsewhere in the forum one question would be - How much memory does your system have? I can't recall if it was a Windows or Mac thread but there was a recent post indicating that the poster was seeing some problem with his installation in certain situations running with 8Gb RAM but none once he had upgraded to 16Gb.
FWIW my machine came with 8GB but quite early in my ownership I added a further 16GB (it had 2 spare slots) since the primary reason for purchase was beta testing some business application software with very large data sets and it seemed silly to attempt that with only minimal memory available.
I assume you have already discussed the issues with C1 support?
Do the log files suggest anything like a consistent pattern for what was happening just prior to the freezes?
I can understand your frustration but it would seem that your experience is not typical though it may not be unique.
HTH.
Grant0 -
This has been something that I also reported to Customer Support back in October 2014 and as of May 2015 was still not resolved. Although it happened regularly in Win 7/8.1 it no longer seems to happen in Windows 10 Home with v8.3.4 or v9.0.1.13.
In my case the symptoms could be repeated regularly but only happened on the first start-up of C1 after rebooting the PC ... i.e. turning it on for the first time or rebooting, it seemed to be that turning on tethered support for one camera seemed to fix it at one point in time (I think v8.0.2.24) but by 8.2.2 it had all started happening again.0 -
[quote="AiDon" wrote:
This has been something that I also reported to Customer Support back in October 2014 and as of May 2015 was still not resolved. Although it happened regularly in Win 7/8.1 it no longer seems to happen in Windows 10 Home with v8.3.4 or v9.0.1.13.
In my case the symptoms could be repeated regularly but only happened on the first start-up of C1 after rebooting the PC ... i.e. turning it on for the first time or rebooting, it seemed to be that turning on tethered support for one camera seemed to fix it at one point in time (I think v8.0.2.24) but by 8.2.2 it had all started happening again.
You know that almost sounds like it is something to do with cache or temporary files.
It's interesting that my lowly GPU card has, according to the log files, always been rejected as being an underperformer. Fine by me since CPU processing of my files is fast enough.
Suddenly with V9 C1 seems to be using it.
Interestingly (but in need of re-checking) when I recently used V8 after installing V9 it also seemed to activate the GPU having always rejected it before.
The log file would always give a message to the effect that the card had been "previously assessed and rejected" - suggesting there was a record of performance retained somewhere that meant retesting was not required an just don't use it. Whether that was something to do with the GPU drivers or settings (which I have recently played with just to confuse matters) or something new in V9 that removed or bypasses older information in the C1 archives I don't know.
I mention this since it might just have some sort of similar root cause to the freezing problem.
On the other hand in terms of Richard's original description, seeing some but not all of the files sound more like a preview/thumbnail calculation in progress but not complete. Why would that be?
The log files would, I imagine, provide some clues about what is supposed to be happening even though it may not specifically identify what has happened if the process has been killed off.
HTH.
Grant0 -
Thank you everyone for your input.
Regarding the log files, where do I find them and yes all of this information has been fowarded onto technical support.
I'm running Capture One Pro 9.0.2 onWindows 10 and have 8GB RAM.
When I open a catalogue and then use the verification to check other calologues it might tell me that a particulat cataglogu is corrupt, I then repair it and am told everything is now fine.
I then go back and check the same catalogue only to be told that it's corrupt... ?0 -
Richard,
I have not bothered with 9.0.2 but as far as I can tell from the announcement there is nothing different other than the added support for the new Phase back.
I'm not running Win 10.
I would strongly suggest increasing memory since 8Mb is not a lot these days - especially if your camera produces large RAW files that will result in an even larger working data set in memory.
If you motherboard has spare slots buy more memory cards. If not you will need to swap the existing one(s) for larger capacity. Go for as much as you can justify - it will make running multiple applications at the same time a more rewarding experience.
That alone may not be the cause of your problem but more memory can only be better. For a newish machine memory is not too expensive - usually.
Log files can be found on Windows 7 at
C':/Users/[User Name]/AppData/Local/CaptureOne/Logs
I understand it's much the same for Win 10.
Whether you can understand the relevant logs enough to spark an Idea about what might be happening is another matter. Some entries will be easier to get a feel for than others.
Make a copy and view the log using notepad.
If you have not sent these to Phase already as part of the Support Case ... then I am slightly surprised they have not asked for them.
HTH.
Grant0 -
Thank you for your advice; I'll double my RAM to see if that helps, but I somehow suspect not, worth a try though... 😊
I have contacted support about this problem many times with regard to Capture One 8 as well and they have never asked for any logs.
Oh well, off to order some more RAM... 😊0 -
[quote="Richard_Allen" wrote:
Thank you for your advice; I'll double my RAM to see if that helps, but I somehow suspect not, worth a try though... 😊
I have contacted support about this problem many times with regard to Capture One 8 as well and they have never asked for any logs.
Oh well, off to order some more RAM... 😊
I'm not sure that RAM is actually an issue as my environment is:
Win 10 x64 System with Intous 5
Sys : Intel i7-2720QM @2.0Ghz x 4 core/8 thread, 8GB RAM
GPU: NVIDIA GeForce GT 540M, 1GB, OpenGL v4.5, OpenCL v1.1
And the performance is satisfactory using CR2 images from a 5DsR (60MB average) and RAF images from a Fujifilm (32MB average).
In my case the performance isn't an issue ... just other things 🤓0 -
There are many variables involved here but other have reported problems solved by going beyond 8Gb RAM and I think it is inexpensive enough these days to make some sense as a purchase partly because it eliminates one line of investigation and partly because it is always likely to be of some benefit.
I don't have such large files but I do tend to have other application running at the same time as C1 - often quite a few and the system copes well with typical active RAM usage at around 14 to 16Gb.
If I am really pushing things it can get close to the 24Gb max, especially if I have a lot of tabs open in Firefox.
But yes, there is more to performance and stability than just RAM but whatever else may turn out to be required the ready access to RAM is always likely to help in some way.
Interesting about the logs Richard. Maybe they have seen enough to and feel there is nothing useful recorded?
One of the problems with a freeze is that it probably means the final problem that caused it cannot be written to the log, especially if the process is killed. Entries leading up to the freeze may not suggest a common pattern.
One might think the Windows Events log could have something in it - but maybe not and for the same reasons.
Grant0 -
I can hardly believe that 8 GB RAM is enough for anyone, for me it is not. Not sure it solves you specific problem though.
I am going to buy a new computer mainly because of that (my system is maxed out with 8 GB RAM). (I am no longer satisfied with performance, that is another reason...)
I also only have C1 and Firefox running and often end up restarting C1 when total system consumption goes up to 7.8 GB.
(Edit: Performance suffers then too.)
Meanwhile the official recommendation is 16 GB, and Lionel (a development lead) from P1 recommended 32 GB or more.
cheers
BeO0 -
My apologies, same same no difference still hangs ... 1 of 96 images and never moves ...
LOG says ... "[2016-01-16 21:43:55.480][545][ID:061, [THD] Logg]{WAIT } | Info : WAIT [7] started"
8 minutes later .... nothing have to kill (in this case 8.3.4) same as v9.
Forgot to add the link to a image: https://drive.google.com/file/d/0BzkxCa ... sp=sharing0
Post ist für Kommentare geschlossen.
Kommentare
10 Kommentare