Capture One Freezing - Again
Hello,
I am curious if anyone else is having problems with Capture One freezing on them?
Iam running 9.0.3 and last night I was attampting to edit an image when Capture One froze on me and the only way to shut it down was to use the Task Manager in Windows 10.
I then opened another catalogue and verified the catalogue that had frozen to be told that it was faulty.
I repaired it, opened it and it froze on me.
I then replaced the main files with the ones in my backup and Capture One opened and worked alright, for a short time, and then froze again.
Capture One still opens the catalogue that I have problems with but freezes before all the images are loaded.
This is very frustrating as I have had this problem (on nad off) for almost a year now.
I've even bought a new computer and upgraded the RAM but it hasn't helped.
I'm even contemplating switching over to an iMac but can't afford the expense of doing so and shouldn't have to!
I'm paying monthly for an application that freezes on me and think I should get a large discount.
I have never had any problems with Lightroom or Photoshop, only Capture One!
I am curious if anyone else is having problems with Capture One freezing on them?
Iam running 9.0.3 and last night I was attampting to edit an image when Capture One froze on me and the only way to shut it down was to use the Task Manager in Windows 10.
I then opened another catalogue and verified the catalogue that had frozen to be told that it was faulty.
I repaired it, opened it and it froze on me.
I then replaced the main files with the ones in my backup and Capture One opened and worked alright, for a short time, and then froze again.
Capture One still opens the catalogue that I have problems with but freezes before all the images are loaded.
This is very frustrating as I have had this problem (on nad off) for almost a year now.
I've even bought a new computer and upgraded the RAM but it hasn't helped.
I'm even contemplating switching over to an iMac but can't afford the expense of doing so and shouldn't have to!
I'm paying monthly for an application that freezes on me and think I should get a large discount.
I have never had any problems with Lightroom or Photoshop, only Capture One!
0
-
[quote="BeO" wrote:
I think you're too far away from me for a beer in a pub π π
Hehe,
There must be a great opportunity for a liquid refreshment version of 3D printing as part of a Virtual Bar and Club App.
Or perhaps Teleporting might work?
I'm not sure about that though. On Holiday in Malta one time many years ago we discovered this really nice white wine - the expensive local stuff at the time - and brought a bottle back to share with friends.
It did not travel well ...
I cannot imagine Teleporting would help.
Grant0 -
[quote="BeO" wrote:
My assumption is that google synchronisation on the E drive might possibly interfer with some locks on C1 files. Could be wrong but I personally would try to take this out of the equation.
I've just moved all of my original images from the google Drive folder into their own folder on my E: drive, I thn opened Capture one and all of my images loaded first time. π
So far so good...
Now I have Capture One looking for the original images in a directory that isn't there any more so it says that all of the images are 'Offline'.
So how can I tell capture One where all of the new images are now located bearing in mind that we're talking about 1000's of images over multiple catalogues?
Richard0 -
Richard,
This is a sensible test to undertake and if the problem is to do with opening the files (as seems likely) the catalogue would open because it can't find the folder and at that point has no interest in going looking for the files.
However you should perhaps think of it as a temporary situation (for now). Bear in mind that you only have problems with the current year catalogue. If all the catalogues had their files in the E: Google Drive folder previously what was different about 2016 compared to earlier years that seemed to work without freezing or crashing?
Was 2016 active and the others not?
Or something like that ....
I would not yet seek to re-locate all of the files for all of the catalogues. Just do 2016 (or even one or two days of 2016 that have been noted as problems if that is possible) and see what happens.
As I don't use catalogues I'm not really familiar with the process you need but I believe there is a option on the menu to go and locate the absent files - often discussed in the forum although perhaps most commonly in the Mac section.
Grant0 -
I agree, in order to really be sure Google drive together with C1 caused the issues, I would try working with C1 for a few days.
I would copy all C1 files (i.e. the catalog) and all folders (Adjustments, Cache,...), not only the raw files, out of the realm of google drive.
To make your raw images online again you have to rename the original top folder so that C1 not only says your images are offline but also enables the "Locate" (folder) in the context menu item in the library tool. Then you can choose the new top folder. This usually works but I have some images for which it didn't, not sure it was related to my network storage, such images would stay offline until located one by one.
Alternatively, you maybe can reconfigure google drive to synchronize a different folder and stay with your C1 where it is?
Please report back if this is really the final solution. π
Cheers
BeO0 -
Grant, I've been there too (not in the shop but on the island) and enjoyed the wine too... π
Local wine tastes best when enjoyed locally π0 -
[quote="BeO" wrote:
I agree, in order to really be sure Google drive together with C1 caused the issues, I would try working with C1 for a few days.
I would copy all C1 files (i.e. the catalog) and all folders (Adjustments, Cache,...), not only the raw files, out of the realm of google drive.
To make your raw images online again you have to rename the original top folder so that C1 not only says your images are offline but also enables the "Locate" (folder) in the context menu item in the library tool. Then you can choose the new top folder. This usually works but I have some images for which it didn't, not sure it was related to my network storage, such images would stay offline until located one by one.
Alternatively, you maybe can reconfigure google drive to synchronize a different folder and stay with your C1 where it is?
Please report back if this is really the final solution. π
Cheers
BeO
I have just spent half an hour wondering how to get Locate to come alive. It's not in the Help as far as I could find.
You have to rename the original folder? Hmm.
Indeed Rename in Explorer since it's not possible, as far as I can see, from within C1 and, if it was, in some situation Locate would not be required..
OK, well, I guess it works and if you had moved the entire folder and renaming is, in effect, the equivalent of moving the entire folder.
Simple enough but a little obscure and non-intuitive at first sight.
Grant0 -
yes, as long as C1 finds the original (empty) folder (not moved, not renamed) it just thinks "uups the images are missing", and locate folder seems not necessary, only the images. If C1 can't find the folder as such, then it allows to locate it. 0 -
Richard,
I decided to Google about Google Drive to see if I could uncover any information about how it works, lock files and stuff like that.
Most of what I have found so far is 2 or 3 years old but basically says, leaving out the detail, that it doesn't really work at all. Except in a few circumstances and if you don't push it too hard.
Things may have changed in the past periods but personally I would be very tempted to follow through with what you have done so far and see what happens with the files on your E: drive but not connected to the Google Drive service folder.
FWIW I know I can successfully keep sessions on an external drive and access them directly (with occasional small glitches with response times if I let the drives spin down) so the E: drive itself should not be a concern (at the moment). If the drive was failing (I had one a few year back that slowly lost the will to write to disk although reading was fine. It was external and had inadvertently been dragged of the desk a few times .... probably did not help.) it might appear to freeze but in fact would probably still show some very slow activity.
BeO,
OK, thanks. I understand that now. The question is will I remember it in the future when I might need it again?
It would be most interesting to be able to invoke a system search that one feeds the missing files to by name (and maybe a few other parameters for greater sophistication) and then waits to see what is found. Automatching ought to be possible in many cases.
But then just how often would most people need such a facility?
Grant0 -
[quote="SFA" wrote:
It would be most interesting to be able to invoke a system search that one feeds the missing files to by name (and maybe a few other parameters for greater sophistication) and then waits to see what is found. Automatching ought to be possible in many cases.
I fully agree. If I remember right a user in this forum recently told that Aperture has such a feature which actually works fine. (And C1 does not under certain circumstances, I have a about hundred images which are not found by the locate folder feature.[quote="SFA" wrote:
But then just how often would most people need such a facility?
My workflow until recently was that I used to store my most recent raw files on the notebook, after finishing most of my images / adjustments I moved them over to my NAS for permanent storage. I moved them (the respective folders) sometimes via explorer (or robocopy) (and then used locate), sometimes I used the explorer to create the folders only and moved the images then within C1.
I sometimes rename my raw file folders or regroup sub folders (cannot be done within C1)
Now that I have a new computer and also need to locate function. The permanant storage is /will be on an internal drive so no need to move them to the NAS anymore.
Anyhow, there are a few occasions where locating folder and images are necessary, imo.
If you work with sessions like you do it seems to be a different story I think.
cheers
BeO0 -
Yesterday evening I started up Capture One and my 2016 catalogue opened and worked as it should.
This morning I tried it again and I was back to Capture one not loading all of its images and freezing.
I then turned off Google Drive so the original images (and it is only the original images that are store here) aren't being accessed by google and opened Capture One, the result I got when opening is here https://drive.google.com/file/d/0BzpHeS ... sp=sharing
Back to square one... ;(
Regards,
Richard0 -
Richard,
Once you are 100% sure google drive is ruled out (disabled) for all C1 files and folders, you might want to share a new set of log files?
Cheers
BeO
Edit: Nice image, btw... π0 -
Google was 100% turned off.
I would try moving all of my original images to a new loacation outside of the Google folder but when I attempted that yesterday I fould that Capture One was telling me that all of my images were off-line.
I used the 'Locate' feature but could only do this for one image at a time (not suitable when I have 1000's of images) and then found that when I did use the Locate feature the image I used it on vanished, permanently; I still have no idea where it went to! I did a search through my computer and couldn't find it and looked in the Trash but to no avail.
I'm not willing to do that with 1000's of images.
Regards,
Richard0 -
Richard,
I think it would be a good idea to copy all of your originals so far for 2016 to another clean new folder and, given there are still only a few hundred at the moment, create a new catalogue (2016b?) from those files. No edits to be carried over, just and entirely fresh catalogue and then see what happens to that.
Right now there are so many factors that might or might not be influential (but are "visible") that I think you need to assess them one step at a time to make sure things are basically working at the simplest level.
For example, if you have something strange and intermittent happening with part of the hardware (such things are not unknown) it would likely show up when stepping through a clean start catalogue creation. It might not .... but if you do see problems at that point then anything that may or may not be happening related to GD is likely to be a separate issue.
In general the log files report some evident crashes but there is not much that I can see that offers useful clues about the "freezing". Christian may have something on that but from my perspective I have yet to see any log lines written around the time of a freeze that I do not also see in the logs from my system running sessions and not freezing.
Whether the Windows event log (if one can identify which of the many records might be relevant) could help here I don't know. I would guess possibly but would have to seek confirmation elsewhere.
It's certainly an interesting challenge.
Grant0 -
Grant, Beo and Christoper,
I've just had a response from Technical Support where they stated...
"as a workaround please disable sidecar XMP sync to see if this solves the issue. set "auto sync side XMP to NONE" and then only check the prefer sidecar XMP over embedded medata, (or click ΓΒ΄the defaults button)"
I tried this an low and behold capture One opened, allowed me to edit images and closed down as it should.
Hopefully this might, at last, solve my problem.
For the rest of the day I'll open and close Capture one, edit images and shut down and re-start my computer to give it a good 'shakedown' so to speak.
I did mention to Technical Support that if this was the problem then they might want to 'sort it oput' in any future updates.
I'll get back to you tomorrow to let you know how I, and Capture One, are doing.
Crosses fingers and toes just to be sure... π0 -
Richard,
I'm hoping that the XMP Load turns out to be the challenge so that at least you know what it is.
Do you need to use that facility?
I had noticed it and was, at some point, thinking it ought to be turned off as a test. However since it applied to old catalogues that were not currently causing problems as well as the 2016 catalogue AND still applied even if there were no problems in open to close edit session it was a target but not quite a front line target.
Lack of a clear and specific reported task line in the logs (so far as the inexperienced eye can tell) certainly did not raise its profile!
XMP files are another facility I don't use that that black art is lost to me in terms of understanding anything in detail about how it does what it does, when and, frankly, why!
Should we assume that, for the future, no news is good news?
Grant0 -
Grant,
I did point out that maybe technical support should look into this as an issue and include a fix in a future update. If a feature is there it should work as described and not cause problems.
So far, re-starting my computer and opening and closing Capture One multiple times hasn't caused any problems and Capture One is still working as it should do.
I did find it easier to add the metadata to images in Lightroom and then let Capture One pick it up via the XMP files. I'll now do all of my metadata within Capture One.
So it looks like the XMP feature was the problem.
Going back to Lightroom to do some editing (whilst I was having problems with Capture One) showed my just how good Capture One is. My images in Lightroom never quite looked as good as I thought they should do, in Capture One they do.
Regards,
Richard0 -
[quote="Richard_Allen" wrote:
Grant,
I did point out that maybe technical support should look into this as an issue and include a fix in a future update. If a feature is there it should work as described and not cause problems.
True enough although one would assume that the expectation is that it should work - hence the amount of time it has taken to isolate it as a problem.
The thing is though, just how does it work?
LR, presumably, creates a file and leaves it somewhere and C1 finds it, reads it and records the information it supplied. Or, perhaps, just reads it as as - always. So the file is constantly being read to see if anything has changed. Maybe?
Where is the file? Is it always accessible? Is it subject to other influences for availability and accessibility?
As I don't use XMP fles I have no feeling for how C1 deals with the functional needs. It will be interesting to find out.
Glad everything is rattling along for you now. I assume you could find a way to manage the metadata transfer as a planned batch exchange if required.
Grant0 -
[quote="BeO" wrote:
"XMP Sync is set to : Load"
Do you need this?
We now have the answer, however eliminating this is also a good idea. If not google drive than LR and C1 might have caused a deadlock on the xmp files when both trying to read or write...
Good luck, glad you like C1 image quality which hopefully rewards you for the huzzle π0 -
[quote="BeO" wrote:
[quote="BeO" wrote:
"XMP Sync is set to : Load"
Do you need this?
We now have the answer, however eliminating this is also a good idea. If not google drive than LR and C1 might have caused a deadlock on the xmp files when both trying to read or write...
Good luck, glad you like C1 image quality which hopefully rewards you for the huzzle π
Good point! I remember now that I mentally noted that you had made that observation.
Grant0 -
I thought it was too good to be true...
Capture one was working as it should do for a few days but has 'hung' again.
I've sent a new CaptureOne.dmp file to technical support to see what they have to say.
They had said that all of my frevious 'Dump' files and Crash Reports ahd been sent through to R&D0 -
Richard,
Do you have C1 set to Automatically backup your catalogue?
Also, on a very long shot, have you checked whether the XML file preferences are still set as recommended when the problem seemed to go away?
Grant0 -
[quote="SFA" wrote:
Richard,
Do you have C1 set to Automatically backup your catalogue?
The Backup is set to remind me once a week.
Also, on a very long shot, have you checked whether the XML file preferences are still set as recommended when the problem seemed to go away?
I think you mean XMP? This is set the the defaults of Never and with nothing ticked.
I re-started Capture One and it's still going strong, working as it should although on checking the Catalogue Database (after it hanging) it said that it was corrupt, so I fixed it using the auto feature for this.
Grant0 -
[quote="Richard_Allen" wrote:
[quote="SFA" wrote:
Richard,
Do you have C1 set to Automatically backup your catalogue?
The Backup is set to remind me once a week.
Also, on a very long shot, have you checked whether the XML file preferences are still set as recommended when the problem seemed to go away?
I think you mean XMP? This is set the the defaults of Never and with nothing ticked.
I re-started Capture One and it's still going strong, working as it should although on checking the Catalogue Database (after it hanging) it said that it was corrupt, so I fixed it using the auto feature for this.
Grant
Hi Richard, you are quite correct - XMP. Poor proof reading on my part.
I just wondered if, somehow, the system might have picked up old preferences settings - seemed like a good idea to check that they were still correct.
You may have stumbled across something left over in the DB from previous problems and kill actions or blue screens. Hopefully the repair will have resolved it or them.
Grant0
Post is closed for comments.
Comments
83 comments