What have I done? And how do I fix it?
I switched from Dxo Optics Pro 10 to CaptureOne when I realized that 8.2 would allow me to do round-trip processing and I have been happily using it until I apparently did something that changed how it handles my images when I create a new catalog.
I have not used CO to import images from my camera or flash memory since I normally just copy the images directly onto my computer at the end of each day. I work on a Mac and have only limited SSD space so I purchased a Transcend JetDrive (which is a 128 GB flash memory that sits flat in my MBP’s sd slot) and store my images on it. When my wife and I return from a trip I begin processing by going through the images from day to day. I create a catalog (on the SSD) for each day and I tell CO to store the files in their current location (so I don't lose any extra space) and to do Auto Adjust and I have been happily creating catalogs this way for each day’s images without a problem. Until yesterday.
Suddenly, when I create a new catalog using the JetDrive flash memory, CO tells me it needs to import the images into the catalog and that it “Cannot store files in current locationâ€. This is brand new functionality for me as I have never seen this message before. I have done some testing and found that if I copy a day’s images to the SSD and try the same process when I create a catalog using it (the SSD) I don’t have this issue, but I did not have it using the JetDrive until yesterday so I assume I somehow screwed something up.
The flash memory is not write-protected and, in fact, I can find nothing that has changed on my system that should cause this change in functionality. Aside from finding out what is wrong I assume I have only 2 options - reset CO to its default settings (and I don't know how to do that) or uninstall and reinstall it. Perhaps that will solve my problems, but it would probably mean that I would lose all of my workspace settings so I would prefer fixing what is wrong.
Can anyone offer a suggestion?
Thanks.
By The Way - If it is important, the JetDrive is formatted as FAT32. I may try formatting it as a Mac drive, but I do not believe that should be a problem.
I have not used CO to import images from my camera or flash memory since I normally just copy the images directly onto my computer at the end of each day. I work on a Mac and have only limited SSD space so I purchased a Transcend JetDrive (which is a 128 GB flash memory that sits flat in my MBP’s sd slot) and store my images on it. When my wife and I return from a trip I begin processing by going through the images from day to day. I create a catalog (on the SSD) for each day and I tell CO to store the files in their current location (so I don't lose any extra space) and to do Auto Adjust and I have been happily creating catalogs this way for each day’s images without a problem. Until yesterday.
Suddenly, when I create a new catalog using the JetDrive flash memory, CO tells me it needs to import the images into the catalog and that it “Cannot store files in current locationâ€. This is brand new functionality for me as I have never seen this message before. I have done some testing and found that if I copy a day’s images to the SSD and try the same process when I create a catalog using it (the SSD) I don’t have this issue, but I did not have it using the JetDrive until yesterday so I assume I somehow screwed something up.
The flash memory is not write-protected and, in fact, I can find nothing that has changed on my system that should cause this change in functionality. Aside from finding out what is wrong I assume I have only 2 options - reset CO to its default settings (and I don't know how to do that) or uninstall and reinstall it. Perhaps that will solve my problems, but it would probably mean that I would lose all of my workspace settings so I would prefer fixing what is wrong.
Can anyone offer a suggestion?
Thanks.
By The Way - If it is important, the JetDrive is formatted as FAT32. I may try formatting it as a Mac drive, but I do not believe that should be a problem.
0
投稿コメントは受け付けていません。
コメント
0件のコメント