Aller au contenu principal

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

Time to move on.....

Commentaires

2 commentaires

  • Ulf Liljegren
    Ian

    I would love to prove you wrong and there might be reasons why you are experiencing things you where but to be honest you have never given us the chance to help you out.

    I took the liberty and looking up it you had ever been in contact with Phase One Technical Support and you have not.

    I hope you will reconsider and contact technical support at http://support.phaseone.com and allow you to help you.

    It has been a interesting transition time to Capture One 4 where we learn something new all the time. Capture One 3.7.x was a very good application but that is after years of work. Capture One 4 has clearly since it launch been proven to stabilize and has gotten features implemented faster then ever seen before.

    If there is something specific in your system that is causing instability the let us help you. Maybe there is something on your computer causing this or there might something in the application that has to be corrected. Either way there is everything to win and nothing to loose except a few minutes of your time which you might win back by us providing you with a better application.
    0
  • Ian A
    Ulf-

    Thank you very much for taking the time to reply to my ramblings. 😊

    While you are correct that I had not opened any support cases for any crash problems I had seen, I had in fact used the Crash Reporting mechanism that used to be built in to Capture One to report every crash that I encountered. In the early days of 4.0, this was a daily occurrence, sometimes multiple times per day. And the particular crash I used to experience (which now looks like it may have returned in the last version of 4.5 that I downloaded) was dismissed by Ole Wahlgreen, who replied to my comments on Feb 25th, as a problem only I was seeing and could not be recreated by the developers. (He was very thorough in his questions and appeared to do a pretty good job of collecting the information he needed) Needless to say I was more than a little surprised to see that the next release informed in the release notes that the problem I (alone!) had been experiencing, was now fixed!!!

    And sure enough, it remained fixed until 4.5.2, when the problem reappeared. Unfortunately, the crash reporting mechanism had been removed (too many reports, perhaps?) and I no longer had a way to send anything meaningful (i.e. machine state, core dumps or whatever useful info you guys generated through the crash reporter) to you.

    I guess that felt like the last straw. With my confidence in the product now ebbing, this has spurred me to try out Lightroom. I'm sure I will be keeping an eye on updates to C1 and keep trying them until I feel it has its old stability back. But until then I will move forward with Lightroom, enjoying the increased feature set and better image management than is provided with C1.

    However, should I encounter problems any time I switch back over to C1 then rest assured I will follow your directions and open up support cases to cover those events.

    Sincerely,

    Ian
    0

Cette publication n’accepte pas de commentaire.