メインコンテンツへスキップ

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

C1 can't cope with networked drives!?

コメント

5件のコメント

  • sizzlingbadger
    The CO catalog is a sqlite database it will not perform well on a network drive. This is why Adobe and Apple don't let you do it.
    0
  • brianmerwin
    David,

    This is a common issue with nearly all image editing/cataloging tools on the market. If you MUST work using networked drives (ie. you're in a corporate environment etc) then you probably need to look into an enterprise grade asset management tool such as Portfolio by Extensis.

    There aren't any solutions I'm aware of that allow you to do an effective job working on image files remotely (via networked drive) that won't be terribly slow. Most organizations I encounter that must store their files on remote drives, will have a workflow that essentially involves keeping files they are actively working on/editing on a local drive, and then moving the images to a remote drive for long term storage.

    Ultimately the bandwidth available through networked drives (unless you've got an actual thunderbolt network setup - which is amazing but incredibly expensive) this is going to be an issue for you regardless of whether you're trying to work with CaptureOne, Lightroom, or any other solution on the market. It's a hardware issue more than software when it comes to speed.

    The software is an issue when you're trying to share a library with multiple users and have access to the same files/directories at the same time - and if that's a critical need for you then you absolutely need to look into enterprise grade solutions for asset management.
    0
  • harald_walker
    [quote="sizzlingbadger" wrote:
    The CO catalog is a sqlite database it will not perform well on a network drive.

    How about keeping the catalog local and the referenced files on a network drive? Since the previews are embedded in the catalog, most activities should be fairly fast then and only if the original file is needed, it would use the slow network drive. How does that perform?

    Personally I would never use a network drive for DAM. In contrary, you want to the fastest drive you can afford. I've already been wondering if it would be worth it splitting the catalog from the raw image files. In my case both are now on the same external Thunderbolt raid drive. I was thinking that a Thunderbolt SSD drive just for the catalog might make a big difference but that adds more complexity then to the backup system.

    Would be nice if something better than SQLite could be used. I don't mind running Postgres or MySQL on my local machine.
    0
  • David Gordon
    [quote="sizzlingbadger" wrote:
    The CO catalog is a sqlite database it will not perform well on a network drive. This is why Adobe and Apple don't let you do it.


    Apologies. I've not explained myself well.

    My setup has the C1 catalog file "Capture One Catalog.cocatalog" on my local Mac. My pictures are 'referenced', they live on a hard drive which is connected to another Mac and are accessed over the network connection. This is exactly how I have been using Aperture and, lately, Lightroom to manage my picture archive. To be clear, the catalog is not on the network, the images are.

    Previously both Aperture and Lightroom have been able to add images from the network drive to their catalogs. My point is C1 cannot do this.
    0
  • NNN635158767546269381
    Hallo,

    You can try to set to "none" (disable) "Auto Sync sidecar XMP". You will find it in Preferences -> Images.

    I have a similar setup as yours (Catalog on local Mac, Assets/pictures on a NAS). C1 was dead slow with this options enable but usable disable.

    PS: Ah PhaseOne, keep optimizing !
    😊
    0

投稿コメントは受け付けていません。