Cinematic Studio Solo Strings cutting off when exporting in FL Studio 20

947th · 2022-11-07T11:49:45+00:00

There was an error rendering this rich post.

I tried a number of different ways to fix it. It's not related to the Kontakt version, DAW, or export settings. "Notify rendering mode" is on and I've tried changing the instrument preload size. All other libraries export normally except for the ensemble patch in CSS.

Find more posts tagged with

Bug

FL Studio

Accepted answers

947th

https://community.native-instruments.com/discussion/comment/39117#Comment_39117

Hi Jeremy, I just figured out it was related to the hard drive. I moved it from a HDD to an SSD and that seemed to fix the problem 😅. However, there's still some minor issues like short freeze-glitches during playback, and sound not playing sometimes from the start. Would this be CPU related? I have an i5-11400F. The hiccups occur when playing large chords with the ensemble patch.

All comments

solsta

Hmmm I wonder if this was the same thing I used to experience with acton strings.

whenever I loaded the project on my old machine, if it was not fully loaded internally (it has this loading bar when you load the plugin0

then I would find that my audio was "incomplete" like the strings cut off and didn't sustain properly and it was because somehow the instrument was being rendered out as audio while not fully loaded itself, so you could try make sure all the notes are playable and instrument is able to play all notes then try export again,

sorry if this isn't what you meant, but I did experience something similar and my processor not loading the instrument quickly enough turned out to be the problem that I had specifically

947th

No, sorry. The library plays perfectly, the problem is only when exporting. Thanks for replying.

Jeremy_NI

Is this library installed on an external hard drive ? What format is that drive? Does it make a difference if you select a different sample rate when exporting?

947th

https://community.native-instruments.com/discussion/comment/39117#Comment_39117

Jeremy_NI

What's the format of the drive?

Have you checked this article? How Can I Optimize the Performance of KONTAKT?

In some cases batch re-saving the library can improve performance: How to Batch re-save a KONTAKT Library

inha

Any updates on this? I use another DAW but note dropouts and cuts (especially during render) seems to be a common issue on Kontakt 6/7 + Cinematic instruments. Super frustrating issue.

Jeremy_NI

@inha If you check the thread, OP has found the solution to this issue. Maybe you can give us more details? What DAW are you using, what operating system? Audio settings? Are your libraries installed on an external hard drive? What's the format?

inha

I'm using Windows 11 home + Presonus Studio One 6 Pro. I use a Scarlett with Focusrite USB.

Initially I assumed it's a DAW problem and have been in contact with Presonus about it, but further googling revealed it seems to be relatively common problem specifically with the Cinematic Kontakt instruments in spite of DAW. You can find a whole bunch of discussions about this specific problem starting 2022 across the webs by googling.

All my Kontakt libraries are on an external drive (NTFS) and I'm unable to move them to internal SSD. However, I am slightly skeptical about that being the only cause, solely because I have not experienced this problem before with any other Kontakt instruments, ever, and still don't, while all my libraries have always been on the same external drive. It's a regular HDD but all my ports and cables are SuperSpeed! I'm experiencing this problem solely with Cremona Quartet instruments.

Usually problem occurs only when bouncing/rendering, does not occur on playback unless you really, truly try.
Usually problem occurs when playing long notes, and even more if playing long chords (which is rather logical, since the same period of time has 3-4 times more notes to drop if it's all chords).
Just emphasizing that seeminly random notes drop even when rendering a "monophonic" track, albeit not as often. It does not matter how many simultaneous notes are in the section, some drop out anyway.
Notes that drop are not entirely static. Often times rebouncing/re-rendering the track fixes the problem (except for Stratovardi Cello, which is the worst), or, some new notes may drop out instead.
Sometimes you can replicate the same note dropouts in playback if you try hard enough, for example, play/loop only the notes that will drop and the notes before that; now suddenly some notes are not playing either.
If you have Kontakt with its keyboard open and visible, you can observe during render that the dropout-notes are not being "pressed" at all on the Kontakt keyboard while rendering. You see only some key or keys "pressed" of a full chord.

As already stated, problem occurs with all the Cremona instruments, and so far for me Stratovardi Cello is the worst by far.

Currently the only way I can bounce/render Stratovardi Cello is to explode pitches to their own tracks, and add a new Kontakt instance with the same instrument to each one and do a few bounces. Those tracks will instantly bounce 20x more correctly than when trying to render long chords with a single Kontakt instance.

Dude in another forum is blaming the problem on "loop xfades".

Another DAW developer says "On my 10-core Mac M1 configuration, Kontakt 7 (VST3) drops many notes if processed with five or more parallel threads at 100% CPU. That's five cores, each running a different instance of Kontakt, bouncing without pause. One, two, or three parallel threads don't seem to reproduce the problem."

May I ask what is the minimum disk read speed requirement for Cremona Quartet instruments? That's something I can improve, probably.

Jeremy_NI

@inha I've contacted you by email and I'll forward your case to one of our Kontakt specialist.

Wayne.Liu

Hello Inha! May I ask have you fix this problem? I met same problem with you, if you fix, could you please tell me how did you solve it?

Quick links

Unanswered questions