User Forum

ppjmd · #1 18-07-2009, 18:30

Howdy - just wondering if anyone can give some feedback as to how 3.5 behaves in Logic. Specifically, does it still slow Logic down (GUI, channel strip sluggishness, etc.) like previous versions did? I can't take the leap until I know this has been fixed...

Fingers crossed - any feedback appreciated!

Thanks,

Jim

rimskykorsakov · #2 18-07-2009, 18:43

Hi Jim ,

I'm still on a Mac G5 (Dual 2,3 / 16 GB / OS 10.4.11 ) with Logic 8.0.2 & 7.2.3 .

Let me tell you that K35 works great in Logic8 , as well as in L7.

The overall performance has incredibly improved compared to any former version, including K2 .

Thanks to Kontakt's new KMS (KONTAKT Memory Server), I've loaded 11GB of samples ( "EWQLSO Plat pro" library ) within Logic , using two Kontakt3.5 instances , and I did not notice all these nasty "sluggishness" symptoms within Logic8 like in former versions.

Best

Gerd

ppjmd · #3 18-07-2009, 19:18

Thanks so much Gerd - that's awesome news!

Frank @ NI · #4 28-07-2009, 10:35

Hi everyone,

We highly recommend to upgrade to Logic 9.
We can confirm that the mixer sluggishness and key focus issues have been addressed by apple.

regards,

Frank

mpmusicny · #5 28-07-2009, 15:40

Confirmed! It's a good day! Thank you for working with Apple on this. BTW, also fixed with L9 - entering search criteria in the database now correctly takes priority over Logic key commands . . . yay!

lagavulin16 · #6 28-07-2009, 16:10

It works great with Logic 9, at least so far...

Marsdy · #7 28-07-2009, 18:48

Frank @ NI wrote:

Hi everyone,

We highly recommend to upgrade to Logic 9.
We can confirm that the mixer sluggishness and key focus issues have been addressed by apple.

regards,

Frank

Thanks for the info Frank. Glad to hear this as I'm getting the sluggishness in Logic 8. Not gone for 9 yet as I'm mid project.

Also I'm some slight clicking and popping I wasn't before. This is when the Memory Manager gets over 1.5 GB or so. I have 14GB in an 8 core Mac Pro. Tried increasing the Logic buffers to 256 and turning on multi core support (3 cores) in Kontakt but it didn't help.

Great work on the upgrade though. This is a new era of sampling! I'm on the verge of going to down from 5 to 1 computer in my studio!

robjohn33 · #8 28-07-2009, 20:26

Works fine with Logic 8.02 on a Mac Pro Nehelem (8-core), but only with multi-core turned OFF. When I had it ON, I experienced an incredibly array of crashes (KMS is always on). Anyone have a recommendation for what the multi-core setting should be set to? (or should I always leave it off completely when using K3.5 as a plug-in within Logic?)
- robjohn33

mpmusicny · #9 28-07-2009, 20:30

robjohn33 wrote:

Works fine with Logic 8.02 on a Mac Pro Nehelem (8-core), but only with multi-core turned OFF. When I had it ON, I experienced an incredibly array of crashes (KMS is always on). Anyone have a recommendation for what the multi-core setting should be set to? (or should I always leave it off completely when using K3.5 as a plug-in within Logic?)
- robjohn33

I have it set off always. when i was messing with K3.5, turning on multi-processor support came with a very stern warning. I decided not try it. everything worked fine. Now, with Logic 9, and the fixes that Frank mentions above ( + the text input fix) integration between Logic and Kontakt appears to be spot-on . .

robjohn33 · #10 28-07-2009, 20:37

mpmusicny wrote:

I have it set off always. when i was messing with K3.5, turning on multi-processor support came with a very stern warning. I decided not try it. everything worked fine. Now, with Logic 9, and the fixes that Frank mentions above ( + the text input fix) integration between Logic and Kontakt appears to be spot-on . .

Will do. I suppose with my new MacPro using more than 1 multi-core is not as critical, since the computer is already presumably so fast...Certainly, having that extra memory, though, with KMS, is a blessing!
- robjohn33

mindbanding · #11 31-07-2009, 17:14

Hey,

I was just wondering because i never got an answer for this during the beta stages

when i have K3.5 as one multi in Logic 8 & 9 and i close the session and reopen another or even the same, logic crashes every time and its always when loading the k3.5 that is use in the new session i am running a quad G5 with 16GBRAM, 10.5.7?

Thoughts ?

MB

robjohn33 · #12 31-07-2009, 18:18

Another question: if I'm using several separate single plug-in instances of K3.5 in Logic, does this somehow automatically distribute the CPU load among several cores even with multi-core set to off?
Robjohn33

ppjmd · #13 31-07-2009, 18:53

robjohn33 wrote:

Another question: if I'm using several separate single plug-in instances of K3.5 in Logic, does this somehow automatically distribute the CPU load among several cores even with multi-core set to off?
Robjohn33

It should, as each channel strip is a separate thread, and separate threads are distributed among cores. The trick is to balance a reasonable amount of load among those instances...

robjohn33 · #14 31-07-2009, 19:39

ppjmd wrote:

It should, as each channel strip is a separate thread, and separate threads are distributed among cores. The trick is to balance a reasonable amount of load among those instances...

In other words, you're presumably saying to make sure that no one instance contains too much ram, for example, by using multiple instruments in the same instance? Since I tend to use 1 instrument/plug in instance, I'm assuming this isn't a problem..(?)
Best
robjohn33

ppjmd · #15 31-07-2009, 19:57

robjohn33 wrote:

In other words, you're presumably saying to make sure that no one instance contains too much ram, for example, by using multiple instruments in the same instance? Since I tend to use 1 instrument/plug in instance, I'm assuming this isn't a problem..(?)
Best
robjohn33

Unfortunately there's no easy formula to this because it depends on what you're running, but generally you can certainly run a good handful of patches/samples in each instance. You just need to be careful to not load too much in each instance.

Here's a theoretical example. If you're running EastWest's Platinum Orchestra, you should be OK to load a 16-channel multi of string articulations in one instance, another 16-channel instance for brass, another for winds, perc, etc.

On the other hand, if I were using a 3 GB piano sample in one instance, I'd stop there with that particular instance and open another if needed.

Hope that makes sense. Also, keep in mind it's not just RAM per instance, but CPU; if you have a 16-channel multi and several of those channels are using Kontakt's built-in FX (especially convolution verbs), that plugin could really tax the core it's running on, so you might want to split that multi up between plugin instances.

Here's a link that might help with some of these concepts:

http://support.apple.com/kb/HT3161

JD