CO keeps me waiting again and again and again....
hi,
i'm having a serious issue here with CO10 (latest version) on an iMac 4K (late 2015) and and external TB Raid. independent of the amount of images i have in a session (only working in sessions since adjustments are stored with the file and i can easily move from desktop to laptop) CO has to "think" in between and every time on startup where it gets unresponsive with massive disk access. sometimes this happens along with a spinning beachball and i wonder: what the hell are you doing, CO? i leave a session just fine, previews updated, metadata written. reopen the session and the next best thing i have to do is wait for about 2-3 minutes for CO to do SOMETHING torturing my RAID..... it's freaking me out! this also occurs erratically in between, where CO just freezes for 1 minute and then we're good again.
the setup and storage are fine - lightroom does not show any of these issues with my external RAID. same goes for bridge, photo mechanic etc.... no reading or writing of XMP/sidecar enabled.
thanks for tips!
best,
t
i'm having a serious issue here with CO10 (latest version) on an iMac 4K (late 2015) and and external TB Raid. independent of the amount of images i have in a session (only working in sessions since adjustments are stored with the file and i can easily move from desktop to laptop) CO has to "think" in between and every time on startup where it gets unresponsive with massive disk access. sometimes this happens along with a spinning beachball and i wonder: what the hell are you doing, CO? i leave a session just fine, previews updated, metadata written. reopen the session and the next best thing i have to do is wait for about 2-3 minutes for CO to do SOMETHING torturing my RAID..... it's freaking me out! this also occurs erratically in between, where CO just freezes for 1 minute and then we're good again.
the setup and storage are fine - lightroom does not show any of these issues with my external RAID. same goes for bridge, photo mechanic etc.... no reading or writing of XMP/sidecar enabled.
thanks for tips!
best,
t
0
-
If you are Syncing Metadata via XMP try turning it off to see what happens. 0 -
that's exactly what i wrote in my post. it is disabled already. to be perfectly clear here's the screenshot of my settings. thanks so much!
https://snag.gy/TAjLpJ.jpg0 -
[quote="Tim Hufnagl" wrote:
that's exactly what i wrote in my post. it is disabled already. to be perfectly clear here's the screenshot of my settings. thanks so much!
https://snag.gy/TAjLpJ.jpg
Sorry, somehow skipped it when reading.
There have been some discussions about external storage and RAID systems in the past.
I don't use one so I am not up to speed on the details.
I suspect that LR, et al, use a very different approach to Capture One (and other programs I have used) with regard to what they present to the userat start up and how they present it. (Also during editing in some instances).
The effects of whatever is happening seem to be far more evident on Mac systems than they are on Windows systems.
That said there have been a lot of posts about mixed experiences for performance in different configurations so you may find something of interest by going through previous posts. If you have already done that then perhaps just wait for someone with related experience to pop up and share thier understanding.
Or create a Support Case and ask for a technical explanation.
You mention session as opposed to Catalogue.
Assuming you are using a session based workflow the two things I can think of that might be happening as the session opens are the selection of images according to some filter(s) left in place when the session was last closed or the regeneration of Preview files if the default Preview size is different as start up compared to the size saved when the session was previously closed - or something similar to that if using multiple monitors, etc.
The Log files may provide some guidance as to the source of the workload you observe.
HTH.
Grant0 -
sfa! filters are a good point, although i would really take for granted that such settings would not lock down CO for 1-2 minutes. i do have a dual monitor setup and set the preview size to the same value for all of my installs of CO using the same sessionfile and -folders. i also suspected this to be part of the problem. great to idea to check the log files - any hint on where those do hide?
i guess i'll now copy a full session over to my built in SSD and play around with it for a while and see if i can provoke similar behaviour. thanks again for your good info!
t0
Post is closed for comments.
Comments
4 comments