Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

C1 Use with SSD

jonpaul
Hello all:

Many PC users have already (or will soon) put an SSD for the C:\ boot volume. Big improvemtn in boot time and windows performance.

But an SSD is rather small (typically 30..120GB) and has a life limited by the number of accesses. Therefore you have to limit the use of C:\ to C:\ windows, system and documents and settings ONLY
and avoid any other use. All programs and caches, and data should be on other HD, not the SSD.

C1 seems to not take this into account: Even if you install on a different drive, it still sets a cache and image files in C:\ by default. So you must change at least 3 default file locations:

Program
Image files
Cache

I am sure my C:\ still has more P1 files or folders in it!

Finally some errors and bad behavior of C1 may be due to its assumption that all the folders and files are in the default location in C:\ and it seems to have issues when one use D:\ for the program and E:\ or F:\ for images and cache.

It would be very fine if P1 can modernize the C1 PC installation and be more friendly to those who have an SSD for C:\.

Anyone else out there that has noticed this?
Can P1 please comment?

Kind Regards,

Jon
0

Comments

7 comments

Date Votes
  • Paul Steunebrink
    First, what you describe are issues with multiple drive setups in general, and not specifically SSD related. The same could be through for multiple HDDs.

    I run CO6 on a double SSD drive Windows 7 installation without any hiccups (C: for programs and Windows, D: for data). The cache and settings are stored with the image files, which reside on the D: drive in my system. A central cache is not used since CO4.

    I do not share the limitations you describe. To the contrary. CO6 fully complies to Windows program specifications in how it utilizes and separates both program and user data. Both can independently be redirected to other volumes but it needs a proper Windows setup in the first place. Maybe you could start there, because what you describe and assume to be there isn't.

    A tip to start: redirect the user's Pictures folder to another location from within Windows. CO6 will automatically follow the new path without issues. This includes the default Capture One Library session folder.

    By the way, SSD drives are way beyond the 30-120 GB spec range. And in my book, you exaggerate the limited lifespan of a good SSD.
    0
  • Coach
    I wasn't aware of any issues with SSDs (it sounds a little like a disease). This thread did get me searching the web. Apparently there are, or at least were some issues with how often a sector(?) can be written to, not the number of accesses. For power users I wonder if it is still a consideration. Capture One does a lot of writes with the cache and settings folders.

    I just got a new system with an SSD and I'm using it to hold my working files until I've finished processing them. Then I'm moving them to the HD to free up the SSD. I'll be reading up more on this and may change my workflow.

    I agree with Paul_E though, it is a simple matter to use a different drive, even if C1 support prefers staying with C:. (Try changing the default Trash folder and you'll get a warning against it.)
    0
  • Jim MSP
    [quote="Paul_E" wrote:
    ...

    A tip to start: redirect the user's Pictures folder to another location from within Windows. CO6 will automatically follow the new path without issues. This includes the default Capture One Library session folder.
    ..


    I have a new laptop arriving this week with a SSD for the boot drive (at least I requested it this way). I intend to install CO, MP, PS Elements, & LR on it. Everything else including all photos, catalogs, and documents will go on a internal HD. We'll see how well this works.
    0
  • jonpaul
    Hello all:

    The point Paul makes about SSD size is well taken, but many of us have installed small 30..100GB, drives already.

    Costs are now about 1$/GB. Expect them to fall with time. If you shoot big sessions, you will quickly fill even a 120 or 240G SSD.

    Regarding SSD degradation due to R/W cycles, I do not agree with Paul that is not a problem. It depends on the flash technology, the flahs controller, the cell size, the write block size, file size TRIM implementation and other technical and usage factors.

    SSDs production history is too short to accurately predict life. Please see for instance:

    http://lifehacker.com/5802838/how-to-ma ... f-your-ssd

    http://www.storagesearch.com/ssdmyths-endurance.html

    http://solid-state-drive-review.toptenreviews.com/

    To be conservative, and for those with smaller sized SSD, I would still avoid any unnecessary use of C:\ especially for frequently accessed or large files like C1 images or cache.

    Meanwhile my main workstation has developed a bad error when I do a C1 process. P1 support asks me to relocate the RAW files to C:\. So it seems that C1 is not fully comfortable with the program at D:\ and files at F:\.

    I still think P1 should have a more SSD friendly disk allocation selection during C1 installation and more thoroughly test C1 use over multiple drives and partitions.

    Kind Regards,


    Jon Paul
    MSEE
    0
  • Mitch1
    I configured my SSD for OS and Programs only, and repointed my pictures library to a separate HDD. The Capture One Library automatically established itself on the HDD as expected.

    However, I'm not sure where C1's cache is - how do I find that, and how do I redirect it? I don't see any settings in C1 that allow it. Thanks.
    0
  • Coach
    The cache and settings files are now always stored in a subfolder "CaptureOne" below whatever photo folder you're using so it automatically went with your picture library.
    0
  • Mitch1
    Thanks Coach! I see the cache/settings/proxy folders now. 😄

    Now if I could just get C1 to use OpenCL with my new (as of yet 'unsupported') video card, I'd be set ... but that's another issue, for another thread...
    0

Post is closed for comments.