Output location not retained
I've posted this alongside my "session becomes empty post" as it is more straightforward.
New install of 7.0.2. All trace of previous install removed manually fron registry. Only new images imported.
Capture one on install produces a session folder in c:\users\<name>\pictures\capture one session: I have 3 images in this processed to my chosen "processed" folder instead of the default "output". Returning to this session so far maintains this location.
I created a new session d:\capture one\capture 1\. This has 10 new images which I processed to the "processed" folder. (same folder created above). I Shut down C1, reopened C1 and imported 2 extra images to this session, processed them and found they had been sent to C drive default "output" - didn't check. Reprocessed them to my D drive "processed" folder. Shut C1 reopened C1 and the session has the folder "output " showing in output location not "processed" as in the last use. Repeating this my chosen output "processed" folder location reverts to "output" at each use.
Has to be a bug the output location was always remembered in v6 (and I think in 7.0 - can't be 100% on this.
Really annoying to have to check the output location on every use in case it has changed. So far the location is remembered on the default session but I do not want to use this as it is on my SSD drive.
New install of 7.0.2. All trace of previous install removed manually fron registry. Only new images imported.
Capture one on install produces a session folder in c:\users\<name>\pictures\capture one session: I have 3 images in this processed to my chosen "processed" folder instead of the default "output". Returning to this session so far maintains this location.
I created a new session d:\capture one\capture 1\. This has 10 new images which I processed to the "processed" folder. (same folder created above). I Shut down C1, reopened C1 and imported 2 extra images to this session, processed them and found they had been sent to C drive default "output" - didn't check. Reprocessed them to my D drive "processed" folder. Shut C1 reopened C1 and the session has the folder "output " showing in output location not "processed" as in the last use. Repeating this my chosen output "processed" folder location reverts to "output" at each use.
Has to be a bug the output location was always remembered in v6 (and I think in 7.0 - can't be 100% on this.
Really annoying to have to check the output location on every use in case it has changed. So far the location is remembered on the default session but I do not want to use this as it is on my SSD drive.
0
-
I've had the same problem. Everything works fine for a while using my chosen output folder then for some unknown reason the the target directory will change to "Output". Now I have to monitor it every time I process images. Never had this problem with all previous versions. 0 -
I agree. This is really bugging me. Get it? Haha.
Another thing I also found and reported is that if you rename the default output folder to something else, you will see that when you exit and restart the session, C1PRO 7.0.2 will create the folder named "Output" and sometimes place processed into that created "Output" folder. It is annoying.
When C1PRO7 debuted on October 25, 2012, I found this bug and reported. It used to be that, when you select an untethered session, C1PRO7 will make it a tethered session anyway with the creation of "Capture" folder. When 7.0.1 came out, that was fixed. When a user select an untethered session, C1PRO 7.0.1 would honor the instruction and NOT create the "Capture" folder. BUT the creation of "Output" remains as a residual. If you read my posts several posts below yours, you will see this problem.
Best to do is to log into your P1 account and file an official complaint with them.0 -
i will do this. Thanks for confirming it's not just me with this.
Ray0 -
I have copied this to support. Just to confuse things I processed a couple of shots in my preferred session location earlier. On reopening C1 to check on details to use in my reply to my support case, found it remembered the output location this time. Seems to be random.
Ray0
Post ist für Kommentare geschlossen.
Kommentare
4 Kommentare