Logic 9: Not enough free memory bug!!!

[Ashermusic]

Originally Posted by ultrasound6

Here, here Mr. Shanabit - the shit don't work ! But Jay, you sound like a reasonable and intelligent guy, and I don't want to get all narky and prolong my sarcastic analogies, since it is the dawning of a fresh new decade - but your faithful allegiance with Logic is getting a bit out of hand. Forget the 32 v 64 bit issues, I would just love it, if - when every time I record a simple midi part, (with no plugs or audio), that Logic 9 wouldn't copy the freakin' thing over one hundred times by automatically ticking the loop box in the inspector. Another issue is when I undo a simple midi take, the beast freezes and thinks about it for around 3 secs, although this seems like a ram thing. These are just two of many little anomalies that shit me to tears every time I work - and I don't expect too much from my machine by bogging it down with heaps of plugs, (particularly 3rd party ones), since my beginnings were on a humble Atari and Tascam DA 88. In summary, it would be nice if software developers were more responsible prior to releasing their "wonderful, mind boggling, wash the dishes" type product.
Who cares about "Flex time" and "Amp models", (which are amazing BTW), when basic midi flaws are abundant. Having said all that though, Happy New Year ;-)
(Quad Core - 16 GB Ram with P Tools HD box) ULTRASOUND6.COM | Al Harding

First of all if you open a new empty project with a software instrument and record, you will see that Logic does NOT automatically loop it unless the Loop box is already checked before recording .Then it will default to checked for the next one. The same is true for Quantize settings.

Secondly, I do not have the MIDI freeze thing. It is a system specific issue.

Finally, if Logic's anomalies "shit you to tears" then by all means use another DAW and if its anomalies, and they ALL have anomalies, bother you less, then clearly for you it is the better choice.

[ultrasound6]

First of all if you open a new empty project with a software instrument and record, you will see that Logic does NOT automatically loop it unless the Loop box is already checked before recording ...............................Oh really Jay, gee................ thanks for that............I don't think you read my post correctly..........it is a bug................next you will be telling me how to put it into record and what midi means, etc...........

[yore]

I just want to see if I git this right.. you mean that every time you record a simple midi pattern and hit stop that region gets copied many times ? I've never seen that happen in all these years I've used Logic but maybe I misunderstood something here.

[everythinglouder]

Originally Posted by audiomichael

Worse than the "Not Enough Free Memory" error, is the "Sorry, cannot save your session" error.

Originally Posted by Ashermusic

There is no such thing as a "session" in Logic, they are projects. "Session" ia a PT thing.

Originally Posted by shanabit

Actually the guy who bought the Lamborghini couldnt get the door to open since he kept pushing the SESSION button on the remote instead of PROJECT

LOL!

[ultrasound6]

That's correct Yore - and it doesn't happen everytime - and as we know, that's the worst kind of a problem - a RANDOM one !! I know my way around Logic too - being using it since 1997 and have loved it up until about 12 months ago - but that is the tip of the iceberg with funny little buggy things in Logic 9. Read the other posts and see for yourself - Jay Asher is the only one staunchly standing by his beloved Logic. ;-) I also use P Tools 8 - & it is way more stable - (never thought I could bring myself to say that) :-(

[Ashermusic]

Originally Posted by ultrasound6

That's correct Yore - and it doesn't happen everytime - and as we know, that's the worst kind of a problem - a RANDOM one !! I know my way around Logic too - being using it since 1997 and have loved it up until about 12 months ago - but that is the tip of the iceberg with funny little buggy things in Logic 9. Read the other posts and see for yourself - Jay Asher is the only one staunchly standing by his beloved Logic. ;-) I also use P Tools 8 - & it is way more stable - (never thought I could bring myself to say that) :-(

All I can tell you is that here in Los Angeles, I help a lot of pros with Logic, many of whose names you would recognize.

At various times, they have all seen what they call bugs. Sometimes they are indeed bugs but more often they are system specific issues. Much of time I have been able to resolve or at least improve their issues, but sometimes I cannot because they are bugs so I can only help with workarounds.,

BTW, in my mind the difference is that a bug is something that happens to a large number of users regardless of what plug-ins and audio interface they use where a system specific issue is just that, one that happens to a much smaller number. on their rigs.

Based on my experience over the years 9.0.2 is no more buggy than either 8.0.2 or 7.0.2 was, just some different bugs as some older ones were fixed but some newer ones were introduced with the new features. My friends who use DP tell me it is the same with DP.

