Zum Hauptinhalt gehen

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

Capture One Pro 8 not shutting down

Richard Allen
I hope that someone at Capture One might be able to help with regard to a problem that I am having regarding Capture One Pro 8 not shutting down completely in Windows 7.

The issue has evidently been raised before here... viewtopic.php?f=57&t=16994&st=0&sk=t&sd=a&hilit=not+closing

I haven't had a previous version of Capture One Pro on my computer as I am still new to this application and this is the only version I have ever used.

When shutting down Capture One Pro 8 the process for it can still be seen running by using the Task Manager; leaving it alone for a few hours and coming back to the computer I can still see it running in the background although not actually running as an application (if you see what I mean?).

I'm pretty sure that this can't be a problem with all of the other people who have had this problem so maybe the support team can look at it as being a 'problem/bug'?

I very much look forward to your comments... 😊

--------------------------

PS
By the way, even though I always tick the box to be notified when a reply is made I get no notification of any reply.
0

Kommentare

5 Kommentare

Datum Stimmen
  • SFA
    Richard,

    I did have a problem like that with an early release of V8 and it prevented C1 opening until the orphaned process was killed off.

    This, for me, was resolved at the 8.1 release if I recall correctly, or maybe one before.

    There was an interim solution as I recall which involved setting the Preference value for OpenCL to never (notably for Processing). In my case that was easy to accept as I use a Notebook Workstation and the GPUs available are not considered powerful enough to make them worth using compared to the main processor.

    I am currently running C1 8.1.1 on Windows 7 Pro with no problems when shutting down or starting up .

    The forum email for replies does not seem to be operational and, as far as I know, never has been.

    This is not uncommon on forums these days I find and, speaking personally, I'm actually quite grateful - less email clutter to tidy up and the volume of posts here is not usually so great the threads cannot be followed. However I can understand if you find it frustrating.



    HTH.



    Grant
    0
  • Richard Allen
    Thank you for taking the time to respond, it's very much appreciated.

    I have set both Display and Processing to Never and my problem still persists.

    I may have to upgrade my computer one day soon as it's a Dell Precision M6300 dating from 2008.
    0
  • SFA
    Hi Richard,

    Are you running the latest version?

    Have you re-booted the machine since the last time you closed C1 and killed the orphaned process?

    Are you using sessions or catalogs? I have no idea whether that would make any difference (I use sessions) but I wonder about the catalog backup routine.

    Is your Windows installation up do date with all the .NET stuff as well as WIndows 7? So many things that should not be involved but one can't rule out....

    If nothing works I would suggest you create a Support Case and send Phase the Log File. All the information provided helps to build a knowledge base of the interactions occurring which will hopefully benefit everyone in the future.

    FWIW I run a Precision M4700 purchased 2 years ago. It's a great machine. You probably don't have a SSD as the system disk in yours but when you change I heartily recommend you do.


    Grant
    0
  • Richard Allen
    I've re-booted the computer and it still doesn't close down properly.

    I'm using Catalogues.

    My Windows 7 installation is up to date.

    You're correct in that I don't have an SSD, well almost correct as I ordered the new Samsung 850 EVO SSD and it turned up yesterday; I just need to get a cable to connect it up and transfer files across before I install it.

    I'm hoping that with the SSD the increase in speed will help with Capture One. I'll let you know once I have the new drive installed.

    I'd also like to increase my RAM from the measly 4GB I have now to 8GB (the most this computer can take) but the cost of new RAM is about £160 which is NUTS!!! 😉 Being a pensioner now I can't afford that kind of money.
    0
  • SFA
    At the risk of this thread going a long way off topic ....

    The recent M6xxx series have spare disk slots. Not sure about the more venerable versions. If you can get a caddy you could use both drives but running the system form the SSD would still be best option.

    My 4700 came with a 512GB SSD (840) and had a spare mSata slot for a comms card. It seems to be half full SATA speed but took a 1TB mSata drive and is fast enough to be effective.

    It also came with 8GB RAM and 2 spare slots. So I added another 16GB. Being a more recent machine the memory is currently more commonly available and so more competitively priced. Sometimes upgrading the entire machine makes more sense than adding non-portable enhancements. You can move an SSD to a new machine but probably not the memory. Plus the new device will have improved speed in the internal components all of which greatly helps with applications like photo editing.

    I find that around 8GB RAM is where C1 (running a single Window - i.e. a single session) seems to peak most of the time. Running multiples it will creep up. Having a browser open with a lot of tabs at the same time and possibly some other applications can see it creeping up towards the 20GB mark. Very rarely does it go over that and then usually because something ungood has occurred with videos in the browser. All figures are approximate and based on observation.

    Have you checked the bus speed available for the SSD - will it limit performance?

    I'm not familiar with C1 performance using catalogues. I use sessions. I would think sessions would be easier on the system but I don't know. That's not why I use sessions though - I just prefer working that way.

    The problem I had with the orphaned program, when that suddenly occurred, is that C1 would not start up until the orphaned routine was killed. I think the startup code was modified initially to deal with this but then the problem went away anyway with a later release. Pretty sure it was 8.1.0 but might have been the 8.0.2 (?) release as I ran those a few days apart. If you are on 8.1.1 and still have the problem I would report it to Phase and send the log file so that they can make a recommendation. That said in my case it was a minor annoyance rather than a big problem ... but with a sufficiency of available memory and computing power (currently at least) I can afford to take that view.

    Have fun.


    Grant
    0

Post ist für Kommentare geschlossen.