Mar 5th, 2009, 04:58
1. 32bit logic does not have enough internal memory to run even fairly modest 3rd party libraries/plug-ins. 2. therefore logic would have to become 64bit which is NOT going to happen for many VERY good reasons, or else the 3rd party plug-ins will have to use the same mmap trick as the exs24. 3. the mmap functionality requires a certain amount of internal logic memory to make work. this severely curtails the amount of memory you have for your 3rd party stuff, which is why reducing your physical RAM could actually increase how much you have available for logic. the amount of memory logic sets aside to run mmap is set in your plist file. even a fairly low level programmer could adjust this. i have had mine adjusted and it has made a huge difference. 4. the only real solution for those who are working with a fair amount of 3rd party stuff is to use an AU host. this really is not the end of the world and actually brings its own benefits. in this case a 32bit au host has its own 4 Gb memory space which makes far better use of your systems RAM. 5. logic is much more stable close to its memory limits than it ever has been before, but it reaches the limit far sooner because of the 512 Mb set aside to run mmap. i stress, if you are running close to the memory limit you need to consider another AU host. 6. it absolutely has nothing to do with computer model, intel vs PPC, or whether your RAM is paired, coloured purple or has furry dice hanging off of it. it is all to do with the internal RAM address space limitation with logic. some further thoughts: - generally if you get the unable to save message, it may save anyway. look for the file with a tilda ( ~ ) after it. - there are many features in logic which have not been thought all the way through; file management, communication with other DAWs, beat mapping, working with video, the library drawer, score editing, and finally mmap. mmap was clearly meant to address the problem of working with large libraries and is partially a good solution. but the reality is, most modern sound libraries are only available for 3rd parties plug-ins and not available for the exs. missing this point makes the mmap virtually a redundant feature - how can you miss it? simply saying its up to the 3rd party manufacturers to sort out is not helpful to the poor user who is wondering why their expensive macpro with a gazillion gigabytes of RAM falls over sooner and runs no faster than their old coal-powered G5. having spoken to very smart programmers not related to logic development (that i know of) there are a myriad ways of exploiting RAM on your system and certain advantages at least in the short term to remaining a 32bit application. logic developers have not thought all the way through the problem of running large libraries and this annoys me somewhat. an integrated secondary hosting program such as RAX or plogue bidule, created by the logic developers would be much easier and more efficient to manage, more tightly integrated and would make a lot more sense than an obscure programming trick that they didn't even announce when it came out. a big problem of running combined libraries is that when switching songs, the 3rd party samples have to be reloaded. keeping them in plogue bidule running in rewire, means that switching songs takes a fraction of the time it used. the technology exists for logic to run a secondary application very easily and would have been a far more practical and obvious solution than the one they came up with, because the situation as we have it means that people get burned all the time as they come against the memory wall.