mceric

just got logic 9 for my home system which runs snow leopard. I created a project on my office system (on leopard 10.5) and took it home to open. The first think i get is "there is not enough free memory to open this project". This is not a really huge project - 8 tracks and 20 seconds of music. 8 gigs ram btw. I thought that logic 9 on SL would solve all my problems and here I can't even open a project. Anybody got any clues before I throw this whole system in the garbage.

i'm working in Logic 8 on leopard at the office but when I've tried to open two different projects on my home system which is using Snow Leopard, the project won't open. However, it doesn't seem to be a problem going from the opposite. Is this a documented issue? is there a way around this problem?

got it. ended up being the Melodyne plugin (didn't even recall I had it) which I have heard causes problems. Oddly, I didn't add this plugin, only when I upgraded to Leopard does it seem that it became a problem.

recently added a new drive and moved all my plugins to new drive. After this I tried to open logic and now it crashes every time when it gets to loading core audio. tried moving plugins back to old drive, but no luck. also, not sure if i opened logic since upgrading from tiger to leopard 10.5.8 (not snow leopard). I have 2 plugins Kontakt 2 (which works fine as standalone) and Omnisphere which i'm suspicious of since it will no longer open in Plogue standalone. I've also tried re-installing logic and removing all old logic preferences as well as disk repair. Nothing. any tips would be appreciated.

great...totally forgot about that function. e.

thanks fader8, this does seem to be a viable solution. I've applied this to the flexible envelope which allows me to automate the same effect without using the pitch bend wheel. It's still a little clumsy because you have to key frame it and adjust the envelope release to compensate for the sound jumping or abruptly shifting as soon as you release the key. Question is, if I build this elaborate pitch rise and want to use it as a template for other patches rather than rebuilding it for each new patch, is there away to copy these attribute to another patch or import a patch/instrument to utilize this?

seems like I keep striking out with my topics. Did you guys figure anything out on this?

right, sorry, keep forgetting controller vs. synth. Using Plugins - primarily Kontakt 2 as my virtual instrument, but also have omnisphere and a few native instruments. Don't use exs24 as much. Don't see how this can be done through Kontakt 2. If you're familiar with this plugin, I tried using the flexible envelope filter on the pitch fader and this only allows me an octave range (even though when using the pitch knob manually, you can get 8 octaves).

Using the Oxygen 8, but also have a Yamaha Axiom 25. As I understand it Logic only see this numerically 0-127, with 64 being the midpoint or at rest position. So i guess i would need to know how to correlate those values to a greater pitch range. Ultimately, just need to modulate pitch of one note more than two octaves over time - preferably post performance.

Wondering if anyone knows how to increase the octave range of a pitch bend. I'm using hyper draw to add in pitch bend on a sustained note over time (i.e. 10 seconds). When I use the line tool to drawn in the value from lowest to highest the resulting pitch bend range is around an octave. Would love to get this to be at least 3 or 4 octaves. Any tips?

Is there anyone who can use more than 8 tracks with 3rd party plugins like Kontakt 2 or Play instruments without crashing, running out of memory or overloading CPU. Even with 7gigs of RAM, my system is barely keeping up. Do I need to add another computer? I was told that opening several instances of a plugin in Logic places a greater burden on the CPU (more likely to overload) and that it is preferrable to load several instruments (assigning each to a different midi channel), into one multi or one instance. You would then assign each new track to whatever midi channel corresponds to the next instrument in your multi. That's my understanding of using one instance of a plugin across several tracks. If this is correct, I'm uncertain as to how Logic recognizes this multi as the same instance when you're creating a new track. Do you have to use the Duplicate Track With Same Settings option when creating a new track? Do you just save the Multi you created on track one and call up the same one? However, I was also told that even opening new instruments in the same Multi/instance still eats into Logic's RAM limitations in which case 8 instruments in one multi would be the same as opening one instrument/plugin on 8 different tracks. Also, I was advised that it is better to open up at least four instances regardless, since each instance uses a different core (in a four core computer).

i'll check it out...although as I mentioned the RAM has helped with CPU, now it's a matter of dealing with Logic's RAM limitations in actually loading the plugins.

Interesting tip. I'm unfamiliar with routing these synths into logic using the plugin while in standalone mode. Are you bringing them in as audio like an external synth or module? Also, in the case of a plugin like Omnisphere or even Absynth, how do you open a separate instance of the plugin in standalone mode? I know Kontakt allows you to create a fairly large multi - but Omnisphere sample engine only allows for 8 parts max including any layers and something like Absynth only loads one instrument at a time (i think). Perhaps you can break it down for me.

I had a consultant come in and take a look at my setup. We ran some tests which clarified a few things. First, adding RAM from 3gb to 7gb. This did eliminate the CPU issues and I found I could play significantly more tracks even without freezing. However, another issue surfaced when I tried to open a new track with a Kontakt 2 instrument. I got an error message claiming that there was "not enough memory" to perform this task (or something like that). This seems to happen with more than 8 instances of moderate to large Kontakt instruments loaded or otherwise after 8 tracks. Because this happened when I opened Kontakt, I assumed that it was purely a Kontakt issue. However, what I learned and some of you may know is that Logic can only process 2.7 gigs of RAM which means each instance of another 3rd party plugin is eating that space just by being loaded into Logic. In the case of another plugin Ominsphere - the applications just started locking up with no error message. So it seems the only way to solve this is to add another computer to my setup and load some of the plugins on that system - this should save some of the RAM in Logic on my main system. I'm still a little foggy on this, so if anybody has experience in doing this let me know. I was also considering a Muse receptor but not sure about that product.

thanks for your responses. I'm going to try more RAM to start. I was told by an "apple specialist" that Logic can only process 2.5 Gigs of RAM so I assumed that extra RAM wasn't the problem. Perhaps I should have assumed he had no practical knowledge of integrating plugins. I'm reluctant to reinstall the OS and I don't know that going to 10.5 is going to make a big difference but won't rule out. First I'll run a test with a current project to see how many tracks I can run before overload. I'll add the RAM and try the same test. I'll let you know if I see any improvement.