C1 running Very Slowly
I searched the forums & unfortunately not found an answer and wonder if someone can throw some light on this.
Is there a limit to what constitutes a sensible number of files in a session. If there are too many does this cause C1 to slow to a snail's pace?
From a shoot I did over the weekend I have 2500 files off a D700. Going through them & having to make individual adjustments, the redraw/reload times are dreadfully slow & getting slower, making it extremely tedious & irritating.
It doesn't seem to make any difference whether I'm working from the session created on the main hard drive or the one created on the 'fast workspace'(see below for config).
Any help would be most appreciated. Have I too many files in this session & should I separate them out into smaller sessions of say 2>400 or so images?
Capture 1 v 5.2.1:
Mac - 2x 3Ghz Quad-Core; 18gb RAM; OS 10.5.8: 4x 1.5Tb Int h/drives - 1 as the OS disc & the other 3 striped to Raid 0 to create a 'fast workspace'
Is there a limit to what constitutes a sensible number of files in a session. If there are too many does this cause C1 to slow to a snail's pace?
From a shoot I did over the weekend I have 2500 files off a D700. Going through them & having to make individual adjustments, the redraw/reload times are dreadfully slow & getting slower, making it extremely tedious & irritating.
It doesn't seem to make any difference whether I'm working from the session created on the main hard drive or the one created on the 'fast workspace'(see below for config).
Any help would be most appreciated. Have I too many files in this session & should I separate them out into smaller sessions of say 2>400 or so images?
Capture 1 v 5.2.1:
Mac - 2x 3Ghz Quad-Core; 18gb RAM; OS 10.5.8: 4x 1.5Tb Int h/drives - 1 as the OS disc & the other 3 striped to Raid 0 to create a 'fast workspace'
0
-
[quote="David27" wrote:
I have 2500 files off a D700
David,
Speaking in approximations, you are accessing roughly 85GB of information at one time. Granted Capture One generates Proxies so that it does not read the entire RAW each time you access it but the folder of RAW files as a whole is being looked at by the software. The performance with the initial browsing of the folder would be similar to opening an 85GB file in Photoshop, which would be quite the[quote="David27" wrote:
snail's pace0 -
Hi Drew Thanks for that & I understand what you mean although I'm not sure my question is fully answered. So, would you suggest separating them out into folders of say 150>200 images per folder? if this is the case do I then keep the named folders within the root folder ie Vogue October as the header and within that say, swimsuits, blouses, skirts etc etc
(This is not who I've been working for BTW)
Look forward to hearing back from you
Thanks David0
Post ist für Kommentare geschlossen.
Kommentare
2 Kommentare