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. ⚠️

Will v4 ever work correctly with network drives?

Ben421
I run a small Mac workgroup based around OS X Server. All our image files reside on the network, and for years v3 has has no trouble accessing and working with source (RAW) and process (Output) folders over the network.

v4 hangs when attempting to access these same folders. Copying files to work locally and copying back severely disrupts our workflow.

Is v4 ever going to work reliably with network shares?
0

Comments

2 comments

Date Votes
  • Paul Steunebrink
    I would not know, to answer your question, nor any other user here I think. But you might discuss the issue here if you like when you provide more details like version of OS X on clients and server, and version of CO4, what happens good and bad. Network drive issues appear regularly here, not in large numbers, but they exist. More details might increase response.
    0
  • Ben421
    Thanks for your reply, Paul, and I apologise in advance if I come across as upset, but I'm tired of being given the run around by Phase One support on this matter.

    My network is high-quality and well maintained (Cat-5e cable with 3com gigabit switches). My Xserve and MacPro clients have run Mac OS X 10.4.11, 10.5.5, and 10.5.6, all with the same results. I have tested using all versions of v4 (v4.1, v4.1.1, v4.5.2, v4.6 and v4.6.1 - though we're currently on v4.6 per Phase One advice).

    Our working folders are shared from the Xserve using AFP. No other application has a problem reading from or writing to these shares, including: the Adobe Creative Suite (CS3 and CS4); Lightroom, other RAW processing applications (Canon's DPP, Hasselblad Phocus, Leaf Capture), iView Media Pro, Apple Preview AND CAPTURE ONE v3.7.9.

    Until recently, we used Network Homes folders (server stored home folders) in our office, but v4 would NOT EVEN RUN in this configuration - it hung on every launch. I have thus re-configured my entire office to use Local Home folders, SOLELY TO GET CAPTURE ONE V4 RUNNING.

    Capture One v4 now launches, though it still hangs when accessing the shares.

    I have been advised to delete my caches, my preferences, my default sessions, re-install the app, try a new OS X user, and sacrifice a fresh chicken-head by the fifth-night-moon.

    None of this makes a difference. Capture One v4 is inherently broken when accessing network shares.

    The application hangs as soon as I browse to a shared folder.
    0

Post is closed for comments.