Logic Pro 8, Kontakt 2.23 & Memory usage

Hello -
*What type of known memory problems might exist between Logic (Logic 8 in particular) and either Kontakt 2.23 or Kontakt Player 2.23??*
*If there are known memory usage issues, what can be done to help/fix the situation??*
My computer set up is listed below. I have not upgraded to Leopard (but did upgrade to Logic Pro 8). By-in-large, Logic Pro 8 works fine. However, I usually "network" the Logic sequencing projects with Muse Research's Receptor (version B) and/or an aging Dell Precision Workstation 650 using Musiclab's MIDIoverLan CP3. This has proven stable for me. For my most recent project, I decided to see how many instrument plug-ins I can utilize within the Logic Pro 8 program (without benefit of this "network" set-up). For this project, I'm using one instance of MusicLab's RealGuitar and 16 instances of +*Kontakt Player version 2.23*+ for a total of 17 instrumental tracks. The instrument libraries used are Garritan's GPO and JABB. With this many individual (not multi) track instances used, the activity monitor is showing high RAM usage. For some of the instruments, I could not use the KS choices (trumpet, trombone) because the extra RAM caused Logic to crash as I mounted more instruments.
I tried adjusting the DFD. Still, there remained high RAM usage and the occasional crash. For some of the crashes, I either got the endless colored spinning wheel or a message basically stating that there was no memory available for the DFD. I am no expert with the advanced workings of Logic and the DFD associated with the Kontakt plug-ins. But I am surprised that using just 17 instrument tracks with this newer Mac Pro computer (with 5 GBs RAM) is causing problems. Sadly, I am not an expert Apple user to be able to tell whether it's the computer or Logic or Kontakt. I suspect, though, its some kind of issue between Kontakt and Logic.
For my audio, I use MOTU's 2408 MK3. For my midi in-put I use M-Audio's Keystation Pro 88. I do not think either one of these devices are causing the apparent memory problems.
By the way. . . before I purchased my newer MacPro computer, I had a similar instrumental set-up using my aging Dell Precision 650 workstation with 2 GB of RAM using Steinberg's SX 3 program. I used the same GPO and JABB sound libraries. It did "challange" the Dell computer (I had to adjust buffer/latency settings to MOTU's 828 MK2 used with the Dell computer), but the computer didn't crash like what I'm experiencing at present.
I don't mind "networking" my computers together in order to use larger instrumental plug-in tracks. But I would think that given the "power" of my newer MacPro I should be able to handle more than 17 GPO & JABB tracks. Yes? No?
*Given my current computer set-up, how many instrumental tracks (using libraries associated with Kontakt or the Kontakt Player) should I get??*
Thank you in advance.
Ted

Sadly, I can chime in with the same basic problem. Namely, that
Kontakt2 seems to leak ram. I've watched the activity monitor show
an increase in ram allocation to logic if i simply LOOK at a kontakt
instance. Just clicking on the instance causes ram to be allocated, and no matter how much I purge samples, I just can't retrieve that ram. Once 2 gigs are sent to logic, crash.
The only solution I've found is to save & restart before it climbs too high. I can then work for an hour or so until the ram overflows again. This is obviously a major bug, and I agree that Logic doesn't appear to be the culprit.
Have either of you tried K3? I wonder if the problem is more under control there? There's no way Kontakt will bother to fix this bug
in v2.23 with v3 on the shelves. The question is, how do we know that v3 fixes it without buying it? I've heard reports that v3 is even
more bloated than v2.
I've recently done a clean install of leopard on a blank drive, and
i'm patiently waiting until NI updates the installers for K2.
Then, i'll have a clean OS, clean newly installed logic 8, and
a cleanly installed K2. Maybe that will help mitigate, if not solve the problem.
I'm almost sure that Kontakt is the source of the problem, but
I've also been told that Intels have serious flaws in their ram
allocation WITH TIGER.
Some people with G5's have reported having access to 3.5 gigs ram.
Intells can only use 2 gigs with any one app. This was thought to be a problem with Tiger and and Intels. So maybe Leopard will expand the RAM wallet, and then we just have to wait for Kontakt to stop spending so much.

