Slow performance on CO 9 and CO 10
Hi
I have discovered some poor performance with CO 10 (and also on CO 9) in following areas:
- adjusting slides after long work in CO (30-60 minutes). Suddently updates to image after adjusting sliders takes 3-5 seconds.
- processing JPEGs takes massive amount of time. Exporting 75 images in 100% full size JPEG takes approx. 45 minuttes.
I work with rather large files from Nikon D810 (36mpix) on a max spec'ed MacBook Pro (late 2015, i7 2.5 GHz, 16 GB RAM, 512 GB pic-e SSD, macOS Sierra).
Is it just because my MacBook Pro isn't quick enough ?
Merry Christmas to you all 😊
/Anders
I have discovered some poor performance with CO 10 (and also on CO 9) in following areas:
- adjusting slides after long work in CO (30-60 minutes). Suddently updates to image after adjusting sliders takes 3-5 seconds.
- processing JPEGs takes massive amount of time. Exporting 75 images in 100% full size JPEG takes approx. 45 minuttes.
I work with rather large files from Nikon D810 (36mpix) on a max spec'ed MacBook Pro (late 2015, i7 2.5 GHz, 16 GB RAM, 512 GB pic-e SSD, macOS Sierra).
Is it just because my MacBook Pro isn't quick enough ?
Merry Christmas to you all 😊
/Anders
0
-
Well lets hope that they are quick 0 -
[quote="NNN636156073736100359" wrote:
I'd like you to be aware of this: It's been some days I'm working with the support team by sending them materials, screen recordings, elements from the OSX monitor activity
I have just done the same and will report back with their feedback. Let's see what they have to say. I do like their support case system.0 -
I have heard back from Phase One support and they have confirmed it as a performance bug however as to when this is going to fixed and in which update, I have no idea.
They did indicate that they read the entire TIFF file upon import and when zooming into the file at 100% or beyond. The thumbnails you see in the browser window are "regenerated proxies". I am not sure what they imply by "generated proxies" whether Capture One is creating its own thumbnails and storing it in SQLLite or reading the embedded JEPG inside the TIFF. Something i am waiting for clarification upon.
Edit: As soon as I posted this I had received an update of my query from support. I have pasted their reply verbatim.
"I can not say when it will be fixed, or in what future release. as this is beyond what I can tell. If there is an easy fix in the code it might be a quick fix. If there is a complicated underlying issue that connects to a whole lot of other things it might take time to fix. However, R&D are aware if this and I am sure it it a quite high priority to solve this. The generated proxy is stored in capture one cache in a catalog or *.cop file in a session, it is basically a lower res jpeg of the original file. this we call the "preview" and this is the one that regenerates if your "regenerate preview" size of this is set in capture one preferences. You never view the original unless you zoom in to 100%. hence why you always need to do your proofing at 100% view and not in fit view. Proxy/preview is not stored in the sqllite. as this is considerad as cache and can be rebuilt from original file. thumbnails are a bit different. But if there is no thumb in the Tiff we will generate one and this does on mac take more time then on windows, due to underliend image handleing "engines".."
I would like to know if any Windows users are experiencing the TIFF issue. There is hope.0 -
I'm running the trial version of Pro 10 for now and have been a paid Pro user of C1 for quite a few years.
I bought a new iMac 27# 5K machine about a week ago. Referring only to C1 pro execution, it was almost unusable with its baseline 8GB of memory (hardly surprising) and I received my new 32GB yesterday and found the expected great improvement.
HOWEVER:
I simply cannot get C1 Pro 10 to import files into a new Catalog. No error message is generated but nothing happens. I found it worked if I copied an existing Catalog and import new files into that, however bizarrely even that is impossible. The imports I did achieve were incredibly slow.0 -
[quote="col_du_aspin" wrote:
I have heard back from Phase One support and they have confirmed it as a performance bug however as to when this is going to fixed and in which update, I have no idea.
They did indicate that they read the entire TIFF file upon import and when zooming into the file at 100% or beyond. The thumbnails you see in the browser window are "regenerated proxies". I am not sure what they imply by "generated proxies" whether Capture One is creating its own thumbnails and storing it in SQLLite or reading the embedded JEPG inside the TIFF. Something i am waiting for clarification upon.
Edit: As soon as I posted this I had received an update of my query from support. I have pasted their reply verbatim.
"I can not say when it will be fixed, or in what future release. as this is beyond what I can tell. If there is an easy fix in the code it might be a quick fix. If there is a complicated underlying issue that connects to a whole lot of other things it might take time to fix. However, R&D are aware if this and I am sure it it a quite high priority to solve this. The generated proxy is stored in capture one cache in a catalog or *.cop file in a session, it is basically a lower res jpeg of the original file. this we call the "preview" and this is the one that regenerates if your "regenerate preview" size of this is set in capture one preferences. You never view the original unless you zoom in to 100%. hence why you always need to do your proofing at 100% view and not in fit view. Proxy/preview is not stored in the sqllite. as this is considerad as cache and can be rebuilt from original file. thumbnails are a bit different. But if there is no thumb in the Tiff we will generate one and this does on mac take more time then on windows, due to underliend image handleing "engines".."
I would like to know if any Windows users are experiencing the TIFF issue. There is hope.
Thanks for the update, which confirms my suspicions.
As for;But if there is no thumb in the Tiff we will generate one and this does on mac take more time then on windows, due to underliend image handleing "engines".."
well, that's BS, since A) my TIFF files do have embedded previews, no need to generate one, and B) Aperture (or Lightroom) handle TIFFs just fine on the Mac. What their statement is really implying, is that C1's engineers don't know how to take advantage of macOS's underlying architecture. Begs the question whether they ever thought about actually asking Apple for advice on how to build a performant RAW editor. It's not like Aperture is a competition anymore.0 -
[quote="dredlew" wrote:
What their statement is really implying, is that C1's engineers don't know how to take advantage of macOS's underlying architecture.
Over the Christmas break, I had reinstalled Mac OS Sierra on my mac together with all the other applications I use. Since I had ample space I partitioned and installed evaluation copies of Windows 10 Enterprise, Capture One 10 and Photoshop CC.
I copied one of my projects (including catalog and images) that I had shot and edited in December to the windows partition. I could not believe my eyes how well Capture One v10 handled the large TIFF files. My TIFF files varied from 1.1GB to 3.5GB with a lot of layers. Changing between TIFF files was lightning fast even the same between NEF to TIFF or TIFF to NEF.
Even under a freshly installed version of Sierra, the TIFF files from the project lagged.
Albeit not being a scientific test but it does prove that Capture One v10 under the mac os has some underlying issues pertaining to the OS.
On a different note I am impressed with Windows 10 as well. The question is do I move to Windows 10 ?0 -
I cannot believe my eyes !!! Seems like Phase One with their release of 10.0.1 seems to have fixed the large TIFF file issue I have been so vocal about in my various posts.
There is literally no slowness when going from NEF to TIFF or vice versa especially with >2GB TIFF files.
Bravo Phase One !!! You have made me very happy. I just hope its not short lived.0 -
[quote="col_du_aspin" wrote:
There is literally no slowness when going from NEF to TIFF or vice versa especially with >2GB TIFF files.
Sorry if I missed it: are you talking layered or flattened TIFFs?0 -
[quote="alan_b" wrote:
Sorry if I missed it: are you talking layered or flattened TIFFs?
All my TIFF files are layered. I cant have flattened files as I will be shooting myself in the foot.0 -
Great news - thanks! 0 -
[quote="alan_b" wrote:
Great news - thanks!
any chance you can share your feedback on layered TIFF performance ? I am well aware that you will have a different mac system compared to me hence the feedback as it could help someone else.0 -
[quote="col_du_aspin" wrote:
[quote="alan_b" wrote:
Great news - thanks!
any chance you can share your feedback on layered TIFF performance ? I am well aware that you will have a different mac system compared to me hence the feedback as it could help someone else.
I stopped using layered TIFFs in C1 since they were unusably slow.
I'm not much help here - not upgrading from 9.3 until 3 showstopper bugs are fixed:
Open CL crashing
Lens movements -> histogram disappears
Layered TIFFs (fixed?)0 -
After the upgrade to C10, I experienced painful export speed. 30 files 20 minutes.. I was thinking either my comp. is to slow or the new version of c1 is...
If I wouldn't come across OpenCL term and method of disabling it, I'd definitely go trying to install v9 again or do other silly stuff.
All the speed issues from my experiences and were related to OpenCL (graphic card memory if I understand correctly)...Whatever that is, it helps maybe with previews but for sure disable it for 'processing'. My CPU worked with 20% with OpenCL set on 'auto' mode while exporting files in C1, only 20%! And therefore it took a century.
After I disabled 'OpenCL' for processing, CPU kicks in with 100% and 30 files are processed in 2minutes.
To disable OpenCL:
c1-> edit -> prefferences -> General ->Hardwareacceleration (use openCL for)-> display auto/processing NEVER!0 -
Might be that a GPU bug is also back in V10 that was solved in 9.2 somewhat and fully in 9.3.
You might want to have a look here
viewtopic.php?f=61&t=21549
If the time it takes to export TIFF or JPG images increases over time almost linearly than this is most likely this bug. I don't see it on my machine but in V9 days not all machines have shown the GPU bug either.
Switching off GPU is the only work around I know off but it has some drawbacks on overall computer performance.
Best
Frank0 -
Hello everyone here. I'm back because as I wrote previously here the bug was so horrible and made CO10 so sluggish I had to reuse Lightroom again. No fixed given by the support even a month after I contact them, I decided to ask them to cancel my subscription because I couldn't use CO10 normally.
I just came back yesterday to ask them if it's now fixed and they just answered me few minutes ago, "It's mark as fixed in 10.0.1". I know it's written fixed in the release note of the 10.0.1 but just in the WINDOWS column not in the MAC one.
So please users, can you confirm me now you don't undergo any slow performances with CO10 on MAC OSX when clicking, displaying multi layers TIFF files please?
Thank you a lot.0 -
At least with simple layered TIFFs 10.0.2 seems to work correctly for me (older versions would hang for several minutes with the same files).
However, I still have a raft of performance issues relating to the catalogue handling and OpenCL dropping out with errors. I have an open support case for these, but there is as yet no solution. For example, launching CO10 is an embarrassment if "all images" was selected when you last quit - as it just sits there seemingly doing nothing for about a minute. Not good if you are with a client. As a work around, all you can do is to avoid ever selecting "All Images".
Part of the problem is that CO10's SQL handling appears to have a number of problems. One issue I had was lags of up to 10 seconds when selecting more than one variant. I fixed this by opening the catalogue DB in an SQL editor and deleting the indexes. Once CO10 had rebuilt them, selection now works quickly again. I can not say that I have ever needed to do this with any other software 😕
On the "all images" hang, I suspect that what is happening is that CO10 is trying to update the contents of the DB while also trying to read from it (likely an update run the first time that an album or similar is selected). The result is a huge amount of conflicting IO on the database, with not much to show for it.
I have no idea if my problems are specific to my catalogues, or if they are generic. However, if a solution is not forthcoming shortly, I will have to dump CO and revert to Lightroom - which at least works reliably and quickly. The performance problems are particularly galling because one of CO10's primary improvements was supposedly its performance.0 -
No it is not you. There are lots of similar comments and observations and several people have filed bug reports. Unfortunately 10.01 was even worse than 10.0 and 10.02 did not show any improvements at all. I myself have submitted more than 5 technical support cases over the months since the first release. Support has not yet been helpful and for some cases I just don't get any answer at all.
As there no other points official point of contacts provided by PhaseOne all we can do is wait and see...0 -
[quote="NNN636156073736100359" wrote:
So please users, can you confirm me now you don't undergo any slow performances with CO10 on MAC OSX when clicking, displaying multi layers TIFF files please?
Thank you a lot.
You and I had similar problems with regards to layered TIFFs. I can confirm that there is zero slowness when it comes to clicking between NEF to TIFF, TIFF to TIFF or TIFF to NEF. I could not believe my eyes. Yes all my TIFF files are massive, greater than 1.5GB. I even tried putting my catalog file and image files on an external hard drive (5400RPM) via USB 3.0 and it was very fast.
I tested it using v10.0.1.0 -
[quote="col_du_aspin" wrote:
[quote="NNN636156073736100359" wrote:
So please users, can you confirm me now you don't undergo any slow performances with CO10 on MAC OSX when clicking, displaying multi layers TIFF files please?
Thank you a lot.
You and I had similar problems with regards to layered TIFFs. I can confirm that there is zero slowness when it comes to clicking between NEF to TIFF, TIFF to TIFF or TIFF to NEF. I could not believe my eyes. Yes all my TIFF files are massive, greater than 1.5GB. I even tried putting my catalog file and image files on an external hard drive (5400RPM) via USB 3.0 and it was very fast.
I tested it using v10.0.1.
Unfortunately, I cannot confirm this. Still seeing this lag with TIFF files in v10.0.2. Created a brand new catalog, imported images and made some TIFFs with layers out of it. With comparatively small (~400MB) files, I do get about 5secs lag when selecting a TIFF file. Would you mind providing one of your TIFF files for download so that we can see whether it would be file related? TIA0 -
@dredlew - sorry for the late reply. Are you still have slowness issues? direct message me and I can send you a TIF file over to see if you still have speed issues. 0 -
[quote="col_du_aspin" wrote:
@dredlew - sorry for the late reply. Are you still have slowness issues? direct message me and I can send you a TIF file over to see if you still have speed issues.
No worries, thanks for checking in. I did have the issue still with 10.0.2 but it's finally gone for me in 10.1.0.
I also don't experience locking up of the UI anymore when trying to import a folder of images that has a bunch of TIFF files in it.
So far so good, fingers crossed it stays that way! 😄0
Post is closed for comments.
Comments
51 comments