What's new

Cinematic Studio Strings 1.7 - audio examples and general discussion

Ok. Finally had a chance to properly sit down and play with it.

Nothing particularly polished, but had a play with a lot of the new features. The new mixing opportunities are excellent. You can bring a lot more focus to an ostinato with those spot mics.

Maybe too much focus. Dunno. Just playing. ;)

This also has a touch of seventh heaven over the top of it and some eq.

View attachment StringActionThing.mp3
 
Ok. Finally had a chance to properly sit down and play with it.

Nothing particularly polished, but had a play with a lot of the new features. The new mixing opportunities are excellent. You can bring a lot more focus to an ostinato with those spot mics.

Maybe too much focus. Dunno. Just playing. ;)

This also has a touch of seventh heaven over the top of it and some eq.
Great work!
 
Fantastic!
Ok. Finally had a chance to properly sit down and play with it.

Nothing particularly polished, but had a play with a lot of the new features. The new mixing opportunities are excellent. You can bring a lot more focus to an ostinato with those spot mics.

Maybe too much focus. Dunno. Just playing. ;)

This also has a touch of seventh heaven over the top of it and some eq.
it sounds very elegant!
I hope it will be apropriate to kindly ask you upload your midi file
i would like to analyze it!!!
 
I agree. Unfortunately, I notice it too. Slow legato is not so smooth in the new version.
Since some of you have posted comments like that: instead of needing to find the best way to keep 1.6 after having installed 1.7, it would be great if this could be solved in a different way.

I certainly want to install 1.7 due to all the goodies, but also want the option to use the 'legacy legato', if it's correct that it offered something for slow passages which 1.7 doesn't – or at least doesn't do in the same way as we are used to. Would it be possible to an extra legato preset in a not-too-distant future? That would solve a lot of problems (eg less need to juggle between two versions with all that implies). I wouldn't at all mind if this was done with the new version of the samples, so no need to keep the samples from 1.7 and earlier.

This isn't only about CSS – I've seen similar situations with other libraries as well, which also could be solved by keeping (recreating) the legacy/previous version as an extra preset.

Maybe the same could be done for those who also want access to the layered spiccatto/staccato articulation from earlier versions.
 
Since some of you have posted comments like that: instead of needing to find the best way to keep 1.6 after having installed 1.7, it would be great if this could be solved in a different way.

I certainly want to install 1.7 due to all the goodies, but also want the option to use the 'legacy legato', if it's correct that it offered something for slow passages which 1.7 doesn't – or at least doesn't do in the same way as we are used to. Would it be possible to an extra legato preset in a not-too-distant future? That would solve a lot of problems (eg less need to juggle between two versions with all that implies). I wouldn't at all mind if this was done with the new version of the samples, so no need to keep the samples from 1.7 and earlier.

This isn't only about CSS – I've seen similar situations with other libraries as well, which also could be solved by keeping (recreating) the legacy/previous version as an extra preset.

Maybe the same could be done for those who also want access to the layered spiccatto/staccato articulation from earlier versions.
As far as I understand, it's not a matter of simply having different legato scripting but the samples itself have been edited and processed differently (including the denoising of the main and room mics).

So, you'd probably need a lot of duplicate samples to get the old legato back which would then bloat the library size on disk further which isn't practical either.
 
If not tried yet I'd recommend to call the provider and let them reset the connection. That can resolve speed issues. Mine was ridiculously slow. After a robot reset the connection it was as fast as it gets all the time.
I live in the middle of the forest, I have a 4G connection with an external antenna, so 30mbps at night is the best I can get (from my 200mbps connection)
 
I wouldn't at all mind if this was done with the new version of the samples, so no need to keep the samples from 1.7 and earlier.
so, in essence, you get a new and better library free of charge, and now you want them to spend extra time assembling the old and the new into a hybrid because it's more convenient for you. Although there is an easy workaround to have both? :shocked:
 
I'm only asking if the idea I mentioned is a possible option for the future, babylonwaves. I certainly didn't expect them to offer all they did with 1.7 in a free update, and I don't expect them to do anything for free – or paid – just because it would be more convenient for some of us.

Edit: when we add legacy or other former versions of stuff for reason like that (they already take up some space on my main drive), workarounds aren't always that easy, but again: I don't (and didn't) expect any of this.
 
Last edited:
Ok. Finally had a chance to properly sit down and play with it.

Nothing particularly polished, but had a play with a lot of the new features. The new mixing opportunities are excellent. You can bring a lot more focus to an ostinato with those spot mics.

Maybe too much focus. Dunno. Just playing. ;)

This also has a touch of seventh heaven over the top of it and some eq.
This is awesome!
 
