This just started to happen about two hours ago, I managed to export 4 files without problems. Then, I changed the watermark, and, since then, the exported files do not actually appear!
As I said, I DID change gthe watermaark..
Does anyone have any suggestions?
Do I need to do a reinstall?
When dealing with exported files not being produced, it can be frustrating and problematic, especially when you rely on those files for important tasks or projects. There are several possible reasons why exported files may not be generated, and it's important to troubleshoot the issue to identify the underlying cause to mayphunsuonganthinh
Firstly, ensure that you are following the correct export process and using the appropriate settings. Double-check the file format, destination folder, and any specific export options that need to be configured. Mistakes or oversights in these settings can prevent the files from being generated as expected.
Secondly, verify if you have sufficient disk space available. If the destination folder or drive is low on storage capacity, it may prevent the generation of exported files. Clearing up space or choosing a different destination with ample storage can help resolve this issue.
Additionally, check for any error messages or warnings that may appear during the export process. Error messages can provide valuable insights into the cause of the problem and guide you towards a solution. Look for any specific instructions or troubleshooting steps mentioned in the error messages and follow them accordingly.
^^ spam reply with dodgy link included. ^^
Thanks for the replies,..
In desperation I used "Open With" and sent the file to Apple Preview.. which presented it in nicely!
So, I tried save it and Apple OS said "No, you cant have a file name starting with . "
So,that means that Cpture One 22 may not checking all the error returns from Apples API's when it writes a file!
Anyway, I won;t start a file name with "." again, but, don't quite know know I did it..
Capture One 22 please chack this in the next and existing version, and,please fix.
Typically files that start with . are hidden files in MacOS. You could try enabling visibility of hidden files in Finder - the quick way is to press Cmd + Shift + . and then Cmd + Shift + . toggles them off again. With them enabled you could look in the location where you thought they were being exported to and see if they are now visible there. Don't forget to turn of visibility of hidden files when you are finished.
Thanks Ian, I'd forgotten that, I'll locate them and bin them, they are taking up space.. Even so, Capture should have warned me.
Perhaps you could rename the files to remove the dot at the start of the name?
Also don't delete any files starting with a dot unless you are absolutely sure what they are. Some are put there by the system and hidden so that you don't inadvertently break something by deleting them.
I had the same problem since MacOs Sonoma both beta as well as final version, using CaptureOne 23 Pro.The jpg's are exported, but hidden. You'll be able to find and open them with spotlight search.By default, finder doesn't show hidden files, and these are not prefixed by .To show them in Finder, as hidden files, hit command-shift-. (dot), as this will toggle showing hidden files slightly greyed out. You've probably have quite some as like me you tried ten times. I created a script called fixpix, which i put in /usr/local/bin (don't forget to sudo chmod a+x /usr/bin/local/fixpix) which helps me unhide them. I', sure there's more elegant automator ways, but I just go to the location with terminal (from status bar folder location, right click, "new terminal at folder" after i had pressed "show" on the export notification pop up from CaptureOne.
find . -name "*.jpg" -print0 | xargs -0 chflags -v nohidden
this will search for all jpg files and test them for the hidden flag, if they are, it will unhide them.
I've updated to 23.2.5 and the problem persists.
Capture One please look into this issue with MacOs 14
Apple says Sonoma is actually not yet released.
Fair point Ian Wilson and quick response!. As IOS17 became available I checked on my Mac if the beta had been promoted to final - which it had, see below - I was not aware the website is lagging the date 3 more days.I've just installed the final version on my mac (note no beta indicators). I'd been beta user and noted the issue and did flag it to Apple as part of the beta feedback. The OS image being rolled out to all your customers in 3 days will have this effect, likely. I suggest you give it a spin. Happy to support.
Iniciar sesión para dejar un comentario.