Why so SLOOOOOOOOOOW....?

pwnell

August 11, 2015 22:51

So I need to get this off my chest. C1 is to me like that woman you had an affair with. It is incredible with certain things, like image quality, the user interface, LCC corrections, Structure slider etc. But all the standard, boring, day to day activities it SUCKS at. And it sucks so much that one starts to wonder whether the things it does do well, is worth it. And I have come to the conclusion it is not. Of course I am referring to C1 as the mistress and LR as the wife.

I have decided after more than 4 hours of waiting for C1 to delete 28000 referenced photos from my catalog, that I will kill the Capture One process. Should not be an issue, right? As far as I know C1 uses SQLite, which is an ACID compliant database. So I tried re-opening it, and Capture One never ever starts again. I get:


Process:               Capture One [5993]
Path:                  /Applications/Capture One.app/Contents/MacOS/Capture One
Identifier:            com.phaseone.captureone8
Version:               8.3.2.6 (8.3.2.6)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Capture One [5993]
User ID:               501

Architecture:   i386
Date/Time:             2015-08-11 15:23:59.459 -0700
OS Version:            Mac OS X 10.10.4 (14E46)
Report Version:        11
Anonymous UUID:        7967B2D3-41DB-FE0B-8579-375AF2D7117C


Time Awake Since Boot: 11000 seconds

Crashed Thread:        0  UI  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000382fede0bec0

VM Regions Near 0x382fede0bec0:
    __LINKEDIT             00001234804a6000-00001234804b9000 [   76K] r--/rwx SM=COW  /System/Library/Extensions/AMDRadeonX4000GLDriver.bundle/Contents/MacOS/AMDRadeonX4000GLDriver
--> 
    MALLOC_NANO            0000600000000000-0000600000600000 [ 6144K] rw-/rwx SM=PRV

And no, OpenGL is disabled in Capture One. I cannot get it to load - ever. The catalog seems fine - at least, the SQLite DB verifies OK. I did log a support ticket for a similar issue with another catalog. This is the second time Capture One refuses to open after it crashed / was hung / got killed. Imagine if I had completely moved over to C1, and deleted my LR catalog?? Or if this is an important client shoot and I cannot open the catalog while the client is waiting for me to show them the results from a shoot?

I love what Phase One have done with the software, but they need some additional team members that focus on reliability and stability. I would much rather send a client a photo with slightly inferior image quality than not being able to send them any image at all, because my catalog will not open. And I am sure my clients would agree.

These issues together are blocking issues for me preventing the use of C1:

1. Stability issues - I have not managed after 2 weeks of trying, to get my 180000 photos from LR in to C1. I have not even managed to get 60k og photos moved over. Every time I have to start from scratch because I cannot open the catalog. And P1 support has not yet come up with any solutions.

2. Performance. I wait 2 minutes on a 6 core 3.5GHz Mac Pro with 64GB RAM and 1TB SSD PCIe drive to open a catalog with 60000 photos. LR opens my 180000 photos within 4 seconds. Same machine. I cannot delete 28k photos - after 4 hours of waiting I gave up. Searching is horribly slow too.

3. Do not import duplicates - this is a very important feature for me and its absence would make it very hard to continue with my old workflow.

4. Do not export certain keywords - this missing feature also would require several compromises on my part and massive modifications to my existing photos - coupled with the lack of mass removal of keywords, if I want to export any photos I will have to manually remove all internal keywords one by one from each image. Not cool.

For now it is back to DSLR Remote Pro + LightRoom + Photoshop. At least that combo never crashed on me. What a shame.

0

LSdigi.com

August 12, 2015 09:05

I always felt like Catalog's were a bad move for C1. 90% of complaints I read here are for Catalog problems and endless comparisons with LR and Aperture etc. C1 works best at individual sessions, its highly reliable and lightning fast tethering even with 80mp backs. Since catalogs are fairly new in comparison, I'm sure phaseone will catch up with performance issues soon.

0

Eric Nepean

August 13, 2015 01:22

I was about to post that I fully commiserate with pwnell as I have had the same experience of spending alot of time importing into CaptureOnePro and not being able to actually do real work on my cataloged images because of hugely long delays after each mouse click. But, things have improved!! Thank you, Phase One.

Having being away for some weeks due to a severe arm injury and consequent surgery, I logged into COP 8.3.2 tonight to remeasure the speed (slowness) for the purpose of this post, and except for the occasional hiccup, it is working reasonably OK and quickly. Occasionally it hangs for 50 seconds or so, then it comes back.

I observe that I have changed several things since my COP slowness problems disappeared. First, I have set "AutoSyncSidecarXMP" to "Never" on the realization that sidecar XMP files are used to sync CaptureOnePro Metadata with other editors, and I don't have any other editors I want to sync with. I think this helped a lot.

The other change has been the upgrade to 8.3.2.

