EXS in L8 versus L7: no more 3.5 GB RAM limit (with screen grabs)

okay

i’ve done some testing of EXS in Logic 7.1.1 and Logic 8. while all of this testing originated in the “is logic 64 bit” thread, i’ve started a new thread to post these results since, honestly, i really have no idea where to post in that old thread anymore. suffice it to say that Orren and Rohan are absolutely correct -- if we use Virtual Memory in EXS in Logic 8, we are no longer limited by Logic's 3.5 GB RAM limit for EXS and we can now use all of the RAM in our computers with EXS and Logic.

a couple of notes:

1. all songs were created and/or opened on a fresh system directly after a reboot. i never reopened a song or switched songs without a reboot in between. and all testing was done on my dual G5 with 8 GB of RAM, OS 10.4.10, Logic 7.1.1 or Logic 8.

2. i never had any programs other than Logic, Activity Monitor, and Grab open.

3. all testing was done with the EXS Virtual Memory option Active and set to “disk drive speed: slow” and “disk recording activity: extensive”. one of the confusing things in reporting this testing has always been that both EXS and Activity Monitor have a thing called “Virtual Memory” and they are not the same thing. i use Activity Monitor VM as my “how much RAM is this program using” reference because it is the one consistent figure i can find: when Logic hits 3.55 GB of Virtual Memory space in Activity Monitor, it crashes. but Activity Monitor’s Virtual Memory figure is a completely separate thing from the EXS Virtual Memory option. so from here on, when i refer to VM, it is the figure as reported by Activity Monitor. please know that the EXS VM option was active for all testing reported here.

so i started by creating a song in Logic 7 and i added EXS instruments (and ONLY EXS instruments) to the song until i was about to hit the 3.5 GB Virtual Memory limit. as you can see in this screengrab...

User uploaded file

...once i had loaded 18 EXS Vienna Symphonic Library instruments, Logic’s Memory figures in Activity Monitor were:

Logic Pro 7.1.1

Real Memory: 3.08 GB
Shared Memory: 47.4 MB
Virtual Memory: 3.42 GB

the system was using 4.15 GB of RAM, leaving 3.85 GB of RAM free. when i tried to load a 19th EXS VSL instrument, the program crashed.

so i then rebooted and opened this same song in Logic 8. as you can see in the screengrab, the memory figures as reported for Logic 8 are very different:

User uploaded file

Logic Pro 8

Real Memory: 1.94 GB
Shared Memory: 562 MB
Virtual Memory 2.45 GB

Logic’s Real and Virtual memory figures are much smaller, but the Shared memory figure is much larger. also, the system is using almost the exact same amount of RAM: 4.13 GB (leaving 3.87 Free).

i then proceeded to add EXS instruments (and ONLY EXS instruments) to this song (it has a new name because i didn’t want to save over the original song) until the System RAM was almost all used. as you can see in the following screengrab, the song now has 32 EXS VSL instruments loaded and the system is using 7.68 GB of RAM.

User uploaded file

what’s interesting is that despite all of the added EXS instruments, Logic’s memory figures have seen little change. they are:

Real Memory: 2.12 GB
Shared Memory: 571 MB
Virtual Memory: 2.62 GB

and while Activity Monitor isn’t showing a process that is responsible for storing the EXS samples, all 14 of the new EXS instruments are playable (as are the original 18).

so clearly what Rohan and Orren reported about EXS in Logic 8 is true -- we can now load/stream more instruments in EXS in Logic 8.

to test further, i removed a couple of instruments from this song so that i wouldn’t be running quite to the edge of my system RAM, saved it, rebooted and reopened the song. as you can see in this screengrab...

User uploaded file

there are now 28 EXS instruments open and Logic’s memory figures are reported as:

Real Memory: 2.07 GB
Shared Memory: 562 MB
Virtual Memory: 2.52 GB

The system is using 6.75 GB of RAM, leaving 1.25 GB free.

so then i added 7 Altiverb plug ins to 7 channels in Logic 8 (different settings for each altiverb instance so they were each using their own RAM).

User uploaded file

as you can see, not only has the System used more RAM, but Logic’s memory figures have increased as well because Altiverb is loaded into Logic’s RAM. Logic’s RAM figures now are:

Real Memory: 2.63 GB
Shared Memory: 582 MB
Virtual Memory: 3.15 GB

so i then proceeded to add two more EXS instruments to this song and you can see that the System is now using a lot more RAM (around 750 MB more RAM) but Logic’s memory figures have remained almost the same:

Real Memory: 2.65 GB
Shared Memory: 587 MB
Virtual Memory: 3.16 GB

User uploaded file

and, of course, all 30 EXS instruments are playable. how well they will perform in real world use remains to be seen. but they all work.

finally, as near as i can tell, Logic 8 doesn’t let EXS have its own memory space until Logic hits around 1.75 GB of Virtual Memory (as reported in Activity Monitor). before that point, it appears to me that Logic keeps EXS “inside” the Logic memory space. the “real” and “virtual” memory figures for Logic continue to rise as EXS instruments are added and the “shared” memory figure for Logic stays at around 40 MB.

