Unable to create session on network drive / Capture One Por Windows
My pictures files and session data are stored on a network drive (Y:). This has been working fine for years. Since the upgrade to V20 I can't create sessions on the network drive any more. Even though I have writing access Capture One prompts. "Unable to find: Y:\...". For some reason Capture One does not see what the OS (Windows) is seeing. Any way to fix this? Otherwise we might have to change our storage structure.
-
Have you already re-booted the PC?
Have you tried re-mapping the drive? (Or simply re-discovering it via the System Folders section of the Library in C1)?
0 -
Hello,
I have just tried to create a session on my NAS using the latest version of Capture One V20 (13.1.2) and it works fine. I was able to create the session on the drive. Check that your drive mapping is still in place through Windows Explorer and as SFA said, try remapping the NAS drive.
0 -
It's mapped and I can write to the drive with other software, like a word processor.
0 -
Andreas,
I am not sure what the answer is. I have tried on my computer and it works, so it is unlikely to be specific Capture One issue, it is more likely to be a computer configuration issue in my opinion. Did you try remapping the drive as SFA suggested. If you don't want to destroy your existing mapping then you could create another mapping as a test and then try and create a session to that mapping.
A work around could be to create a session on your local drive, then move the session with Windows Explorer to your NAS and then open the session from the network drive via Capture One.
0 -
Can you connect to it by searching through the System Folders in the C1 library?
It's not just a case of whether the PC can see it but also whether the internal references that C1 has to tell it where that drive and folder may be still matches anything that the Windows system now identifies to point to that "drive name".
You should be able to navigate to the cosession or cocatalog files on the Networks drive, click on theme and had C1 start up and load them.
It may, however, also need you to identify where the image files are. There is a "Find" facility in C1 to make that easier.
If you have the session or catalog on the regular C: drive the chances are that you would be able to fire up the session but it might not recognise the path to find the network drive to get at the images.
I have a NAS - so a network drive - and there are times when it can become unknown to the system or, perhaps, its internal system identifier string has changed in isolation from C1 so that the PC can still see it but C1 still thinks it should be looking elsewhere. This one has to re-discover the drive for everything to work again.
Whether that sort of thing is the result of some sort of Windows activity or something in the NAS I don't know.
If your Network drive is not a NAS device it will still have similar internal cross references to identify devices in the system that can be broken from time to time in different ways, sometimes unintentional as far as the OS is concerned.
Heck, it can happen internally with no Network drives required! Usually fixed in that case by a re-boot.
0
La publicación no admite más comentarios.
Comentarios
5 comentarios