On import issues, using COP 8.2.3, I observe that you must import images in batches of no more than several thousands of iamges, and let the import process completely finish. For about 5000 images, this takes about 2 hours all told on my iMac with 2.66GHz i5, 16GB RAM and Magnetic hard drive. First, there is about a one hour period where COP dutifully reports its activities and resource usage is fairly moderate. Then, when it says there is about 3 minutes to go, it becomes uncommunicative and unresponsive, and spends about another 45 minutes to an hour doing some kind of processing, during which time it is unresponsive. Using activity monitor's memory pane, you can observe that there are periods of time when it is using HUGE amounts of virtual memory, I saw over 50GB in use.You MUST let this processing finish, and it must finish successfully, i.e. without you having to terminate the process or it hanging or crashing. If the import is too large (for example 9500 images in my case), eventually it hangs and declares a resource unavailable error because it can't get enough virtual memory

IMO for large imports from Aperture or Lightroom, the key to success is to start with about 3000 images per import into a separate catalog, and check the import for completeness and correctness. For example, count the images after importing, and see if they have all been imported. Be aware that some image sizes and type cannot be imported. If not correct or incomplete except for unsupported images (at 3000 images, usually a finger problem or configuration problem), dump it and try again. If it is OK THEN import the new catalog into the main catalog.

If you have problems solving a configuration issue, import a hundred or so images into a test catalog, this will take only a few minutes, and you repeat it quickly while you sort out your problem. One you have the solution, back to your imports of 1000's of images.

Once you are successful, Increase the size of the imports by 1000 or 2000 each time until the import process chokes, or the size is inconveniently large to check.

I have a more detailed description of an import process for a large Aperture library and its metadata in this thread ....

0

NNN635158767546269381

August 13, 2015 09:26

[quote="pwnell" wrote:
I am trying to delete 28701 photos I just imported, because for some reason Capture one only imported 28701 out of 40000 images with no explanation / indication why the other files were skipped (they are standard JPEG and very readable by the OS).

Anyhow, it has been 4 hours and it is STILL busy. Beachball cursor, CPU at 200 - 400%, disk IO going crazy. This is a FAST system - 3.5GHz 6 core Mac Pro 2013, 64GB RAM, RAID10 hard drive for images and catalog is on a 1TB PCIe SSD. I cannot see any reason why this should be taking so long. Ideas?

I got the same issue...

Remember C1 will not import virtual copies. So they will be missing.

I imported my 80k lr catalogue in one day, painful slow. Yes, import a big catalogue from Lightroom is a time consuming, painful slow operation right now...

but then I did not use Lightroom anymore... Oh yes, only to make sideshow.

The DAM function in C1 is still behind Lightroom, I confess, but it is catching up.

Regards

0

SFA

August 13, 2015 12:42

Nicolas,

Taking your figures to mean 80,000 images imported and some recalculation undertaken in the process and "a day" to mean a period of not more than 24hours ...

There are 86,400 seconds in a 24 hour period so each image import would have taken around 1 second. Probably less if you include the sort of internal system activities that computers tend to take time out for now and again as they operate.

Is that really painfully slow?

Or is my interpretation of your numbers wrong?

Or maybe my understanding of your message?

Grant

0

jlarocco

August 23, 2015 16:23

I'd also like to complain about slowness.

I have a little over 19k images in a catalog, and switching to the "All Images" collection can literally take minutes with the spinning beachball cursor. Jumping around with the scrollbar will also usually beachball.

At this point I'm not even sure what to do. Trying to organize is painful because I have to jump back to All Images, and it *always* takes minutes, despite my having just been there 2 seconds ago.

0

Achim von Flatow

August 24, 2015 10:53

Well,
I don`t have a solutution at all, I only had run a test on my catalog.
Little more than 20k
To switch from a selection of 300 to show all, needs about (less than) one second.
I did this several times with different filters, the response is still as fast.
This ist my equipment:
Mostly EOS MK II/III
C1 8.3.2
MBP early 2011, 16G, SSD
The catalog is on a DOBO 5D, (with SSD cache)

Achim

0

Drugstore

August 24, 2015 13:04

Same experience here. Coming from LR because I thought it was slow I was just keen enough to buy C1 8 pro because of image quality just to find out that day to day workflow is way too sloooow. Especially when you have to handle lots of images every day. I have to fiddle too long with the interface just to go back to LR to do my tasks there to finish in time on latest iMac fully equipped.

Pitty!

0

Boris Sheikman

August 24, 2015 13:43

Yeah, the cataloging and managing of images is really really really really slow in Capture One compared to other systems. As I re-read that statement I realize I don't have enough "really" in there. 😕 I'm not sure why it's so slow. Cataloging is not a new technology considering that Adobe and Apple blazed the trail for everyone to follow. I think the software engineers are great mathematicians and they are great coders but they may be they do not fully understand database theory.

I am going to guess that they are also swamped with work. It wouldn't surprise me if Phase One only has 20-25 people working. Half are business leaders, 1/4 are marketing, and 1/4 are technical. I am going to further guess that Phase One is overwhelmed with the number of new Capture One users. Phase One used to cater to a small group of professionals. Then Apple stopped development of Aperture and Adobe went to the cloud. Lots of people found themselves wanting a new home and they found it in Capture One. My last guess is that there are now more amateurs/hobbyists using Capture One than professionals. Phase One doesn't know what to do with all of us! 😂

0

Comments