Similar Messages

Logic Pro 7 running out of memory!?!

Hi!
I am working on a project were I basically want to cut up every beat of a drum recording on 12 tracks and correct their timing individually (I have my reasons for doing this).
This creates a decent amount of regions and for some reason Logic starts complaining about running short on memory and not having enough memory for the undo history.
It bugs me because I am working on a Dual 2.5GHz G5 with 2 GB of RAM. Activity monitor says I have 480 MB of inactive memory and 1.25GB of free memory. Logic uses 300 MB of real memory and 762 MB of virtual memory. No other apps running.
How can I make Logic use ALL the available memory?
Is there a limit on the amount of memory that Logic can address? What is this limit, and how much memory is reasonably motivated for a PM running Logic?
How about plug ins? Do they have separate memory spaces not limited by Logics potential limits? "Drumkit from ****" can by itself use a couple of Gigs of RAM if available...
Thanks in advance!
/Jont Olof

Jont Olof Lyttkens, "Logic Pro 7 running out of memory!?!" #5, 03:19pm Sep 7, 2005 CDT
However in the earlier days, running under Mac OS pre 9.x the ability to allocate memory to a specific application could increase the amount for the song event memory
No, it didn't. It increased application memory, but the song event memory remained the same, just as it does now.
I think, though, that with all Logic's new features, there is more actual data in an equivalent song, so the limit may be coming earlier. (I can't be sure of that though)
I know you don't want to, but did you at least try reducing the undo history size (in prefs) ?
Does deleting undo history and then saving help ?
Another thing to consider, although I don't think it generates warnings like you are seeing, is Virtual Memory. If the computer has been up for a long time, running memory-intensive apps, like Logic, then it can get overloaded (too many pageouts) which can slow things down a lot. If you do notice things getting slower, then restarting the computer will flush the Swap File and get things going again.

Problem with working: logic pro x & kontakt 5

My logic pro x bounces o.k (with the mini mac that i use), but it can not bounce well when i creat a project that uses the kontakt 5 instruments
why?
thanks

Hi
You can check the version numbers various ways:
Open Logic Pro X:Preferences:Audio Units Manager: This lists all AU plugins and their versions
Open Kontakt, click the NI logo top right: the version is displayed top left of the splash screen
CCT

Premiere Pro CC 2014 60GB virtual memory usage

The longer Premiere stays open, the slower it runs and the more memory it uses until the system errors out and makes me close things.
Any ideas? 60GB memory usage seems ridiculous. The total footage size is only 10GB.
Running Premiere Pro CC 2014 and After Effects CC 2014 with dynamic linked files, app nap turned off.

Am having the exact same issue - premiere clogging up my system with excessive memory usage until I am forced to close things. Using most recent premiere update 8.1. Please help adobe! I'm on a deadline!

Logic Pro Midi Kontakt Issue...

