Skip navigation

LOTS of Memory problems on new 8 core

806 Views 13 Replies Latest reply: Oct 11, 2011 1:33 AM by The Answer Guy RSS
dbeiden Calculating status...
Currently Being Moderated
Oct 8, 2011 6:11 AM

I just moved from my totally stable G5  running Logic Pro8 on Tiger to my new Mac Pro 8 core. I am having nothing but problems with

low memory issues. Everything is up to date and it doesn't seem to matter if I'm in 32 or 64 bit, running reason in Rewire or not. I am having

trouble narrowing down the problem. It seems to be random. I have seen a lot of posts about this but no real solutions. I'm thinking I got

a bad computer. it's 2 months old. This computer has 6 gig of RAM. I have talked with lots of friends running the same systems with

no problems. What is the latest? I have been on the phone with Apple and Sweetwater and it's all vague. A couple examples and as you can see I don't have

that much going yet. WAY less than I could run on my G5. I have also been unable to get a second monitor to work with the mini display to DVI connector

but it did work with mini display to VGA on the same monitor which is weird, and it seemed slow.

 

(Mac Pro 8 Core Snow Leopard 10.6.8 - Logic Pro9 9.1.5 - Reason5 (tried 6 for 64 bit as well) - APOGEE Ensemble - Omnisphere, Stylus, KONTACT4,

East West Play, Superior Drums, UAD 2 and others)

Notice-LowMemory.png

Plug-ins Disabled.png

Logic Pro, Mac OS X (10.6.8)
  • AppleandtheMan Level 1 Level 1 (125 points)
    Currently Being Moderated
    Oct 8, 2011 2:27 PM (in response to dbeiden)

    You may have bad ram. Have you tried to swap it? Just as a general idea, you can remove the ram modules, use some compressed air to clean around it and replace them in a different order. Do you have access to the Apple Service Diagnostic cd/dvd? If it's 2 months old it's under warrenty so maybe take it to an Apple store and let them check it out. Your new computer is pretty powerful and shouldn't have these issues.

  • Allan Eckert Level 8 Level 8 (39,395 points)
    Currently Being Moderated
    Oct 9, 2011 12:18 PM (in response to dbeiden)

    The Hardware Test is not the best at finding problems with RAM. A much better one is Rember.

     

     

    Allan

  • Pancenter Level 5 Level 5 (7,505 points)
    Currently Being Moderated
    Oct 9, 2011 1:39 PM (in response to dbeiden)

    Both Logic 9 and Leopard/Snow Leopard take considerable more memory than their predecessors.

    Running in 32-bit gives you a little over 3.5GB to work with so that's a problem as well. By the time you load the

    In fact, Logic was designed 9 to give the memory warning users wouldn't keep loading samples/efx and crash the system, possibly corrupting the project.

     

    The Reason bass sound and rewire together are probably using a lot of memory as well.

     

    You will have to go 64-bit and 8GB RAM to have any comfort level.

  • CCTM Level 6 Level 6 (8,550 points)
    Currently Being Moderated
    Oct 9, 2011 2:16 PM (in response to dbeiden)

    Hi

     

    You have reached the RAM Limitations of a 32bit (Logic 9) setup. Reverting to an earlier version of Logic 9 is unlikely to help.

     

    Things you could do:

    1 Superior drums... reduce the amount of samples loaded here. If you have all the mics/bleed etc on you will be using loads of RAM.

     

    2 Reduce the amount of samples loaded by Omnisphere

     

    3 Use the Bounce in Place functins to print some to audio

     

    4 Check Activity Monitor to see how much RAm you have left (Reason will be using up some too)

     

    5 Get more RAM

     

    6 Consider running in 64 bit mode

     

     

    CCT

  • Pancenter Level 5 Level 5 (7,505 points)
    Currently Being Moderated
    Oct 9, 2011 2:26 PM (in response to dbeiden)

    Doubtful any version of Logic 9 will help your situation.

     

    In the example you gave, the combination of Logic 9's increased memory footprint, Snow Leopard's higher overhead + Reason/Rewire and you're probably nearing the memory limit of the 32-bit version.

     

    Logic 9 immediately grabs 600MB more memory than Logic 8, it's supposed to free it up if/when needed but so far I've not seen much proof of that.

     

    You will need Reason/Rewire to go 64-bit.

     

    pancenter-

  • Pancenter Level 5 Level 5 (7,505 points)
    Currently Being Moderated
    Oct 9, 2011 3:00 PM (in response to dbeiden)

    dbeiden wrote:

     

    I just assumed I'd be flying with the new system. I think what throws me, is when I check my Activity Monitor I still have up to 3 gig available when I'm having these problems. If it said none availble, or very little that would make sense to me, but I still have so much availble when I'm getting the messages.

     

     

    The problem is that running 32-bit Logic (or any single application) only has access to approximately 3.6GB of RAM. Less if the operating system is running in 32-bit.

     

    What Activity monitor is showing you is how much the system sees free.

     

    pancenter-

  • QtheMusic Level 2 Level 2 (340 points)
    Currently Being Moderated
    Oct 9, 2011 6:10 PM (in response to dbeiden)

    I am running a new(ish) 8 core with 16 gig ram. Although it won't outrageously outperform my old 2.66 dual core intel, I would have to say that it's gutsy and stable. re. your 9.1.5 question, I am running 9.1.5 on OS 10.6.4 and it's stable. Mostly. You don't want 9.1.4. There was an intermittent graphics issue where dragging a region would crash the computer. Once it appeared in your song, it came up every minute or two, and wasted hours of time. Fixed in 9.1.5, even for those of us still on 10.6

     

    Also, no problems running 2 dvi monitors, one from the dvi and one from the mini port with an adapter.

  • The Answer Guy Level 1 Level 1 (20 points)
    Currently Being Moderated
    Oct 11, 2011 1:33 AM (in response to dbeiden)

    I notice that the memory issues are specific to your Spectrasonics plugins - verify that you have the latest versions installed: Omnisphere 1.5.6d, Stylus RMX 1.9.6e, Trilian 1.4.1d.

     

    For the monitor issue, try resetting parameter RAM: restart while holding down the command-option-P-R keys until you hear the startup chime twice, then release the keys.

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.