Posted
A large library has been taking 30 seconds or so on a new fast W7 64bit computer with a SSD drive. At one point a library didnt load and an SFP error (I think) about out of space of some sorts. Only had it once and didn't write down the exact message.
Mi., 14.12.2011 - 23:52 Permalink
Did you use the 'clean up for shipping' command? it edits out some material. I have noticed if I build a large library (ten 40kb midi files to start with.) - it will take quite a while to load.
Better to make them with 3 - 5 files.. Of course depends on complexity and length of files. You can also just analyze part of a song too.
Do., 15.12.2011 - 01:06 Permalink
They are very fast to load on SFP 1 so must be a bug with SFP 1.5.
Sa., 17.12.2011 - 16:42 Permalink
Actually, just noticed that the libraries that I have imported from midi files are all over 20mb, I tried to send the smallest one but your server bounced it back. All the libraries are from midi file from here: http://www.classicalarchives.com/midi.html
Sa., 17.12.2011 - 21:33 Permalink
20 megabytes is quite fat. No wonder it takes that long to load. You should thin a library out before saving it. For complex and long compositions like classical, it is also advisable to create one library per imported midi file and drag/drop their phrase pools together in a new library after you prepared them.