but after 1.75 GB of VM, the “shared” figure starts to rise with each instrument until Logic hits around 2.4 GB of VM, at which point, all EXS appear to be loaded into non-Logic RAM because the “used” System RAM increased but all Logic figures remain almost the same. (i’m sorry if describing this is confusing -- i’m doing the best i can)

anyway, i apologize for the long post, but i wanted to clarify as best i could what the state of EXS is on Logic 8 for anyone still curious.

while i certainly make no claim to know how or why this is happening, i can say that on my system, what Rohan and Orren have reported is correct: EXS in Logic 8 is no longer limited to Logic’s 3.5 GB RAM limit so long as you have the EXS Virtual Memory option active (if it isn’t active, the old RAM limit remains).

thanks to all who helped get to the bottom of this. i hope this post is helpful in demonstrating what EXS can now do in Logic 8. if not, well, i tried. 😉

cheers

Posted on Sep 18, 2007 12:49 PM

Reply
103 replies

Sep 19, 2007 1:00 PM in response to Mike Connelly

well, to be fair, although i was careful about what i was saying, i kinda assumed this info had been made available to devs myself. but there was nothing i can recollect to suggest firmly that that had been the case.

If this is the case, then apple should really share this information with developers ASAP. I suppose other developers might be able to figure it out on their own but if Apple has the info why not just share it. I can't imagine why they wouldn't want third party plugin performance to be as good as possible.


nor do i, which is where my statements saying things like 'i am sure apple cough up the info to us all publicly' came from. in fact, what i thought had happened is that some info had been made available but not made public. i still don't know if that's the case or not.

again, here is my guessing (probably wildly); maybe the developers of logic have relationships with developers of other 3rd parties, some of which are good and some of which are bad. or maybe the argue amongst themselves about whose fault is whose (i am thinking for example of the buffer refresh problem). so maybe some have got inside info about what is going on and some haven't.

i really have no clue, but i will be honest about what i am certain of and what i suspect, and i thought i had been all along.

Sep 23, 2007 10:47 PM in response to stupid8track

Stupid, do you recommend that I upgrade my Dual 2.7 G5 Power PC from 4.5gb ram to 8gb ? I want to run my new version LP8 (soon arriving), and Lp7 during transition. Will both versoins of Logic benefit with 8gb.Been following this thread to try and optimize my ESX24 experience within my current configuration (no LP8 yet). I am scoring a film and starting to load up many instances of the ESX24 with Orchestral library. BTW, my ESX samples are on my internal media drive (7200 rpm 280gb). Any comments or suggestions will be appreciated.

Sep 24, 2007 9:07 AM in response to Mike Connelly

Mike, it is absolutely possible to utilize 64 bit addressing in Tiger. There are limitations, however. These limitations can be worked around if a developer really wanted to support this feature. At this stage, it would not make sense (in my mind) to bother with this implementation since 64 bit through the entire OS + frameworks will be available 'in October'.

J

Sep 24, 2007 9:54 AM in response to Rexy

Rexy

well, 4.5 GB of RAM is a pretty good amount so i would only recommend installing more memory if you find you really need it. IMO, the best way to tell if you need more RAM for Logic 8 is to keep the program "Activity Monitor" open while you work. if the "system memory" pie chart starts to show very little "green" (free RAM) and/or you see a lot of "page outs", then more RAM would be helpful for you. but until you see that, it probably won't be.

also, more RAM will only improve things for you in Logic 8 -- EXS in Logic 7 can not exceed the Logic 3.5 GB RAM limit, regardless of VM setting.

as for keeping the EXS samples on your media drive, i don't see a problem with that if it's not keeping you from getting work done.

if it is inhibiting creation, then if you can have 3 drives, great (2 internal, 1 firewire): you could use one internal for audio, one for all samples, and then playback the movie file from the firewire drive and be good to go.

heck, you can probably get by very well with just 2 internal drives if you're not recording too much audio -- one drive for audio and movie file, one for streaming samples.

IMO, i think it's always best (and cheapest) to try to get the job done with what you've got first and, if you find you can't, add hardware then because at that point you'll know exactly where you should spend the money.

once you get Logic 8, a good place to look now would be Activity Monitor. if you are running out of RAM with your current workflow, then extra RAM could be a good buy for you.

hope this helps

cheers

Sep 24, 2007 10:22 AM in response to stupid8track

Hey Stu, OT....I still got my Fostex 1/4" 8 trk (mothballs)... You know, smpte on trk 8, midi in the Mac Plus, mics on tape, bump up to 2" Studer/ Neive/SSL odub-mix days ! Thanks for the advice, Logic 8 just arrived, I will watch the activity monitor. I tried your ESX configurations and was able to load a HEAVY Kirk Hunter Orch template that at first crashed Logic 7 almost completely loaded, but then I tweaked and walla it loaded up and ran smooth under 3gb used. Thanks