I've just bought the Spitfire Albion 1 library and love it already. Although there is one problem which I can't seem to find the answer to anywhere, which is that when i am recording for instance a legato strings section from my midi keyboard, and using the kontakt modwheel (my keyboard doesn't have a modwheel, so i use the one on the kontakt interface), moving the mod wheel up and down makes all the difference it should, however when I stop recording and play back what i have recorded, it is wherever the mod wheel is placed after that determines the sound outcome. This means i can only have one modwheel value for one recording, which restricts the dynamics of compositions. Hope that all made sense and wondering how i can fix it? I'm relatively new to logic and kontakt, so am unsure about the whole situation

Hi
Kontakt does not pass the internal Mod Wheel info out to Logic. For libraries such as Albion, recording into Logic or creating the MIDI CC info offline, is essential.
You could manually create it using MIDI Draw, the Step Editor etc., though you may want to look into getting an additional keyboard or controller with a decent Mod Wheel.
CCT

Logic pro X CPU is off the chart since Yosemite

I'm having some Logic Pro X issues. The CPU usage is off the charts. CPU shows active when I'm not even playing a track. I have no other applications open. I have repaired permissions etc. It's so bad that the CPU spikes if I play just one track of audio, and Logic will show "system unable to play back.." error. This really is ridiculous. Should I go back to the previous version of OS X? I'm out of ideas. Strangely, somedays it works just fine. As soon as I think the problem has past, it starts up again. I definitely seems like some kind of CPU or memory issue. Any help would be appreciated. I know my system is a little light but I've never had these issues before upgrading to Yosemite. And no, I foolishly don't really use time machine, so that's not an option either.
Thanks,
MikeD
21.5-inch Mid2011
2.5 GHz Intel Core i5
12 GB memory

At the moment, Yosemite and LPX is not a recommended combination.... Many people have reported the same behavior of 10.10 and 10.0.7 working fine one day and then it all falls apart the next....
Nothing much you can do as you didn't make backups... which means you can't easily roll back to a previous configuration...
So, your only two choices are
A) Manually backup your personal data/projects/photos/music etc... to an external HD and then wipe your System drive (assuming your recovery partition is still showing 10.9) and reinstall Mavericks from scratch... holding down Cmd + R at startup... Then reinstall LPX plus content plus any 3rd party plugins and libraries you use.
or...
B) Wait for a while (maybe quite a while) until Apple releases fixes for Yosemite and/orLPX to resolve these issues.... and put up with the current problems.
In the meantime, I suggest you start making backups using something like Time Machine or my preferred method which is using the HD cloning utility SuperDuper! as one day, you will need them.....
http://www.shirt-pocket.com/SuperDuper/SuperDuperDescription.html
Not what you wanted to hear I'm sure.. but that's the current state of play.

Logic Pro 7.1.1 stability

Hi,
I'v been using logic on mac since v6, I have never bin able to have logic run continuously for more than an hour!! It always locks-up on me (crashes). I am at the end of my tether. I love the look of logic and love the way it works, (wen it works!) Am I missing sumthin? anybody?
I have checked all the following things:
I have checked all my memory modules. (removed 1 faulty 512mb)
temporarily removed addional internal/external fiwi drives
repaired drive permission,
Installed pro application suport 3.1
disabled ALL third party au's (Absynth, atmosphere, minimoog v)
reset logic pro7 prefs
removed motu av/audiophile 2496 drivers and used interal audio
tweaekd audio preferance settings.
...and still it crashes! slight improvement yeah, but crashes after hour or so
I am using logic pro 7.1.1 1/2gig ram, 4/5 audio tracks,sum logic au effects.
Am i doing sumthin wrong.? I'v checked and double checked all my g4 hardware with apple hardware tester. could there a seriouse bug in MY copy/version of logic that prevents it from running a few audiomidi tracks for an hour? Can any1 help advise?
Considering i spent ova £600 on my logic pro,
my heart sank when i (out of curiosity) downloaded and installed Logic Express Trial on sun 4th, I set it to play.. and to my astonishment it ran from 10:00 sunday morning to 23:00! all the time iwas swapping/jumpng around screensets editing and generally USING it, trying to crash it! Express remained rock solid all the way ever since, is there an pro equivalent?
any1?
Thanks guys...
Mac G4 MD dual 1.4Ghz Mac OS X (10.4.3) 120gig hd. 1gig mem 17in macdisplay
Mac G4 MD dual 1.4Ghz Mac OS X (10.4.3) 1gig omem 17in macdisplay
Mac G4 MD dual 1.4Ghz Mac OS X (10.4.3) 1gig omem 17in macdisplay

logic 7.1 runs ok here, but that's on a G5. Did you loop the hardware ckecking prg? A guy at applecare told me that the memory is only checked random. If you want a thorough check you could press ctrl-L ( or something like that; I forgot) when starting the harware check to loop the prg, run it overnight and see what comes up. I can imagine logic pro uses a lot more memory than logic express, so it would be more sensitive to memory failure.
Any other prg that uses a lot of memory? Is your mac stable when running a load of prg at the same time?
Goodluck
Budy