I have friends who are ProTools users and they pretty much all tell me that PT 8 is not as stable as PT 7, particularly if you start using 3rd party software instruments. That is not surprising as it has introduced a lot of new features. And they say that if you do not have an HD rig, then frankly, you are not really using ProTools. It is simply too limited to really compete with Logic, DP or Cubase.

BTW, while I cannot be more specific, those of you betting there will be no more LP9 updates with bugfixes are wrong IMHO. I will be curious to see how many of you who have written that will have the integrity to come back and say that they were wrong if I am correct. Those of you that do will probably write, "Yeah, I guess was wrong, they did fix some more bugs but they did not fix bug a, b, or c, .so they still suck."

My final points and then I am done with this as Apple does not pay me:

1. If you want a totally bug free environment to work in, you cannot use ANY of today's DAWS in a meaningful way.

2. If you want the most stable system on the planet, buy a PT HD rig and run PT7 but if you want great sounding software instruments you will be out of luck and if you want great sounding TDM plug-ins you are going have to spend a lot of additional cash, so I hope you have a lot of good paying clients.

3. If you want the most stable native system on the planet, then arguably use Logic Pro 6.4.3 on a G4 with the last version of OS9. Of course, you also will not be able to use much in the way of software instruments and powerful new libraries either.

Or you can do what most working pros do: choose the DAW whose workflow best suits you, live with the bugs until/if they are fixed, find workarounds, curse occasionally but deal with the frustration and instead of wasting your time bitching and moaning on forums, simply GET TO WORK.

And if you find a DAW that you think it less buggy and therefore better, switch to it and deal with the learning curve. But more often than not over time you will find that you have as much frustration with bugs and anomalies the new DAW as the older one. It is simply the nature of this work.

Happy New Year folks, and my new book "Going Pro With Logic Pro 9" will probably be out in mid-March.

[valis]

I'd agree with most of what you said in the last half of that post, and has been the case since I was on Nuendo 1.x and Logic 4.x (running on separate machines). In fact I even had bugs with my older hardware based sequencers (Akai MPC & before that MMT8) and even in non-digital analog hardware that was complex enough (spurious sounds being generated by pressing too many keys on a hardware synth and so on)

Most of my Logic issues these days can be either traced back to plugins (even when not loaded into a project sometimes!), logic prefs, OSX permissions (sigh) and occasionally a midi or audio interface driver. Usually the last 2 are easier to troubleshoot as they don't cause weird midi part behaviour, just application crashes and (in the case of some midi interfaces) a lot of obvious stuff logged in Console.

[TEMAS]

Back on topic again..... Memory getting Low.....

I've been monitoring what's going on with Logic in my activity monitor and here's what I've discovered. If I open a new empty arrangement, Logic is using about 170mb. If I open a virtual instrument, say Absynth or Omnisphere, the memory goes up, as you'd expect, but as I browse through the presets one by one the memory keeps on getting higher and higher.

By the time I've browsed through about 300 Absynth presets (or about 50 Omnisphere presets, or 10 Trilian presets), the memory is up to about 2gb and soon after this I get the warning message or Logic quits.

This is with just one plugin open and before I've even recorded anything, just an empty project. Does anyone know why this is. And BTW, I've got the number undo steps set to 1.

Thanks.

[davey boy]

Originally Posted by audiomichael

I'm gonna up the ante here. Worse than the "Not Enough Free Memory" error, is the "Sorry, cannot save your session" error. It happens when you're close or past the Free Memory safe-zone, and you can still keep working, but not actually save anything you're doing...AND you can potentially crash at any time because you're low on dfegad free memory... WOW... that's great.

My workaround is to bounce some VI's to disk and use the audio files, or tracks with lots of plugins will get bounced. The one saving grace is that now with L9, I can go back to an older session to re-import a track into my session if I need to tweak the sound later.

This happens to me occasionally. But, it's fixable. Go into your audio prefs and turn off your audio engine. Then you can save. After that restart the app or just turn the audio engine back on.

I have the memory error at around 1.5gbs of actual memory being used (and I have 10 gigs installed). Then it will usually crash when I get to around 1.8. I hate it. I switched from DP last year to Logic 8 so as to improve things. Well, this is not an improvement. I hope this new feature gets fixed in the near future. I hear from some inside source that apple is well aware of this and that it's related to many 3rd party plugins (no kidding). The "workaround" is to run your vi's outside of Logic using bidule or something like that. As Jay said, there are always problems when you go form one DAW to another so pick your platform and move on. Back to work....

[Tui]

