Spitfire Solo Strings will be released July 12th

[Muziksculp]

Spitfire Solo Strings will be released July 12th !

[Guy Rowland]

Finally got round to listening to this - legato transitions sound very good, the vibrato sounds just like an on/off switch sadly. But there are some progressive vibrato patches elsewhere which should help here, albeit baked in.

I'm one foot on the fence still, mostly because it's not a bad deal to upgrade from the original SSS (anyone know how long that runs for?). It won't outshine Bohemian for front and centre, but as a replacement to the old library which is far more complete than it was, then it has a place I guess.

[playz123]

Guy...from Spitfire:
"Spitfire Solo Strings is now available to pre-order, and will be released on 12th July 2018.

Based on your commitment to the original Solo Strings, we would like to offer you an extended loyalty discount of over 50% during the promotion period, and 37% off the RRP thereafter. Spitfire Solo Strings will be available on promotional price until 26th July 2018 at 23:59 BST. Just add Spitfire Solo Strings to your cart, and it will intelligently calculate your crossgrade. Be sure to login first."

So you still have more time to decide.

[Scoredog]

I just chatted with SF and they said there is user controlled vibrato for legato patches. there will be further vids coming.

[Guy Rowland]

Thanks Frank.

Scoredog - well he was playing with the vib fader and it switched on and off, wonder if its still a work in progress?

[Lawrence]

Well, on and off is user control. Just sayin’

[Guy Rowland]

Well, on and off is user control. Just sayin’

Ha, yes indeed! SSS had some beta patches that switched and they were just awful, unplayable. What that demo shows is that its waaaay smoother than that at least, even though it's very limited in how you can use it.

To be fair, it's exceptionally difficult to get a smooth vibrato crossfade without phasing and what not, unless the vibrato is fake (and I hate all the fake vibratos that I've heard). In fact, LASS FC is as playable as anything I've heard on the modwheel, but the vibrato only ever gets fairly tame in keeping with its intended purpose of first chairs, not solo instruments.

[Lawrence]

I have often wished for vibrato control of LASS FC.

[Lawrence]

So-out at an introductory $339. Spitfire pricing seems to be getting more competitive. I’m curious to hear some user demos. (hint)

[Killiard]

I just bought it a second ago. I probably won’t have time to play it much today though...

[Lawrence]

Hey, tomorrow is fine

[Killiard]

First impressions are that it sounds nice 'n' all that. I'm not too keen on some of the loop points on the long notes - they're a bit too short/loud. I'll post examples when I get a chance. The vibrato crossover aint too subtle either. Sometimes i think it's ok and sometimes it feels quite abrupt.

[Killiard]

If anyone wants to hear it do something specific then let me know.

[Guy Rowland]

You've mentioned mine already Jordan, hearing those vibrato transitions, though TBH I'm not expecting it to be useful mid-note, more of a keyswitch for use between notes. And on that - how possible is to integrate the baked in vibrato arcs with a legato patch? Or do you need to have 2 patches and switch between them?

[Killiard]

Exhibit A - Funny loops on Viola Legato

https://www.dropbox.com/s/gpdzseir7868x ... s.wav?dl=0

The last note I play is a D4 at about 5-6 seconds the loop points seem to be about every 2-3 secs!. I played the same thing in CSSS and it was sounding a lot better.

[Killiard]

Hmm...Haven't tried doing anyting with the baked in vibrato arc. I think that's just a patch on the longs? Unless I've misunderstood you.

[Guy Rowland]

Will listen when I’m back at base shortly to the looping. Yes, might just be the longs in which case that’s a big big negative for me. I want a legato patch with the ability to have progressive vibrato, if it’s not possible to cross fade with a CC.

[Guy Rowland]

Just listened to the loop point - yes, not great.

So back to the vibrato issue - there are 3 different violins, right? Do they all have different vibrato intensities? And none of them have progressive baked in vibrato on legato patches? As for the other four instruments, I'm guessing they're all on/off vib of a single intensity for their legatos?

[Killiard]

Sorry, been out all day.
Three different violins, yes. But only one violin legato patch. If I get a chance I’ll maybe do a quick vibrato comparison.

There’s no progressive legato patch, no. The legato violin is the first chair.
The only progressive patch is the “progressive longs” patch that all three violins have.

[Guy Rowland]

Thanks Jordan, think that counts me out.

[Muziksculp]

Hi,

For those who bought this library, there are users reporting that Kontakt 5.8.1 crashes when doing a batch-resave, once it gets to re-save the Viola Economic Patch.

Also reported by a user on another forum, that There are three patches in the "_Advanced_/Other patches" folder that will cause Kontakt to crash -- either loading or doing a batch resave. The three NKI's to avoid are: (1) b - Violin (1st Desk) - Economic; (2) d - Viola - Economic; and (3) e - Cello - Economic.

Hopefully Spitfire Audio will issue a fix update soon.

Anyone here experience any of these issues with this library ?

Thanks,
Muziksculp

[tack]

I'm waiting for user reviews before deciding if I want to buy it so I can't comment on the issues, but if Kontakt is crashing on a batch resave, I hope more that NI fixes the issue than Spitfire.

(Though Spitfire can likely implement a workaround of the Kontakt bug quicker.)

[playz123]

Several years ago, for awhile Spitfire libraries crashing Kontakt during batch resave became a regular occurence for me. When I reported the problem to Spitfire, Blake contacted me and ask for assitance to help him solve the problem that others were having as well. After back and forth correspondence and tests, he eventually found out what was happening on their end and fixed the problem. After that it never happened again for me, and yet I had really done nothing on my end. So I expect Spitfire may be able to quickly figure out what is wrong this time, and offer a fix. I also recall that file names caused a problem previously, but have no idea if that is the case this time. Therefore, I for one am reluctant to blame Kontakt directly right now, and will wait and see what Spitfire does first.

[tack]

Therefore, I for one am reluctant to blame Kontakt directly right now, and will wait and see what Spitfire does first.

If Kontakt is crashing, Kontakt has a bug that needs to be fixed. Spitfire's patches may be doing something wonky, or even if not may be able to work around the issue, but fundamentally Kontakt as a platform shouldn't crash by something done by a patch.

It's a bit like if you opened a text editor and Windows bluescreened: the right thing to blame is Windows, not the text editor.

[Guy Rowland]

I agree Jason, but pragmatically if 99% of your patches dont crash, it’s not unreasonable to expect the developer can sort the patches that are crashing. If, say, the crash was because of a mis-named sample, it’s Kontakt’s fault that this results in a crash, but entirely fixable by Spitfire.