Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

CO 8.0.1 is still buggy and unstable

Vaughn
I am not a big complainer and I certainly don't point fingers. I just wish that this CO would work. I've written earlier and pointed out that I've been using CO since probably version 5. I have never had the problems I now have.

I am trying it edit a collegiate soccer game I just shot. I probably started with about 500 files, and I am deleting quite a few for various reasons. After a number of deletions, the keys don't work such as the delete key. At that point I need to shut down CO and start it again. I have tried ULC auto and never, no difference. I just had CO crash and I have to start it again. I have never had that problem before.

My machine is not trivial. I am not bragging and I know that there are better than mine. I have Windows 7 64-bit with Core i7 @ 3.5 Ghz. I have 16 gigs of usable memory.

I don't want to complain—I just want CO to work!

Vaughn
0

Comments

5 comments

Date Votes
  • SFA
    Vaughn,

    First question - have you created a support case?

    Second question - have you looked at the log file to see what is reported?

    Third question - are you using session or catalog? If session, do you create a new session for each project?

    Fourth Question - are you running on an internal drive or something external? If external is is a network share or a variety of USB (?Firewire) connection? What sort of drive - SSD, spinning platter or hybrid?

    I have a similar machine spec to the one you describe.

    Running on its internal SSD I have no problems at all.

    Running on a fast external HDD using USB3 works pretty well BUT quite frequently things slow or pause for a while - usually some seconds - leaving C1 unresponsive for an extended period. I can see there is disk activity of some sort - could be Windows rather than C1 (or any other applications that is running). Eventually things come back.

    If the disk has not been active for a while it may also display poor response as it "wakes up" and re-establishes connection with the computer and C1 - or any other application that has been using it or needs to read data from it.

    When things stall I always find it tempting to keep hitting keys and doing so often enough can build a string of commands into the buffer that may overload the application when it starts to respond again thus crashing the current application more often than not.

    Beyond that some other things that might be happening but no obvious.

    There are some specific windows commands related to the deliberate use of repeated keystrokes that may be inadvertently activated from time to time.

    Likewise there are system commands that might be instigated unknowingly. Accidental key strokes (I use a notebook and often find the cursor jumping around when editing text. I assume I am inadvertently causing this by (it just happened ....!) touching the touchpad but after some months I have still not observed such a thing happening when the problem arises. I have also cleaned and vacuumed the keybaord just in case ....

    The only other thing I would observe is that I don't use delete very much. For the sake of the investigation me might consider whether using delete might be part of the problem. It seems doubtful but we need to eliminate it. But first it would make sense to see what the log file(s) tell us. Or, better, what they tell the Support Team at Phase One.


    HTH.


    Grant
    0
  • Vaughn
    Wow! Good questions.

    I created a support case pretty soon after my install of CO 8. in September.
    If log file is My Cases, yes, I followed and watched. Support says that they have seen this with Windows 7. I never did, but sensed a general lack of interest in helping.
    I run sessions. No, I never have created a separate session for each job. (I don't even now understand catalogs, but I think that my workflow is better with sessions).
    I run only on internal hard drives. I have two 2-terabyte drives, one which is kind of full, but all the sports from September to now is on the newer one which is almost empty.
    Using the soccer game as an example, I was reviewing the match and deleting as I went. There was definitely no time for the drive to go to sleep. Quite the opposite, it seems like CO freezes after a number of deletions. But there is a delay between deletions 'cause I have to move to the next image and look at it first.
    I understand your comment about wanting to keep hitting the delete key. After the first no response, I will wait, but nothing happens. Then in frustration I'll hit the delete key again, but I have waited for the deletion to occur. Remember that I've been using CO and this method of reviewing files for several versions now. CO 8 is the first to act this way.
    Finally, I'm not sure what the Log Files are. Where do I find them? I'll certainly be happy to copy and send them to Support if that would fix the problem.

    Thank you so much for your extended answer.

    Vaughn
    0
  • SFA
    Hi Vaughn,

    The Log files will most likely be here:

    C:\Users\<Your User Name>\AppData\Local\CaptureOne\Logs

    If not run a systemwide search for *.log or Capture*.log and you should find them UNLESS your user name account has restricted access for some reason in which case a folder somewhere in the path may be hidden. See what you find and lets take things from there.

    Meanwhile - and probably the first thing to experiment with - I would suggest creating a new session - any name you like but not the one you currently use - and work with that on your most recent shoot project.

    Go through the same process as you did already and see what happens. (I'm thinking the selection process and deleting rather than taking the time to do full detailed editing at this point. Just trying to establish whether the same problem appears with an all new session.)

    One time about 18 months ago using V7 I had a situation that sound similar to what you see. For some reason unknown a session started to play up and crash seemingly rather randomly as I was sequentially process the images having previously dived in to the set (about 2000 as I recall) to pick a few for early processing and distribution.

    There seemed to be no real pattern to the problem but it would occur every 10 images or thereabouts. By chance I spotted a corrupt preview file in the set. Recreating the preview left it corrupt still. So I deleted the edit file (deleting from within the session and re-importing the RAW as I recall) and re-edited from the RAW and everything was fine

    My assumption was that something (no real idea what) had caused the edit file to 'go bad' somehow and that in turn had effectively messed up the links between files in the COSession database file. Thus from time to to time as you move to a new file (or perhaps try to delete an existing file) the links in the database are unexpectedly just wrong and C1 is unable to work out what to do so seems to hang and then crashes either of its own volition after a while or because we keep hitting keys and the Windows buffer overflows or something along those line.

    If you can spot a corrupt preview try deleting it as I did. However if not just go for a new "clean" session and see what happens.

    Do you import files to the session or just navigate to the folder(s) you need? To test the theory I don't think it would matter which way you go but I am slightly concerned that it C1 see existing edits it may use them and in such a case is there is also a problem with such a file you might still get the problem. We may need to take a couple of stabs at this idea if that happens - there is no certainty that the issue I saw and managed to resolve is the same as the one that you are seeing. It's still worth trying though.


    HTH.


    Grant
    0
  • Vaughn
    Yipee! I started a new session and have edited for an hour or so with lots of deletions. No freezes.

    I think the problem is solved. Hope so.

    Thank you so much.

    Editing and processing is time consuming as it is and to have the frustration was really getting to me.

    Vaughn
    0
  • SFA
    [quote="Vaughn" wrote:
    Yipee! I started a new session and have edited for an hour or so with lots of deletions. No freezes.

    I think the problem is solved. Hope so.

    Thank you so much.

    Editing and processing is time consuming as it is and to have the frustration was really getting to me.

    Vaughn


    Excellent news Vaughn. Well done.

    It might be a useful idea to complete the immediate project and then go back to the original session to see if you can spot any potential problem thumbnails. If so we could investigate them in greater detail to see if the cause of the problem becomes evident. It may not.

    I would suggest that you stick with the new session (or create a new session for each shoot as I mostly do) for future use.

    If you are likely to need to go back to the old session from time to time to deal with images therein it could still be worth doing some deeper analysis on it when time allows.


    Grant
    0

Post is closed for comments.