Preview sizes
I'm struggling to import pictures from my existing "archive" either via the Aperture imported or manually. C1 is very unimpressive so far but I know it has a good reputation and I want to like it.
I'm wondering if generating previews is the cause of much of my trouble (freezing up, not responding, slow) and if reducing their size in the preferences will speed things up. The tutorials I've seen say keep the 2560 pixel default. I'm not sure I need that for every single picture (I think Lightroom has the option to save space by deleting full size previews after a set time).
Does everyone use the default, has anyone changed to a smaller size and noticed any benefit? Remember I want to use C1 as an archive catalog as well as raw processor.
Thanks!
I'm wondering if generating previews is the cause of much of my trouble (freezing up, not responding, slow) and if reducing their size in the preferences will speed things up. The tutorials I've seen say keep the 2560 pixel default. I'm not sure I need that for every single picture (I think Lightroom has the option to save space by deleting full size previews after a set time).
Does everyone use the default, has anyone changed to a smaller size and noticed any benefit? Remember I want to use C1 as an archive catalog as well as raw processor.
Thanks!
0
-
David,
People here seems to have had a range of experiences in this regard but basically creating a new catalog by whatever approach will take some tome and involve quite a lot of processing in foreground and background.
As an "outside observer" (I don't use Mac/Aperture or C1 Catalogs) my unbiased opinion is that you should create a Support Case and cut straight to the chase.
It should be better for you to help get your installation up and running and for Capture One developers in that they will have more information about system configurations and how things seem to interact from which they can make development decisions. Yes it's a one-time activity (at least in theory) but there are still reasons and opportunities to make improvements if such can be identified.
HTH.
Grant0 -
Thank, yes, I'm also bothering support about this!
Meanwhile I've just asked C1 to import a folder of 27 pictures whic it currently says "Generating 5 out of 27 previews - About 57 minutes left".
An HOUR to generate 27 1920 pixel previews? That really can't be correct. Can it...0 -
[quote="David Gordon" wrote:
Thank, yes, I'm also bothering support about this!
Meanwhile I've just asked C1 to import a folder of 27 pictures whic it currently says "Generating 5 out of 27 previews - About 57 minutes left".
An HOUR to generate 27 1920 pixel previews? That really can't be correct. Can it...
No, but the estimates are usually based on what it has managed to achieve in the time taken so far. Not sure about Macs but in windows that can extend to forever so long as the program has not crashed. So it's not usually terribly meaningful except to tell you the routine is still running.
I would look at any performance monitoring applications you may have available to see if they throw any more light on the subject.
Grant0 -
I did a test and importing 500 photos on my computer (from the local SSD into the Catalog) with 640px previews took 8 minutes and at 2880px previews it took 14 minutes. So the size does play a role in the ingest time.
As far as importing from an Aperture Library, I have seen at least a few complaints here and there about importing large libraries simply stalling or not importing successfully. You might want to partition your Aperture Libraries into smaller Libraries before you import. Maybe by year or subject or something.
Now in terms of previews, one thing I have noticed is that C1 tends to do some wacky stuff if your previews are not larger than the display area of the viewer. I haven't had endless amounts of time to track down what exactly is going on and on what kinds of systems it appears on, but it's certainly a problem on my 4K display where even 2880px previews are not big enough to fill the viewer at times and I've even seen some strange issues with different sized previews on my laptop (connected to a 2560x1440 27" Apple Thunderbolt Display). My advice would be to use larger previews than your viewer could possibly be. So on a 2560x1440 display, you probably can have a viewer that consumes 2000px of your screen... make sure your preview images are larger than 2000px. Whether you use 2560 or 2880 probably doesn't matter, but make sure they are bigger than 2000. I don't know what happens when the viewer is larger than your preview... whether it's upscaling it or generating a live preview from RAW, but it can cause some issues with the viewer not matching what's actually going on with the image.0
Post is closed for comments.
Comments
5 comments