Process Recipe Problem! Processing wrong images.
I was wondering if someone can please help me! I'm tearing my hair out right now... :(
I've been a long term user since I can remember of Capture One, as both a photographer and a digi-tech, running on both Mac and PCs. I recently upgraded to Capture 21 and not sure if this is a new issue?
I've just finished a bit retouching job, and went to my usual process recipes to send to the client, exporting both TIFFs and JEPGs of all the images. I checked my Output folder to realise that instead of two versions of each of the 30 or so images in total, its now just giving me multiple versions of the two or three of the files?!?
That the heck is going wrong?!? It's been absolute bullet proofs stable and now I can't even export the files? Can anyone please help as I need to get this fixed asap with a lot of upcoming work on!
PS: On my main editing machine I'm running CO 21 on a Windows 10 machine, alongside a Macbook Pro running C0 21 too.
Thanks everyone in advance for any help you can give me!
Best wishes,
Gavin
-
Hi Peter & SFA,
Sorry it's been a while on this thread, just life among other things...!
Anyway, I got back on top of this issue as I wanted to sort it out once and for all!!!
After much pulling my hair and fair number of expletives I just decided to remove everything c1 related from Windows 10 machine and go for a completely clean install of the latest version of the software. I used the newest version available which is 14.0.2.36 .
So.... it worked!!! So far it's been working well, and the previous issues I had noticed, particularly with the troublesome exports from the same commercial session have all cleared up (so far so good, fingers crossed!). The client came back to me a few days asking for anthor set sent to their web desinger, and I was able to export everything as I wanted, using two separate recipes to generate full size JPEGs and 8bit Adobe TIFFs.
I would note that firstly I uninstalled the program with the regular uninstaller. I then went and searched for all the files I could find, all those sneaky setup and config stuff locoated in App Data for example, just to try and completely erradicate everything, from this current version as well as past updates.
The down side was that sadly I lost all my C1 setttings, shortcuts, workspaces and recipes, but I scribbled everything down on paper and took screen grabs so it was easy to put it all back in 30 mins or so.
I hope this help folks?
All the best,
G
0 -
Gavin,
Glad you seem to have is fully sorted.
Most of the Appdata stuff is unlikely to be part of the problem - although the personalised settings may also be unused these days if they were created years ago!.
Temp and Windows work files would be fairly likely as problem sources. One odd one that might take some time to analyze unless one was a developer would be the user.config file that also resides in the Appdata area thee days. That is dynamically adjusted as one works with C1. Its effect, if any, could be tested quite easily by making any current files non-available. move them somewhere or, in an extreme case, delete it/them.
One action that seemed to make Windows clean up old temp and work files more effectively (or at least eliminate them from consideration as a problem source) was to re-boot the system 2 or 3 times without starting an application.
My rationale for that is that there may be a series of file dependencies produced during a process. If the clean up process is doing a sensible job and finds a file that has a later dependency file not yet assessed for redundancy and possible deletion it should probably skip it. It may not be a process written to re-visit the files it has previously skipped.
Running the clean up process again (via another reboot) would revisit the skipped files. If the dependent file has already been deleted then the previous skipped file no longer has to be retained and can also be deleted.
And so on.
It's an extreme case and probably more likely to be a factor after a period of instability where processes may have left files orphaned when a system crashed. However It does seem to have worked for me on a number of occasions. It might have been coincidence but only takes a few minutes to run the processes so certainly worth trying. It's especially quick if running an SSD based system!
0 -
Hey SFA,
You could be spot on there, it was around the time (earlier this week) that I was doing a big clean up of my system, running some applications to clear old temp files, update old drivers etc, so that most likely had a positive effect too.
So far it seems to be working, but I'm sure it was definitely doing a combination of a deep system clean-up, combined with a completely "fresh" install that somehow did that trick!
At least if it happens again I now know how to fix it without too much trouble!
All the best,
G
0
投稿コメントは受け付けていません。
コメント
33件のコメント