No files were exported. Please check Events log for details.
Error Message "No files were exported. Please check Events log for details".
Mac OS Catalina 10.15.2 16. GB of Ram
Capture One 20 Fuji
-
What does the Events log report? -1 -
Files failed to export........
Additionally C1 Support emailed me and told me to disable OpenCL in the Preferences panel and stated C! is currently exhibiting issues with Open GL!!!! Im like what???? I did as stated it worked one time and started to exhibit the same issue. This is not a good look Phase One!!!! I have a catalogue I can't export images from I have 4 weddings due in a week and this crap started....0 -
Where are the raw files situated that you want to export output from? Where is the target location that you are trying to export to? Have you checked that both the source and destination locations are connected to the computer? Have you checked the read and write permissions on those locations? If you are trying to export from or to locations that are not on an internal drive, have you checked whether you are able to export with raw files on the internal drive to a location on the internal drive, or is there a problem with exporting even then?
Ian0 -
It doesnt matter where the images are housed, it doesnt matter if its a catalogue or a session. Support sent me this... I followed all the steps and still no bueno... I even reinstalled capture one 12 and same issue.....
https://support.captureone.com/hc/en-us/articles/360002404937-Troubleshooting-OpenCL-in-case-of-viewing-processing-exporting-problems
They have to find a remedy for this.... I am on a serious deadline here...0 -
So what happens if you restart the computer. Before opening any other apps, open Capture One to create a new empty session, add a couple of images. Create a new process recipe. Can you export them?
Ian0 -
I cannot export too! I don't know how to fix it. I did all things right but the photos weren't exported. I'm desperate... 0 -
NNN636734992295691259 wrote:
I cannot export too! I don't know how to fix it. I did all things right but the photos weren't exported. I'm desperate...
If you like to join a running thread, that is ok. But please be more specific than "I did all things right" if you want a meaningful reply.0 -
Having the same issue right now, on today's imported files.
Surprizingly enough "Process files" works.
But export brings me to the same problem "no file was exported" and the Event log doesn't say more..
MacOS Mojave
0 -
Are you using Export File or Export Variant (i.e. a File with edits.)
Session or Catalog?
Where are you exporting to?
0 -
It was Export Variants, from a Session, to a folder on the same SSD (the same folder where C1 successfully « processed » the files into JPG
0 -
Tried it also from Catalog, Export Variants, to the same SSD folder. Same result.
"Process" works, export variants not.
Appeared in 13.1.2 - never had this phenomenon before
0 -
Assuming all of the export settings are valid, I would try re-selecting the target folder to which you are exporting. The name may look right but the full link data under the name may not be correct.
I would expect the problem to be reported but it may be the sort of problem that is only really reported in detail in one of the C1 Log files.
I don't often use Export (Process is much preferred in my opinion unless round tripping) and and I'm on Windows so my observations may not be much use. But I do vaguely recall seeing this message and although I cannot recall the details the reason was due to something I was doing or some compromised setting I was re-using to select the output folder from a previous link that was incorrect for reasons unknown. Something like that.
0 -
Looks like you hit the jackpot !
I had several destination in a scroll list.
- The one not working was "C1 output" - but the path shown was correct.
- I changed to the second in the scroll list: "desktop". Export worked as expected
- I changed back to "C1 output" - still from the list. export worked as expected.
So for a reason I don't explain, the path to the Destination folder became corrupted when installing 13.1.2...
But now I have learned something :-)
Thank you for your help
0
Post is closed for comments.
Comments
13 comments