Terrible Performance with C1Pro on Windows 7 64 bit
I have been experiencing appaling performance from C1Pro V6.1.1 on Windows 7 64 bit. The operating system was newly installed and the system has a Pentium 4 Dual Core 2 E8400 3Ghz processor and 4Gb of RAM. The Graphics card is an Asus EAH 4650 HD with 1Gb of onboard memory and the motherboard is an Asus P5Q Pro. There is more than enough hard drive space on 4 sata 7200 rpm hard drives. No other applications are showing any problems on this system, all are running just fine except C1Pro
I changed up to this 64 bit operating system from XP Professional 32 bit because C1Pro V6 was lousy on that and I was advised to upgrade by a C1 Tech at Focus. He actually told me, 32 bit is not very good for V6.1.1 (I kid you not)
I have already gone down the road of raising a support case and after lots of messing around and inconvenience, they have told me they have no idea whats wrong and will look into it. I asked how long a solution would take but havent received an answer.
My performance expectation benchmark is based on my experience of using C1Pro since its introduction at V1, and regularly and often ever since then. I have not had good experiences with C1Pro since the demise of V3.7.10.
An example of how poorly C1Pro V6.1.1 is performing is that the computer will just hang, indefinately, when doing something as simple as just "selecting" only 9 Nikon RAW files, when C1Pro has been the only program running. I can go in to detail about how much RAM etc, needs and uses, when even just being open and not doing anything, plus when you actually try to get it to edit, if need be.
This recent catastrophic experience has left me extremely inconvenienced and frustrated.
PhaseOne support have told me that they have no Knowledge of anyone else suffering performance issues, in fact they say, their feedback suggests the opposite.
This doesn't help me and so far PhaseOne support are unable to, either.
Does anyone have any answers and/or suggestions?
Thanks in advance
I changed up to this 64 bit operating system from XP Professional 32 bit because C1Pro V6 was lousy on that and I was advised to upgrade by a C1 Tech at Focus. He actually told me, 32 bit is not very good for V6.1.1 (I kid you not)
I have already gone down the road of raising a support case and after lots of messing around and inconvenience, they have told me they have no idea whats wrong and will look into it. I asked how long a solution would take but havent received an answer.
My performance expectation benchmark is based on my experience of using C1Pro since its introduction at V1, and regularly and often ever since then. I have not had good experiences with C1Pro since the demise of V3.7.10.
An example of how poorly C1Pro V6.1.1 is performing is that the computer will just hang, indefinately, when doing something as simple as just "selecting" only 9 Nikon RAW files, when C1Pro has been the only program running. I can go in to detail about how much RAM etc, needs and uses, when even just being open and not doing anything, plus when you actually try to get it to edit, if need be.
This recent catastrophic experience has left me extremely inconvenienced and frustrated.
PhaseOne support have told me that they have no Knowledge of anyone else suffering performance issues, in fact they say, their feedback suggests the opposite.
This doesn't help me and so far PhaseOne support are unable to, either.
Does anyone have any answers and/or suggestions?
Thanks in advance
0
-
You can use the Process Explorer http://technet.microsoft.com/en-us/sysi ... s/bb896653 to obtain more detailed information of which programs/processes are taking the CPU when your system hangs. Sometimes, it can be the AntiVirus program that is the culprit. 0 -
I think most are very pleased with the performance of CO6. Urukhai is correct, Process Explorer will help you in examining if anything is taking too much system resources.
The question I have for you is when you updated to Win 7 64 bit, was the install of Win 7 a clean install where the old Win XP partition was deleted, and reformatted, or an upgrade install (simply installing the new OS over the old). When doing the upgrade install, if you had any system problems from the prior OS, they will still appear in the new OS install. Why I do not know.
However my belief is the system itself. The Pentium 4 is an old processor, a dinosaur by today's standards. My computer is not the newest by no means, I am running an E8400 Core 2 Duo with two gigs of memory running XP Pro 32 bit, and have no issues with CO 6 performance. Depending how large your RAW files are, this will also require more system resources for higher MP cameras.0 -
I have some problems.
CO 5 do not have such issues.0 -
@Paul1921
Hi Paul, I did a "clean" install if Windows 7 64 bit, there is no way of doing an "upgrade" to it from 32 bit XP Professional.
I can see in Resource manager in Windows 7, what is using what, there is nothing amiss not until C1Pro is turned on, then the memory is completely swallowed with very little effort given to C1 to perform.
I think I have already mentioned, Paul, I too am using a Pentium 4 Core 2 Duo E8400 processor but I have 4Gb of Ram and on 64 bit windows 7, the performance is terrible. I have already tried it with 8 Gb of RAM in and the problems still manifest.
All of this information and more has been given to PhaseOne support in the support case, raised previously and they have still not come back to me with any answer beyond saying something seems very much amiss and that they are looking in to it.
I am still awaiting a conclusion!
P.S. I am trying to process Nikon Raw files from D1X, D2X and D300, The largest being about 13Mb but the most problematic are perhaps those from the D1X but that is not to say things are rosy with the files from the more recent cameras0 -
[quote="Urukhai" wrote:
You can use the Process Explorer http://technet.microsoft.com/en-us/sysi ... s/bb896653 to obtain more detailed information of which programs/processes are taking the CPU when your system hangs. Sometimes, it can be the AntiVirus program that is the culprit.
As far as I am concerned, the problem is that the 4gb of memory is being swallowed up almost intantaneously even when C1Pro V6 is selecting as few as 9 images.
I have tried it with 8Gb of RAM in and that gets swallowed up with very little demand made on C1Pro but it is clearly shown that it is C1Pro swallowing all of the memory0 -
Another user's take...it is not so much that COne "swallows memory" but rather it utilizes as much as it can...and that's a good thing. I have 3 installs under Win 7 64 bit...with 8, 16, and 24 Gigs ram respectively....I see a difference between the 8 and the others with files on a local drive, which is the benefit of having more RAM. I cannot belive you see no difference between 4 and 8 gigs...leads me to belive this is not a RAM issue but something else....
Minimum system requirements are those that will run a program, but in the case of graphics programs...from Photoshop to COne...there has always been a speed benefit to faster CPU's, drives, and amount of RAM accessed...currently with both PS and COne, the GPU becomes a major player also....
...in both programs, as features are added over time, if the computer/components are constant...new versions likely run slower, even though at one time PS updates enhanced performance over the life of the version, I haven't noticed that in a number of years.
I find V6 runs best on my system with an i7, 24 gigs of RAM, 480 NVidia, and all SSDs....but acceptably well on the base system with 8 gigs of RAM and an older GL240....and I think it's real good advice to move to 64 bit to address more RAM than the 3.4 or something XP would do.....
Rather than viewing COne as the problem...have you fine tuned your computer? Win 7 offers some speedup tips...you don't say wether you tried those. At a minimum...turning off "indexing" on all drives will probably double the performance of programs like COne and PS that write files to disk as they work...if you see little difference between 4 and 8 gigs of RAM...I suspect your system is not optimized.0 -
I downloaded "Process Explorer and ran C1Pro through its paces, it didn't take long before it crashed.
I turned it on and selected just one D1X Nef. The figure for Private Bytes shot up to 1,137,508, Working Set to 901,428, CPU settled at 0.60.
I selected 8 files and then the figures for Private shot to 2,901,324 and for Working Set to 2,725,504, CPU settled at 0.72
I selected 16 files and the figures shot to for Private Bytes, 3,296,048, Working Set 2,649,212, CPU jammed at 49.88 as soon as I went into styles and tried B&W. The program had now hung, wouldn't do a thing.
All of these figures above are from just what CaptureOne was using as displayed by Process Explorer. The processor was not having any problem (archaic or not)
This tells me nothing apart from confirming what I already knew, CaptureOne is swallowing all of the available memory out of 4Gb to just "select" only 16 D1X nefs.
No other application or program seemed to be doing anything out of the norm and nothing was coming anywhere close to using as much memory as COne was, not by a long chalk.
After writing this, I went and made a coffee and when I returned, COne was still "Hung" but it would be wouldn't it because it was hogging all of the available memory from 4GB of Ram and it was the only program running.....
It had gotten in this state by just selecting 16, 7mb files and trying the B&W in "Styles"
I did read that it was actually compatible with D1X files, didn't I?0 -
[quote="NN122830UL" wrote:
As far as I am concerned, the problem is that the 4gb of memory is being swallowed up almost intantaneously even when C1Pro V6 is selecting as few as 9 images.
I have tried it with 8Gb of RAM in and that gets swallowed up with very little demand made on C1Pro but it is clearly shown that it is C1Pro swallowing all of the memory
C1 v6 takes enormous amount of RAM to run is definitely a programming problem, rather than any achievement that it is more advanced.
I found this in the CaptureCore.log:2011-04-03 08:15:17.875 (0x05c0) | TERMINATING CaptureCore
2011-04-03 08:15:17.875 (0x0494) | Thread 1172 (0x494) exited [P1 Cam Finder - monitor thread]
2011-04-03 08:15:17.890 (0x05c0) | Error: CaptureCore object leak detected. 7 objects not released.
2011-04-03 08:15:17.890 (0x05c0) | ------ CaptureCore terminated ------
Memory was simply leaking. Moving to 64 bit Windows will just buy C1 more time before the this leaking hitting the limit.0 -
Hi Urukhai,
PhaseOne support asked me to provide those logs to them along with others which I did, last week. They dont seem to have been able to make any progress in solving this problem since they have had them, bar stating that something seems amiss (Tell me about it???????).
And COne is still "Hung" and completely unresponsive. I will have to close it down in Task Manager (yet again)0 -
I realized I still have an older 4 GB RAM, dual core system with Win7 standing idle currently. I would love to run some tests with some D1X NEFs. However, I do not have the those D1X files. Any chance you can make one available here with a download link from a file transfer service on the internet? 0 -
[quote="Paul_E" wrote:
I would love to run some tests with some D1X NEFs. However, I do not have the those D1X files.
as usual imaging resources might be helpful
there should be 2 raw files available :
http://www.imaging-resource.com/PRODS/D ... U_COMP.NEF
http://www.imaging-resource.com/PRODS/D ... UNCOMP.NEF
also I think here is one more = http://www.rawsamples.ch/raws/nikon/d1x ... ON_D1X.NEF
but if you want to stress C1 w/ some batch processing you can just produce multiple copies of those 3 raw files (make it 300) and that should be good enough0 -
[quote="Paul1921" wrote:
However my belief is the system itself. The Pentium 4 is an old processor, a dinosaur by today's standards. My computer is not the newest by no means, I am running an E8400 Core 2 Duo with two gigs of memory running XP Pro 32 bit, and have no issues with CO 6 performance. Depending how large your RAW files are, this will also require more system resources for higher MP cameras.
my experience is that v6 runs just fine w/ up to 16mp raw files (Panasonic GH2) on 4GB W7 provided that it is a 32 bit system and you do not attempt to run something like photoshop at the same time and deal w/ your raw files one by one... people really should not use 64bit Windows (and C1) on just 4Gb RAM.0 -
[quote="deejjjaaaa" wrote:
...
as usual imaging resources might be helpful
Thank you for the links. I used to go there; apparently I missed it. Downloaded the files, will create some copies and go.
Note that the D1X files are of special interest because of the necessary computation that is necessary for creating output (and preview). This is due to the non-square pixels (stretched in 1 direction). This is the only DSLR sensor I am aware off that has this specific characteristic. This may affect performance different than comparable NEFs with approx. the same resolution.0 -
The actual "developing" of jpgs, tiffs etc from the RAW files doesn't seen to be the problem. It is the actual editing of them that causes the massive memory drain. As I have pointed out, even just "selecting" only 16 RAW files seems to have the program struggling.
Please find below, a link to down load a zipped folder of files (about 20 0f them)0 -
[quote="Paul_E" wrote:
[quote="deejjjaaaa" wrote:
...
as usual imaging resources might be helpful
Thank you for the links. I used to go there; apparently I missed it. Downloaded the files, will create some copies and go.
Note that the D1X files are of special interest because of the necessary computation that is necessary for creating output (and preview). This is due to the non-square pixels (stretched in 1 direction). This is the only DSLR sensor I am aware off that has this specific characteristic. This may affect performance different than comparable NEFs with approx. the same resolution.
Perhaps, Paul, but I havent read anywhere that COne is now not compatable with such files.....
And also note, this problem is not only with D1X files, the performance isn't brilliant with D2X and D300 files, either.
I must add to, it is disappointing in the extreme that I am having to resort to using this forum to address this problem myself, considering that I have seemed to have exhaused what PhaseOne Support are going to do about it.0 -
[quote="NN122830UL" wrote:
[quote="Paul_E" wrote:
[quote="deejjjaaaa" wrote:
...
as usual imaging resources might be helpful
Thank you for the links. I used to go there; apparently I missed it. Downloaded the files, will create some copies and go.
Note that the D1X files are of special interest because of the necessary computation that is necessary for creating output (and preview). This is due to the non-square pixels (stretched in 1 direction). This is the only DSLR sensor I am aware off that has this specific characteristic. This may affect performance different than comparable NEFs with approx. the same resolution.
Perhaps, Paul, but I havent read anywhere that COne is now not compatable with such files.....
And also note, this problem is not only with D1X files, the performance isn't brilliant with D2X and D300 files, either.
I must add to, it is disappointing in the extreme that I am having to resort to using this forum to address this problem myself, considering that I have seemed to have exhaused what PhaseOne Support are going to do about it.
Regarding D1X, my intention was not to imply any incompatibility. See it as a special interest from my part.
Regarding other files like from D2X and D300, I noticed you performance issues, but I understood D1X was particularly troublesome.
I am sorry to read about your disappointment. I hope the discussion with other users here brings some relief. It is worth a try.
By the way, do you use the 32- or 64-bit version of CO 6.1.1 on your Win7 x64 system? (you can check the menu Help, About)0 -
Hi Paul, I am experiencing these problems on the 64 bit version of COne. I am using that after being advised by PhaseOne at the Focus Trade show in the UK that the 32 bit version was not good. This advice alse necessatated me to change my operating system from Windows XP Professional 32 bit to Windows 7 64 bit, so you can imagine the inconvenience and upheaval this advice has caused me. 0 -
Have the people who asked/suggested for the RAW files to be made available, managed to discover anything??
I ask before I take them down off my server as I'm guessing they have been up long enough to be accessed by those who requested them.0 -
[quote="NN122830UL" wrote:
Have the people who asked/suggested for the RAW files to be made available, managed to discover anything??
I ask before I take them down off my server as I'm guessing they have been up long enough to be accessed by those who requested them.
I have downloaded the files. Thank you.0 -
[quote="Paul_E" wrote:
[quote="NN122830UL" wrote:
Have the people who asked/suggested for the RAW files to be made available, managed to discover anything??
I ask before I take them down off my server as I'm guessing they have been up long enough to be accessed by those who requested them.
I have downloaded the files. Thank you.
And?, Paul
Any wiser?0 -
[quote="NN122830UL" wrote:
[quote="Paul_E" wrote:
[quote="NN122830UL" wrote:
Have the people who asked/suggested for the RAW files to be made available, managed to discover anything??
I ask before I take them down off my server as I'm guessing they have been up long enough to be accessed by those who requested them.
I have downloaded the files. Thank you.
And?, Paul
Any wiser?
Work in progress. Prepared a workstation, will run some tests with different versions of CO (5 & 6, both 32-/64-bits of 6) on it. To be continued...0 -
Sandy bridge i7 8 gb of ram with win 7 64 bit GeForce GTX 750
The performave is Excelent, cannon 7D RAW 25mb plus raw files0 -
So do you need an i7 processor and 8 gb of RAM to make it work? 0 -
[quote="NN122830UL" wrote:
So do you need an i7 processor and 8 gb of RAM to make it work?
Nope - Cap One 6 flies along on my Intel Core 2 Q8300 2.5 ghz Quad Core and 6gb RAM - 7D files here too.0 -
And?, Paul
Any wiser?[/quote]
Work in progress. Prepared a workstation, will run some tests with different versions of CO (5 & 6, both 32-/64-bits of 6) on it. To be continued...[/quote]
I might take a look back on this forum and see if there has been any progress, but its unlikely as I dont think this is getting anywhere. Thanks for your help anyway0 -
I do think this has something to do with the Nikon files....my positive report earlier was with larger files, but they were Canon. Shouldn't make a significant difference...and the initial thread did not specify Nikon.
I'd certainly give Paul more than a 48 hour window to do some research before getting testy. He is another user rather than a support person (although the most knowledgeable user here) and perhaps he is in a Master's pool this weekend...0 -
[quote="NN122830UL" wrote:
I might take a look back on this forum and see if there has been any progress, but its unlikely as I dont think this is getting anywhere. Thanks for your help anyway
Paul's just a user, and this is officially just a user forum - have you raised your problem with Phase One in a support case?0 -
I had some friends over for the weekend.., 😉
But spend some hours on the topic nevertheless. Setting up some procedures, running the tests (even the most basic) and making notes is rather time consuming. Brief observations (cliffhanger alert) are:
With regard to memory use there is a great difference between CO5 (modest use) and CO6 (both 32 & 64 bit: extensive use). Second, there is a great difference in memory use by CO 5 & 6 between different raw files, with the D1X leading the pack in that it uses significant more memory when you open and select a file. Memory use with the D2X and D300s files I tested was considerably less.
I made a remark about the D1X earlier in this thread (complex computations) and my assumption seems to be confirmed (fine for me, not for the user).
Add both early conclusions and you have an explosive mix with D1X and CO6: when I only selected the 1 D1X image, CO6 uses 1 GB of memory; selecting 18 images and this grows to 3 GB.
However, although I was able to crash CO 6.1.1 32-bit with an Out of Memory dialog (different issue), CO 6.1.1 64-bit (and CO 5.2.1) kept running. This is in contrast with the OP's experience, pointing to the fact that another issue specific for his setup is affecting the performance (see remark below about the video adapter).
My assumption is that the very modest graphics adapter might help the 4 GB setup afloat in combination with CO6's extensive memory use. The OP's system with 4 GB RAM and 1 GB video memory would not be my preferred setup (too much video RAM versus main memory). This has to do with Windows memory management, although this should theoretically be a non-issue with Win7 x64, but might work out differently in day-to-day practice. Unfortunately, I could not verify this. More RAM might help however.
Best advise: do not use Multi View mode in the Viewer
When selecting multiple images (for applying adjustments or batch process) it is best to stay in Primary View because CO5 and 6 eat up a lot of memory with D1X NEFs when displaying multiple images in the Viewer.
Second advise: stick with CO5 until new developments surface
This is only for the OP with D1X files. You can use CO5 (installed and activated) next to CO6. Use your CO6 key to activate CO5. Do not use both versions concurrently.
Hardware and OS I used:
Pentium D 820 (dual core, 3.2 GHz), 4 GB RAM, 80 GB HDD, Matrox 128 MB graphics adapter (all this was very much 'en vougue' in 2006 😁 ); Windows 7 Ultimate SP1, 64-bits. I think this setup comes very close to that of the OP.
I might find more coming week; if so I will report.0 -
[quote="Paul_E" wrote:
Add both early conclusions and you have an explosive mix with D1X and CO6: when I only selected the 1 D1X image, CO6 uses 1 GB of memory; selecting 18 images and this grows to 3 GB.
W7 32 bit / C1V6 32 bit = select all 18 files, apply different adjustments to all of 18 them several times, process = CaptureOne.Exe stays in 600-700 Mb ram, ImgCoreProcess.Exe stays in 100-200 Mb Ram beats me how you managed to get it grow to 3GB ?
and yes, multiview will lead to C1 running out of memory...0 -
I use 6.1.1 32-bit standard edition on a system with 4BG mem and will get the 'out of memory crash' without selecting multiple images or using multiview or even using any of the new v6 features. Just by going from one image to the other it will soon crash - as long as some of those images have rotation and/or cropping applied. I am still waiting for Phase One to fix this. 0
Post is closed for comments.
Comments
40 comments