(fixed) Why does C1Pro 8 so slooooooooow on mac
I was using C1Pro 8 on windows and it was working properly, I like it so much!
However when I use C1Pro 8 on my new purchased macbook pro, it was FXXKIN slooooooow!!!! Loading all the time and I am not able to know what it was loading!!! Selected a picture, loading for a minute; open a session, loading for few minutes; scrolling down, loading; even i haven't click anything (or i dunno what i did so let it unhappy...), loading...
I am sure I have a good control of number of pictures - under 2000 pictures each session... I have not enough courage to use catalogs to manage all my raw files...
I am using:
Macbook pro 13inch
OSX 10.10.4
Capture One Pro 8.3.2
I love it but I am not able to work with it =(
However when I use C1Pro 8 on my new purchased macbook pro, it was FXXKIN slooooooow!!!! Loading all the time and I am not able to know what it was loading!!! Selected a picture, loading for a minute; open a session, loading for few minutes; scrolling down, loading; even i haven't click anything (or i dunno what i did so let it unhappy...), loading...
I am sure I have a good control of number of pictures - under 2000 pictures each session... I have not enough courage to use catalogs to manage all my raw files...
I am using:
Macbook pro 13inch
OSX 10.10.4
Capture One Pro 8.3.2
I love it but I am not able to work with it =(
0
-
Why? I don't know. Maybe you can share some more information on your way of working, storage location, etc?
I am using CO on old Macbook Pro mid 2009 and Macbook Pro Retina late 2014. No problem on both. The old one is just a little bit slow on masking, import (preview creation) and export. Local sessions with up to 2k images, referenced catalogs with up to 50k images on USB HDD.
Regards,
Hans0 -
There can be several reasons for a slow response. Hardware resources like processor, RAM and disk drive. The 13" MBPs are not the fastest in town, depends on age. For example a Core2Duo processor, 4 GB RAM and 4200 rpm disk won't make CO8 fly.
Are you always using the same session or create new ones regularly?
Are the sessions you run created on Mac or Windows?
What you could try is to create a new session and start with 10, next 100, next 500 images in the Capture folder. See how it performs after previews are created.
Looking forward to your response.0 -
[quote="HansB" wrote:
I am using CO on old Macbook Pro mid 2009 and Macbook Pro Retina late 2014. No problem on both. The old one is just a little bit slow on masking, import (preview creation) and export. Local sessions with up to 2k images, referenced catalogs with up to 50k images on USB HDD.
I noticed that my statement wasn't as clear as it should be. I wanted to write:
I am using CO on old Macbook Pro mid 2009 and Macbook Pro Retina late 2014. No problem on both. Editing in my local sessions with up to 2k images and referenced catalogs with up to 50k images (catalogs local, images on USB HDD) is working fast and without delays. The old one is just a little bit slow on masking, import (preview creation) and export.
Regards,
Hans0 -
Thanks for your reply.
I know MBP 13" is not the fastest system in Mac family, however why I emphasised the problem on mac because I used C1 for several version on Windows, it was acceptable even on my 4 years old laptop with i5, 8Gram, external not SSD HDD, at least I know why I was waiting for response.
Why does its performance better on 4 years ago pc? It was not fast but smooth.
I am using session on external HDD with USB 3.0, will try it on my new thunderbolt external HDD (not SSD).
I found that it slow performance and always loading problem is not a only case on me in this forum. I hope development team face against this issue.0 -
[quote="NN404UL" wrote:
... I am using session on external HDD with USB 3.0, ...
It's pretty well documented in these forums that the Session or Catalog should be on your internal HD (HDD or SSD), otherwise you can expect all sorts of issues, as you've experienced.
If you feel it should work anyway, please raise a support case via the website.0 -
From my personal experience I can tell you that C1 is performing poor when the Session or Catalog file is located on an external drive. This is, as mentioned earlier, documented in this forum. Also, from my experience, images on a NAS can lead to a poor performance as well, while storing images on an USB HDD seem to work fine. The first step you could do is to store your Session on the local SSD and see whether it helps or not. 0 -
I am having slowness problems with a 2008 quad core Mac Pro but only related to browsing (so far as I know, I am still testing it out). C1 takes a long time to load thumbnails so it constantly pauses when I am browsing through images and it usually pauses or beachballs for at least 20 seconds whenever I switch from one folder or collection to another. Every time it is paused or beachballing my drive (internal drive) is going like mad. Aperture and Lightroom do not have the problem. They pause once in a while or there might be a blank thumbnail for a second or so but that's about it.
I have my images (mostly Canon raw files) and the catalog on an internal drive that has plenty of extra room on it and nothing on it other than the images and catalog. It is a standard 3GBs drive that works fine with the other apps.0 -
[quote="NN635776644845284578UL" wrote:
I am having slowness problems with a 2008 quad core Mac Pro but only related to browsing (so far as I know, I am still testing it out). C1 takes a long time to load thumbnails so it constantly pauses when I am browsing through images and it usually pauses or beachballs for at least 20 seconds whenever I switch from one folder or collection to another.
...
What is the size of your previews? (Preference setting).0 -
My preview size is 1920. Displaying a particular image is quick but displaying the grid of thumbnails is often slow. It takes a while to catch up when scrolling through a folder, often pausing until it fills in blank thumbnails, and I can hear the drive working hard when this is happening. Clicking on "All Images" really shows it. My comparisons are Aperture and Lightroom. Aperture has absolutely no trouble doing any of this. Lightroom is not as quick as Aperture but still much faster than Capture One. 0 -
[quote="NN635776644845284578UL" wrote:
My preview size is 1920. Displaying a particular image is quick but displaying the grid of thumbnails is often slow. It takes a while to catch up when scrolling through a folder, often pausing until it fills in blank thumbnails, and I can hear the drive working hard when this is happening. Clicking on "All Images" really shows it. My comparisons are Aperture and Lightroom. Aperture has absolutely no trouble doing any of this. Lightroom is not as quick as Aperture but still much faster than Capture One.
Capture One is very likely re-creating the preview files and thumbnails to take into account the Process Recipe/Active Proof profile and all of the settings that are present for the current edit session. These may not be the same are the saved thumbnails and previews.
I have no idea what Aperture might have done.
From my memory of V1 LR it displayed a preview jpg from past activity and worried about re-displaying it with any new values only when you changed something. It also deployed an interesting approach to appearing to be fast by flashing up the most obvious major visual changes but actually completed the work more slowly in the background. Whether that still applies in more recent versions I have no idea.
Which method should be considered best is open to discussion. And personal opinions. An possibly a new thread started every month.
Grant0 -
Thank you for all your reply!! And I apologize for late update!!
First of all, I have to strike myself, Second, upgrade to C1Pro 9 without reason, without check for the new features, and immediately!!
For the slow story, after i got a thunderbolt hdd with formatted Mac OS file format, it all fixed!! I checked that the problem may caused by the old hdd was using NTFS format, the tool for read and write NTFS format made it slow.
Thanks all!!0
Post is closed for comments.
Comments
11 comments