20.1/13.1 catalog import
Hey all,
A quick question to see if anyone else is seeing the same thing before I report it as a bug...
I use a shell script to unload images from memory card to their final location on disk and verify the copy is correct before deleting the image from the memory card. The script opens a finder window showing me the imported images. I select the images and drag them onto the capture one icon in the dock to initiate an import. In the import dialog I set the "Import To" to "Current Location".
That works, importing the images into my master catalog. However, starting with version 20.1/13.1 Capture One creates a Capture One folder. The Capture One folder contains a Settings131 folder. The Settings131 folder is empty.
Those are folders used for sessions. I'm importing into a catalog. Is anyone else seeing the creating of these unneeded folders?
-
Yes, I am seeing them as well. But they only show up in the first subfolder of a multi-folder import. They are completely empty. I would appreciate any response on how to deal with them.
0 -
Yes, I have begun seeing them also. I have not of my own experience been able to identify or isolate what is causing them to appear. Considering that the Settings131 folder is empty, they seem pointless.
0 -
Yes same issue. Would love to get guidance from C1. TY
0 -
Same issue. See my post. No answer yet.
I have a fresh C1 install. No specific configuration. Unless, there is a hidden session by default, I still think it is a bug.
0 -
Response from Capture One Support:
I reported to Capture One Support that . . .
"A session-like Capture One folder (with an empty Settings 121 or 131 folder) is created during Import of images into a Catalog and shows within the folder with the imported image files. If I import more than one image (with "Include Subfolders" checked), that session-like folder only appears in the first image folder, not in any of the following image folders"
Capture One Support responded by saying that this is indeed a bug in the current Capture One version (13.1.1.24) and that it will be addressed in a future update.
Robert Henderson
0 -
I'm still having this problem in version 13.1.2.37.
1
Post is closed for comments.
Comments
6 comments