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. ⚠️

Is it just me or is C1 20 extremely buggy?

Comments

3 comments

  • Keith Reeder

    I am getting increasingly curious about the users not having problems with it

    That this group seems to be hugely in the majority, it does rather suggest that your problems aren't with Capture One...

    0
  • Michael Goodwin

    What are you suggesting here Keith Reeder?

    Are you saying that the problem is my computer, my cameras, my lenses, or that the problem lies between my ears?

    I understand I am not looking for answers to problems in my post. It is a rant indeed. But your offering what exactly here?

    0
  • SFA

    Michael,

    I have been using C1 for about a decade or so and have rarely had any significant problems  - maybe a couple of things that took some discovery and resolution and which seemed to be random events that could not be willingly reproduced. No more issues that I have had with any other software I regularly use or have used running Windows. (I'm mainly looking at Win 7 here. I avoided the interesting development period of Win 10).

    To be fair I do not use catalogs. I could see that the catalog concept offers greater potential for "interesting" data management events.

    You mention copying a catalog from one system to another and importing to an existing catalog. It is not directly compatible but a Session set up and managed as intended by default structures is a very easy thing to manage and more than likely a reasonably sensible size. I could imagine that a catalog would be far more work especially if using referenced folders.

     

    In general, for my needs, problems are few and very far between and I suspect that is the case, relatively speaking, for the majority of users. I have no doubt that some users have severe problems  - perhaps more sever amongst Mac users than Windows users based on what can be read in the forums - but they are clearly not all down to fundamental problems with the application. If they were everyone would have the same problems. 

    Win 7 seemed fairly stable. Usually I could do almost anything with total disregard for what Windows was doing for memory and disk management and get away with it. Now and again  - very rarely - I might get to a situation where nothing happens when a command is entered - something like your delete description. Clearly that means that something on the process is stuck for some reason or an intermediary instruction or settings file, perhaps floating around in memory, has become corrupt somehow. Maybe what had been doing had resulted in a recursive activity to a process not yet finished - something like that. So long as a restart or a re-boot resolves the problem it's not a big deal as far as I am concerned. Given that I regularly run with local disks full I am amazed that Windows, using an SSD, is so forgiving.

    I may have been lucky with my hardware selection 8 years ago when I had to upgrade to move to 64bit. Perhaps that luck provides me with a better experience that other experience.

    For what it's worth when buying a new device a few weeks ago in order to "enjoy" the Win 10 experience for the first time I returned to the same supplier and the equivalent level of system that I purchased 8 year ago.

    So far so good, although this machine does seem to get extremely hot for a laptop. 

    Win 10 has some things I like a lot and some I am less keen about. Also, for some reason, this device seems to take two bites at Wi-Fi connectivity after it has been woken up. Just when you think the reload after hibernation has completed it seems to pause and take second opinion. I have yet to work out why. It would be very easy to end up with some typed ahead instructions that would be invisible until the pause had finished. Good potential for causing havoc if one forgets and in impatient.

    But in general it seems to work well and Win10 manages maxed out memory use (I will be adding more memory and disks - that was always part of the plan) across multiple heavy usage applications without any evident problems so far.  Whether all systems would do that I don't know. This one seems very competent and does better than I would have expected.

    As a fellow Canon user I can only observe that I like the results I seem and lenses are correctly applied unless I have my 2x adapter attached. But for those lenses use regularly (and that are not 100% manual anyway) the auto correction, such as seems to be required if required, is applied every time. Whether or not that matters at all in terms of the ultimate use of the images I am not sure. Probably not. But it's done so I'm happy with it.

    SO from my perspective, as you can probably tell, I have a rather different user experience to how you describe your experience. Why they should be so different I cannot explain, obviously, but it seems that they are. Clearly that does not help you but maybe it offers a little bit of an alternative perspective.

    0

Post is closed for comments.