メインコンテンツへスキップ

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Locate... After hard-drive letter change

Cass Cassim
Hi there,

Just a question for anyone else that has lots of images. My catalogue holds 75K, and yesterday I reconfigured all my drives to include faster cache drives etc. The net result was that my main external image drive was swapped from the E: to the F: drive designation. The folder structure on the external drive remained untouched.

When i loaded C1, it of course showed all folders offline. An hour ago I selected the top-most folder, found Locate in the menu, and pointed to the F: drive. Right now, it seems to be doing something. This used to take a couple of seconds in Lightroom.

Is this normal to take so long in C1? Does every one of my images need remapping? How comes the top drive letter isn't just remapped in just a second like other software? Anyone know exactly what it is doing?

Perhaps another pointer towards exceedingly primitive database operations... ☹️
0

コメント

10件のコメント

日付 投票
  • Cass Cassim
    Well, in case anyone is interested, just locating the 75,000 images after a drive letter change took one hour and 20 minutes, and that is on a machine with an i7-7700HQ, 32Gb RAM, a Nvidea GTX 1070 MaxQ GPU, and two blazingly fast PCIe NVMe M.2 SSD drives... you, know, I just don't think it is hardware-related.

    A quick look through the structure, everything so far looks okay. Not sure what it was doing, but however it stores the folder hierarchy data for the file/folder positions definitely does not lend itself to changing the drive letter... Best keep that to a minimum if possible... and sometimes it is not possible...

    Hmmm... I just don't get why some operations in C1 are just so time intensive. ❓
    0
  • Ian Leslie
    I cannot speak to how long it took or what it was doing but my personal tactic for this issue is to remap the drive letter. Long ago I set my photo drive to be V:. The one time I moved to a new HD for images it was a piece of cake and took no time at all for the catalogue to switch to the new drive. I just plugged the new drive in and after the images were transferred over I changed the drive letter in Windows.
    0
  • Cass Cassim
    Yes, choosing a drive letter further down the ranks is a good idea... Just thought I'd mention my experience in the 'lacate' action.

    Thanks for the input...
    0
  • SFA
    [quote="easycass" wrote:
    Well, in case anyone is interested, just locating the 75,000 images after a drive letter change took one hour and 20 minutes, and that is on a machine with an i7-7700HQ, 32Gb RAM, a Nvidea GTX 1070 MaxQ GPU, and two blazingly fast PCIe NVMe M.2 SSD drives... you, know, I just don't think it is hardware-related.

    A quick look through the structure, everything so far looks okay. Not sure what it was doing, but however it stores the folder hierarchy data for the file/folder positions definitely does not lend itself to changing the drive letter... Best keep that to a minimum if possible... and sometimes it is not possible...

    Hmmm... I just don't get why some operations in C1 are just so time intensive. ❓


    You should probably have a look at the log file(s) to see if they provide any clues.

    I would guess it's los verifying that everything still exists where it expects to find it, remembering that editing in off-line mode is still possible but C1 would need to assess for on-line or off-line status.

    75k images will result in a lot of files for which to verify their presence.

    Fast SSDs, especially externally connected, may not be as fast as one might like for large batches of small files.The log files perhaps give some indication for that?
    0
  • Cass Cassim
    [quote="SFA" wrote:
    You should probably have a look at the log file(s) to see if they provide any clues.

    I would guess it's los verifying that everything still exists where it expects to find it, remembering that editing in off-line mode is still possible but C1 would need to assess for on-line or off-line status.

    75k images will result in a lot of files for which to verify their presence.

    Fast SSDs, especially externally connected, may not be as fast as one might like for large batches of small files.The log files perhaps give some indication for that?


    Hi there... thanks for the comment.

    I guess I am just thinking that when we plug in an external drive with the normal drive letter, C1 does not spend 1.3 hours going through all the files while locking out the user. So, I am not quite sure why a simple change of drive letter should give it any more reason to do something special in terms of checking things for the images. It just needs to change the root path. Other programs that check loads of files (back-up, renaming, drive-imaging, other image cataloguing software etc), can whisk through directory checks in pretty fast measure, so why not C1?

    I really just want to help highlight areas that Phase One could look at in terms of improvement to be honest.

    But still, I am interested to know what C1 is doing... Can you tell me where I can access the appropriate log file for that?
    0
  • SFA
    The Logs can be found here in Windows 7. Probably much the same in WIn 10

    C:\Users\[user name]\AppData\Local\CaptureOne\Logs

    There are several log files available. Open with a text editor.

    You likely won't need to look at the Tangent log or the Capture logs.

    It might be worth sending them to the support team as part of a Support Case in order to get an interpretation of the results.

    Grant
    0
  • Permanently deleted user
    [quote="easycass" wrote:
    An hour ago I selected the top-most folder, found Locate in the menu, and pointed to the F: drive. Right now, it seems to be doing something. This used to take a couple of seconds in Lightroom.

    Is this normal to take so long in C1? Does every one of my images need remapping? How comes the top drive letter isn't just remapped in just a second like other software? Anyone know exactly what it is doing?

    Perhaps another pointer towards exceedingly primitive database operations... ☹️

    That; plus it would lose the folders again and again! (version 10.x.x at least) I lost patience and had to give up on catalogs altogether when I moved computers.

    Now I keep the recent pictures on my laptop in an import/editing session, and everything else is stored on a local server. Session performance over the network is jolly good. Even on WiFi!
    0
  • Cass Cassim
    [quote="gusferlizi" wrote:
    That; plus it would lose the folders again and again! (version 10.x.x at least) I lost patience and had to give up on catalogs altogether when I moved computers.

    Now I keep the recent pictures on my laptop in an import/editing session, and everything else is stored on a local server. Session performance over the network is jolly good. Even on WiFi!


    Yes, well the good news is, despite taking a long time, ver 11 seems to be a little more able to hold things together than ver 10. I did have to do a database repair after this operation, but all seems good and intact, and I don't seem to have any mislaid folders or files, which is good. I understand your caution by using sessions, but I do prefer the catalogue approach, having spent the last many 15 years or so cataloguing with iMatch, MediaPro and Lightroom... suits my mental organisational approach 🤓

    [quote="SFA" wrote:
    It might be worth sending them to the support team as part of a Support Case in order to get an interpretation of the results.

    Grant


    So, looking at the log file, it appears that each collection (as in folder) is 'loaded', followed by some kind of 'autosave' and then some database update. I need to run a more controlled test on a few folders to be sure of what is part of the 'Locate' process, and what might be happening as part of C1's normal background work.

    I guess, either way, at present, it is pointing to C1 acting on on each folder and each instance of every image to get the 'locate' done. While I imagine this is useful if one really has lost connection to a mess of various images and folders, a switch of drive letter should perhaps be a simpler, separate type of process. Indeed, some applications have three types of actions: synchronise (to make sure the content of a folder is coincident with import/database contents), locate (to find missing folders and files) and change source (to specify top level folder/drive for a hierarchy). It is the latter we need in C1 i guess.

    I shall report back if I find anything new, but will anyway send these observations as a support message to Phase One - as I seem to do quite a lot 😉.

    Thank you everyone for their comments.
    0
  • Robert Whetton
    You can always change the drive letter back using Disk Management under Admin Tools in the Control Panel - or if you're on Win10 right click Start, and select (right click on the drive and select "Change Drive Letter and Paths..)
    0
  • Cass Cassim
    [quote="Bobtographer" wrote:
    You can always change the drive letter back using Disk Management under Admin Tools in the Control Panel - or if you're on Win10 right click Start, and select (right click on the drive and select "Change Drive Letter and Paths..)


    Ah yes, this is what I would normally do, having a lot of external drives for various media projects, but in this case, I just installed a nice second internal nVME SSD drive into the machine to aid with video software caching, and I wanted it to have the E: slot. Consequently had to bite the bullet and move the image drive from E: to F:. To be honest, I thought it'd be a quick job like all my other software, and was a little surprised (or not really) at the meal that C1 made of it... It took longer for C1 to do its thing than to open the computer and install the drive 😉

    Never mind, I don't intend adding any more internal drives, so I'll be okay in the future... Cheers for the comment anyway.
    0

投稿コメントは受け付けていません。