Logic Pro slower on 2011 MBP than 2008 MacBook? Especially with NI Kontakt

Hi I just got a new MacBook Pro, late 2011 model, and I was really stoked but I've come to find Logic Pro runs slower in general than on my old MacBook (not pro, mid-2008 model). I know the MBP is a faster computer but I can't figure out why Logic is so slow and I was wondering if you guys could help me out with some optimization or answers. The main issue lies in Kontakt, which I was able to run far more instances of on my old macbook than my new MBP. I frequently get system overload despite having more cores on the CPU and the same memory.
Below are the differences:
2011 MBP (stock)
Logic Pro 9.1.6 64-bit
NI Kontakt 5 (4-8 instances)
NI Pro-53 (2-3 instances) through 32-bit AU bridge
NI Massive through 32-bit AU bridge
2008 MB (stock, except 4GB memory upgrade)
Logic Pro 9.1.0 (32-bit)
NI Kontakt 4 (8+ instances no problem)
NI Massive (2-6) instances

I'd also add that when running large native instrument sample libraries, they advise (in the start up guide) to install large sample libraries on a dedicated hard drive. If you have a FireWire 400/800 drive, it might be worth it to install kontakts huge library on there and see if that frees up some CPU. Trying to run logic / the plugin applications, the sample libraries and your recorded audio/logic files on one drive will severely hurt your CPU performance.
I know is doesn't really answer why you'd be faster/more stable on your old Mac, but might help you get the most out of your new machine.
Cheers!

How to reduce CPU usage when working in Logic Pro and Kontakt5

Hello All,
I have a MacBook Pro 15" early 2011 2.0 GHZ. My main acitivity is making music with my macbook pro. I am using Logic Pro 9 in combination with Kontakt 5.
I want to get some suggestions in the setup so I can reduce the usage of the CPU. By the way I have upgraded my system with a SSD 256GB , 16GB RAM and have removed the optical drive and installed the the previous factory set HD in the optical bay. I have placed the samples of the Kontakt 5 in the HD so I have enough space on my SSD to run the progrmas fast and smooth !
If possible give your advise on an optimum setup such as reachanaling the sounds through BUS to AUX channels and other methods in order to reduce the CPU usage. You may even post some good links where I can find more info.
Thanks in advance
Wkrgds, Levon

welshwiggle wrote:
So Center of Pan,
If you were to run something like Omnipshere on an active SI track do you get anywhere near the "1 core CPU" spike I'm getting on my Late 2011 TOTR MBP?
I still dont really get why L9 on a new MBP peforms worse than eg your PC.
Older versions of Logic (ie: 5.5) don't see individual cores, there is one disk meter and one CPU meter. In some ways it's a more efficient system. This is running on WinXP which happens to be a very good system for audio. Consider this, XP can be installed and take up only half a gig of disk space and do 90% of what most operating systems can do today.
I do see single core spikes on my single processor quad core Mac Pro. There's no way to get around a processor intensive plugin on a single track. A channel strip is tied to a single process (core). I stopped upgrading at 10.6.8 and Logic 9.1.3, because it works. I still get the occasional single core use even with multiple plugs and tracks but I can usually break the logjam by quickly starting and stopping Logic 2 or 3 times.
I will not upgrade Mac hardware or software unless the next version of Logic is outstanding, I'm fine where I'm at for the next year or two. I enjoy recording performers more than anything else so al I really need is a good sounding, solid system.

How to save kontakt sample files in Logic Pro X project?

Hi,
I'm using Kontakt (Komplete, Native Instruments) as my samples for my midi in Logic Pro X, and my sample libraries are stored in an external hard drive which I bring around.
I need to send my Logic file over to another computer which will not have my hard drive that contains my sample libraries.
Is there a way to save my Kontakt Sample midi files together with Logic's folder, so when I open Logic without my ext Hard Drive, the midi can still be read?
I tried clicking Save As --> Organize my project as a "Folder", and ticked EVERYTHING --- Audio Files, EXS instruments and samples, Ultrabeat samples, Space Designer impulse responses, Movie file, Include Apple Sound Library Content.
But when I unplugged my external hard drive (which my sample files are stored), and clicked open that logic file which i saved, windows pop up saying it cannot locate my samples.
Is this a bug in Logic Pro X, or am I doing something wrong?
Or is it totally not possible to copy sample files over?

