Menu
What's new
By:
Filters

CSS (Cinematic Studios) Control Panel - CSS/CSSS/CSB/CSW legato delay solution + other features (1.8, now with Winds!)

Kent said:
I thought that the ‘start’ button was to enable the UI of the multiscript, not to enable its functionality. Does it not work that way for you?
Click to expand...
Hi, that is almost certainly the case actually and makes way more sense- I think I need to work on my ear skills for the delays - I have trouble interpreting which instruments are ahead or behind and separating the track delay from the scripts delay. So in summery, it’s me not the plug-in!
 
Hello, this is the first time I am trying this, I am on the latest FL studio version, and the KSP script tab show that a delay of 100 is applied for all my notes. But there's slow legato (portamento) and marcato notes, so it shouldn't stay at 100 for all the notes.

Anyone have an idea ?

1657395946378.png
 
I'd try adding keyswitch and maybe CC data at same time to communicate with it about what types of samples are occurring; see if that jolts it into action. The velocity data should do the rest in terms of the 3 legato lengths.

There's also the first note of a phrase issue where I think it has a different delay; I had to adjust those by ear /experiment with velocities.

For legatos too I started to use the CC to activate sustain pedal which helps with re-bowing repeated notes.

I don't remember the specific delays for each type of sample off hand so I'm not sure if it's supposed to be at 100 for those. Maybe to a test with just the 3 legato delays to see if it is adjusting for those. I've taken a break for a bit and have been using Noteperformer, but plan on circling back to practice more with all the CS libraries.
 
Dr Bensmir said:
Hello, this is the first time I am trying this, I am on the latest FL studio version, and the KSP script tab show that a delay of 100 is applied for all my notes. But there's slow legato (portamento) and marcato notes, so it shouldn't stay at 100 for all the notes.

Anyone have an idea ?

1657395946378.png
Click to expand...
The script is set up by default to use the keyswitches as they are set when you load the instrument. Possibly you have changed the keyswitches but not done the same in the script?

Alternatively, as mentioned in the release notes, certainly Cubase does not send two values for a CC in the same tick. If you are using Keyswitch CC (58 by default) to switch between Sustain and Marcato, and turn legato in and off with that CC too, try sending the Legato Keyswitch as well.
 
Dr Bensmir said:
Hello, this is the first time I am trying this, I am on the latest FL studio version, and the KSP script tab show that a delay of 100 is applied for all my notes. But there's slow legato (portamento) and marcato notes, so it shouldn't stay at 100 for all the notes.

Anyone have an idea ?

1657395946378.png
Click to expand...
Hit all the right keyswitches at all the right velocities. I believe that's two switches needed, the Sustain articulation (C0 i believe?) and then the Legato is enabled by hitting A#1 (again, double check me, this is from memory.) That one is velocity sensitive.
 
PROBLEM SOLVED

Thanks for your help guys, turn out that FL Studio "C2" is actually "C0" so I wasn't hitting keyswitches in the right octave. I knew FL Studio had that thing.... but I never used keyswitches patches, only single articulation, so I forgot.
 
Does the script allow for switching between Marcato (40 ms) and Legato ? Within the same patch

1658150973987.png

And can you load the script only for specific midi channels within multi timbral kontakt ?

EDIT : oh? i just saw multi channel support by @img , just checking
 
Last edited:
No
Dr Bensmir said:
Does the script allow for switching between Marcato (40 ms) and Legato ? Within the same patch

1658150973987.png

And can you load the script only for specific midi channels within multi timbral kontakt ?

EDIT : oh? i just saw multi channel support by @img , just checking
Click to expand...
As long as you're triggering the proper keyswitch between articulations, it should work just fine
 
Marcato and Fast Legato have really different delay.
Fast legato (100 ms)
Marcato (40 or 60 ms)

Ihnoc, Thank you very much for the script! Is it possible to add different delays for Fast Leg. and Marcato, or is it impossible due to technical limitations?​

 
Last edited:
This diagram is from the official video for the Cinematic Studio Strings about legato. It is unclear why the Slow and Medium does not coincide with the manual, but the Marcato delay is less than the Fast legato.
2022-07-20_13-27-59.png



