Speed over a gigabit network
we have a gigabit network. The session folders and files are all accessed over the network and have been since the c1 3.x.x days. In 3.x.x there was no delay making adjustment and loading up sessions. In c1 4.x there were a lot of delays and crashes whilst the sessions loaded up. In c1 5 our experience is that the network speeds are slower again even with sessions previously opened in c1 5. I'm assuming that the session previews are re-created so i can accept it the first time. The software is very often unusable. Sessions seem to crash or hang with no explanation very very frequently.
0
-
I've also experienced this.
after I shoot I load my sessions onto a FC RAID. Functionality wise V5 is great on the host machine but virtually unusable over a network.
Back when I used V3 I often shot tethered to one machine and networked in to the same session from another running V3 to edit and sort whilst the host machine handled the capture. It was a great workflow allowing my client to choose and move shots while I was shooting.
This sadly wont work with V4 or 5. Will it be implemented in the future?
please let me know if there's any tweaks to make V5 run better over a network.
kind regards to the phase 1 team.
Andy0 -
Is slowness the major issue? or does it crash much more than when using a local drive? 0 -
Its probably permission conflicts. Is your session on the boot drive? And make sure that if its on a non boot drive make sure you ignore permissions. 0 -
[quote="rap_digital" wrote:
Its probably permission conflicts. Is your session on the boot drive? And make sure that if its on a non boot drive make sure you ignore permissions.
Can you explain in more detail? Where in C1 can you tell it to ignore permissions? If this is the case why is it never a problem in v3?0 -
I had major issues with V4 but have been improved hugely with V5.
Dont upgrade to snow leopard if you want to carry on using V3.
I raised this issue with support, apparently this software isnt supposed to be used across a network0 -
I used to do this type of thing a lot in the past I'll try find some time over the week end to find the best way to run it with Vers5. 0 -
[quote="monkeybiz" wrote:
I raised this issue with support, apparently this software isnt supposed to be used across a network
why don't they mention this anyhere then?[quote="rap_digital" wrote:
Its probably permission conflicts. Is your session on the boot drive? And make sure that if its on a non boot drive make sure you ignore permissions.
The sessions load quickly with no issues in c1 3, but in c1 5 they are awfully slow and the application often crashes. The network is fine for all other apps including BNLT adobe photoshop, bridge and photomechanic.
It is definitely C1 4 & 5 that have the issue.
BTW we have getting on for 15TB of images and growing. If we can't work over the network how else are we supposed to do it? Copy sessions to local drives then copy them back? Call that a workflow?0 -
I know photographers that use Capture One 5.0 over a network without issues. I think it must be something about your server configuration. Try creating simple folders of images first on your server (1 image then 10 images etc...) and see at what point things stop working... 0 -
Of course you should also contact Phase One's support with your server information... 0 -
we did contact support but to approximate their words, they only support their software and not other peoples networks. 0 -
Have you tried storing the session locally then incrementally backing up the session to the network every minute or so? What is your goal by having the session on the network, two people can simultaneously apply adjustments and process or as a backup procedure? 0 -
I don't have a spare 1.6TB locally which is roughly how much image data we currently have. We have a network based DAM system called gotit which runs on a server. The files must be local to the server, hence on a network to the three workstations. Copying sessions to a local drive to use is asking for trouble in a multi person envirnoment. The other reason is that's the way we do it! 0 -
[quote="NN1311111" wrote:
I know photographers that use Capture One 5.0 over a network without issues. I think it must be something about your server configuration.
Capture One v3 worked fine in our server environment. Neither 4 nor 5 have. We also use CS4 Photoshop, Bridge, Indesign, iView Media Pro, PhotoMechanic, Mac Finder, QuickTime, Silkypix in the same server and network environment with no issues.
P1 say it's our problem and to "check our settings". Check them against what? They make no recommendations for server environments.
They have said that they are a small company with an insufficient labour resource to support C1 in server environments. What on earth are they doing marketing to professional studios in 2009 for then? If they can't stand the heat get outta the dogdamn kitchen!
Over our southern summer I'll be testing Aperture (new version on the way I hear) and Lightroom 3 in our server environment.[quote="rap_digital" wrote:
What is your goal by having the session on the network, two people can simultaneously apply adjustments and process or as a backup procedure
We have two workstations with C1 and PS installed as well as two laptops and an iMac in our studio all with C1. We have a third workstation which doesn't have C1 but has PS. We use C1 for raw conversions and Photoshop for final retouching. It is not uncommon for one person to be performing raw conversions on one workstation and another person retouching the converted files on another workstation. The simplest, and safest, way to manage this is to store the sessions on a server.
Copying a session to a local drive is problematic;
• it slows workflow down massively
• unless a byte for byte comparison is done you risk file corruption. Byte for byte comparison roughly doubles the copy time each way.
• it introduces complication and human error - a *very* bad combination.
Our session folders are moved from one machine to another only by Retrospect. Retro manages the copying, byte for byte verification, and deletion of original. Additional copies of sessions one three local drives creates a versioning nightmare - the possibility that newer work will be written over by older work exists and believe me, where that possibility exists it will become a reality.
The only way around the potential data loss issues is the creation of a new session (on a local drive) every time a client places an order for final files and duplicating the select raw files into the new session. This is messy. You wind up with duplicate raw files in different sessions with different adjustments as well as multiple output folders to go collecting converted files from when the client comes back wanting everything from one shoot delivered together. Incomplete work would have to be tracked down (we always know where everything is in our studio because it's *always* on the server).
Far better for all the finished files from one shoot (one session) in one folder. Multiple sessions are fine but creating new ones for every set of conversions would more than double the number of sessions we maintain.
I'll say it again - it all worked fine in version 3 (like so many things). It all works fine in EVERY other piece of software we use.0
Post is closed for comments.
Comments
13 comments