Hello,
I have a problem where Spitfire Studio Strings crashes Kontakt when selecting "Edit Mode". Kontakt version is 6.7.0. The same thing happened with Spitfire Studio Woodwinds and Spitfire Studio Brass. Any ideas?

 

Yes, with 6.7.0 and 6.7.1 in standalone mode too. I have to try Studio One, in CAUBASE crashed also.

 

Same here. Win10 Reaper Kontakt 6.7.1 portable.

 

Crashes w Kontakt-Spitfire-Sacconi strings - more RAM? SOLVED. yes, more RAM!
https://duc.avid.com/showthread.php?t=389492
.....................................................................................................
I am done with Spitfire Audio’s Labs.

I finally got Spitfire Audio Labs running reliably on my Windows 10 Reaper DAW today. The problem I was seeing was that Reaper would crash every time I tried to remove an instance of Spotfire Audio from a track. I had tried multiple restarts on the PC but that had no effect.

To fix it I did the following:
- download and install the newest version of Spitfire Audio App: 3.2.20
- reset my computer (this step may not have been necessary)
- run the Spitfire Audio app and allow it to update each of the individual "instruments" I had previously downloaded.

I'm now able to have multiple tracks with Spitfire Audio and I can remove and re-add instances of the VST. I played with it for a couple of hours and no Reaper crashes.

www.kvraudio.com/forum/viewtopic.php?t=564825&start=15

 

I don't think it's a RAM issue. The library only uses around 400 MB. The crash only happens on these 3 particular libraries, my other libraries work fine.

 

Hello @The_Pro, I agree with you, maybe this will help you:

Yes EvilDragon I´m in contact with Spitfire Audio. They don´t know what´s going on and we are trouble shooting. I have had a reply from NI support and deleted the KONTAKT 5 folder as well as the KONTAKT 5 prefs file and that seems to work for NEW projects that I create and load KONTAKT + Spitfire Audio libraries into. My OLD sessions crash in the same way as before. I´m hoping that at least I can create new projects and use PT from now on..

www.native-instruments.com/forum/threads/kontakt-crashes-with-spitfire-audio-libraries-in-pt12.343933/

 

Last edited: Apr 17, 2022

keep a Kontakt 6.6.1 if you want to edit instruments.
the regular 6.7.x versions don't enable to edit these instruments, it only launch instruments option. it is a bug.

i managed to get the editing part loading in 6.7.1

by saving instrument as monolith from 6.6.1, but it only worked 1 time. it revert to crash on a second opening.

i try to re enable the edit but it also crash now. something is wrong with these spitfire libraries.


the more simple is to use 6.6.1 to edit this stuff. untill spitfire or Ni correct the bug.
it seems to be related to long name issue + output surround 7.1.

 

Last edited: Apr 17, 2022

Hey there! @bobdule and @The_Pro

I seem to have a clue as to what's going on with some of these instruments.

I'm able to show that what's actually causing the crash are certain "Groups" in the group editor. Which is to say, simply clicking on certain groups in the group editor can reproduce the same crash, despite loading the instrument initially without a crash.

For example, with Spitfire Chamber Strings (which has the same issue), loading the base "c - Violas" nki patch, and selecting "Edit Instrument Mode" causes no crash. However, simply clicking on the "Major 6th" Legato Group in the Group Editor reproduces the crash every single time without fail.

Not sure if this helps.

Edit: In fact, I can show that the instruments that DO NOT crash in the same library, have reasonable Group names, like "rr2 sus p," in the case of the "f - Ensemble" base patch.

For whatever reason, for some of the instruments the developers added loooooonnnngg group names and comments, like for example:

"_________Major 3rd_______________________________#Normal Legato#"

(I subbed the spaces with underscore). That is legitimately how many spaces the programmer added to the name of the group.

Instruments that have these long group names full of spaces are susceptible to crashing.

Instruments that have reasonable shorthand group names don't crash, ever.

However, simply editing the group name and removing the spaces for one group alone doesn't seem to fix the issue.

I'm not knowledgeable enough about coding to know how to batch rename all the groups together to see if that fixes the issue...

 

Last edited: Jan 7, 2023

I was also experiencing the same issue with Spitfire Studio/Symphony series and found the following info:

Any patch that contains a legato articulation is locked by Spitfire. (i.e. the logo of edit mode is a cog instead of a wrench).
And, somehow, they managed to make Kontakt crash if the patch is being edited in an ''unofficial'' version of Kontakt. You'll find that patches that do not contain legato never crash.

This is weird, as some Studio/Symphony patches w/ legato don't seem to crash. I wonder if the findings of the user @eyotehgabagool has something to do with how this works.

Luckily, there are a myriad of longs/shorts/individual articulations patches in Spitfire libraries which means there is at least some form of workaround. I mean, at least until someone finds a solution :P