skylurker wrote:
I tried clicking Save As --> Organize my project as a "Folder", and ticked EVERYTHING --- Audio Files, EXS instruments and samples, Ultrabeat samples, Space Designer impulse responses, Movie file, Include Apple Sound Library Content.
<snip>
Or is it totally not possible to copy sample files over?
Hi
Logic will not copy over any 3rd party samples etc. If you really need to, you would need to copy the appropriate libraries manually, though with Kontakt, some libraries would need to be re-authorised.
CCT

2.3 or 2.7 GHz (Primary usage Logic Pro)

Hello everyone!
Have been looking around for this topic but havn't found SO Im posting my thing out here.
I am a long time Mac user with music production as profession and with Logic Pro as my primary program.
I am about to buy myself a new MacBook Pro and have to great choices but when it comes to the details I would be thankful for some guidance.
Choice nr 1 is the latest MacBook Pro 15¨ - Retina Intel QC i7 2,3 Ghz - 16 GB Memory - 512 SSD
Choice nr 2 is probably a little bit older but with the same specifications but with Intel QC i7 2,7 Ghz.
My following question is how big difference is it between 2,3 and 2,7 GHz? As I mentioned - music production and Logic Pro is my primary use with my computer and I know that when it comes to music - RAM-memory is the most important. The price difference is not so big but still enought for me to post this topic and - is there anything else than the GHz that have been improved in this latest MB Pro that matters to me here?
Very thankful for any thoughts or answears here. I will buy one of them and after what I have heard is it very little difference so I am probably going for the Choice nr 1 (since it is the latest) but what do you folks here think?
Cheers!

Memory is not necessarily the lynchpin. I remember tracking 24 channels of 192/24bit audio simultaneously with 512mb of ram, SATA 1 5400RPM HDD with nary a hiccup. Nothing different about audio now, 14 years later. Same bits.
While music processing can be somewhat processor intensive if you use a lot of plug-ins, the difference between 2.7 and 2.3gHz will not be immense. It may be a matter of one or two plugin instances (depending on the plug). A lot of this will depend on how the plug-in is actually written as well as the number of cores on the CPU. This introduces a lot of uncertainty into looking at straight gHz.
Storage will be a factor here. Even at 512gb, you may find yourself cramped for space if you have lots of multitrack audio projects on the go. If you end up using an external thunderbolt drive this will negatively impact your performance (though probably not much, see my opening sentence).
The other factor to consider is the possibility of using external audio processors such as that which is available from Universal Audio and which take some load off your computer's CPU for processing effects. I've been using their UAD-2 PCI card on my Mac Pro and I love it. Great product, great effects.
You can also freeze tracks or commit the effect by doing offline processing which will release your CPU of some tasks.
Perhaps some more information about the exact type of projects you are doing would help. I primarily do multi-track (16 to 32 simultaneous inputs) recording and mixing (highly variable track count at mixing stage), which has very different demands on a system compared to say, someone who is doing multi-track midi sequencing and sampling.
Needless to say, both systems will likely be very good at handling whatever you are throwing at them.

How to open kontakt in logic pro 9 on lion os

How to open kontakt player in logic pro 9 on lion osx...???
I have installed the player but it doesnt show up in logic..
what do i do??

Hi
Assuming that you are looking for Kontakt Player in the right place (Click hold the I/O slot on an instrument channel), and it is not there???
Go to Logic Pro:Preferences:Audio Unit Manager, and see if it is listed in there
Make sure you have installed the latest version of KP
CCT

Ableton Live 6 vs Logic Pro 8 CPU usage/audio quality.