Originally Posted by TEMAS

Back on topic again..... Memory getting Low.....

I've been monitoring what's going on with Logic in my activity monitor and here's what I've discovered. If I open a new empty arrangement, Logic is using about 170mb. If I open a virtual instrument, say Absynth or Omnisphere, the memory goes up, as you'd expect, but as I browse through the presets one by one the memory keeps on getting higher and higher.

By the time I've browsed through about 300 Absynth presets (or about 50 Omnisphere presets, or 10 Trilian presets), the memory is up to about 2gb and soon after this I get the warning message or Logic quits.

This is with just one plugin open and before I've even recorded anything, just an empty project. Does anyone know why this is. And BTW, I've got the number undo steps set to 1.

Thanks.

That's interesting, I will have to check this later on my machines.

What type of memory are you referring to, RAM or VM?

[valis]

Originally Posted by Tui

That's interesting, I will have to check this later on my machines.

What type of memory are you referring to, RAM or VM?

And what is your undo level? When mine was the default of 30 I had to deal with the 'Kontakt reloading bug' occasionally. I don't frequently use large sample sets so I don't get it very often but those that do (use large sample libs) complain about that bug a lot. Imo they're related to Logic's undo as they showed up when channel strip gained extensive undo operations (for plugin insertions etc.)

[duckoff]

I think this has been said before, but turning the airport off seems to give me a lot more leeway, memory-wise.

Ditto to the undo reduction ( mines set at 7 ) plus it's good practice to delete undo history regularly

No doubt there's some annoying errors ( esp memory issues ), but as far as some of the weirder errors .. looping and all that kind of stuff I've never had that - sounds like a system or project template problem to me.

[TEMAS]

As stated above, undo steps was set to 1. It wasn't a scientific test and I didn't document anything - it was just an estimate and to be honest I don't even know what virtual memory is.

Anyway I had 15 minutes spare today, so I just did another test with undo steps set to 0. As you can see, memory starts off at about 442mb (434 virtual) with one Omnisphere open. After about ten minutes random browsing through my favourite instrument channel strips, ram is at 1.49gb (1.32gb virtual) and the memory getting low warning comes up as I try to load a NI Massive instrument.

Just after this I tried to open a Vienna Imperial Piano, Logic crashed and I was unable to take a snapshot.

[whinecellar]

Originally Posted by TEMAS

...I just did another test with undo steps set to 0. As you can see, memory starts off at about 442mb (434 virtual) with one Omnisphere open. After about ten minutes random browsing through my favourite instrument channel strips, ram is at 1.49gb (1.32gb virtual) and the memory getting low warning comes up as I try to load a NI Massive instrument.

Wow! I'm slammed right now but as soon as I get a few minutes to spare, I want to look into this. Trevor, please report this at Apple - Logic Pro - Feedback (if you haven't already). Same to anyone else experiencing this stuff - and be sure to provide as many details as you can.

In my limited time with Logic 9 on Snow Leopard, I've been using my scoring template that I built back in 8.0.2, and I have yet to see the low memory warning. This template uses 3.02 GB real RAM in Logic 8.0.2/10.5.6, so I don't know what I'm doing right - but in SL 10.6.2 things are WAY more efficient for me. I'm in the process of rebuilding my template from scratch right now though since I moved all my non-EXS stuff out of Logic...

Interesting stuff!

[TEMAS]

Yeah, I'll do that.

To be honest I've had so many problems with my 8-core mac that it could well be that this is something that it is specific to my machine. There are so many variables to put into the equation that it is difficult to diagnose, but I'd certainly be interested to know if other people experience the same thing or if they know why this is happening to me.

Another recently problem, for example, is that the URS Channel Strip Pro plugin update doesn't work on my machine and URS say I'm the only person who has reported an issue.

[Radiogal]

You don´t say anything about your Mac specifications.

FWIW: THE RULE: Macs should have at least 1GB ram for every core..

This also means that new Macs are sold with to little ram in the factory configuration.
Keep this in mind and add as much ram as you can afford.

[Rufuss Sewell]

The same thing happens to me. Logic 9, Snow Leopard and the latest 17" MBP with an Apogee Symphony mobile card. 4gb ram. Logic doesn't clear it's ram, it just keeps filling up until I eventually have to reboot my whole system. With a fresh reboot my system looks like this:

Free: 2.7 GB

Active 386 MB

Still 1.3 Used with nothing running. I suppose Snow Leopard takes that much to run.

Several hours later, on the same boot. I've edited drums on one song by slicing into many thousands of regions. After shutting down Logic I have:

Free: 767 MB ?!?!?!?!?!?!?!?! NO APPS ARE RUNNING AT ALL!!!!

Active: 1.89 GB

A gig and a half is being swallowed up by something and all I did was open Logic, work in it, and close it.

[TEMAS]

Mine's an 8 x 2.8ghz / 10gb / 4 x 500gb / OSX 10.6.2 / Logic 9.0.2.

No other applications were running, except Activity Monitor and whatever OSX needs to operate.

[whinecellar]

Well, I haven't loaded any 3rd party VI's into my new template yet, but I found this interesting:

I spent the last few hours organizing my new scoring template (assigning track icons, colors & names). Note that so far, this template only consists of external MIDI, all routed to slave machines hosting samples - there are NO software instruments loaded yet, so essentially Logic is a simple MIDI sequencer at the moment. I got about 70 tracks into it, and of course noodled a bit on each track to be sure MIDI was going to the right place.

After doing this, I noticed Logic's footprint had grown from 200 MB or so to over 500 MB! Not cool, considering I haven't even DONE anything yet other than change track icons, colors and names! So I quit Logic, immediately restarted it and loaded same template; memory was back to ~200 MB.

So, it does seem Logic's footprint grows with every step you take (I feel a Sting tune coming on)...

Keep the reports coming in, and remember to report at Apple's Logic Feedback page! In the meantime, I have always been in the habit of deleting undo history right before I hit Save - that will help.

Jim

2008 8-core Mac Pro, 16GB RAM, OSX 10.6.2, Logic 9.0.2
RME FF800 on a dedicated PCIe FW card; Unitor8mkII MIDI interfaces
(5) internal SATA drives
(5) external SATA drives on a dedicated host card
ipMIDI (MIDI over ethernet LAN) to slave Macs

[ultrasound6]

Hey Guys - just back from a two week holiday in sunny old Australia - and much to my delight, I see that there is a Logic update to 9.1 - NOW we are talking - it's much more stable - can't wait till the the 3rd party AU companies get their respective 64 bit gear
worked out - and then maybe we can finally utilize the massive amounts of RAM that we all seem to have - yippee - Jay Asher - you must be a happier man now ;-)

[RasCricket]

Originally Posted by audiomichael

I'm gonna up the ante here. Worse than the "Not Enough Free Memory" error, is the "Sorry, cannot save your session" error. It happens when you're close or past the Free Memory safe-zone, and you can still keep working, but not actually save anything you're doing...AND you can potentially crash at any time because you're low on dfegad free memory... WOW... that's great.

My workaround is to bounce some VI's to disk and use the audio files, or tracks with lots of plugins will get bounced. The one saving grace is that now with L9, I can go back to an older session to re-import a track into my session if I need to tweak the sound later.

Man, I just dont get it. Why the hell even bother with Logic if it has errors like that? I mean, sounds like your able to use a whole 15% of your Mac's resources.

The error detailed in the first paragraph clearly says ALOT about the company charging money for this product ~ as well as the people who continue to use it. You can keep working but cant save? AND its $500? Without argument, I think we can all agree theres a memory allocation issue or something of that sort.

I havent had enough coffee yet to be able to fathom why people would stick with a program with such bugs.

[esplace]

Once i loved Logic and i loved Apple, now the ego of this company has taken hold and from my experience they don't give a damn about you unless you can afford the top of the range of their products, hell my new Macbook pro has trouble running itunes let alone logic 9,

My questions to Apple, will logic 9 run stable on a new macbook pro, using waves and other 3rd party software, "yes"

Is Macbook pro 2.5ghz Stable "yes"

Is Logic 9 worth upgrading to, "yes"

After buying both, Logic 9 is going into the bin with all other versions, my next computer won't be an Apple, I can now see why the price between version 7 and 8 dropped so much, though version 8 didn't cause many problems on either of my other mac comps, just Vers 9

Too much B/S from Apple

Anyone out there who is considering 9, just don't use 3rd party plugs and it will probably be ok, but check out the competition too.

[mackie824]

Originally Posted by TEMAS

Back on topic again..... Memory getting Low.....

I've been monitoring what's going on with Logic in my activity monitor and here's what I've discovered. If I open a new empty arrangement, Logic is using about 170mb. If I open a virtual instrument, say Absynth or Omnisphere, the memory goes up, as you'd expect, but as I browse through the presets one by one the memory keeps on getting higher and higher.

