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
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.
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.
I have posted a link to this page on the other thread (as I've provided the terminal blurb here to patch the exported files above).
I can see the hidden files with Cmd-Shift-[dot], and I can see the files with Graphic Converter with app Display Settings to show Hidden Files. but when I change the Display Settings to show [dot] files and not Hidden Files the files disappear. This leads me to believe that the files are invisible for another reason. And it's quite disappointing that I don't have a utility application which will change the attribute easily, despite having accumulated utilities over the years.
And if I find the files and move them from my iCloud Drive to a temporary folder ("transit") in my Pictures folder the visibility remains disabled. Hmmmm.
BatCHmod has no facility to change the visibility attribute of the file, from what I can see, but Tinkertool System does, albeit singly.
The workaround of street.thesis was mentioned by CaptureOne staff also. If you change your recipes to output to folders outside iCloud, it will export without hiding.Should you (like me) insist on pushing them onto the cloud for purposes of automatic backup, you can create a automatic fix using the automator app. Open it with command-space, type automator (it will complete the .app) and hit enter.It will default to a file requester to open an automator script, ignore this.Instead create a new automator script, File->New (or hit command-N)and select a folder action, like belowin the top search bar of the automator app, type unix, so it filters down to show "Run Shell Script" which you drag into the window to the right, like below
You are now editing the action that will be called every time in the folder you're going to select a file get's added. Select your own output folder; mine's maesland, as that's my website's name. In the box below type chflags nohidden "$1"
The $1 is the name of the file that got created/exported by any program, in any way on in that folder you selected. This will trigger the automator script once you save it.
So save the script, the name is not relevant, Automator suggests a location, I didn't change it.
That's it. You can close automator, as it will be triggered by MacOs every time that folder gets new files. I haven't found an elegant way to track multiple folders like this, as i have a few recipes that output to different folders.
Hope this helps you.
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?
^^ spam reply with dodgy link included. ^^
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.
Some of this has been discussed here: https://support.captureone.com/hc/en-us/community/posts/12450169671069-No-export-of-images-can-be-performed
I opened a support ticket on it during the beta period, which was closed. I have since reopened it since the OS was finalized (which to alleviate any lingering confusion was released in its final form a few days early to beta participants). Unfortunately it's been 5 days since I opened the ticket and have had no response yet.
Please fix this really anoying bug asap. Searching for the filename in in a desktop folder where the file was exported will bring it up. I've been dragging it to a different folder created for the file, and then it's fine. The shift command period command to show hidden files is also useful to see what's been missed. I just exported to web use format to update my profile photo here, and it was fine. Then when uploading to this site the image was not visible in the upload dialog. Just weird.
As a workaround until it gets resolved (either by Phase One or Apple), I can vouch for maesland's workaround above. I haven't tried the script method, but just copying that string into a terminal window in the output folder has saved me a lot of headache:
It's not the most convenient thing in the world, but it does seem to catch all the invisible jpegs in the folder and make them visible in one shot. The folder view doesn't update automatically, so refresh the view to see your newly unhidden files.
For anyone who isn't familiar with the Terminal, I made a short demonstration of one way to open it in the right location: video
I added an entry in Notes with the command, so I won't lose it.
If there is enough interest, let me find out how to automate it with an Automator script. That should make it a right click action. I’ve never looked into it as I’m a unix person, but should be straightforward.
I just created a folder in my user account on Mac, non iCloud, and export there, then put an alias to it on my desktop for easy access. Simple work around.
I had.the same problem after upgrading to pro 23. I couldn’t find my exported photos in the folder I used to keep exported photos. Actually these exported photos became ghost files.
Use commands+shift+. combination, the ghost files will appear as “grey” files in that folder. Then I moved the grey files out of the folder to desktop on my Mac. They are still shown as grey files on desktop. Next move them back to that folder. Now they become normal files.
I found this way accidentally. I don’t know why it worked for me. But you can try.
Please sign in to leave a comment.