C1 v12 uses a lot of disk space while exporting
SInce upgrading to v12 (I hadn't noticed this happening in previous versions) I have noticed my free hard disk space disappearing rapidly while I am exporting a large number of images from a catalogue.
I create a new catalogue for each job and save it, along with the all associated raw files, to a fast external HD.
However when I export jpegs from the catalogue, again to the external HD, the free disk space of my MacBook Pro goes gradually down from 32GB to 100MB during the 20 minutes or so it takes to export. After the export crawls over the finish line, and I quit C1, this space miraculously returns.
I know 32 GB of free space isn't exactly capacious, but C1 is the only thing that causes this to be an issue.
Anyone know what is happening here? Is there a preference somewhere I should be looking at?
I create a new catalogue for each job and save it, along with the all associated raw files, to a fast external HD.
However when I export jpegs from the catalogue, again to the external HD, the free disk space of my MacBook Pro goes gradually down from 32GB to 100MB during the 20 minutes or so it takes to export. After the export crawls over the finish line, and I quit C1, this space miraculously returns.
I know 32 GB of free space isn't exactly capacious, but C1 is the only thing that causes this to be an issue.
Anyone know what is happening here? Is there a preference somewhere I should be looking at?
0
-
[quote="NNN636477603096344064" wrote:
SInce upgrading to v12 (I hadn't noticed this happening in previous versions) I have noticed my free hard disk space disappearing rapidly while I am exporting a large number of images from a catalogue.
I create a new catalogue for each job and save it, along with the all associated raw files, to a fast external HD.
However when I export jpegs from the catalogue, again to the external HD, the free disk space of my MacBook Pro goes gradually down from 32GB to 100MB during the 20 minutes or so it takes to export. After the export crawls over the finish line, and I quit C1, this space miraculously returns.
I know 32 GB of free space isn't exactly capacious, but C1 is the only thing that causes this to be an issue.
Anyone know what is happening here? Is there a preference somewhere I should be looking at?
I would think it is using temporary files for the process.
I would suggest either increasing you disk capacity or processing in smaller batches.
Increasing dusk capacity would be the best option by far for a number of reasons not all related to C1.
HTH.
Grant0 -
Thanks Grant - I agree that must be what's happening, although 32 GB of temp files to export 1GB of jpegs seems a bit excessive... 0 -
[quote="NNN636477603096344064" wrote:
Thanks Grant - I agree that must be what's happening, although 32 GB of temp files to export 1GB of jpegs seems a bit excessive...
How much RAM memory do you have?
Bare in mind the processing starts with a full RAW file and at some point has to do some processing work and then deliver a compressed version of that file before disposing of the work files.
In a big batch like that, unless you have a lot of RAM, the system will likely need to use disk space for swap files to support the RAM.
Grant0
Post ist für Kommentare geschlossen.
Kommentare
3 Kommentare