By the time I've browsed through about 300 Absynth presets (or about 50 Omnisphere presets, or 10 Trilian presets), the memory is up to about 2gb and soon after this I get the warning message or Logic quits.

This is with just one plugin open and before I've even recorded anything, just an empty project. Does anyone know why this is. And BTW, I've got the number undo steps set to 1.

Thanks.

I'm glad someone else has noticed this.

I have exactly the problem with both 9.02 and 9.1

______________________________________________________________
Mac Pro Quad Core 3ghz, 8GB RAM. Logic 9.0.2, 9.1 OSX 10.6.2. RME HDSPe AIO.

[whinecellar]

Having been mysteriously spared all these memory headaches others have had, I think I finally got caught. I'm noticing Logic's memory footprint growing by leaps and bounds, for no apparent reason.

In a fresh template I just finished, it uses around 700 MB real memory when loaded. So I import a QT movie, save a new screenset with it, locate to a few markers and mute/unmute a stereo temp (audio) track. Logic is now using 1.02 GB. I haven't edited or moved anything, haven't opened any plugins - all I've done is what I just described.

What gives?!? All my big samplers (Kontakt, Play, VSL) are running outside Logic via IAC MIDI - all I have in the song are a bunch of empty MIDI tracks, my EXS sampler tracks, some audio input strips and auxes with Space Designers on them. Nothing's even recorded yet!

I also noticed memory "mushrooming" while I was building this template; after simply renaming a few dozen empty tracks, Logic would be sucking up about 300 MB more (real) RAM. This is NOT good. BTW, I keep my undo level set at 10 and I ALWAYS delete undo history just before saving.

Back in 10.5.6 Logic 8.0.2 I could get up past 3 GB of real RAM usage and work all day long without a glitch. Now in 10.6.2 and Logic 9.1 I've finally seen the dreaded "memory is running low" message, but with only 1.02 GB real ram usage (~700 MB virtual)?

I suppose I could use 64-bit mode since I'm not using any 3rd party stuff in the writing phase, but then I'm afraid I couldn't open the sessions back in 32-bit mode when necessary...

Grrrrr...

[GCL]

Originally Posted by whinecellar

but then I'm afraid I couldn't open the sessions back in 32-bit mode when necessary...

You can, they said 9.1 is backwards compatible with 9.0.2. Do a test though, just to make sure.

[whinecellar]

Originally Posted by GCL

You can, they said 9.1 is backwards compatible with 9.0.2. Do a test though, just to make sure.

Sorry, I didn't explain myself clearly. My concern is that I might build a project in 9.1/64bit that ends up being too big to be opened in 9.1/32bit with those memory constraints.

Still, there might be a reasonable workaround: I could get all my writing done in 64-bit mode (since I address all my non-EXS VI's via standalone slaves), bounce all the stems and then open those in the 32-bit version when it's time to start mixing and using all my 3rd party plugs...

Who knows. I'm just ready for everything to make the 64-bit transition, and to stop constantly worrying about memory!

[Tui]

Originally Posted by whinecellar

Back in 10.5.6 Logic 8.0.2 I could get up past 3 GB of real RAM usage and work all day long without a glitch.

Same here. In Logic 8, memory usage wasn't great, but at least it was stable.

In fact, I've given up on Logic 9 and gone back to 8. 9.1 was crashing all the time on my 8-core Mac Pro. In 64-bit mode, the 32-bit bridge crashed every single time I quit Logic, so I had to force-quit Logic to even close the programme. Unbelievable.

I was really enjoying being able to use lower latencies in Snow Leopard/Logic 9.1/64-bit.

**** it.

[zackpennington]

I'm on a white Macbook, 2.16ghz 3gb ram.

I'm using 1.77GB of ram in the Active category. I was on Logic earlier today cleaning up my projects. I'm currently only running firefox, ichat, mail, and activity monitor.

This is not cool.

[bebopxx]

Originally Posted by Firechild

Ok, as already discussed there is an annoying "memory getting low" box at approx 2.0 Gb RAM usage in logic 9 but you can just continue working but then at 2.30 Gb RAM usage this box comes up and you have to quit Logic ! Why! Any workaround?

Might find your answer here: Apple - Support - Discussions - Logic Pro

[Firechild]

Originally Posted by bebopxx

Might find your answer here: Apple - Support - Discussions - Logic Pro

Hi Dude, welcome to Gearslutz...

One of the rules here is read thread before posting.

You won´t find much useful stuff on Apple´s own forum because the Apple team is deleting every post and thread that gives "badwill" to Apple software or hardware.