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

Processing adjusted images

Michael Sonshine
Since no one else is reporting this issue I understand it is unique to my machine, but I don't see what could be wrong ...

I am running 9.2 (9.2.0.97) and started to process some images this afternoon. After I completed the adjustments I filtered for those I wanted, selected them, selected a processing recipe, made sure that the Destination was set, hit the process button and got up and did something else while it processed. When I got back I realized that nothing had processed and the 33 images, which should have taken about 2 or 3 minutes, had not even had one image written out.

I stopped the processing, removed the jobs from the library folder, selected them again and started again. Still, nothing.

I stopped the processing, removed the jobs, quit C1, restarted C1 and restarted processing. Still nothing.

I stopped the processing, removed the jobs, rebooted, started C1 and restarted processing. Still nothing.

I have tried the Processing icon at the top of the screen, I have tried right-clicking on a selected image and I have tried pressing the Process button in the Process section, all with no effect. The process display (that circling icon that shows up next to the top level toolbar) just keeps circling, but nothing processes. I know I must be doing something wrong but I have no idea what it might be. I have no message from C1 telling me of an error. The only thing left that I can think of is to reinstall C1 and that seems like overkill. Does anyone have any helpful suggestions?

Thank you.

If it is helpful - I am using a Catalog set to leave the files in place. The files being processed are resident on an external usb drive, not on my main SSD.
0

Comments

7 comments

Date Votes
  • Ian Wilson
    Moderator
    Top Commenter
    Mike

    I wonder whether it would be worth moving a small sample of images to a folder on the computer, rather than on an external drive, and seeing whether they can be processed from there This would at least test whether it is to do with where they are located.

    Ian
    0
  • Michael Sonshine
    [quote="Ian3" wrote:

    I wonder whether it would be worth moving a small sample of images to a folder on the computer, rather than on an external drive, and seeing whether they can be processed from there This would at least test whether it is to do with where they are located.

    It seemed like a good suggestion so I tried it. I move a handful of the images to the main SSD, adjusted a couple and tried to process them. Same result. The twirling circle indicating processing twirled and twirled, but nothing got processed.

    I should mention that I have been using the same setup (C1 installed on the main SSD, raw images storied on an external usb 3 flash drive, processing to jpgs/tiffs and calling external pixel editors using the external ssd and processing to the flash drive) for a long time now without any error. It is only since the installation of 9.2 that this problem has occurred. I will next reinstall C1 as I don't seem to have a choice. Nothing else has fixed this issue and if, as I assume, this is either something I have done to C1 myself or something having to do with software on my system, I have no idea what that might be.

    Thanks for the suggestion.

    UPDATE:

    Well, for what it is worth, reinstalling did not help either.
    0
  • Frank.O
    Mike,

    reinstalling may not help if you didn’t completely remove the program and all it’s traces before (plist).

    If you think that some setting you made caused this you may want to try deleting the preference file so a new one ist built up from scratch.

    PLISTs are cached by a system service in MacOS and for changes on the plist-file to take effect you have to empty that cache by restarting your computer or killing that service immediately after applying changes to the plist. Otherwise the plist will be restored to its old state upon the next start of the application it belongs to.

    -So first close CO9 and move ~/Library/Preferences/com.phaseone.captureone9.plist to the desktop
    -open activity monitor and look for a process named cfprefsd, there should be two, one running under root and one under your user name
    -kill the one running under your user name, it will restart on its own
    -close activity monitor, launch CO9 and check
    -you may have to rearrange things in C1 afterwards

    Regards,
    Frank
    0
  • peter Frings
    Did you try exporting these images? If that works, you can rule out problem with the images.
    Did you try another recipe? Make one from scratch and see if that works?
    0
  • Michael Sonshine
    [quote="peter.f" wrote:
    Did you try exporting these images? If that works, you can rule out problem with the images.
    Did you try another recipe? Make one from scratch and see if that works?

    I did try creating a new recipe, but that made no difference. What I finally did that fixed the problem is go to the library folder for CaptureOne and rename it. That forced CaptureOne to create a completely new folder structure when it next started and that solved the problem, whatever it was.

    What I had not done (because I had not see it before I did the above) was what Frank.O suggested. I am going to restore my folder system (along with my workspace) and try what he suggested.
    0
  • Michael Sonshine
    [quote="Frank.O" wrote:
    Mike,

    reinstalling may not help if you didn’t completely remove the program and all it’s traces before (plist).

    If you think that some setting you made caused this you may want to try deleting the preference file so a new one ist built up from scratch.

    PLISTs are cached by a system service in MacOS and for changes on the plist-file to take effect you have to empty that cache by restarting your computer or killing that service immediately after applying changes to the plist. Otherwise the plist will be restored to its old state upon the next start of the application it belongs to.

    -So first close CO9 and move ~/Library/Preferences/com.phaseone.captureone9.plist to the desktop
    -open activity monitor and look for a process named cfprefsd, there should be two, one running under root and one under your user name
    -kill the one running under your user name, it will restart on its own
    -close activity monitor, launch CO9 and check
    -you may have to rearrange things in C1 afterwards

    Regards,
    Frank

    Thank you. I am going to try this and I will let you know if it works.

    As I responded above I fixed the problem by renaming the entire CaptureOne library folder and thus forced CaptureOne to create a new one. I am going to restore the old one and try what you suggested as well. The more I know about how all of this works the less likely I am to be surprised again.

    Thank you for your post.
    0
  • Michael Sonshine
    For anyone keeping up with this thread - I have had some interesting further discoveries and wanted to post them just in case someone else has this problem.

    1) My statement that the problem was solved by removing the CaptureOne folder structure in Library was wrong. What actually happened was that when C1 re-created the folder structure it used its default values for the recipe I was using. Those default values worked (and hence I posted my response indicating that the problem had been solved).

    2) When I took the default recipe that worked and changed the values to write the output jpgs to a subfolder of my image folder on my usb3 drive (instead of the output folder on the ssd) the system again did not work.

    3) When I changed the output to be back on the ssd the processing worked again.

    Hence it seems clear that choosing to write the output jpgs to a subfolder of the image folder on the usb3 drive creates a recipe that will not actually process. Changing the output folder to the main ssd solves the issue. The thing is that I have been using this same recipe (raw images stored on an external usb3 drive, outputs written to a subfolder of the image folder) for years (literally) and it has always worked. It worked with the beta versions I have been testing but no longer works for me on 9.2

    I have filed a bug report.
    0

Post is closed for comments.