KONTAKT 5 PLAYER PERFORMANCE VIEW FULL
KONTAKT 5 PLAYER PERFORMANCE VIEW PRO

Like when there's a chord change, there's a slight pop. For me, it went away when rendering the final audio in non-realtime. (10-26-2018, 01:57 AM)Samulis Wrote: Just a single pop right after the very start of the sample? I've seen this problem before. Can you set Kontakt's sample rate independently of the DAW? (10-25-2018, 11:14 PM)bigcat1969 Wrote: Saw someone fixed a popping problem by matching the sampling rate between Kontakt and DAW. The convo verb has been off all along while testing this. (10-25-2018, 11:14 PM)bigcat1969 Wrote: Oh try turning off the convolution reverb. This doesn't appear to make a difference either. (10-25-2018, 11:14 PM)bigcat1969 Wrote: You could try turning the max voices down a lot as well to see if that fixes some of the problems. (10-25-2018, 11:14 PM)bigcat1969 Wrote: Have you tried the shorts to see if they pop? The longs tend to run three x-fade samples and then pop three release samples? The shorts are less sample intensive. I tried this, and the popping still happens. It is also easy to run Task Manager along side the stand alone to see actual CPU/HD usage. This might tell if it is a conflict with Reaper.

KONTAKT 5 PLAYER PERFORMANCE VIEW FULL

(10-25-2018, 11:14 PM)bigcat1969 Wrote: Can you run Player as stand alone with the instruments and see if it has the same problems? I haven't used Player in a long time, but in the full Kontakt I can run it stand alone. The only thing I haven't tried at this point is running Kontakt Player in another DAW, which I guess I should do just for troubleshooting. Popping and clicking is just annoying and makes me feel like my system is about to go into a hard freeze at any moment.Įdit: REAPER's 'Buggy plugin compatibility mode' doesn't help either, though it has for me in the past with plugins that throw random glitches.

KONTAKT 5 PLAYER PERFORMANCE VIEW PRO

Performance is snappy enough otherwise and VSCO2 Pro is a lovely yet idiosyncratic library that I'm going to have to review once I get everything up and running smoothly.

So what the heck is going on here? Is this some weird bug that I've come across or are Kontakt's/REAPER's performance meters not showing me the whole picture? Using Kontakt 5 or Kontakt 6 makes no difference either. Neither does increasing Kontakt's DFD buffers. Increasing my ASIO buffers to even non-realtime playable levels makes no difference. So these numbers seem to indicate that I'm nowhere near running out of horsepowers, yet I get pops. Looking at REAPER's performance window, my total CPU hovers around 18% and my realtime CPU at ~30%. None of these peaks appear to correlate with the pops. And before you say 'ah-hah! that's your dinosaur computer!' let me add that this single Kontakt instance occasionally peaks at 15% CPU but normally hovers around 8-10%, with the disk streaming going up to 25% from time to time.

The thing is, with only one instance of Kontakt Player loaded and only a handful of instruments playing, I'm getting pops and clicks at almost every note start. I know that Kontakt is quite well optimized, but my computer is getting long in the tooth (Athlon X4 2.8GHz, 16GB DDR3 RAM, samples on a WD Black 7200 RPM 1TB HDD) so I had no idea what to expect in terms of performance. This is a plugin that I haven't used much at all except for the Drum'Mic'a kit years ago and the occasional ethnic instrument from the factory presets. Less than a week ago I received VSCO2 Pro Edition as a kind donation, which in turn meant my first orchestral foray into the world of Kontakt, or Kontakt Player to be precise.

Kontakt 5 player performance view