Same problem here since a year ago, it happens only with kontakt, Sine, Omnisphere, etc is perfect, also when you bounce the entire project you’ll find these “cuts”, if you render in real time you’ll have better results, but yes, it’s a pain… (i’m running nuendo in Rosetta and Native)
1 Like
1 Like
OK that’s amazing it’s not just me going mad. So on the cut bug video you delete many regions either side and your print seems OK is this the workaround?
I should also say I am only seeing this on certain Kontact instruments. I use lots of Spitfire Audio plug-ins as well and it never happens with any of
those
But it does happen with some Spitfire Audio libraries , I’ve contacted them as well. The main one I’m having problems with is symphonic strings
Same Trouble. Cubase 12.
I use The orchestra VST and Native Symphony Series in Kontakt. Problem always with different instruments in different parts
Gear: Windows Core i7 12700KF - 16GB Ram
Is there any chance that your perfomance meter is hitting 100% and the audio is getting chopped because of it? If so, have you tried increasing interface’s buffer size?
I’m not sure, how are you change the buffer . All I can find is the buffer size for the UAD , but I’m running really powerful M1, MacBook Pro, and I am bouncing hundreds of samples from kontakt all other VIs . I’ve pretty much pinned it down to certain libraries within kontakt my end .
It’s not connected with buffer size, it must be a problem with some Kontakt component, not all the Libraries have this problem, Noire and Alicia Keys always have problems with RIP… I moved all my libraries to a m2 SSD disk (2gb read and write) and it didn’t fix it… 
Hi @Pablo_Borghi ,
typically the samples use the disk as the source reading from it only the first time you load it. After this it’s cached on RAM so disk’s speed matter just for the first time loading a library.
The buffer size is something different, and yes @grayedout it’s your card’s buffer size that I a talking about.
It’s frustrating, this could be a setting in Kontakt or something we never imagine. It’s got to go the trial and error way. Have you messed with kontakt’s settings at all?
I’m actually a Kontakt beta tester so I’m gonna raise the subject there is definitely no issues bouncing these instruments in logic, and I’ve bounced hundreds if not thousands over the last month in Cubase with no problem just specific instruments within kontak, . I have a really fast hard drive in my MacBook Pro and I often set buffer sizes to almost 0 there’s no problem. I gotta get this sorted
I’ve done quite a lot of tests changing settings nothing seems to matter
1 Like
About Kontakt Buffer Size I’ve also tried with different values and nothing change…
I’ve been with this problem since I moved to m1, at first I have a Mac Mini with M1 chip, a year latter i bought a Mac Book Pro 1m Max (32 gb) and nothing change…are you running windows or OS?
with Logic everything worded as expected, the problem is Nuendo / Cubase, Rosetta and Native mode.
OK this is weird after doing the Export Mixdown which worked Fine , RIP now seem to also be working !
this file was created using RIP
OK done some tests and did screen grabs … for anyone used Kontakt look out !!! I have a support ticket and have spoken to support I will keep this thread updated
Export Sym String
RIP Export Sym String
RIP Neo
RIP INT Str
2 Likes
Thanks very much my friend !
Any update about it?
Hey guys!
Experienced the same problem for a while and, what was strange, it always seemed, based on my search for a solution, like there were so little encounters with this problem that all I could find was complains that this problem existst and not the solution to it. I’ve also noticed that these glitches occur not only when mixing down to a file that you will play outside of your DAW in a regular media player, but also when you try to mixdown/bounce a midi track to a *.wav file within your peoject in DAW. So here’s what I’ve found for myself:
You can try changing the “Source Module” of the instrument itself in Kontakt. To access these options - you press that little “wrench looking button” in the top left corner of the Kontakt instrument window. There - in the “Source” tab you will find a drop-down menu in which you can pick, basically, from “DFD” and “Sampler”. There are other options as well in the drop-down, but you’re interested in these two… (If you’re interested to read more you can search for “the-source-module” in the Native-Instruments manual on their website)
The “Sampler” option may be the solution, as it stores sample data in system memory, reads it out from memory. But if you choose to stick with “DFD” which stands for Direct From Disk… As the name suggests, what happens here is only the beginnings of all Samples are loaded into RAM (where they can be accessed instantly) and, as soon as a Sample is being played, streaming its remainder from your hard disk then you might solve your glitch problem by:
Fiddling with the “DFD preload buffer size”. This option is found by pressing that same “wrench looking button” in the top left corner of the Kontakt Instrument window. Then pressing the “Instrument Options” button and then pressing the “DFD” tab. There you will find a slider. Try changing it to a higher level.
I must say it still gives the same problems from time to time, but at least gives you a higher chance for a good mixdown. As I understand it has to do with the capacity of your RAM so another recommendation would be to close all other apps that consume RAM when you are mixing down/rendering/bouncing/exporting.
Hope this helps)
2 Likes