Mac Pro with 64 GB of RAM fails on import due to ...
"Out of Application Memory" message.
Using a MacPro5,1, MacOS 10.13, dual quad core Xeons, with 16 terabytes of disk space, 64 GB RAM, and 85% of the way through an import operation, system locks up due to "Out of Application Memory" message. The catalog drive has 400+ gigabytes free space. Capture One installation drive has 120+ GB free space. Minimal other applications running.
Are there specific limits to number of files / folders / file size / cumulative file size / ??? that are present in Capture One Pro 11.01?
From my side, time is not the issue. I understand that the process will not be fast. I'd like to know if there are other factors involved in importing my large collection of files into Capture One, but I'd really rather avoid manually selecting many hundreds of folders individually.
I tried importing all the files in one of my external drives, but the whiole system crashed. Then I tried one year's worth at a time ... which worked for a few imports (<8000 files or so at a time) , then failed as described when imprting a busy year's worth of 17K files. Importing individual days worth of files at a time is simply too onerous, and Capture One does not allow multiple folders to be selected - just a folder and subfolders.
Ideas, suggestions ?
Thanks!
Tim
Using a MacPro5,1, MacOS 10.13, dual quad core Xeons, with 16 terabytes of disk space, 64 GB RAM, and 85% of the way through an import operation, system locks up due to "Out of Application Memory" message. The catalog drive has 400+ gigabytes free space. Capture One installation drive has 120+ GB free space. Minimal other applications running.
Are there specific limits to number of files / folders / file size / cumulative file size / ??? that are present in Capture One Pro 11.01?
From my side, time is not the issue. I understand that the process will not be fast. I'd like to know if there are other factors involved in importing my large collection of files into Capture One, but I'd really rather avoid manually selecting many hundreds of folders individually.
I tried importing all the files in one of my external drives, but the whiole system crashed. Then I tried one year's worth at a time ... which worked for a few imports (<8000 files or so at a time) , then failed as described when imprting a busy year's worth of 17K files. Importing individual days worth of files at a time is simply too onerous, and Capture One does not allow multiple folders to be selected - just a folder and subfolders.
Ideas, suggestions ?
Thanks!
Tim
0
-
Hi Tim
It would be useful if you would say where you are importing from.
I suggest you open a trouble ticket, if you haven't already.
With 64GB of RAM, you should have more than enough. I have 24GB on this machine (late 2015 iMac) and haven't hit a memory problem yet, in normal operation of CO. However, I have triggered bugs which result in memory issues.
In earlier releases of CO, imports were a resource problem, and one strategy I adopted was to create a dummy album with no images. Once the import started, I would click on that album, so that Capture One would focus it's resources on Importing, and not on displaying the rapidly accumulating imported images.
Another thing I have discovered is that the Filter Tool if active (means on the active tool tab or on a floating tool) automatically sorts and catalogs all unique values of ALL metadata fields (not just those shown by the tool) every time there is any change to the GUI - meaning a key click, mouse click or new image. For small to medium numbers of images, no problem.
Once the number of images gets above 8000 or so, if one or more of the data fields contains a unique value for each image (e.g. original path & file name, original capture date & time) then COP is faced with an enormous challenge (which is not handled well), since the number of comparison operations for each index & catalog operation increases as n-squared.
The unfortunate thing is that this operation occurs often, and the results that take so long to compute are of no value to the user, since they result in very very long lists of radio buttons that are difficult to use (but usually the user doesn't select these fields for viewing in the Filter Tool anyway).
If Filter Tool is active during Import, and All Images is the visible folder, then this may also be affecting your import.
For this reason I usually remove the Filter Tool from the Library Tool Tab, and put it on a custom tab. And then I know that if use it in the "All Images" folder, I will be faced with very slow operation.0 -
Thanks for the reply, Eric.
I have two, 2 terabyte, external eSATA RAID drives with 20 years worth of photos. Those are what I importing FROM. The catalog drive is an internal 500 GB SSD that is dedicated to nothing but C1 catalogs. Currently less than 20 GB used for the current (initial) catalog.
I attempted to send the crash results to PhaseOne, but since little could be done until I restarted, I doubt it went through.
I'll have to wait for the current import to finish so I can look over your suggestions in context. In particular, the display of images seems promising.
Thanks!0 -
[quote="tjod" wrote:
Thanks for the reply, Eric.
I have two, 2 terabyte, external eSATA RAID drives with 20 years worth of photos. Those are what I importing FROM. The catalog drive is an internal 500 GB SSD that is dedicated to nothing but C1 catalogs. Currently less than 20 GB used for the current (initial) catalog.
I attempted to send the crash results to PhaseOne, but since little could be done until I restarted, I doubt it went through.
I'll have to wait for the current import to finish so I can look over your suggestions in context. In particular, the display of images seems promising.
Thanks!
TIm,
If you just sent a crash dump that is anonymous info for background information. Interesting as generic assessment but not so much help for you personally.
If you created a Support Case and sent the requested Log files I would expect the support team or developers could look at what has been recorded and maybe workout what seemed to be going on and the overall state of play at the time of the crash.
You also get personal attention for free. And you are much more likely to find some official guidance about your import options that you can consider alongside the practical advice from other here in the forum. Bear in mnd the forum is, primarliy, a User to User facility not an official Phase support channel.
HTH.
Grant0 -
I've seen the same thing, several times. there's a serious memory leak in C1. it's the one application on my Mac that can't be left open in the background indefinitely. 0 -
[quote="tjod" wrote:
Thanks for the reply, Eric.
I have two, 2 terabyte, external eSATA RAID drives with 20 years worth of photos. Those are what I importing FROM. The catalog drive is an internal 500 GB SSD that is dedicated to nothing but C1 catalogs. Currently less than 20 GB used for the current (initial) catalog.
I attempted to send the crash results to PhaseOne, but since little could be done until I restarted, I doubt it went through.
I'll have to wait for the current import to finish so I can look over your suggestions in context. In particular, the display of images seems promising.
Thanks!
I sure hope that you are importing these images as referenced images and not managed images. With that many managed images, the catalog files would become enormous. And you'd be critically dependent on the completely robustness and stability of the catalog files.
When I was transitioning and having trouble (in Capture One 9), after failing with the big import, I started with 100 images, and got most of the settings right. Then I imported 1000, debugged some more, then 2000, 4000, somewhere in there a bit more debugging, and then eventually the entire library of 15000.
I imported from an Aperture Library - I had to learn how to bring over hierarchical keywords, what to do about smart albums and stacks, that images less than 500 pixels in one dimension are not supported (and what to do about them), certain video files are not supported (eliminated audio and video files entirely) , certain kinds of tiffs can be a problem (imported those separately), at one time Canon cdraws were a problem.
Currently I think there are problems with images having more than one "dot" in the file name.
Basically I would import a bunch of images, count them before and afterwards, figure out which ones were missing, which ones were imported but uneditable and then remove those kinds from subsequent imports.0 -
Yes, I'm using referenced images stored on 2 separate external drives, each backed up to another set of drives.
Years ago I learned the hard way with Aperture not to import the files into the database itself. Lightroom's retreat to the cloud just reinforced that lesson. I really hope Capture One is the last stop on the DAM software experience.0 -
Hi, I keep having similar problems with Capture One and opened a thread on that topic before. My personal experience has been that C1 is simply way to unreliable and buggy when it comes to larger amounts of files. Phase really needs to fix the DAM functions and memory management of Capture One. Not sure if Windows people have the same problems.
In case you have a subscription with the big competitor: Lightroom handles huge catalogues with ease and speed.0 -
[quote="tjod" wrote:
"Out of Application Memory" message.
Ideas, suggestions ?
Thanks!
Tim
My suggestion is to as helpfully as possible collect the data and circumstances that caused this Out of Application Memory error message. It appears to me that you were using the software well within the confines of expectations and it died without recovery during a pivotal moment. The important factor here is repeatability. Can you cause that error again?
Regardless this isn't great architecture. If we have web browsers that don't crash due to one rogue tab/process.... Capture One should be much further along the line as it's an application entirely built around a database and it seems a user suffers due to it. I've used this software since Lightphase was even a saying and we've come leaps and bounds in many ways, but sadly at the expense of stability and usability. And more feature's are added with the caveat of new bugs. We've gotten to a point where the new features are breaking old one's and it's cat and mouse for a stable version -- and as soon as we're close, we're a new release away and paying a couple hundred dollars for the privilege.0 -
[quote="Eric Nepean" wrote:
Basically I would import a bunch of images, count them before and afterwards, figure out which ones were missing, which ones were imported but uneditable and then remove those kinds from subsequent imports.
Wow. I'm so sorry.0
Post ist für Kommentare geschlossen.
Kommentare
9 Kommentare