1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

Kontakt Player using higher peak CPU than expected BUG

Dieses Thema im Forum "General Chat" wurde erstellt von Magolor, 11. Januar 2022.

  1. Magolor

    Magolor New Member

    Beiträge:
    3
    I've been trying to use Tokyo Strings patch (around 10 to 14 GB RAM consumption) in Kontakt Player for days, and I found that:
    When using Kontakt Player as standalone, as a Cubase Pro 11.0.41 plugin, or as a Vienna Ensemble Pro 5 instance, all gets CPU meter peaked and audio cut, while the activity monitor displays only around 5% of CPU usage, small RAM usage in terms of percentage, and megabytes of disk/SSD read operation. Also, the environments and settings I've been using are listed at the bottom, which are definitely good enough.
    The weird thing is that only when using Kontakt Player as a Pro Tools plugin, it works as expected, being able to play the patch smoothly, with way more than sufficient CPU and RAM. So this ruled out the possibilty of having BUG on the VST, DAW, VE pro, hardware or anything else, lefting Kontakt Player the most suspicious source of this behavior.

    Things tried:
    Multiprocess setting
    Buffer size setting (barely enough for 512, not working for anything below, which shouldn't be happening since the hardware configuration is definitely good enough for lower buffer size, as shown in Pro Tools)
    DAW setting (e.g.: power scheme, ASIO-Guard, etc.)
    Output device setting
    etc.

    Thank you! Have been working on this for days, and I would really appreciate your help!

    Envrionment:
    2 Computers, both using Kontakt Player 6.6.1
    computer1: Mac Pro macOS Catalina 10.15.7 3.3GHz 12 cores Intel Xeon W, 640GB RAM. SSD around 7G/s reading speed.
    computer2: Mac Pro macOS Big Sur 11.5.1 3.3GHz 12 cores Intel Xeon W, 128GB RAM. SSD around 2G/s reading speed.
    Test settings:
    All kinds of ASIO drivers, including Built-in, Dante Virtual, RME, HDX, Pro Tools, etc.
    All sample rates set to 48k and all buffer size set to 128.
     
  2. pedro55

    pedro55 NI Product Owner

    Beiträge:
    49
    Try doing a Purge All Samples to see if it improves things.

    I have an iMac (High Sierra,though) and cubase pro.
    All the samples are on a separate ssd,which is highly recommended, even if it's via an usb3 hub.

    Recently discovered the purge method and it has transformed sample playing etc.

    Perhaps it's worth checking that Kontakt and the mac computers have the same sample rate setting.
    Sometimes these can get altered on a mac Audio Midi Set Up applet,somehow,which will affect audio playing etc.
     
    Zuletzt bearbeitet: 12. Januar 2022
  3. Magolor

    Magolor New Member

    Beiträge:
    3
    Hi! Thank you for your reply!
    As I've mentioned, the problem is not on the insufficient RAM or CPU resources, but on unexpected high usage of the resources, under the circumstance that the resources ought to be sufficient. So, no, purging does not help.
    Also, I've checked about sample rate and they are aligned well, and I also tried several different sample rates and it did not make a difference.
    Thank you for your help, any other guesses?
     
  4. Magolor

    Magolor New Member

    Beiträge:
    3
    Problem Solved. But this is definitely a BUG.

    Does not work:
    Cubase + Kontakt
    Standalone Kontakt
    VEPro5 + Kontakt
    Cubase + KOMPLETE KONTROL + Kontakt

    Does work:
    Pro Tools + Kontakt
    KOMPLETE KONTROL + Kontakt
    VEPro7 + Kontakt
    VEPro7 + KOMPLETE KONTROL + Kontakt
     
  5. pedro55

    pedro55 NI Product Owner

    Beiträge:
    49
    Thanks for providing an update.
    Good to know there’s a partial success.

    It’s surprising a problem exists in Kontakt stand alone mode when it works within another app, though.

    What is the Latency setting you’re using in Kontakt stand alone ?

    Perhaps increasing the Buffer size from 128, may improve things, especially in Cubase,even at the expense of increased latency.
    Comparing with the other apps that currently work may be of some interest.

    However,probably a better suggestion would be to contact Impact Soundworks for further advice/information.
     
  6. Jeremy @ NI

    Jeremy @ NI Support Team NI Team

    Beiträge:
    1.339
    Hey, sorry to interrupt but our community has moved! This forum is now a read-only archive. Please visit our new community: https://community.native-instruments.com/ Just search for a topic and continue the conversation over there, or create a new post if it doesn’t yet exist in the new forum.Thanks and see you over there.