Referenced file location changes when moving catalog
I have a significant problem that has implications for making backup copies that can function in locations other than the original. It is not straightforward. I have submitted this to tech support.
I recently moved my referenced files from an old Mac Pro running OS11.6 to a new iMac running 13.2. To test the speed of having the referenced file on the SSD of the iMac or a USB 3.1 external HD, I placed a copy of my referenced files on the internal drive and another copy on a partition of the external drive. I made a copy of the catalog with a new name so I had copy A and copy B. I wanted to run the catalog from the internal drive for best speed. From within Capture One, on one copy I (re)located the referenced file location on copy A (to the iMac SSD) and on the other copy (copy B), I (re)located it to the external hard drive. Both catalog A and B correctly located their respective referenced files. Sounds great.
So I made a backup copy of both catalogs on 2 different external drives, including the Mac Pro. The result was that in the copies of B, the referenced files listed in the "In Catalog" folders reverted to referencing the same folders as in copy A, not the location defined in the source catalog B.
I finally resolved it, sort of, by making a fresh copy of my original catalog on my old computer, placing it in the external drive with the B copy of the referenced files. When I opened it, it referred again to the referenced files in the drive with the A copy, so I (re)located the files to the drive with B copy. I was then able to copy the referenced files and the catalog to a portable drive. I could open the catalog on that drive and it had the correct references. I mounted the the portable drive on my Mac Pro (I have the catalog and the referenced files on the same drive, there) and Capture One correctly referenced the files on the internal drive. I mounted the portable drive on my Mac Book pro, which has no catalog or referenced files. Again Capture One loaded the database from the portable drive and correctly found the reverend files.
So, how is Capture One able to change the location of the referenced files. If this is a OS 13.2 issue, how can the OS change the references?
I recently moved my referenced files from an old Mac Pro running OS11.6 to a new iMac running 13.2. To test the speed of having the referenced file on the SSD of the iMac or a USB 3.1 external HD, I placed a copy of my referenced files on the internal drive and another copy on a partition of the external drive. I made a copy of the catalog with a new name so I had copy A and copy B. I wanted to run the catalog from the internal drive for best speed. From within Capture One, on one copy I (re)located the referenced file location on copy A (to the iMac SSD) and on the other copy (copy B), I (re)located it to the external hard drive. Both catalog A and B correctly located their respective referenced files. Sounds great.
So I made a backup copy of both catalogs on 2 different external drives, including the Mac Pro. The result was that in the copies of B, the referenced files listed in the "In Catalog" folders reverted to referencing the same folders as in copy A, not the location defined in the source catalog B.
I finally resolved it, sort of, by making a fresh copy of my original catalog on my old computer, placing it in the external drive with the B copy of the referenced files. When I opened it, it referred again to the referenced files in the drive with the A copy, so I (re)located the files to the drive with B copy. I was then able to copy the referenced files and the catalog to a portable drive. I could open the catalog on that drive and it had the correct references. I mounted the the portable drive on my Mac Pro (I have the catalog and the referenced files on the same drive, there) and Capture One correctly referenced the files on the internal drive. I mounted the portable drive on my Mac Book pro, which has no catalog or referenced files. Again Capture One loaded the database from the portable drive and correctly found the reverend files.
So, how is Capture One able to change the location of the referenced files. If this is a OS 13.2 issue, how can the OS change the references?
0
-
Followup:
It's been a while since I relocated my referenced files.I suspect when I thought I had relocated the files, I had just added another drive to the list. So the files in that drive looked like my referenced archive on a different drive, had the right number of files, but were not actually connected to the images in the browser. The actual links were to the original archive on another drive and also displayed in the referenced files folder.
The key is, when files are relocated correctly, the activity window shows the relocation process. When I did this, the locations were correct.
For some reason Capture One has a lengthy process of relocating that looks at each file. In Aperture, you display all images, select all, and point to any one, and select "relocate all." It takes a second to complete. Obviously the Aperture database is much different, and the DAM was easier to work with in some ways, but it was otherwise not competitive with Capture One.
Moral of the story, no relocation shown in the activity window, no relocation.0 -
Just righthand click on the folder containing your files and choose locate, point to the new location and.. ready! It works for me 😉
Henk0 -
Yes, it works especially well when you remember to point to the top level folder, and not the drive to which you want to relocate the files. Pointing to the drive, rather than the folder really confuses Capture One. 0 -
Part of the problem is that while OS 10.11 let you to keep up with two drives with the same name, OS 10.13 adds a number suffix to the most recently mounted drive with the same name as an already mounted drive. You have to be careful which drive you are relocating. 0
投稿コメントは受け付けていません。
コメント
4件のコメント