Sep 24, 2007 10:50 AM in response to Mike Connelly

I wouldn't go as far as to call it 'hacky', just clever thought out design. There are a few ways one could approach it - I don't personally know what the best approach would be because I have not written a real program that truly required 64 bit addressing (AU or not). But there are applications that exist on Tiger that use it - EXS24 is not the first. It can work with clever design. It's no surprise to me that a cross platform developers were not the first to bring this to the arena. Also, one could guess/hope devs are sitting on the technology - considering Leopard's delay.

J

Sep 24, 2007 11:11 AM in response to Justin C

I know in the case of EW they already have a freestanding 64 bit version of their sample player running on the leopard beta and have already shipped the 64 bit version on the PC side. Their original plan was to ship it 64 bit from the beginning, but they're waiting for Leopard to ship the 64 bit app version, then a 64 bit version of Logic to ship the 64 bit plugin version.

Their fix is already finished, they're just waiting on apple to provide the support they need.

Sep 24, 2007 11:28 AM in response to Mike Connelly

{quote:title=Mike Connelly wrote:}
I know in the case of EW they already have a freestanding 64 bit version of their sample player running on the leopard beta and have already shipped the 64 bit version on the PC side. Their original plan was to ship it 64 bit from the beginning, but they're waiting for Leopard to ship the 64 bit app version, then a 64 bit version of Logic to ship the 64 bit plugin version.{quote}


You seem to get a perverse thrill out of accusing others of speculation, and yet you are speculating about Apple. Do you have some inside information that Apple has any intention of releasing a Logic that can accept 64-bit plug-ins as soon as Leopard comes out? What if it takes a year? Two years? What if they decide that Logic runs better as a 32-bit application with 64-bit precision where needed (as it says in the Specs page now) and don't bother at all? Can you point me to your inside information?

You already suggested that 3rd parties have no idea what Apple is doing. So where is your confidence that Apple is going to suddenly tell them their future plans for updating Logic?

Until you deliver me ten screenshots, I assume that you have no idea what Apple's plans are. 😉

I'm not simply being smarmy: my point is, if there is a way now, using either "hackery" (your words) or clever programming or slight-of-hand or whatever to make a plug-in able to address more RAM, it is far, far, far smarter to do it in a way that doesn't require Apple/Logic to give them what they need first, because we don't know if they will. That's why VSL has done what they did—they were clever enough to make their own program so it grabs its own RAM, regardless of the host, be it Logic or DP, be it 32-bit or 64-bit. Even if Logic doesn't go 64-bit, or go fast enough, VSL can go 64-bit and do it all on it's own.

Unless you or EW know something that I don't, they would be far better off not relying on your guess for how to get their sampler more RAM. And if you do know something I don't...cough it up, mister "everything is just an assumption until there is proof!" ;P

Orren

Sep 24, 2007 11:56 AM in response to Orren

"Do you have some inside information that Apple has any intention of releasing a Logic that can accept 64-bit plug-ins as soon as Leopard comes out?"

I've never said that they will release it when Leopard comes out. It could be fairly quick or it could take a year or two. It's also possible that they could never update it, but that would be a huge blunder on their part, especially as other apps move to 64 bit and gain the ability to use more ram.

If you think the backlash on this board has been bad so far, just imagine if the other audio apps updated to 64 bit and Logic didn't. They'd never hear the end of it.

I also wouldn't be surprised if Apple doesn't tell 3rd parties about 64 bit hosting in advance. I don't think I've ever claimed to know what apple's plans are - logic going 64 bit are an assumption, and I think it's very safe to assume they will go 64 bit eventually. It seems like more of a question of when than if. I haven't been saying that apple will go 64 bit soon, just that they should. Unfortunately, apple's actions with logic so far haven't made me very optimistic about taking advantage of what their own hardware and software can provide.

"if there is a way now, using either "hackery" (your words) or clever programming or slight-of-hand or whatever to make a plug-in able to address more RAM, it is far, far, far smarter to do it in a way that doesn't require Apple/Logic to give them what they need first, because we don't know if they will."

Sorry, I just don't agree. Hacks might work, but I don't think they're the best solution for reasons of compatibility, stability, etc. We don't know if Vienna's hack will continue to work on Leopard and future OS updates, we don't know if host apps would run stably if every plugin started doing that. And I wouldn't be surprised if vienna switched back to a standard AU once Logic is 64 bit and other plugs are using more ram as simple AU's. It seems a bit ridiculous to expect every third party to take the time to come up with hacks to fix an issue that has a better solution on the horizon.

64 bit is a known quantity, it's not a guess of mine or anyone else's. Shipping software has already proven that it provides a specific solution to a specific limitation. If Apple doesn't update Logic to 64 bit, the EW plugin can run standalone as an app and take advantage of the ram that way.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

EXS in L8 versus L7: no more 3.5 GB RAM limit (with screen grabs)

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.