• Register
  • Help
Results 1 to 5 of 5

Topic: Kontakt / Pro Tools LE 6.1 / OSX10.2.8 How's the CPU Performance?

  1. #1

    Kontakt / Pro Tools LE 6.1 / OSX10.2.8 How\'s the CPU Performance?

    just wondering how other people are doing with this setup. I have a 1.25 gig with a gig of ram and I can hardly push the system with Kontakt loaded as an RTAS plug-in and a couple of decent sized samples.
    DFD doesn\'t help much.

    Does it just come down to needing a 3 gig machine (next summer?) to run something like Kontakt without crackles and pops?

  2. #2

    Re: Kontakt / Pro Tools LE 6.1 / OSX10.2.8 How\'s the CPU Performance?


    You should be able to achieve better performance from your computer.

    Try bumping up your buffer settings a notch in your audio hardware driver window. Also, you may want to consider upgrading to OSX 10.3 Panther, which provides better performance. If you do this Panther upgrade, be sure to do a clean install by re-formatting your Macintosh system hard drive rather than just doing an upgrade over Jaguar.

    Kip McGinnis
    Bardstown Audio

  3. #3

    Re: Kontakt / Pro Tools LE 6.1 / OSX10.2.8 How\'s the CPU Performance?

    There are only a couple of PT sytsems that have been approved for Panther (HD systems)

    The coming updates for panther to get PT to run, is only for G5s.

    G4 support will be coming later.

    It\'s hard to say what your performance issue might be given the level of details.
    But, here is some general info:

    One is, that the built in effects and some filters in Kontact can eat a lot of cpu resources. So, you can try turning those off, if they are enabled.

    There are 2 basic ways to run Kontact. One is using DFD (direct streaming from disk). In this way, it only loads a portion of the samples into ram..and streams the rest straight off the disk..using the buffer setting in Kontact to tweak things for performance/resource usage.

    The other way, is to not use DFD and to load the entire sample directly into ram.

    The obvious here is, that with large samples...you can quickly fill up a gig of ram this way..with just one or 2 samples.

    So, given what you have reported as to your issue...we first need to determine whether or not your DFD is even working properly or not.

    The way to do this, is to load ONE large sample in Kontact inside of PT...without DFD enabled.

    At this point: open the terminal app window..and type top and hit return.

    This will list all running processes and cpu ram usage.

    You\'ll have to hunt thru it..but what you are looking for..is a ram allocation that is approx the same size as the sample youloaded. (say it was a 500 meg sample), If you see a process...that\'s got a 500 meg or so ram allocation.

    Now, turn DFD on...run top again in the terminal window and find the same process and check to see if the ram allocation has reduced. (it should only be loading \"part\" of the sample into ram.

    If it doesnt\' change. Quit PT and Kontact..and reload them again with DFD on...and check it again (just to make sure)

    If DFD is not working properly...then you should call NI and find out the reinstall procedure for both Kontact and DFD to get them working properly. You can double check the results by running the \"top\" test again.

    If your DFD shows that it \"is\" working currently, then your problem lies else where.

    Start with a new PT session..and just load Kontact and start with one medium sized sample. test to see if it plays properly..etc. Then..add another sample. If at anytime it starts crackling...raise the buffer on the DFD and until that crackling..etc..goes away. Add another sample...etc. You are just checking to see if DFD and it\'s buffer are working/responding.

    Since DFD reduces ram load..but puts the strain on your disk drives..that would be the next logical step to check.
    Where are your samples located? And is that the same drive that you are ALSO using for your PT audio tracks?
    Is that drive fragmented?..etc..etc.

    You can experiment with changing the drive location for your samples vs your audio files...to find the best allocation of things that distributes load.

    Is that drive fragmented? Typcially, if you copy your samples into a fragmented drive...the samples get fragmented and makes it much harder work on the drive and Kontact...to read /stream them...and in some cases can cause early popping..etc..you describe.

    the best way, would be to copy your samples to another drive, then defrag the drive you intend to use...then copy the samples back to the drive after it\'s been defragged. This will write the files in one contigous block.

    anyway, a few suggestions...for just general troublshooting to help you get started.

  4. #4

    Re: Kontakt / Pro Tools LE 6.1 / OSX10.2.8 How\'s the CPU Performance?

    thanks Kip and D...It\'s great to have a forum like this and people such as yourselves willing to help.
    I\'ll let you know how it goes...


  5. #5

    Re: Kontakt / Pro Tools LE 6.1 / OSX10.2.8 How\'s the CPU Performance?

    Also its been said a few times here that u can get better performance from Kontakt by turning off your Virtual memory or Page filling with DFD on. You should be able to get 100`s of stereo vioces that way.Rich

Go Back to forum

Tags for this Thread


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts