C1 Pro 6.x and 7 consuming all RAM (?)
This morning I went to use C1 Pro 6.4.4 and noticed two things:
1. I added some new .cr2 RAW files to a folder, but they don't appear in C1s file list.
2. All 32 GB of RAM are consumed by C1 pro and then the PC locks up.
I uninstalled 6.4.4 and re-installed. Same problem. (The previous files appear, but the New raw files don't appear. The software does say there are 26 image files in the folder, which is correct... But the new files don't show up. Then RAM usage quickly increases to 100% and the PC locks up.)
I uninstalled 6.4.4 and installed 7.0. Same problem.
I thought maybe c1 is trying to re-build a cache or session, but there are only 26 raw files in the folder, so it shouldn't take this long for the program to read/see the raw files.
Does anyone have any ideas?
I am running Win7. 64 bit
C1 worked fine a few days ago and nothing changed on the PC between last time I used it and today.
1. I added some new .cr2 RAW files to a folder, but they don't appear in C1s file list.
2. All 32 GB of RAM are consumed by C1 pro and then the PC locks up.
I uninstalled 6.4.4 and re-installed. Same problem. (The previous files appear, but the New raw files don't appear. The software does say there are 26 image files in the folder, which is correct... But the new files don't show up. Then RAM usage quickly increases to 100% and the PC locks up.)
I uninstalled 6.4.4 and installed 7.0. Same problem.
I thought maybe c1 is trying to re-build a cache or session, but there are only 26 raw files in the folder, so it shouldn't take this long for the program to read/see the raw files.
Does anyone have any ideas?
I am running Win7. 64 bit
C1 worked fine a few days ago and nothing changed on the PC between last time I used it and today.
0
-
This truly is weird. Have you tried to directly engage in correspondence with PhaseONE Technical Support? In my experience of contacting and sometimes reporting issues, they are great with timely responses. This is a user-to-user and I truly feel for your sake that you deserve an official answer from PhaseONE why you are experience your memory anomaly.
If I was in your position, I would try to make backups of my RAW files just in case AND . . . AND expunge all traces of CaptureONE installations on my computer. That means going into the actual directories in Program Files and into your username folder in "Users" on your C drive's AppData and Roaming folders.
C:\Users\[Username]\AppData\Local
In this path, assuming you're using 64-Bit Windows 7, I would delete the "CaptureONE" and the "Phase_One" folders.
Next, I would go into C:\ProgramData and extirpate the "Capture ONE" folder inside the "Phase ONE" folder. On my computer, I have MediaPRO installed and so I don't want to delete the entire "Phase One" folder inside my ProgramData directory on my D drive.
Just remember, that, is it something I WOULD DO to see if the complete deletion of the traces of C1PRO installations would help absolve the problem you are facing.0 -
I did send an email to tech support but figured I would post here too. I'm in the process of running a registry cleaner now. I tried rolling back to 6.4.1 but still have the same problem. I will try the things you suggested too. It certainly can't hurt lol
This is a big problem for me as I have a job I need to finish and I'm stuck until I get this sorted out.0 -
This is unusual but from time to time I have seen problems with some folder that seem to contain files that, for whatever reason, C1 does not like. I have seen similar things with other applications as well.
For me the most common problem area seems to be with images downloaded from various places for experimentation or assisting others. That some of these images may be less than wholesome, technically, is to be expected. The problem, however, is knowing which ones in a folder are causing problems. Get one 'bad' image file and the entire folder becomes a problem.
I would be tempted to remove the folder with your images already in it and then re-import the images, perhaps one at a time with the idea of trying to identify if one (or more) of them has some sort of technical problem. As I recall I did pnce find a .cr2 image that appeared to be of unlimited size. Obviously something was not quite right with it. I forget the details now, it was a while ago and the image was not important so I binned it.
HTH.
ETA: If you can go into C1 V6 and work with previously loaded images (from the same camera) then the problem is not with the C1 installation as such, more how it is functioning with one or more of the new images.
Grant Perkins0 -
I appreciate the feedback, but unfortunately I dont think the files are the problem. I have now noticed that if I attempt to open any folder with RAW files in it, then Windows Explorer (the PC file directory) will crash and close.
Here is a copy of the Event Viewer details from when that happens. Note that the Faulting Module is CaptureOne, which wasnt even open at the time the event happened:
Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d672ee4
Faulting module name: P1.WIC.NativeComWrapper.dll, version: 0.0.0.0, time stamp: 0x4fa0f4c5
Exception code: 0xc0000005
Fault offset: 0x0000000000001134
Faulting process id: 0xee0
Faulting application start time: 0x01cdcb24a19442f1
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: C:\Program Files\Phase One\Capture One 6\WIC\WIC64\P1.WIC.NativeComWrapper.dll
Report Id: 0ce2dd1c-3718-11e2-9b20-c860003196000 -
** Again,** this is something what I would do: at this point, I would just re-format (the long format) my drive and re-install everything. I only have one computer the re-format and re-install seems to work for me if I experience any severe software anomalies. [quote="cdesperado" wrote:
I appreciate the feedback, but unfortunately I dont think the files are the problem. I have now noticed that if I attempt to open any folder with RAW files in it, then Windows Explorer (the PC file directory) will crash and close.
Here is a copy of the Event Viewer details from when that happens. Note that the Faulting Module is CaptureOne, which wasnt even open at the time the event happened:
Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d672ee4
Faulting module name: P1.WIC.NativeComWrapper.dll, version: 0.0.0.0, time stamp: 0x4fa0f4c5
Exception code: 0xc0000005
Fault offset: 0x0000000000001134
Faulting process id: 0xee0
Faulting application start time: 0x01cdcb24a19442f1
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: C:\Program Files\Phase One\Capture One 6\WIC\WIC64\P1.WIC.NativeComWrapper.dll
Report Id: 0ce2dd1c-3718-11e2-9b20-c860003196000 -
Yeah.... I'm in the middle of completing the backups and I'm going to reformat the HDs and reinstall the OS. I tried several different other solutions but none worked. Something is corrupt so it's time to start over. 0 -
[quote="cdesperado" wrote:
Yeah.... I'm in the middle of completing the backups and I'm going to reformat the HDs and reinstall the OS. I tried several different other solutions but none worked. Something is corrupt so it's time to start over.
Maybe not.
Canon some time back provided a RAW file display program that allows CR2 files to be visible as thumbnails in Explorer. More recently this seems to have been embedded in Windows but, iirc, is not problem free - I had some issues some time back.
I'll see if I can find the relevant information.
Grant0 -
Hmmmm. Whatever that was, I didn't have it. I never could see raw thumbnails in explorer. I use ACDSee to manage my files though. iIt would have been nice to have though! I have to open up ACDsee every time I want to see a Raw thumb.
let me know what you find though. Thanks!0 -
OK, here we go.
Canon released a RAW Codec in 2010 but for 32bit only (it seems). It has not bee updated as far as I can tell since 2010.
Microsoft have released a codec pack for both 32bit and 64 bit OS. This covers all manufacturers (or seems to attempt to do so)
Here is a link to the US Microsoft download site
http://www.microsoft.com/en-us/download ... x?id=26829
Country specific sites are likely to be suggested from that screen if you are elsewhere in the world.
The update for this Codec seems to be most recently August 2012. So not really very recent but I have not performed a deep search.
Note also that, acording to the list of supported cameras, there seem to be some omissions and not all of them are recent releases. However I cannot say whether that is significant.
It would be logical for an application that to make use of MS codecs when attempting to display RAW files directly (as Windows Explorer uses the codec). This would typically be based on extracting the embedded jpg thumbnail I would have thought but may attempt an alternative approach if the codec offers it. I really don't know the exact process. However if the file structure is not recognised (or incorrectly recognised) then anomalies may occur. There do seem to be a number of references to such problems in many applications scattered across the internet.
The result of this its that when reading a folder of files if the system comes across a file that appears to be an image file but one that has a problem of some sort, the system may fail to interpret the file correctly and crash. In theory removing the file (if it can be identified) should resolve the problem. If might be all files of course if the camera's RAW's are not recognised correctly.
I can't be sure about this but I do have and have seen from time to time problems of this nature as mentioned previously. I suspect that in some cases, like one that has developed for me this weekend, that the initial problem results in a more significant problem (a corrupt session database in this case) that will repeat perpetually until the offending files are removed - or maybe after that even.
For example, as a quick way to edit a file I used an existing open session and opened another folder unrelated to the contents of the session. The foldr contains all sorts of odd downloads, some edited in C1 (V6 in my case) some not or editing in a different editor. I have used this folder before.
At some point just as I was finishing a couple of new edits and attempting to output them something cause a crash. I had also deleted one of the files in the folder (not one I had been working on) at around the same time. The edits have disappeared from the file I was editing. 2 other files appear as grey rectangles. On re-opening C1 the defual was that folder, of course, the open process looks slow and after a while, more often than not, C1 crashed with the problem of reading the session database. This is a very rare event in my experience of 32bit C1 V6.
However if I open the session directly from the .col file in the 'good' folder all seems well. If I then swap to the 'bad' folder C1 crashes. So something has corrupted the 'bad' folder in a way that C1 cannot cope with (designer can't think of everything strange that an OS might do) but it's fine as long as I avoid that folder. Or make a guess and fix the contents of the folder. (I could do that logically by testing each file but I'm not sure it is worth the effort.)
I am beginning to drift into two possible problem areas here so time to stop speculating. However it may well be worth checking out the MS Windows codec installation in case it is related to your problem. In theory there is nothing much to lose and potentially something to gain (at the windows level even if not in C1).
Unless of course there are problems with the codec pack itself .... but then it can be uninstalled.
BTW I use FastStone or the same reason that you use ACDSee. FastStone is in any case quicker than Windows Explorer so for large numbers of files it made sense although needing to see the RAW files in their folders is a rare need for me. I tend to work through C1 sessions by default and I don't have any cameras that are not yet supported by C1. Lucky for me!
Grant Perkins0 -
You should try Fastpictureviewer
http://www.fastpictureviewer.com/codecs/
" The FastPictureViewer Codec Pack contains 64-bit and 32-bit RAW codecs that enables robust support for 45+ image formats, including RAW formats from more than 400 digital cameras in Windows Explorer, Windows Photo Gallery, Windows Photo Viewer, Windows Liveâ„¢ Photo Gallery and, on Windows 7, also within Windows Media Center and Windows Media Player 12, with full 64-bit compatibility.
The Codec Pack supports raw formats from digital cameras from Canon, Nikon, Olympus, Sony, Hasselblad, Fuji, Panasonic, Leica and more, as well as Adobe DNG, Photoshop PSD, Google SketchUp (thumbnails), and Computer Graphics image formats including OpenEXR, Radiance HDR, TGA, Softimage PIC, Autodesk Maya IFF, PNM, and DirectX DDS including ATI 3Dc compression. See full list below. "0 -
An update on my V6 problem folder - there may be some parallel relevance to V7 problems.
Firstly, other than a ZoomBrowser index file all but one of the files in the folder were relatively small jpgs. Tow of those (2 copies of the same file) were not displaying correctly although a 3rd file in the grooup - an edit file that presents as a jpg and has a thumbnail embedded - was displaying as expected.
When I opened the folder within a session the C1 system activity spinner would constantly spin, stop, spin, stop and so on - usually an indication that it is not keen on something if it continues well after it reports the correct number of identified files.
Plus the processor cores were running at max temp and the fan was flat out and available memory was almost non-existent. All signs that something is not right. It crashed a couple more times, as expected.
I tidied some stuff out to trash and still it crashed. I then deleted the two suspect files having checked that even shutting everything else down hardly returned any significant amount of memory. Killled and re-started the process and all was well. Folder load is fast, no errors, no extended activity spinners, memory (2Gb in the system) back up to about 50% free at the loaded point (less after editing) rather than 50Mb.
Edit completed, output successful. So the two 89kb jpgs seem to have been the problem.
I have no idea whether this experience would translate to a V7 environment but I suspect it might.
No idea why the jpgs were a problem either - they show up well enough in Windows Explorer.
I would be interested to know if anyone can discover a similar problem/solution result for a V7 installation. (The answer may give me a clue about when to budget for my hardware and 64bit upgrade to run V7!)
Grant Perkins0 -
I just thought I would leave a quick note - after installing/ uninstalling several times I manually deleted the AppData folder and that appears to have stopped C1 Pro from causing windows explorer to crash every time I open a folder with a RAW file in it.
Now that I'm able to complete the backups I will reformat the HD and we shall see what happens.0 -
Well.... It sucks to be me. I wiped the HD and re-installed the OS and C1 Pro 6.4.1 (a version I know for sure was working) and the problem remains. I'm not really sure what else to do at this point and have not heard from tech support yet. 0 -
That doesn't sound good at all!
Did you re-install the .Net Framework as required by C1PRO software? What about the rest of your Windows 7 updates? Are they all up to date?
I think it is best now for you to wait for the technical expertise from P1.
Formatting and re-installing is (for me) the go-to solution to augment any software and hardware anomalies. Sorry the format-and-reinstalling solution didn't work out for you.[quote="cdesperado" wrote:
Well.... It sucks to be me. I wiped the HD and re-installed the OS and C1 Pro 6.4.1 (a version I know for sure was working) and the problem remains. I'm not really sure what else to do at this point and have not heard from tech support yet.0 -
I just thought I would post this really quickly in case Tech Support responds to me. I haven't solved the problem, but have noticed an interesting catalyst: As far as I can tell, the problem isn't being caused by a RAW file, it's being caused by some JPGs in some folders.
I am purely speculating here, but I think some of these files were saved to an iPad 3, then moved to my PC. I can't say for sure this is the true cause because I believe one of the folders that caused the crash definitely did NOT contain images from my iPad, but the folder I am having trouble with right now definitely did. One thing to point out about the iPad 3 is that it re-names the images (IMG####) when you save them. (I havent found a way to make it keep the original file name.) Theoretically, I am wondering if there could also be some slight change to the JPG format when it is saved to an iOS device. (There shouldnt be a difference, but anything is possible.)
I re-formatted my primary Hard Drive, re-installed my OS (and other software) and am running C1 Pro 6.4.1.
Win7 64-bit.
I'm not going to load v7 since several people are reporting issues converting their sessions from v6.4.x.0 -
To date, I have still not received any response from C1 Tech Support on this.
However, I do believe I have found a solution: The fix (when running Win7 64 bit) is to rename this DLL file:
C:\Program Files (x86)\Phase One\Capture One 6\WIC\WIC64\P1.WIC.NativeComWrapper.dll
I changed the file extension from .dll to .old and this appears to have solved the problem0 -
Capture One 7.0.1 also consumes all the 16 GB ram in my pc and then halts. After that I can do nothing. Last time it just imported 500 images and then halted. 0 -
[quote="Knud Erik" wrote:
Capture One 7.0.1 also consumes all the 16 GB ram in my pc and then halts. After that I can do nothing. Last time it just imported 500 images and then halted.
Are you in a session, or did you try to import into a catalog?0 -
It happens when I am IN a catalog and when I import images to a catalog. 0 -
The C1 guys never responded to my help request. However, I have noticed that this problem will occur if you have a session open in C1 (viewing RAW files from a specific PC folder) and then load additional RAW files into the same PC directory folder that the RAW images are in. I created a desktop shortcut to the Task Manager so I can shut down C1 when I see the RAM problem starting. 0 -
[quote="Knud Erik" wrote:
It happens when I am IN a catalog and when I import images to a catalog.
It figures. I am now staying away from catalogs completely. I don't like the design concept, and almost all the problems I had, including lockups, occurred when I was trying catalogs.
I currently use Media Pro as a DAM (it has its own problems) and I push files from that into a session in CO7.
I tend to limit the number I push at a time, as that lets CO7 operate on them quickly.0 -
[quote="Jim MSP" wrote:
[quote="Knud Erik" wrote:
It happens when I am IN a catalog and when I import images to a catalog.
It figures. I am now staying away from catalogs completely. I don't like the design concept, and almost all the problems I had, including lockups, occurred when I was trying catalogs.
I currently use Media Pro as a DAM (it has its own problems) and I push files from that into a session in CO7.
I tend to limit the number I push at a time, as that lets CO7 operate on them quickly.
I cannot use Media Pro with Capture One 7, as both the ratings and the labels (colour marks) are not tranferred correctly between the two programs.
I have used sessions but miss the filterering options in the catalog. You can filter in sessions but catalogs are much better and sessions are too slow with many images. When catalog works they are good.
I am very close to skip Capture One, but it is hard to do it. I have used it since version 3 and it is a good program, when it works. I have had problems with bugs since june - first with Media Pro and then with Capture One.0 -
Tech support had a debugging session with me on the ram issue this past Thursday and they have found a problem. They hope to have a fix in the next release which may happen this week if it is ready. 0 -
At least they responded to someone about it. Are they aware this is affecting v6.4 too? 0 -
[quote="NN8899721" wrote:
... They hope to have a fix in the next release which may happen this week if it is ready.
This would be great.
I don't expect any updates to Media Pro until CO 7 is stable; and I really hope that follows soon.0
投稿コメントは受け付けていません。
コメント
25件のコメント