Slow image previews and scanning
I'm new to COne, but I'm quite liking it so far. The biggest thing I noticed that I am frustrated by is the speed - it's incredibly slow compared to the software I was using before it, and never slower than during initial image scanning.
Most operations hit the CPU pretty hard, editing a photo shows a massive spike in CPU activity, with all 8 cores of my i7 CPU hitting nearly 100% until the change has been completed.
However, scanning a directory for the first time and creating thumbnails (or whatever prep it's doing) uses only one core and takes many minutes for a few hundred images. Is there a way to kick this up a notch, and engage all the cores? Is this a bug or a feature? It's the only operation I've noticed where it's not running the CPU as fast as it can go.
Most operations hit the CPU pretty hard, editing a photo shows a massive spike in CPU activity, with all 8 cores of my i7 CPU hitting nearly 100% until the change has been completed.
However, scanning a directory for the first time and creating thumbnails (or whatever prep it's doing) uses only one core and takes many minutes for a few hundred images. Is there a way to kick this up a notch, and engage all the cores? Is this a bug or a feature? It's the only operation I've noticed where it's not running the CPU as fast as it can go.
0
-
First I have to congratulate PhaseOne for the upgrades of the C1 tools. Looks pretty good 😊
But I have also the impression that C1 7pro is much much slower than C1 6.
One example, when developing a picture you bloc every other action, everything becomes extremely slow.
Have C1 7 as a testversion on my laptop (Win 7prof. 64bit - dual core - 8gb RAM - Crucial SSD)
Will install another testversion on my desktop pc to compare the speed there.
But there is one real big disappointment - metadata, especially what concerns the IPTC, there is absolutely no improvement. The IPTC-tool is simply unusable. Compared to the IPTC at vers. 3.7.x it is a big step backwards.
What I mean is the layout and the functionality...0 -
The output from CaptureOne is far and away better than anything else I've tried. Everything about it is better, I am absolutely floored.
But wow, it is so slow. Time to render 503 images in AfterShot Pro: 5 mins. In C1: 38 mins. When running off the quick proofs for a client, guess which one I used?
Making edits is also slow, the software really isn't in a hurry to get anything done, ever. I guess quality takes time, and all that. 😉0 -
[quote="NFG" wrote:
The output from CaptureOne is far and away better than anything else I've tried. Everything about it is better, I am absolutely floored.
But wow, it is so slow. Time to render 503 images in AfterShot Pro: 5 mins. In C1: 38 mins. When running off the quick proofs for a client, guess which one I used?
Making edits is also slow, the software really isn't in a hurry to get anything done, ever. I guess quality takes time, and all that. 😉
For a client C1 or are you delivering less quality to a client. 38 mins is about the time to clean and check you're camera equipment after a shoot (or do something else usefull).0 -
Agree..Very slow compared version6. 0 -
I suggest you experiment with the OpenCL settings in the Preferences. 0 -
They're both set to Auto.
Turning them to Never slowed everything down more (processing time for 503 pics was over an hour and climbing before I killed it).0 -
Just made some simple tests with C1 vers. 3.7.10 (32bit) - C1 vers 6.4.4 - C1 vers 7.0 (all Pro-versions)
Test PC is a Laptop: Sony Vaio VGN-Z11VN - Windows 7 Prof 64Bit - 8GB RAM - 256GB Crucial SSD -
RAW-files from my Canon EOS 1Ds MIII
Tests:
1) Importing Images and calculate Previews (36 images)
2) Developing 36 images WITHOUT adjustments or crops into Jpeg sRGB 8Bit + Tiff 16Bit Adobe RGB
Results:
C1 vers. 3.7.10 (32bit):
Test 1 - Importing Images and calculate Previews (36 images): Time: 1:23 Min
Test 2 - Developing 36 images WITHOUT adjustments or crops: Time: 12:56 Min
CPU-Usage from 52-100% - RAM from 43-45% (lowest an highest during Test)
============================================================================
C1 vers 6.4.4 (64bit):
Test 1 - Importing Images and calculate Previews (36 images): Time: 1:05 Min
Test 2 - Developing 36 images WITHOUT adjustments or crops: Time: 15:28 Min
CPU-Usage from 64-100% - RAM from 50-100% (lowest an highest during Test)
=============================================================================
C1 vers 7.0. (64bit):
Test 1 - Importing Images and calculate Previews (36 images): Time: 1:48 Min
Test 2 - Developing 36 images WITHOUT adjustments or crops: Time: 28:49 Min
CPU-Usage from 94-100% - RAM from 74-84% (lowest an highest during Test)
========================================================================================
So far the Results using a stopwatch.
Concerning the handling of all 3 versions:
Vers. 3.7.10 has the big advantage that when the previews are calculated there is no more recalculating when scrolling through the pictures - so you can scroll from the 1st to the 36th picture in less than 2 seconds - it looks like a movie 😉
In Vers. 6+7 you have always to wait at least one or more seconds for each preview who is recalculated when scrolling trough the images.
In Vers. 7 the whole program slows down when developing a picture!!!
That was one of the big advantages of C1 compared with the most RAW-converters - I could develop in the background and work on the next pictures at the same time. Now we approach more and more the way Adobe goes with LR - first you adjust all the pictures you want than you develop them.
For me as a Press-Photographer the wrong way!
One more word as a Press-Photographer: Guys, please rebuild the IPTC - it is simply unusable - let you inspire by good old 3.7.x concerning layout (size!!!) and usability - or please make it at least possible to change the size of the floating tool not only in the length. Let me make it larger to be able to see my whole caption. !!!Please!!!
In Vers. 7 I had a strange problem when importing the 36 images - 1st the browser was only showing 16 of them but in the folder where the pix where imported all 36 appears - than the browser changes the number of previews which had to be generated from 16 to 38, 60, 64, 42 ....
Only after a restart of Vers 7 the browser was able to show all 36 images correctly.
Once again, the upgrade of some tools is really excellent - the question is, when will it be enough - are more features more important than a fast and stable software - is design more important than function?0 -
@ PhaseoneUser52346
The problem is, that not every one will be satisfied. A group of users want more features, other less features but more stability on their system.
I'am wondering, why my old system can handle C1 7; maybe because of a "new" Videocard (Radeon 6850)? I am really happy, that software developer start to support OpenCl even if it seems very tricky.0 -
I found version 7 slow until I got some help and suggestions here. I turned off OpenCl and I adjusted the screen resolution to the correct one for my monitor and now version 7 is not slow.
Vaughn0 -
[quote="Vaughn" wrote:
I found version 7 slow until I got some help and suggestions here. I turned off OpenCl and I adjusted the screen resolution to the correct one for my monitor and now version 7 is not slow.
The problems you were having were not the same (primarily, you complained about lag when selecting different images). Neither of your solutions apply to the situations I describe. I did try changing the preview size but the change, if any, was too small to be noticed. It didn't help the folder-scanning lag, and it of course has no effect on rendering speed at all.
C1 is ten times slower than competing apps, and I would very much love to see it optimized. Any speed boost will help. I think it must be possible to keep the amazing quality C1 offers without being so frustratingly slow.0 -
NFG is right, these are two different problems. I also tested some Programms a few months ago and C1 was the slowest of all.
In my actual tests V7 is slower then 6.44 and this should the first to be improved after the actual bugs are eliminated.0 -
[quote="PhaseoneUser52346" wrote:
In Vers. 7 I had a strange problem when importing the 36 images - 1st the browser was only showing 16 of them but in the folder where the pix where imported all 36 appears - than the browser changes the number of previews which had to be generated from 16 to 38, 60, 64, 42 ....
Only after a restart of Vers 7 the browser was able to show all 36 images correctly.
I'm getting this too - images I know are in the folder are not displaying in the browser, but if I search for the name of an existing but undisplayed file in the browser search dialogue it appears immediately.
I have no filters in place that would limit the images being displayed; and if I do a "wildcard" search for (say) the first three numbers in the file name, every file whose name contains those numbers will be displayed - even when they didn't appear in the first place.0 -
First time user......
CO7-DB too slow and buggy. I used for first time by up loading images stored on external drive (44031). Then CO7 activities started creating proxies. I was unable to use my computer for 22 hours while it was creating proxies. NOT GOOD.
Then I wanted to delete some non supported files (*.cr2) and the software hanged for ever. I had to full system shutdown the program at least 4 times. Finally I disconnedted the external drive and rebooted removed the search criteria just to get it to operate. Then it hung again so I go to shut down for 5 time. Not Good.
Need pro version to handle my old *.MEF (Mamiya ZD Back) Really?? Got to be kidding!!!
Seems like this program needs better testing prior to release......Going back to LR (never had any issues from the start)
Will not pay for Pro CO7 untill this program gets stable.0
Post is closed for comments.
Comments
13 comments