Kontakt Portable and GGD Invasion causes reaper to lag ass

Discussion in 'Kontakt' started by briandsimulator, May 4, 2020.

  1. briandsimulator

    briandsimulator Newbie

    Joined:
    Oct 20, 2016
    Messages:
    34
    Likes Received:
    0
    Hello everyone.

    I have GGD Invasion library installed for my kontakt portable.

    Im running this in reaper.

    My machine spec:
    Ryzen 5 2600
    16 gb ram
    SSD Crucial bx something or other

    I am able to actually do playback and run an amp sim at 96k and 64 samples with no dropouts in audio. However, actually controlling reaper lags ass. Selecting a time region, entering midi notes on the roll, resizing tracks. zooming in and out on the tracks etc. even playbakc is delayed after hitting spacebar and stop is delayed after hitting spacebar.

    Any advice is appreciated
     
    • Agree Agree x 1
    • Interesting Interesting x 1
    • List
  2.  
  3. Xupito

    Xupito Audiosexual

    Joined:
    Jan 21, 2012
    Messages:
    6,956
    Likes Received:
    3,830
    Location:
    Europe
    That sounds weird. How about with other comparable-sized Kontakt libraries?
    With that PC I assume there's no apparent CPU/memory issues when checking task manager.

    I'd tell you to change Kontakt's preload buffer size, but with an SSD and no droputs... perhaps another thing is messing with Reaper.
     
  4. Pinkman

    Pinkman Audiosexual

    Joined:
    Apr 22, 2016
    Messages:
    2,093
    Likes Received:
    1,942
    There must be other services that are prioritizing processes. I have a Pentium that can handle Reaper just fine. From the description, your system should absolutely be able to handle what you are throwing at it.

    Disable everything you can and then run Reaper. Now enable one by one.
     
  5. ReaperLover34345

    ReaperLover34345 Member

    Joined:
    May 4, 2020
    Messages:
    16
    Likes Received:
    11
    Location:
    Tophet
    I think you should ask in the Cubase forum all the so called Reaper experts seem to hang around in there talking about Reaper and its merits, but are vacant in the Reaper forum :dunno:
     
  6. briandsimulator

    briandsimulator Newbie

    Joined:
    Oct 20, 2016
    Messages:
    34
    Likes Received:
    0
    Yea I don’t know what it is. I don’t actually have audio dropouts playing back the samples. It’s just so frustrating to have the sluggish daw control.
     
  7. El digital

    El digital Ultrasonic

    Joined:
    Nov 23, 2017
    Messages:
    69
    Likes Received:
    29
    What is your soundcard/interface?
     
  8. moneymichaels

    moneymichaels Noisemaker

    Joined:
    Jul 8, 2019
    Messages:
    12
    Likes Received:
    3
    Also, what GPU are you using? I know it seems strange that the GPU could have an effect on a DAW, but it definitely does. Also, Reaper doesn't handle graphics acceleration very well. It does so many things right, but sluggish GUI and graphics performance is a known issue. Tons of posts on the Reaper forum regarding the issue. There are a few settings that you can change that will improve the GUI performance though! Feel free to PM me and I'd be happy to go over some of the things that can help.
     
  9. briandsimulator

    briandsimulator Newbie

    Joined:
    Oct 20, 2016
    Messages:
    34
    Likes Received:
    0
    I am using a native instruments ka6 mk1.

    i have an rx570 ssr5 8GB video card.
     
  10. briandsimulator

    briandsimulator Newbie

    Joined:
    Oct 20, 2016
    Messages:
    34
    Likes Received:
    0
    I still have not resolved this issue. Anyone have any ideas?
     
  11. briandsimulator

    briandsimulator Newbie

    Joined:
    Oct 20, 2016
    Messages:
    34
    Likes Received:
    0
    Still have not found a solution. Anyone now?
     
  12. Hanzlwurst

    Hanzlwurst Noisemaker

    Joined:
    Jul 19, 2019
    Messages:
    4
    Likes Received:
    3
    Hi,

    It's a fact that the GGD Invasion library is relatively very very CPU intensive! And that is absolutely NOT due to the size of it!!
    When using the "Turbo" setting(s) it can easily drain your CPU, and/or flood your RAM. These EQ's/Compression FX etc are rendered real time in Kontakt, it are not only different samples. That's why it's heavy for your CPU. And setting the CPU Profile setting in Invasion on "High" is even a more heavy load. This is a known thing! And not really a problem when you just do what GGD tells is the 'smart' thing to do. They say that - when your system can't handle the load - you should 'compose' with Invasion's CPU profile button at "LOW" or "MEDIUM", and when done bounce your song at the "High" setting. That should work. According to them the majority of the people have to do it this way. The difference in sound between 'Medium' and ' High' is really not that big.

    These GGD libraries sound awesome.. So I gladly accept that way of using it.

    What Guitar Amp Sim are you using? I use Neural DSP Fortin Nameless Suite (awesome). Having oversampling turned on also takes up a lot more from my CPU.

    What Audio Interface do you use? The cheapest Focusrite should be suited.

    What you could maybe try is:
    • Go 48Kz in stead of 96k, why 96 anyway? This could help a whole lot.
    • Set Invasion's CPU Profile to Low or medium.
    • In Kontakt - settings - try to change the number of CPU cores it uses. In Reaper set is to 6, and in Kontakt try 6 or 1. Mine works best when I set both DAW and Kontakt to 8 cores, even when I should set Kontakt to 1.
    • Experiment with changing the Preload Buffer Size in Kontakt. Tick the box on the right and set the value from 60kb to 35kb for example. The bigger this buffer the more RAM is flooded, the smaller the more is being read directly from your SSD, which should be fast enough. This will increase your CPU usage a little. But maybe your RAM is being flooded which causes problems. *When changing this, Kontakt re-load samples right away, it's not crashing, so it can sometimes seem.
    • Go to 128 or 256 samples. Try this! You probably won't even really notice, when you Audio Interface is just okay.
    • In your guitar amp sim turn anything of that has something to do with oversampling (they often call this 'quality'').
    • When recording your guitar turn all plugins off that you don't need to record. When recorded turn everything back on.
    • After recording set your buffer to 512 or 1024 or even 2048 samples.
    • Overclocking your CPU, try not to for now. Somehow this kind of software (DAW) doesn't always respond that well.
    • Same goes for your GPU. It's not a game. Overclocking can cause strange things. Then again, I can't imagine your GPU being a problem. Mine uses an average of 5% of the 8GB, using two monitors.
    • Windows 10? Get rid of ALL bloatware, and kill all services/tasks except the ones that windows needs to only run. Turn off virusscanners, background processes, firewalls etc.
    • Maybe try PreSonus Studio One 4 to see if that also makes a difference for you too. It's free to try. When that helps > you know that it's not you or your PC. *In Studio One, try "Dropout Protection" and set it to medium or maximum.. Do not Interpret the word "dropout" in any way before you experience it yourself.
    • And what someone else mentioned. In Task-manager, make sure the priorities are set correctly. But I don't think that's the problem, because even when you've messed with that, at restart Windows resets these things.

    I'm currently using Studio One, which is working really well. I've tried Invasion - among other things - in Reaper. And it's a major difference, I have to say. The things I want to do seem to simply not be doable in Reaper. Yeah only loading Invasion can be done, sure. But then there's not much CPU resource left for anything else. And Reaper behaves very strange when it's under a heavy load.

    Next to that: My system should be fast enough. And Reaper seems to lack some kind of option that Studio One has. "Dropout Protection". When setting that to medium or maximum solves a whole lot. Cubase 10 isn't a problem also, but Studio one is faster for me.

    There's nothing wrong with Reaper. It just depends on what you want to do. I've read somewhere that they will soon come with something similar to Studio One's dropout protection. But I don't know anything more of that.

    My Machine:
    AMD 5.0Ghz 8-core
    32GB RAM
    2 x 1TB M.2. PCIE SSD (At 3.5GB/second read speed)
    MOTU 828ES + MOTU UltraLite Hybrid MK3 audio interfaces.
    Windows 10 Professional. Without any bloatware, and only services/tasks running that absolutely need to run..
    etc..
    I can use 8 Spitfire Libraries, Eurobass Lib, Omnisphere, 4 x Fortin Nameless over 4 DI guitar-tracks, Soothe 2, a whole lot of plugins, etc.. And Invasion at medium and turbo. And it's not a problem. .... in Studio One.

    Oh... Your Ryzen 5 2600 CPU and 16GB RAM should be enough to do nice things. So don't go buying more RAM or something.

    Hope you figure it out..
     
    Last edited: May 18, 2020
  13. Smoove Grooves

    Smoove Grooves Audiosexual

    Joined:
    Jan 26, 2019
    Messages:
    5,209
    Likes Received:
    1,980
    I think you and I should have a fight! :mad:
    Ah. The old 'Reaper users troll the Cubase users' scenario.
     
  14. Xupito

    Xupito Audiosexual

    Joined:
    Jan 21, 2012
    Messages:
    6,956
    Likes Received:
    3,830
    Location:
    Europe
    From what others users of that library say seems I have to ask this specifically: have you checked the CPU (and GPU while you're at it) usage in the task manager?
     
Loading...
Loading...