C1 saves duplicate of session on C:\ drive
Hello,
I have just discovered that after creating a new session and dropping all of my RAW files in the Capture directory, C1 copies everything to a different directory on my C:\ drive. I don't have enough space on my C:\ drive for all of these files--in addition to storing them elsewhere on my system. My C:\ drive is reserved for applications only, no data.
When I first noticed this, I thought they were a backup. This was (erroneously) confirmed when I checked the files I had made manually on my D:\ drive and found they were all there. So, I deleted all of the files on the C:\ drive. What I did not realize was that every change I made was made to the C:\ drive files and not to the D:\ drive files. This begs the question: What was the point of manually creating a session on the D:\ drive?
After making this unwelcome discovery, I checked through all of the C1 commands to see if there was a path command somewhere that I could change so that it either did not make a duplicate of my session somewhere else on my system or to at least put it on one of my many removable drives. I was unable to find any such command. My question is this: is it possible to prevent C1 from duplicating the entire session directory somewhere else on the system while treating the original files as a backup? If not, is it possible to change the path so that the files do not land on my C:\ drive, which is nowhere big enough to handle this kind of data?
Best,
AP
I have just discovered that after creating a new session and dropping all of my RAW files in the Capture directory, C1 copies everything to a different directory on my C:\ drive. I don't have enough space on my C:\ drive for all of these files--in addition to storing them elsewhere on my system. My C:\ drive is reserved for applications only, no data.
When I first noticed this, I thought they were a backup. This was (erroneously) confirmed when I checked the files I had made manually on my D:\ drive and found they were all there. So, I deleted all of the files on the C:\ drive. What I did not realize was that every change I made was made to the C:\ drive files and not to the D:\ drive files. This begs the question: What was the point of manually creating a session on the D:\ drive?
After making this unwelcome discovery, I checked through all of the C1 commands to see if there was a path command somewhere that I could change so that it either did not make a duplicate of my session somewhere else on my system or to at least put it on one of my many removable drives. I was unable to find any such command. My question is this: is it possible to prevent C1 from duplicating the entire session directory somewhere else on the system while treating the original files as a backup? If not, is it possible to change the path so that the files do not land on my C:\ drive, which is nowhere big enough to handle this kind of data?
Best,
AP
0
Post is closed for comments.
Comments
0 comments