PT Logic
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Logic 9 cpu accumulator?

Discussion in 'Logic 9' started by peterlemer, Sep 19, 2010.

  1. peterlemer

    peterlemer Senior member

    I notice that the more I switch songs, closing previous, the more likely I am to get 'memory getting low' warnings.

    Is there a cache that fills up somewhere that I can only empty by re-launching logic, or is there a way I can clear it on the fly?

  3. JuanTahnahmahrah

    JuanTahnahmahrah Senior member

    That problem can be caused by your "Undo History" getting too large. You can set your preferences to track fewer "undos." You can also manually delete the "undo history" every so often.

    My son had the same problem with his orchestral templates, and he uses Miroslav and East-West. In his case, he could only let the undo history grow until three "undos" before Logic (he was using 8 at the time) would get quirky. I came across the issue way back at 5.51 for PC. Seems to me the memory error message is not as specific as it could be: i.e., "Arrrgh! Delete your undo history to proceed..."

    From Logic's main menu, select "Options --> Project Info" to see how much memory your undo steps are using. If there is no usage, it should say 24.

    To reduce the number of undo steps the system tracks, select "preferences --> general --> editing" from Logic's main menu.
  4. peterlemer

    peterlemer Senior member

    JuanTahnamahra ( are you actually a Juan?) thanks :)

    does this mean that the undo history is project-independent, since once I close a project I would expect no undos with a newly opened one ( and the Undo History pane is blank)? <scratches head>

    I have 24 steps. I also see my long-lost 'reorganise memory' which I will try next time.

  5. JuanTahnahmahrah

    JuanTahnahmahrah Senior member

    Juan, John, Jean, Jack, Howie, Bert or Mongo. Take your pick.

    There is a good list of Tips for Optimizing the Mac for ProTools on Avid's site. Your can find it under their support section.

    Logic's "Project Info" can help you monitor which segments of your workflow are grabbing memory.

    In reading other posts, I see people trying stuff (multiple simultaneous audio apps, for example) that I wouldn't dare attempt. I have seen too many obscure "blue screen" messages from PCs, and I dread the Mac's spinning rainbow cartwheel of doom.
  6. georgelegeriii

    georgelegeriii Senior member


    In my experience with Logic, if working on more than a couple of songs over the course of a day, you should take a few minutes and restart your system.

    Like you mentioned, over time caches get fill, and the Mac OS isn't actually the best for clearing things out... for example, Take a session, close, open another close, and then quit Logic. If you look at system memory in Activity monitor, you will see a large blue or yellow section in the pie graph. That is data the OX thinks you might need.

    I use an app: I free mem. It can restore allot system memory, but it is not always the best way. Restarting your system is.

    I suggest to all my tech clients to work this way (every 2 cues, restart) and while you spend the extra time doing this, in the end their system runs better, they have less crashes, and loose way less time and frustration to crashes.
  7. wonshu

    wonshu New Member

    Yes, Logic is terrible when it comes to releasing RAM after closing songs.


    Only solution is to restart the machine as George said.

    It's a big PITA for me, but hey... that's life.


Share This Page