Posted
I used the batch midi import in a new library to import 40 files leaving everything at default settings. After many hours it finally completed! I then saved the library which also took a long time, not sure how long exactly as I got bored waiting. However, it saved ok and I now had exactly what I wanted - all the songs in their own folder with individual phrases created automatically in the pool.
But now when I try to open the library again, after several minutes I get the following error message:
"Error loading <library name>.coglib. No space available to allocate this object. The file may be corrupted."
Pressing OK does not do anything so the library is empty. The size of the library on disk is 140MB, is there a limit to library size? If so, what is it and how do I know when it will be exceeded BEFORE selecting a folder for batch import?
The library was fine before I closed it and I was able to select phrases without any problems. So I don't understand the error message.
Mo., 08.07.2013 - 01:01 Permalink
yes i get similar error messages very often too.
( actually this was the only reason of my latest 4 or 5 auto crash report submits )
but anyway so far i didn't get any file corrupted to death stuation ..
same library works
if i try to re open second time after this message.
Q:
did you check the Backup folder?
there might be a earlier version of your library.
.....
as a side note and wish ::
i hope we will get Speed up for the Library loading times soon..
current speed sometimes becomes very tiresome / mood killer ... IMO.
...
Mo., 08.07.2013 - 08:36 Permalink
There is no hard limit on how big a library can be. Library contents are deeply nested and structured objects that can require a lot of temporary memory when loaded. You should keep them smaller than 50 MB to avoid this. More and smaller libraries are also easier to handle. You can drag and drop between their windows.
Mo., 08.07.2013 - 12:06 Permalink
Hi petearch
Hi List
As far as I can remember, I had similar problems (SFP, Mac OS 10.6.8) when I had umlauts or special characters in the library name or even in its path, but I dont remember the exact error. So, just maybe(!) "save as" could help.
And +1 to supertonic: small libraries (for my computer about < 5 MB, I have just one library that has about 30 MB, but this lib has minutes for loading so I do not use it much) are faster.
best,
Michael
Mo., 08.07.2013 - 16:13 Permalink
I plan on making libraries become bundles. This would eliminate the need to load all phrase pools into memory. Unfortunately, Windows does not support treating directories like monolithic files. This is a huge advantage of the Mac. Have no idea yet how to substitute or fake this on Windows.
Di., 09.07.2013 - 05:20 Permalink
Definitely make small libraries. When I start pulling parts from different libraries, I save this to a 'Song' library. Just so all the raw materials are in one convenient spot.
Mi., 10.07.2013 - 22:36 Permalink
Ok, I get it now that the phrase pools need to be loaded into memory, I guess a library is treated as one huge document.
Soundcase's suggestion to try to open the library again immediately after getting the error worked :) so I have now split them into smaller libraries of no more than 50MB as supertonic suggested. I have found that selecting MIDI files that are a total of around 800KB seems to translate to less than 50MB per library.
I like markstyles' idea to have a small library per song so I've started to do that. It's just a shame that I can't have all the libraries open as one, which was my original idea, i.e. to have instant access to all the phrases from all my MIDI files.
I hope Andre finds a way soon to handle this in Windows!