Hi,
Any user's have feedback regarding CPU usage between Abelton Live 6 vs Logic Pro 8. I'm currently running Live 6 on an MBP 2.0ghz (CD) and am constantly running into audio drop outs etc etc.I am reading throughout the net that Logic Pro 8 is more CPU friendly than LIve 6... is this true, overall? Also any users ever do a mixing test between the two apps to see if there was an audio difference when rendering your final project to aiff or wav? I am thinking on using Live 6 as a stratch pad to "create" as I enjoy it's flexibility then transfer the project over to Logic, however that depends if there really is a difference in CPU usage and Audio quality between the two DAW's.
Thanks.
guess i should also state that i will be running on the new imac's come tax return time. lol

Logic 8 is very CPU friendly, I can say that much. I never found Ableton Live 5 to be very taxing either, though. Pro Tools is.
But like you I use Ableton as a scratchpad, I love how it works, and Logic for the finishing touches. But that's just because I'm not good at Logic yet. Not fast at it.
Get them both! You'll be glad you did.

Logic pro 9 on mavericks: problems with kontakt instrument Drumlab

Hello!
I purchased drumlab on september 2013. It worked properly on my macbook (late 2009, with expanded 8GB ram) with logic pro 9 and kontakt free player 5. Unfortunately, after a few days my macbook suddenly broke.
Now I have a new macbook pro (2.4GHz dual-core Intel Core i5 processor, 8GB ram, 256GB PCIe-based flash storage) and I downloaded and installed again logic pro 9.1.8, kontakt free player (5.0.1.5371) and drumlab (from my "order history page"). Everything is working (even other kontakt instruments) but not drumlab. When I try to load the drumlab instrument in kontakt the message "THIS PATCH WAS CREATED WITH A NEWER VERSION OF THE APPLICATION etc." appears.
I don't think it's a problem of compatibility (these are the latest versions of the applications).
I tried to do what they suggest here http://www.native-instruments.com/knowledge/questions/346/KONTAKT+Error+Message% 3A+%22This+patch+was+created+with+a+newer+version+of+Kontakt%22, but it doesn't solve the problem. Really hope someone could help me with that!
Many thanks!!

You need to update your Kontakt Player to the latest version which is v5.3.0.. The one you are using (5.0.1) is at least 9 months out of date... which is why you are having such an issue....

Logic Pro 9: CPU usage

I could definitely use some help!
I am a well experience Logic Pro 9 user, and I am having some serious issues with CPU usage. I have a Mac Mini Server with a 2 GHz Core i7 and 8 GB of 1333 MHz DDR3 RAM. With my current system, I run all of my applications and operating system on a dedicated internal HD. All my sessions are run from a seperate internal HD.
Typically I don't experience many issues with CPU usage with exception of this project. Every 5 seconds I get this error.
"System Overload.
The audio engine was not able to process all required data in time.
(-10011)"
I have tried everything under the sun and even the old "who's your father" trick to eliminate this issue. NOTHING has worked yet. Here's what I've done so far:
1. Increase my buffer size to it's max at 1024 samples.
2. Freeze all tracks which I use heavy processing plugins.
3. Flatten and merge all take folders.
4. Merge all audio regions.
5. Delete all unused audio regions in my bin.
6. Set all channels to "No Input"
7. Close out of all other programs.
8. Turn off WiFi.
9. Turn off Bluetooth
I'm currently running 35 audio tracks, 3 Aux tracks and 0 midi tracks. I have very little automation, and I'm not using Flex time. I have never experience this much CPU usage ever, and it's driving me INSANE.
Any help is grealy appreciated.

What does the Drive/CPU usage (Performance) metering look like in Logic? That overload error can mean a lot of different things. Typically... it's a system bus overload and can be caused by Logic's Space Designer and/or Delay Designer. What is the Process Buffer Range set at?
Have you tried a project of this size since upgrading to 10.8.4?
Curious, what sample rate are you using?
I like AOL's idea of importing each track, might narrow it down.

Logic Pro 8, Kontakt 2.23 & Memory usage

Similar Messages

Maybe you are looking for