Anyway, I express my great gratitude to @Ihnoc for this amazing script. I am so excited that I can now easily and quickly control these great very realistic and expressive musical instruments.

It would be great to add an Auto Rebow Leg. button both in CSS for CSW and CSB. Accordingly, it would be an Auto Retonguing Leg. But even without this, everything works with CC64.
 
Hello,

(just to mention, I did not read all 26 pages, sorry if that has already been discussed)

I tried to use the script in Cubase and had the problem, that when I recorded something and
then played it back, the first note was offset as if it was within a legato phrase. For the recording I always set the Delay Control CC to 0 and back to 127 afterwards.

As far as I could figure out the problem for me was, that the legatoNoteCount in the script was increased, but not decreased when the CC was at 0. So I changed both occurrences of
Code: 
$legatoNoteCount := $legatoNoteCount + 1
$legatoNotePitch := $MIDI_BYTE_1
to
Code: 
if (($lastDelayCCValue > 64 and $delayMode = 0) or ($delayMode = 1))
    $legatoNoteCount := $legatoNoteCount + 1
    $legatoNotePitch := $MIDI_BYTE_1
end if
which worked for me to solve the problem. Not quite sure if the legateNotePitch assignment should be within the if statement aswell. Maybe @Ihnoc can say whether this makes sense or not? Just wanted to put this here in case anyone else has this problem.
 
Hello, first of all thank you for this script! It's been very useful for me.

I wanted to ask if the script will still work with the new version of CSS (1.7)? It seems as thought the Advanced legato has been renamed to Expressive mode but it is kept "100% intact" according to Alex Wallbank from his recent post about the update.

I think if that is the case only the Standard legato mode (which has been renamed to Low Latency legato) will be effected because there is an improving in timing. Am I right?
 
1+Humanity said:
Hello, first of all thank you for this script! It's been very useful for me.

I wanted to ask if the script will still work with the new version of CSS (1.7)? It seems as thought the Advanced legato has been renamed to Expressive mode but it is kept "100% intact" according to Alex Wallbank from his recent post about the update.

I think if that is the case only the Standard legato mode (which has been renamed to Low Latency legato) will be effected because there is an improving in timing. Am I right?
Click to expand...
I’m really afraid of updating to CSS 1.7
Time will tell….
 
sathyva said:
I’m really afraid of updating to CSS 1.7
Time will tell….
Click to expand...
I only use this multi-script with the advanced (now expressive) mode. The issue I ran into is that the key switch for the legato on/off used to be on A#0, but is now on G#0.

I'm not sure why that change was made, but you'll have to change the keyswitch for legato in the script.

From some quick tests it seems to be working fine with advanced/expressive.
 
tonaliszt said:
I only use this multi-script with the advanced (now expressive) mode. The issue I ran into is that the key switch for the legato on/off used to be on A#0, but is now on G#0.

I'm not sure why that change was made, but you'll have to change the keyswitch for legato in the script.

From some quick tests it seems to be working fine with advanced/expressive.
Click to expand...
You can also change the key switch in the CSS patch itself. Shift click on the Legato button to bring up the MIDI learn section. I reset everything back to A#0.
 
tonaliszt said:
I only use this multi-script with the advanced (now expressive) mode. The issue I ran into is that the key switch for the legato on/off used to be on A#0, but is now on G#0.

I'm not sure why that change was made, but you'll have to change the keyswitch for legato in the script.

From some quick tests it seems to be working fine with advanced/expressive.
Click to expand...
Thanks a lot !
sounds like it’s time for me tu update ;)
 
Thanks for the great tool!

But all of this just infuriates me to the point that I'm thinkng of dropping CS series altogether.

So here what is going on:

1. Don't use this and accept that I have to carefully move every note which is super tedious and off putting.

2. If I use this tool, I have to offset everything by 330 ms. That messes somehow with my expression map work or rather "musical variations" or whatever it's called in studio one. Negative offset messes with that so say I set "legato" to note B. Then whatever note A is played within 330 ms before note B is triggered with legato keyswitch. Basically variations are firing off early because of track delay. I haven't find a way to solve it..

3. For some reason this tool always start in "disabled" state. I have to go to every kontakt instance and click "start" button for this to work.

Despair.
 
You must log in or register to reply here.
Top Bottom