Menu
What's new
By:
Filters

Cinematic Studio Strings v1.7 - Available August 30!

Had no idea this was in the works, and just stumbled on this thread. Then watched the 1.7 video.

HOLY SMOKES Alex… you have taken the easiest-to-use, best bang-for-the-buck, jaw-dropping string library to new heights. And am I seeing right that this is a FREE update?!? You’re a crazy man. Simply unbelievable. Huge thanks for all your hard work… you have changed the game. Again.

Can’t wait to download the new version!
 
Alex W said:
Yep, we opted to disable purchases temporarily so we don't get anyone purchasing the original version now, only to have to re-install the new version in another day or two. :)
Click to expand...
Coincidentally I had the strings in my shopping cart last night -- tab still open! Very much look forward to it!
 
Thank you for updating this, Alex! Critical post incoming, so I would like to clarify that I'm very happy for this update and appreciate your hard work to make this happen 🙂

With that said, I'm not totally on board with your philosophy regarding the pitch bend questions here. Why isn't this an option in the instruments? Who cares that it didn't sound realistic? Anything using pitch bend rarely sounds realistic anyways. It would not break your back adding a button to turn this on and off. Several of my other libraries also suffers from this over-clean approach, and a lot of others thankfully don't, which are the ones I often end up using, since it allows me freedom to do what I want without having to dive into the Kontakt wrench rabbit hole (which I can't do at all in my current version of CSS). Sometimes sounds like a crappy 80s synth? Sure does, but if that was what I wanted that day, then it's great. Options, that's all I'm asking for.
 
Where are you all listening to demos and watching a video on it? I don't see a video anywhere. Were all of the CSS demos remade with the updated library?
 
@Alex W congratulations on the update, I'm really impressed by what I've been able to hear from the demos so far.

Considering the style I write in, the possibility to write legato lines without vibrato is really huge. And seeing what you were able to achieve with the new marcato version using only clever scripting and no new samples felt incredibly inspiring!

I have a question: will the 1.7 version of CSS occupy around the same amount of room on SSD? Of course I'm not talking about additional MBs, but GBs could matter in my case. Thank you in advance!
 
This is very exciting and great job on the update! I'm looking forward to the low latency legato which would mean less time tweaking. Will the delay compensation remain the same with the legato and sustains patches?
 
So first of all, this sounds absolutely awesome and I'm immensely thankful to get such an update for free. CSS is easily the single best investment I've made and this update is only going to further cement that.

Question, though - can 1.7 coexist in a project alongside other instances of old (present) CSS? Currently deep into a project that would massively benefit from those 1.7 marcatos but I'm not entirely fancying reprogramming the whole thing :rofl:
 
David Chappell said:
So first of all, this sounds absolutely awesome and I'm immensely thankful to get such an update for free. CSS is easily the single best investment I've made and this update is only going to further cement that.

Question, though - can 1.7 coexist in a project alongside other instances of old (present) CSS? Currently deep into a project that would massively benefit from those 1.7 marcatos but I'm not entirely fancying reprogramming the whole thing :rofl:
Click to expand...
Probably not possible with NI
 
Alex W said:
Hi there, low-latency legato is basically just the same concept as what's already there, except with less delay. I first introduced this in CSW, except I've improved the realism since then, and all of the other libraries (including CSW) will see the same improvements when they get their own "v1.7" release.
Click to expand...
So low latency mode still has variable delay times based on velocity? Or all they all the same time now?

Either way is fine, as long as there’s consistency so there is still the ability to use negative track delay and quantize, once the velocity of the notes is set to a fixed value (ie, set to 70 for medium, 105 for fast, etc).
 
Quick question.
Are the legato transition delays for the 3 different transitions in the new expressive mode the same as in the previous version advanced mode?
Currently mostly work with the advanced legato and have a macro in Cubase which sets back the 3 different legato transitions at once according to their velocity so if they are the same delays that would make for an easy transition although I’m curious about the low latency mode as well!

Also, are all the keyswitches the same in this version?

Thanks
 
Last edited:
Alex W said:
the new version of CSS is not compatible with any DAW projects saved prior to updating. To open those projects, you will need to back up the original version of CSS before updating - more info on that below.
Click to expand...
Is it possible to copy the resource and instrument files and have them reference the same samples, or have those changed significantly too?
 
Last edited:
whinecellar said:
Had no idea this was in the works, and just stumbled on this thread. Then watched the 1.7 video.

HOLY SMOKES Alex… you have taken the easiest-to-use, best bang-for-the-buck, jaw-dropping string library to new heights. And am I seeing right that this is a FREE update?!? You’re a crazy man. Simply unbelievable. Huge thanks for all your hard work… you have changed the game. Again.

Can’t wait to download the new version!
Click to expand...
This sums it up for me.

I've always found CSS to be the most consistently scripted and easiest to use string library in my drive.

Can't wait to download this update and try it out!

Thank you very much Alex!
 
Alex W said:
Honestly, this is the first library we've released via Native Access, so it's a bit of a learning curve for us too. I know that the process that I've outlined will work, but I can't guarantee the success of your option there, sorry!
Click to expand...
Thank you for the great update! :)
About Native Access: I'm a bit worried about it: the installation always requires a lot of free GB on the main HD, otherwise the library cannot be downloaded.
 
I’m hoping this update will finally get me to use CSS. Lol. The over the top vibrato really put me off using them, and not thrilled with tone. So if these two things got an upgrade, I’ll be happy to try them again.
 
micrologus said:
Thank you for the great update! :)
About Native Access: I'm a bit worried about it: the installation always requires a lot of free GB on the main HD, otherwise the library cannot be downloaded.
Click to expand...
Yes!!!! I recently had the exact same issue. I’m hoping this is not the case because I really can’t make much more room.
 
jaketanner said:
I’m hoping this update will finally get me to use CSS. Lol. The over the top vibrato really put me off using them, and not thrilled with tone. So if these two things got an upgrade, I’ll be happy to try them again.
Click to expand...
Afaik the vib amount is the same, but the sometimes too intense vibrato can be controlled by avoiding the most intense cc1 and vibrato levels. (CSS has a dedicated CC for vibrato).
 
You must log in or register to reply here.
Top Bottom