Hi,

When bouncing my Kontakt tracks, there are lots of spots where the audio just cuts out of nowhere.
This never happened before and I've done all I could to fix it with no success.

I tried every single audio device with every single backend,
I tried maxing out my buffer size (the maximum I was able to was around 8k samples with FlexAsio, after that Studio One just crashes).
I tried maxing out the load size inside Kontakt Portable as well.

No luck. Maxing everything out causes less dropouts, but they are still there. This was never a problem before. I used to be able to bounce tracks just fine in good old Windows Audio.

Any ideas?

 

We need OS, S1 version, Kontakt version and some hardware specs.

 

Studio One 6 (legit), Windows 10 64bit, Kontakt 7 Portable (bootleg) 16gb RAM, i7-6700HQ 2.60GHz CPU. Let me know if you need more.

 

I am streaming my libraries off an external hard drive (not an SSD). Could this be the culprit?

 

i have all my kontakt libs on different ssd's, since you have bounced your track played by kontakt they become simple .wav files

i have experienced the same problem with recorded audio (guitar/bass etc), when the audio will just STOP playing back at same spots.. and that happened out of no where, even if you return to zero, restart studio one etc. in my case, the culprit was one of the real time audio processing engines for timestretching, i have either disabled or switched to another one.

this is a SERIOUS FLAW in studio one, i have already wrote several threads to their forums, it happens since v5.5 they were never been able to resolve this. i don't know if this may help in your case.

 

It is, yes. For some reason, if you load libraries from an HDD in Kontakt 6 or 7 (VST3), it will drop out constantly. Not sure about v5, but I was forced to buy an SSD for my libraries just because of that, and the problem went away instantly. Back in Kontakt 6, the problem instantly goes away if you switch to the VST2 version. I could reproduce it with 100% success rate. Playback works fine, but it drops out when rendering. Nothing really fixed it for me until I bought an SSD (I was already planning to, but it sucked to be unable to use Kontakt after batch resaving in Kontakt 7).

 

I will try both of these.

 

No luck.

 

Worth noting that Kontakt 7 is VST3 only, I had this issue first in Kontakt 6 when I mistakenly installed the VST3, but blacklisting the VST3 and forcing the VST2 to load solved it until Kontakt 7 was released. Did you already try downgrading to VST2 Kontakt 6?

 

Kontakt 7 Portable has a VST2 version as well as VST3. Both cause dropouts, but at different spots.

 

This is an issue that appears with Kontakt in some versions and affects multiple DAWs. For me (using 6 non portable version) it was fixed using the vst2 version instead of vst3 (to do this in studio one you will have to add an ".unused" to the vst3 file or delete it beacuse both versions use the same ID and S1 detects them as the same thing). I haven't tried Kontakt 7 yet tho.

 

Kontakt 7 is officially VST3 only, so running the portable unofficial VST2 version isn't the most reliable way to test it. The problematic code was most likely just imported from the VST3 version into the unofficial VST2 version.

 

I'm running Studio One v4.6.2.xxx, Kontakt Portable v6.7.1 vkD, and have my libraries on an SSD and have had zero issues.
I only weigh in with this comment so I can now go the puritanical route of those who have become burnt by years of Microsoft use and suggest that you blame Win10 for all your issues... including that persistent rash you have.

 

I guess downgrading to Kontakt 6 is the way to go, unfortunately. A shame, cause some libraries I like to experiment with are for 7. Plus I will probably spend some time redownloading the ones i batch saved. Better than spending time trying to fix this tbh.

 

I downgraded to Kontakt 6 vst2 and Studio One 5.4 and it really did solve the issue. I'm getting zero audio dropouts now.

 

Downgrading Studio One shouldn't really influence that, it's really a problem with Kontakt VST3 that very few people seem to be aware. I think the only reason a SSD fix the issue is that it might brute-force Kontakt by being too fast to cause dropouts.

 

I will test how Kontakt 6 is faring in Studio One 6. Studio One 5 and 6 work without needing to uninstall the other.

 

Yup, Kontakt 7 is definitely the problem.