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
-
[quote="deejjjaaaa" wrote:
[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 ?
Probably because I was using W7 64-bit. In a 32-bit OS an application is limited to 2 GB max. (application space, which is half of its virtual memory space of 4 GB).
Memory management is different in the 64-bit version of the operating system (its main reason of its existence). That is not a problem when using a 64-bit application, but the 32-bit version of CO6, running on Win7 x64 shows the same behavior and that does not look healthy to me. This may be related to the Out of Memory issue on the 32-bit version of CO6, which is addressed here in other threads and has caught Phase One's attention for sure.
The OP's issue is a different one however because he is running CO6 (64-bit) on Win7 x64. His issue is probably related to combination of CO6, his hardware and software setup and (last but not least) the specifics of some NEFs. I have not been able to reproduce the issue. I can only try to point into a direction and give advise for a workaround to the best of my knowledge.
In general: there are so many variables in the equation, that a change of one variable may change the outcome entirely. I hope to present my actions for comparison here (no rocket science by the way) when time is available.0 -
[quote="Alex1" wrote:
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.
As with the OP, which uses the 64-bit version, the 'Out of Memory issue did not occur in my testing (it did with the 32-bit version of CO6). So I tend to believe this is a different issue (but perhaps at programmer's level related but beyond my competence).
The 'Out of Memory' issue has no doubt grabbed Phase One's attention and I think that your efforts in other threads on this forum has been a great help in that process.
Update: I managed to get an Out of Memory error on my CO6 64-bit, Win7 x64, 6 GB RAM, Core i7 setup with the DX1 files in no time. Reported to Phase One.0 -
Regarding the extensive use of memory by CO6 in combination with D1X NEF files, I got a confirmation from Phase One on my report about the issue. It is in the hands of R&D department now.
What remains a mystery still is how OP's system hangs (or at least CO6) after clicking a single D1X file or some NEFs from other camera models. I would like to suggest to do a memory check (memtest86) to rule out any bad chip.0 -
[quote="Paul_E" wrote:
[quote="Alex1" wrote:
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.
As with the OP, which uses the 64-bit version, the 'Out of Memory issue did not occur in my testing (it did with the 32-bit version of CO6). So I tend to believe this is a different issue (but perhaps at programmer's level related but beyond my competence).
The 'Out of Memory' issue has no doubt grabbed Phase One's attention and I think that your efforts in other threads on this forum has been a great help in that process.
Update: I managed to get an Out of Memory error on my CO6 64-bit, Win7 x64, 6 GB RAM, Core i7 setup with the DX1 files in no time. Reported to Phase One.
The only points that seem to be very apparent to me are,
There are very real problems and faults with v6.1.1
Phase One are and have been very aware of those faults and problems since even before I had raised my support case prior to even mentioning it on this forum, despite the fact that they vehemently denied that they had any knowledge of such faults and problems.
I could go on but is there any point??
The memory on my system is working fine, as is the operating system, the processor and the entire configuration.
COne v6.1.1 is the problem and PhaseOnes support or at least poor provision of it is simply compounding the problem and brushing it under the mat until they can work out where they have gone wrong, without actually having to admit they have gone wrong .0 -
As a user of PhaseOne since DSLR V1.01...I think the characterizations you make are illogical and untrue. PhaseOne has always responded to me with great support, and probably were trying to do so with you absent specific information or sample files.
The fact is this apparently occurs with D1X files, and I'm assuming most testing is done with current models. Most performance complaints do not have to do with specific files, but rather system's that are subpar AFA components...that is logically the first place one starts. Which is why you were given that information. And of course, as PhaseOne supported D1X files when the camera was introduced, it is listed in the supported camera database.
So the tradeshow dealer, Paul, myself and probably PhaseOne have attempted the most common advice first, but of course if we're not using D1x files....our results differ.
You read this as nonresponsive or deception....I understand your frustration, but understand that for all intents and purposes you are involved in a specific and narrow userbase, and unless someone with a D1x participates in the beta program...welll....
Also know that while all camera makers are non-cooperative AFA releasing file info...Nikon in particular has had a history of attempting to make theirs entirely proprietary...0 -
[quote="John4" wrote:
As a user of PhaseOne since DSLR V1.01...I think the characterizations you make are illogical and untrue. PhaseOne has always responded to me with great support, and probably were trying to do so with you absent specific information or sample files.
The fact is this apparently occurs with D1X files, and I'm assuming most testing is done with current models. Most performance complaints do not have to do with specific files, but rather system's that are subpar AFA components...that is logically the first place one starts. Which is why you were given that information. And of course, as PhaseOne supported D1X files when the camera was introduced, it is listed in the supported camera database.
So the tradeshow dealer, Paul, myself and probably PhaseOne have attempted the most common advice first, but of course if we're not using D1x files....our results differ.
You read this as nonresponsive or deception....I understand your frustration, but understand that for all intents and purposes you are involved in a specific and narrow userbase, and unless someone with a D1x participates in the beta program...welll....
Also know that while all camera makers are non-cooperative AFA releasing file info...Nikon in particular has had a history of attempting to make theirs entirely proprietary...
I am also a user since V1.01. I have over 135,00 .work files (and whatever the other ones are called) from the many years that I have been using C1 Pro. It was me who first pointed out that although PhaseOne said C1 was compatable with D1X RAW files, intitially, it wasn't if they were compressed. It was me that pointed that out to them and provided the compressed RAW files to them to rectify the situation.
In the support case that I raised over this matter, I provided all the info I thought necessary plus all the info and files that I was subsequently asked to provide. I wasted time and effort, fitting 8Gb of RAM into the machine when PhaseOne suggested this was what might be needed even though I knew it was not the fault.
As I have pointed out in this thread, performance isn't even brilliant with D2X or D300 files.
I use this program to make my living, I dont spend my time playing with it or obessessing over it on forums.
This forum has many references to problems such as I have raised with this program, I am sorry if I do not come across as a fanboy of PhaseOne and I havent only been using COne Pro for five minutes, either.
I am only even using 64 BIT Windows 7 and 64 bit COne Pro because that is what I was advised to do by a PhaseOne tech when I told him at a trade show that V6.1.1 was not good on Windows XP Professional 32 bit,( he actually told me it wouldn't be).
To my knowledge, my system meets the recommended requirements for what I am trying to use. I did not see anywhere that I would have to install a high end, current processor or treble the amount of RAM to get this thing to work properly!
I could perhaps understand your glib comments if I had looked into this forum and not seen any similar reports of the problems that I am experiencing.
I do not appreciate participating in a support case to only eventually be told by PhaseOne that "something seems amiss" and that they will look into it and then to receive no reply as to roughly how long that may take, be it days, weeks or even months..
I thank everyone for their input but all I can see in here is guesses and occassionally, acknowledgements that there are faults with the program and maybe PhaseOne will eventually release another "upgrade" that will mysteriously make it work, properly, while never admitting there is a fault in the first place and consequently wasting users time in having them resort to remedies that can never work.0 -
[quote="NN122830UL" wrote:
...
The memory on my system is working fine....
Can you confirm you have tested it with memtest86 or similar tool or that it is an assumption?0 -
[quote="Paul_E" wrote:
[quote="NN122830UL" wrote:
...
The memory on my system is working fine....
Can you confirm you have tested it with memtest86 or similar tool or that it is an assumption?
Yes, I have tested it. The memory is working, all of it, at its stated clock speed and in Dual Channel mode
The memory was tested by using CPU-Z, it is working perfectly as is the rest of the system. COne Pro, however, sadly isn't!0 -
I was being anything but glib. This is a USER forum...I was stating my bona fides as well as my experience with PhaseOne which is worlds different than yours.
Also different...I installed Win 7 64 bit precisely because I wanted to use more memory and advantage that extra memory. That has been useful for both COne AND Photoshop. I do not expect any programs to work as well with minimum sysytem requirements as with better specs on memory as well as other hardware. I'm not sure why you would want to run with 4 gigs of memory rather than 8, I agree with the dealer that says it will run better with 8.
I also don't expect a timetable with a support case....or releases. That has been tried in the past and found wanting because an estimate was treated as a promise contrary to it's definition.
I think everyone here has been cordial to you, your responses less so....and if you weren't anonymous, I'd promise not to respond to your posts. I can't do that easily with an assigned username here , so any responses I make are not intended to provoke you further...just ignore them if you would. Tia, John0 -
[quote="NN122830UL" wrote:
[quote="Paul_E" wrote:
[quote="NN122830UL" wrote:
...
The memory on my system is working fine....
Can you confirm you have tested it with memtest86 or similar tool or that it is an assumption?
Yes, I have tested it. The memory is working, all of it, at its stated clock speed and in Dual Channel mode
The memory was tested by using CPU-Z, it is working perfectly ...
Excellent tools like CPU-Z read-out and present configuration data. However, this tool does not stress-test memory and won't detect any defective bit in that piece of hardware.
If you are interested in such a test, and considering the circumstances you might, I would recommend a tool like memtest86. By doing this you can rule out memory as a potential cause. Please note that a memory module with a defect can remain undetected for years but break a particular application only. On multiple occasions unrecoverable issues with Capture One in the past were in the end resolved after a memory test utility showed the real cause.
I am aware that a trial-and-error approach of problem solving is time consuming, hence it is your decision.0
Post is closed for comments.
Comments
40 comments