Capture One 22 not exporting
I'm having trouble exporting files.
Capture One won't process the selected files, a pop up window is saying 'could not process file' while the export window adds more and more time to the window telling me how much time is left to process.
Looking at the pop up window the issue seems to be that Capture One ignores the Export location I have set and is trying to export to a different drive that has not been connected to my laptop in days.
I have reset the Export Location, closed and re-opened Capture, connected and disconnected the external drive I'm exporting to, tried to export directly onto my mac but all with no success.
Any advice on what to do? About to miss important deadlines...
Thank you!
-
Similar issue. C1 15.2 [on a Mac mini M1 running Monterey] was exporting just fine up until a few hours ago. Now, it doesn't matter what process I use, what format, or what location. C1 either does nothing or occasionally pops up this error message:
Description: There was an error during the processing of the output file.File: ~/Capture One Master Folder/San Francisco Mar 22/San Francisco Mar 22/Capture/IMG_3738.DNGDomain: com.captureone.captureoneCode: 1I've confirmed C1 has complete disk access in my security settings.0 -
Sorry to have missed the recommendation elsewhere to turn off Display & Processing Hardware Acceleration in the General preferences tab. This seems to have solved my problem.
0 -
Oh that's good to know!
My problem persists unfortunately and C1 will only export when a certain harddrive is connected even though I am not exporting to that hard drive. I have deleted and reinstalled C1, done a software update and just now I tried to turn off Display & Processing Hardware Acceleration but nothing helps.
If anyone has any other advice or tips and tricks I would highly appreciate it!
0 -
Catharina Pavitschitz how did this resolve for you? I am having the same issue. I am able to export to the new location but only when the prior hard drive is connected (even though that hard drive does not hold the images, the library, nor is it the export location).
0 -
@... Thanks for the suggestion. I've spent some time looking through the Mac system's folder hierarchy and cannot find a corresponding user.config file associated with C1.
0 -
@... Yes, I was in there too. Did a search and went through the folders one by one. No mention of a user.config file in there that I could locate.
0 -
On macOS look in ~/Library/Preferences for com.captureone files.
0 -
@... Sorry, but I am not finding the second folder in that location even when pasting into the Go as you suggest. Only the Capture One folder shows up.
Walter Rowe I do find references to the Teneré drive in two files in the Preferences folder as you suggest.
The first is as you see here:
The second is in the captureone16.plist file just below the first. Here's the section with the drive referenced opened in BBedit:
Can I safely edit these and save them back to their original location (i.e. replacing the original files)? What would the edits be?
0 -
So my issue was that there were two ways to set the export location and one was set to a harddrive I was not connected to and that is what created the error as capture one was trying to export to a drive that wasn't there.
I figured this out by clicking on the little arrow next to the sample path in the export location.
Maybe this helps? I didn't have to edit anything in the code to fix the issue
2 -
Walter Hergt .. yes you can.
0 -
In the second example, would you suggest I delete lines 63-67?
0 -
I would try deleting 64-66 and keep the array tags.
0 -
Walter Rowe Thanks very much for continuing to follow up. That did the trick. I have not touched the other file since that was related to focus stacking on the drive correctly mentioned.
Catharina Pavitschitz Thanks for the suggestion. My solution was a bit more involved!
0 -
Glad to hear that. Can you please submit a support case with all these details and how you fixed it? Include your screenshots above and description. This really should not cause the app to crash or fail to start.
0 -
You bet!
0
Please sign in to leave a comment.
Comments
15 comments