C1 Pro v3.7 crashing regularly.
Hi,
logged a trouble report for my laptop when C1 Pro v3.7 kept locking up. Stopped using mousewheel pain in the.
Two seperate machines giving the same problem unexpalined crashes.
1/. Laptop 1.6gb Centrine 1gb of memory and 15gb spare disk space no wacom tablet.
2/. Main PC AMD 64 3500 with 3gb of memory and 100s of gb spare disk, wacon tablet, but hasn't been used. For a while there I thought it was a memory problem as I have been told in the past, so I removed the suspect memory and crash.
Both machines seem to crash if you try to do any work while C1 is creating thumbnails or previews. The work I mean is if you change development directories, scroll using the sidebars through images, try to adjust an image or even move and start a conversion. It doesn't happen straight away, could be 10-15 seconds later.
Today was the first serious attampt at using this machine since the motherboard came back from fan replacement under warranty. C1 crashed about 4 times in a matter of minutes.
This is getting beyond a joke. As I said in an earlier post I reported this problem before the final release of v3.7 (about 3 days). ☹️
Ian M ❓
logged a trouble report for my laptop when C1 Pro v3.7 kept locking up. Stopped using mousewheel pain in the.
Two seperate machines giving the same problem unexpalined crashes.
1/. Laptop 1.6gb Centrine 1gb of memory and 15gb spare disk space no wacom tablet.
2/. Main PC AMD 64 3500 with 3gb of memory and 100s of gb spare disk, wacon tablet, but hasn't been used. For a while there I thought it was a memory problem as I have been told in the past, so I removed the suspect memory and crash.
Both machines seem to crash if you try to do any work while C1 is creating thumbnails or previews. The work I mean is if you change development directories, scroll using the sidebars through images, try to adjust an image or even move and start a conversion. It doesn't happen straight away, could be 10-15 seconds later.
Today was the first serious attampt at using this machine since the motherboard came back from fan replacement under warranty. C1 crashed about 4 times in a matter of minutes.
This is getting beyond a joke. As I said in an earlier post I reported this problem before the final release of v3.7 (about 3 days). ☹️
Ian M ❓
0
-
Ian ~
Seems as though your systems meet or exceed the Requirements:
PC
OS: Windows 2000 or XP
CPU: Min PIII, P4 Preferred
RAM: 512, 1Gb Preferred
This is atypical behavior and the fact is that Capture One is not unstable. Some users have had RAM modules go bad, while some have had to reinstall their OS when it has gone bad.
Any other programs working in the background?
Are you using Sessions from older version of C1?
Where are the image files located?
Previews and Work files are built for a Session when it is Added to Permanent Collection, otherwise they are temp files. Session name on tab is in italicised if NonPermanent. Waiting for these files to build before working on them is good practice.
The Windows platform is 'happiest' when there is a single Set Process Folder to location. The easiest is to checkbox Always process images to associated image folder this way processed images arrive in a subfolder named Develops to the Session folder.
Let us know of your progress.
Sincerely,
k c0 -
Keith,
I think you mis-understood me.
I have been using C1 since ver 1.3. Last year I spent 4 months in Europe using 3.5 on my laptop, it did not crash or hang. 3.6 used to hang, but not crash. I have since re-built my main PC, 3.6 used to hang, but not crash. It is only since 3.7rc1 that this crashing has started on both laptop and main PC. The laptop has had the same hardware configuration for 18 months.
Under previous versions I could use the mouse wheel without a problem, I could scroll through the thumbnails as the were being built, work on the one in the main screen, develop, change directories for the developed photo without crashing or hanging. 3.7 is advertised as a multi threaded application, so far it appears to be a very limited single thread.
I am using the same workflow that I have since I bought C1, I put all my captures in a folder with date they were taken. I develop the photos into suitably named folders rather than develop and then have to move them.
A number of people have submitted an enhancement that each development tab be able to point at a different directory, you are saying that 3.7 is only stable if pointed at a sub-directory under the capture folder?0 -
Keith,
I don't use C1 to capture my photos, I Canon Zoombrowzer, because it allows me to auto assign capture folders. I tried a couple of other capture methods using a capture folder and moving the raws to a specific folder afterwards, but ended up loosing a number of files because the C1 move process is very unwieldy. The \"move to\" process might be fine in a studio, but when you have been on the road all day or for a couple of days, having to re-assign a \"move to\" folder all the time is not a practical way to work.
I just tried making a day file the capture file and it stays in italics, even after a re-start of 3.7
At one stage I did go through a series of crashing incidents, which every one said was memory, but even after a major upgrade of memory it didn't change things. Turns out it was the motherboard and even though it was being used well with in the manufacturers specifications, it actually needed much slower memory than was recommended by the handbook. It just didn't crash with C1 though, it would just stop of its own accord usually with C1 loaded, but not being used.
Didn't have that problem after the motherboard was replaced until v3.7.
Ian M ☹️
Ian M0 -
Ian,
I've been having the same trouble and I'm trying to isolate what settings (if open image after processing is checked for example) might trigger it. It wasn't until I found your post that it occured to me that using my scroll on my mouse might be a problem but after testing it a few times I can get C1 Pro version 3.7 for Windows to crash regularly. To be clear I'm talking about AFTER the previews are finished loading at startup. I learned long ago not to do anything while Phase One's previews are loading. Bad idea. I know of two other photographers that are having the same trouble yet Phase One refuses to acknowledge there is a problem. One of them has already decided to use another product but I still really like the Phase One interface.
I would be very interested to hear from you if you come up with any resolution. Thanks.
Jamie Bloomquist, Camden, Maine, USA0 -
Jamie,
I have reduced the crashing significantly, but still can't stop it from happening with C1 open the background. Sometimes it just crashes of its own accord, somedays many times adya and other days nothing.
I have been able by accident to get oneo2 other applications to crash with the same error message.
It is something to do with the mouse, I have loaded new drivers, at one stage I appeared to have 2 copies of the mouse driver running, don't know how. At the moment the mouse has to be configured every time I reboot the computer, open it in Control panel and close it.
The mouse alos stops working sometimes after a screen saver. If I have my iPaq connected when the screen saver cuts in the mouse won't work after normal desktop use is restored. I have a tablet which works fine and gets me out of a fix occassinally.
Also the mouse only works in one or two USB ports.
My mouse/keyboard set is a Logitech MX700, which I think is a USB 1.0/1.1 only and doesn't like working into 1.x/2.x USB ports.
What I can't remember if I have had this issue since I installed this motherboard, I rather expect I have. It did appear on previous 64 bit mb's, but it also appeared on my Centrino laptop, thatis why I thought it was a C1 problem. But it only happens when I use this mouse/keyboard from memory. At one stage this mb was spening more time at the MB company getting fans replaced under warranty.
In summary, the crashing, not the lockups appear to be a function of the USB keyboard/mouse combination. The mouse is due for replacement shortly I am having button bounce problems with it, worn out.
Sorry for the long post, but I hope it helps explain what you might need to look for and find with your system.
I have used a couple of other convertors and still find C1/PO the best, the work flow is straight forward except for capture and the functionality I am still learning to get the best out of. I think the next release will fix some of your issues. 😄 😄
Ian M0 -
[quote="RF Cat" wrote:
Two seperate machines giving the same problem unexpalined crashes.
This is getting beyond a joke. As I said in an earlier post I reported this problem before the final release of v3.7 (about 3 days). ☹️
Ian M ❓
Just keep remembering Ian, that Capture One is "very stable" (according to them) and that all of us who are having this problem have bad RAM modules, and/or need to totally wipe our hard drives clean, and re-install our OS, even though all of the other software on our systems is running fine... I'm running Capture One Pro v3.5 (the last stable version of this software), Photoshop CS2, RSE-2005, Quark XPress, and a host of other photo/graphic-related apps without issues, and they adamantly suggest that it's "MY" computer that's the problem? With all due respect, I think NOT...
They keep telling us that it's the fault of "our" own computers that this problem exists, even though it really is "their" responsibility to make sure that their software runs successfully on systems with various hardware and configurations.
The folks at Phase One (if there are any left, after the exodus to Pixmantec) need to stop blaming our systems regarding this problem, and start figuring out a fix, before they lose another large chunk of their customer base... I'm running out of patience at this point, and eagerly await the point in time that RSE-2005 introduces their fully featured product, hopefully with Magne Nilsen's profiles...
For now, I'll continue to use good old v3.5, which likes my machine just fine, does not crash, and I'll just have to hold onto the memory of that short amount of time (between crashes) that I enjoyed that dynamic noise reduction slider, and other updated features that v3.7 "sort of" offered us.0 -
I to have all to many regular crashes. I have been running Windows computers now for 10 years and know how to build them from the ground up and have built several. I paid these people good money and they have taken a good product and ran it into the ground. How can they blame so many customers for there creation not working. Are we all stupid, they must think so as they are saying we have faulty computers. I keep mine in tip top shape with as little as possible running in the background, including the C1 card reader.
C1 3.7 crashes all the time at any time. Will they want more money to upgrade if they can fix it? There is a lot of RAW converts comming out. I guess we will all switch to something else. They were the best but are getting left behind with slow upgrades for new camers and a buggy programing.
🤬
Mark McGillveray
Canada0 -
Hi I am Back again
I just tested my memory with a program called Memtest 86 V3.0. It tests chip ram and motherboard ram. It ran for 5.75 hours with not one error. I am running a P4 3.0 Ghz with 1 Gb ram on a ASUS P4P800 SE motherboard. I wanted to see if C1 claims of memory faults were correct. I guess not. C1 is the only program that crashes on my machine, and I have a lot of different programs that I have fun with. I do not make my living with photography, but it has been my hobby for 32 years. I have a now unused colour darkroom with an Omega D760 enlarger. Pitty the pros who C1 claims they are working for.
Mark McGillveray0 -
Now I feel bad. I installed C1 3.7.1 and nothing has crashed for 20 min or so. Switching between C1 and Photoshop and using thumb wheel browsing in C1 and it works. I did the uninstall, cleaned the registery, and reinstalled C1 V3.7 and still crashed. Now V 3.7.1 is stable. Go figure. Thanks C1
Mark0 -
Just thought I would add that I am having some fairly frequent crashes also. 0 -
[quote="Keith Carpenter" wrote:
Ian ~
Seems as though your systems meet or exceed the Requirements:
PC
OS: Windows 2000 or XP
CPU: Min PIII, P4 Preferred
RAM: 512, 1Gb Preferred
This is atypical behavior and the fact is that Capture One is not unstable. Some users have had RAM modules go bad, while some have had to reinstall their OS when it has gone bad.
Any other programs working in the background?
Are you using Sessions from older version of C1?
Where are the image files located?
Previews and Work files are built for a Session when it is Added to Permanent Collection, otherwise they are temp files. Session name on tab is in italicised if NonPermanent. Waiting for these files to build before working on them is good practice.
The Windows platform is 'happiest' when there is a single Set Process Folder to location. The easiest is to checkbox Always process images to associated image folder this way processed images arrive in a subfolder named Develops to the Session folder.
Let us know of your progress.
Sincerely,
k c
The Windows platform is 'happiest' when there is a single Set Process Folder to location. The easiest is to checkbox Always process images to associated image folder this way processed images arrive in a subfolder named Develops to the Session folder.
And where do I find that setting?0 -
I also suffered from serious 'freezings' but all these problems seem to be gone with version 3.7.1 😊 0 -
[quote="GuitarAdoptions" wrote:
[quote="Keith Carpenter" wrote:
Ian ~
Seems as though your systems meet or exceed the Requirements:
PC
OS: Windows 2000 or XP
CPU: Min PIII, P4 Preferred
RAM: 512, 1Gb Preferred
This is atypical behavior and the fact is that Capture One is not unstable. Some users have had RAM modules go bad, while some have had to reinstall their OS when it has gone bad.
Any other programs working in the background?
Are you using Sessions from older version of C1?
Where are the image files located?
Previews and Work files are built for a Session when it is Added to Permanent Collection, otherwise they are temp files. Session name on tab is in italicised if NonPermanent. Waiting for these files to build before working on them is good practice.
The Windows platform is 'happiest' when there is a single Set Process Folder to location. The easiest is to checkbox Always process images to associated image folder this way processed images arrive in a subfolder named Develops to the Session folder.
Let us know of your progress.
Sincerely,
k c
The Windows platform is 'happiest' when there is a single Set Process Folder to location. The easiest is to checkbox Always process images to associated image folder this way processed images arrive in a subfolder named Develops to the Session folder.
And where do I find that setting?
Can anyone answer this?0 -
[quote="GuitarAdoptions" wrote:
And where do I find that setting?
Can anyone answer this?
This is OT in this thread but I'll try to help you :
Go to the process tab, under Batch Editor click on the one before last tab : "set process folder"0 -
Found it! Thanks so much for helping! 😊 0 -
Hi Guys,
it is time I bought back into this thread.
I have done a number of things.
Replaced my Logitech wireless keyboard with a PS2 keyboard
Replaced my Logitech wireless mouse with a USB mouse.
Removed some ECC memory, which I thought was causing the problem, but it wasn't. I bouught it by accident (thought I was buying ordinary memory, don't remember paying any extra for it) at one stage during various recommendations from experts on many different forums and computer shops.
That got rid a of a number of issues that mainly concerned C1, but were occassionally happening to other applications. The crashing being part of it.
The thing to watch is try to avoid USB 1.x ports for just about everything.
I was involved with debugging the alpha and beta versions of the software and at no time did I un-install and do a complete re-install. The installation was always over the top of the existing version.
Now for the good part. At NO time since I installed 3.7.1 have I been able to lock it up or crash it. I have tried to make it crash and it doesn't. I am very happy with the preformance and behaviour of v3.7.1 and believe we are now back to the levles of stability we had before v3.6.
😄 😄 😄
Now roll on v4 with a lot of new features. Mind you I am still learning how to drive the existing tools in v3.7.1.
Ian M0 -
Same here - I'm pleased to say that I've been unable to make 3.7.1 hang during scrolling of the thumbnails.
Galen0
投稿コメントは受け付けていません。
コメント
17件のコメント