It seems I'm unable to add to Kontakt after I've added the new one. It keeps looking for the new one and says it's not the right library when trying to add the old one. Doesn't even work with the backup where I'm fairly certain I didn't do anything except copying it to that place. It also has the nicnt file.
Would be pretty burned if I'd want to go back to the old now.

I managed put the nkis of the old version in the instrument folder of the new version into a folder called "old css". Then resaved those when showing the missing samples notification but with the samples of the old version, in a different location.

Seems to work now, the new version loads its own samples and the old patches load the samples from a different direction.

However it doesn't work when recalling projects because it looks for the old nkis which are away in the "old css" folder.
But it also doesn't work when putting them in the normal instrument folder so they are in the expected place and the new version in a "new css" folder because Kontakt still looks for the files in the folder that is added to Native Access. Maybe I'll try putting the old samples into the new folder to resolve this but I'm tired of experimenting and everything I do seems to break things further.

Well, at least it seems to work for creating new projects. In all old projects I'll have to relocate the files with the missing samples bubble :(
Since I can't add the old version anymore I can't do it the other way around and keep the new versions in a dedicated folder instead while keeping the old one intact.
 
I really love this smooth slow legato in Advanced mode in version 1.5, especially on low and medium dynamic range. Melodic phrases with it are very noticeably expressive not only for long but also for short notes (fast performance in slow legato mode worked). There in legato, at the level of refinement, there was no need to change anything in script programming, it was perfect. Absolutely satisfied with the sound in the new version, but now it seems that this expressive performance with a slow legato for medium and moderately fast performance intensity has disappeared (this is not related to sound and hissing). In version 1.7, it feels like legato has started to be left out. As soon as you exceed some limit in the speed of performance, in the slow legato mode, the intervals begin to sink a little or shut up, not to reveal themselves completely in their singing.

CSS 1.5 Legato Speed Slow
View attachment CSS 1.5 legato slow_01.mp3
CSS 1.7 Legato Speed Slow
View attachment CSS 1.7 legato slow_01.mp3

There is a suspicion that something is broken in the script and this should not be the case.

CSS 1.5 Legato Speed Slow
View attachment CSS 1.5 legato slow_02.mp3
CSS 1.7 Legato Speed Slow
View attachment CSS 1.7 legato slow_02.mp3

Edit:
And so, using the sustain pedal(CC 64), this unpleasant glitch with the break of legato disappears. But as soon as the pedal is turned off, the legato breaks again, only in places of faster performance. I hope @Alex W can fix it. Since the slow legato itself seems to work well, but only with a sustain pedal.

CSS 1.7 Legato Speed Slow + pedal sustain(CC 64)
View attachment CSS 1.7 legato slow_02+sus pedal.mp3
 
Last edited:
I've been downloading for 12 hours now and I still have 6½ to go :)
Damn... I feel so privileged now to download it in 20mn with my 2Gbps Fiber, I almost forgot what it was on slow lines.

I wish everyone could access to fast internet, it makes not only life easier, but it opens the door to more connectivity, more streaming, more download, all that in the same time. I very often watch something in streaming while downloading libraries, while someone else might be playing games and the internet doesn't move the needle, it's rock solid... It definitely changed my life since I'm 24/7 on the internet. And luckily internet here in France is quite cheap in comparison to what I was paying the US... it's like 40 or 45 bucks a month for the 2Gbps Fiber. As said, I feel very privileged.
 
I really love this smooth slow legato in Advanced mode in version 1.5, especially on low and medium dynamic range. Melodic phrases with it are very noticeably expressive not only for long but also for short notes (fast performance in slow legato mode worked). There in legato, at the level of refinement, there was no need to change anything in script programming, it was perfect. Absolutely satisfied with the sound in the new version, but now it seems that this expressive performance with a slow legato for medium and moderately fast performance intensity has disappeared (this is not related to sound and hissing). In version 1.7, it feels like legato has started to be left out. As soon as you exceed some limit in the speed of performance, in the slow legato mode, the intervals begin to sink a little or shut up, not to reveal themselves completely in their singing.

CSS 1.5 Legato Speed Slow
View attachment CSS 1.5 legato slow_01.mp3
CSS 1.7 Legato Speed Slow
View attachment CSS 1.7 legato slow_01.mp3

There is a suspicion that something is broken in the script and this should not be the case.

CSS 1.5 Legato Speed Slow
View attachment CSS 1.5 legato slow_02.mp3
CSS 1.7 Legato Speed Slow
View attachment CSS 1.7 legato slow_02.mp3
Very strange. I played in the same lines to 1.7 and didn't have that issue (tried all possible variations of the legato at all speeds and dynamic layers.)

But I certainly agree that the legato in the recording you uploaded definitely isn't cutting the mustard.

I wonder what's causing it. 🤷‍♂️
 
Top Bottom