"active" folder
I've noticed that since I started using CO V9, a number of .task files have been appearing in the folder:
C:\Users\{username}\AppData\Local\CaptureOne\Batch70\active
There appears to be a .task file for each image file that I have manually exported to JPEG.
In what sense are these task files "active" ?
Searching the forums, I came across this thread: which refers to the sibling folder: C:\Users\{username}\AppData\Local\CaptureOne\Batch70\history
That thread mentions that the history folder can be manually pruned using the "Clear History" button in the Batch -> History tab.
Is there a similar mechanism for the "active" folder?
Individually they are small files, but I wonder how are the contents of the "active" folder are meant to be managed, or do they just keep building up?
C:\Users\{username}\AppData\Local\CaptureOne\Batch70\active
There appears to be a .task file for each image file that I have manually exported to JPEG.
In what sense are these task files "active" ?
Searching the forums, I came across this thread: which refers to the sibling folder: C:\Users\{username}\AppData\Local\CaptureOne\Batch70\history
That thread mentions that the history folder can be manually pruned using the "Clear History" button in the Batch -> History tab.
Is there a similar mechanism for the "active" folder?
Individually they are small files, but I wonder how are the contents of the "active" folder are meant to be managed, or do they just keep building up?
0
-
Just a guess, but when I close C1 during processing of files (I do that when my memory is fully used and processing is very slow, eventually resulting in an out or memory error), then there is a tmp jpg file on disk. Once I restart C1 it resumes processing this file. Maybe (and that is the guess now) for every such image not processed there is a .task file ?
cheers
BeO0 -
[quote="BeO" wrote:
Just a guess, but when I close C1 during processing of files (I do that when my memory is fully used and processing is very slow, eventually resulting in an out or memory error), then there is a tmp jpg file on disk. Once I restart C1 it resumes processing this file. Maybe (and that is the guess now) for every such image not processed there is a .task file ?
cheers
BeO
Hi BeO,
That's not the case for me as the .task files are appearing in the active folder whenever I export an image using the "Export" option from the right-click context menu. It is not necessary in my case for C1 to be terminated during processing.
In contrast, if I export an image using the Process Recipe tab, then the .task file is created in the history folder, not the active folder.
I just tested CO V8 and when I export an image using the right-click -> Export -> Variants option, it doesn't create a .task file in the active folder. This behaviour is new in V9.
Richard0
Post is closed for comments.
Comments
2 comments