PRO v3.7 easily locks up while scrolling thumbnails
About 200 20D .crw files in a folder, Photoshop CS open from a previous edit, selecting one file to process in C1 Pro V3.7 and getting it started, then begin slowly scrolling down through the thumbnails with the arrow key at a rate of about one a second. Though it doesn't happen every time, it happens frequently. The only way to close this hard hang is to use the task manager to kill the C1 process.
This is in Windows 2000. 1.5 gig of RAM, a 10 gig scratch partition dedicated to CS alone, and greater than 5 gig free on all of the hard drives/partitions that any temporary files are located. The working drive where the raw files are located, and the C1 cache is separate from the system pagefile and all other temporary files, with about 20 gig free.
Mike
This is in Windows 2000. 1.5 gig of RAM, a 10 gig scratch partition dedicated to CS alone, and greater than 5 gig free on all of the hard drives/partitions that any temporary files are located. The working drive where the raw files are located, and the C1 cache is separate from the system pagefile and all other temporary files, with about 20 gig free.
Mike
0
-
I've had one lockup withoout any files in the batch queue.
Today another strange thing happend while scrolling the thumbnails with the arrow keys. I had the IPTC and meta data windows open while scrolling when suddenly one image was stuck in the preview window and the image selected in thumbnail was shown above the stuck image.
I changed to the desktop where I had an explorer window open and then back to C1 and now everything was shown semi transparent.
Exiting C1 and then start it again fixed the problem.
This was on a W2K machine.0 -
Gentlemen,
We are beginning to see a few Support Cases involving similar issues. Possibly one of these is yours. If you have not already done so, please send information to Technical Feedback... under Help of Capture One.
Creating a Support Case will help as well. We truly need well documented problems to help solve them. There are so many variables involved, please don't leave out any detail that you feel may help; and certainly offer your theories and insights as well. User input is valued, and needed.
gnordstrom, Please know I did see your earlier posts, and to be honest, I didn't have an aswer for you. We were not seeing this problem as yet. We continue to exchange thoughts and to try to duplicate these problems with all the variables in consideration i.e., Operating system, mouse wheel, Wacom tablet, Meta Data displayed, Thumbnail size, IPTC window open etc.
One case involves loading v3.6 archived Sessions into v3.7, others the culprit were a mouse driver and Wacom tablet driver. Windows 2000 seemed to be the common denominator, until we received a new Case using XP.
So, please continue to provide your input, so that others may provide their experiences as well. Together, we all get a bit Smarter
Sincerely,
k c
And with image files from various cameras. 20D 10D 1DMkII0 -
Keith,
Yes, I did the technical feedback route, too, but also posted here in the hopes that it might generate more information from others to help tracking it down. I assume opening a case file with as many details would be as good as the technical feedback from within C1 as long as enough details were reported?
My W2k system is quite simple because it's the least likely to generate any problems. I don't even have a mouse that uses a mouse wheel, so it's generic W2k, SP4 all the way, unless the motherboard (ABIT NF7) and processor (ATHLON XP Barton 2800) have a bearing. I've run memtest in the past so the three 512 meg strips are known to be okay.
I routinely check my system and application log files and don't find errors listed in either (more vanilla, hohum).
Mike0 -
Keith,
This problem with the Wacom tablet, is it specific to 3.7?
I've been using my Wacom tablet and mouse as long as I've been using C1 for a year and a half now and never have had these kind of problems earlier.
It all began with 3.7 (been an LE and SE user pre 3.7 though so this is my first use of Pro).0 -
gnordstrom,
No, and I confess the Case I'm referring to was on a Mac. We first saw it in v3.6 where 3 photographers in a studio had the same experience. The Thumbnails actually became smeared. After much analyses and many questions later, it came out that indeed all 3 used a Wacom. When they used a mouse, the problem went away... it was that simple!
The MouseWheel driver issue has happened to a few Windows users. Another had a bad RAM module, which is why it is Wise to test this as Mike says he did.
Technical Feedback goes directly to Developers. Cases that give Support problems and that become prevalent, are summarized and sent to Technical Feedback internally. When an issue is sent from Users and Support from both avenues, it tends to get their attention ! 😉
Thanks much,
k c0 -
...Just came to the board searching for a solution to the same problem. Scrolling through the thumbs causes a lockup, more often then not.
Ver. 3.7, Updated Win XP, 2gb ram, P3.2, 3-150gb 7200rpm drives.
I've just started encountering the problem after the upgrade from 3.6SE. I have a folder w/+600 raw, and if I start browsing the thumbs, after maybe scrolling through 20 or so the program locks. This has happened both by itself and while batch processing....
If I only batch process a few (~6) at a time, and only scroll through a few thumbs at a time, no lock up. Feels like some kind of memory issue, but I have a memory monitor and it doesn't show any excessive usage or lack of physical memory, and the scratch disk is not being accessed either...
ja0 -
I've found that the lockup while scrolling the thumbnails can happen even when nothing is being processed. The task manager show memory usage by C1 Pro v3.7 at 99% when it locks up. There is some shifting between virtual memory and real memory, as if some functioning is still occurring internally and gradually moving data in real memory to virtual memory, though the usage very slowly climbs during this hard lockup.
When this happens C1 does not retain the information from the current session.
BUT, this is bad enough (loss of work, data...) that I'm afraid to touch the thumbnails while C1 Pro is processing any images or until it has completed the cache update, generating previews, etc. What seemed originally like an inconvenience, i.e. \"don't do that\" now seems more like a serious, critical bug.
Mike0
Post ist für Kommentare geschlossen.
Kommentare
7 Kommentare