constaneum
Senior Member
I've loaded the script (i'm using FL Studio) but the script doesnt seem to do anything? Did i miss out anything or it doesnt work with FL studio ?
CSS (Cinematic Studios) Control Panel - CSS/CSSS/CSB/CSW legato delay solution + other features (1.8, now with Winds!)
- Thread starter Ihnoc
- Start date
OP
OP
Ihnoc
Active Member
- Have you got CC13 up above 64 (the delay CC)?
- Are you switching articulations with CC58 (default keyswitch CC)?
Henu
Dismember
I have a question as well, if anyone can answer this: Using Cubase 9.5, everything went very smoothly...except for articulation switching.
Due to my track being now delayed negatively for that 300ms, the Kontakt script won't obviously move my articulation switches when using them through the expression map I have made. I also tried with plain midi CC information, but naturally it failed as well. Using keyswitched articulations would move them according to the script, but the script isn't supporting them.
This makes the wonderful script pretty much unusable for me, as I often tend to switch articulations quite rapidly depending on the passage. Am I missing something obvious here or how do people work around with this problem?
Due to my track being now delayed negatively for that 300ms, the Kontakt script won't obviously move my articulation switches when using them through the expression map I have made. I also tried with plain midi CC information, but naturally it failed as well. Using keyswitched articulations would move them according to the script, but the script isn't supporting them.
This makes the wonderful script pretty much unusable for me, as I often tend to switch articulations quite rapidly depending on the passage. Am I missing something obvious here or how do people work around with this problem?
OP
OP
Ihnoc
Active Member
If you are using the negative track delay in Cubase, all of the midi data, including the expression maps and the subsequent MIDI CC or notes, will also trigger earlier by that delay. The script also doesn't delay keyswitches and the keyswitch CC for music performance reasons, so I am unclear why you would stuggle with this.
However, I have been asked for Keyswitch support and it is on my list to do. Most of the work is in the UI as there are already loads of things to show in the tiny KSP window. I will see what I can do.
Henu
Dismember
Yes, that is obviously true. But as you say in the instructions,
...I am unclear why I'd not struggle with this problem.
Or am I just being stupid now?`
If I offset the track delay using this script, all the notes are now perfectly aligned but the expression maps and all subsequent midi CC data is naturally now 300 ms ahead. Do I need then to align my articulation switching 300 ms before the actual place by hand each time, or is there another solution which I just don't understand for some reason?
...I am unclear why I'd not struggle with this problem.
Or am I just being stupid now?`If I offset the track delay using this script, all the notes are now perfectly aligned but the expression maps and all subsequent midi CC data is naturally now 300 ms ahead. Do I need then to align my articulation switching 300 ms before the actual place by hand each time, or is there another solution which I just don't understand for some reason?
OP
OP
Ihnoc
Active Member
Yes, that is obviously true. But as you say in the instructions,
...I am unclear why I'd not struggle with this problem.
If I offset the track delay using this script, all the notes are now perfectly aligned but the expression maps and all subsequent midi CC data is naturally now 300 ms ahead. Do I need then to align my articulation switching 300 ms before the actual place by hand each time, or is there another solution which I just don't understand for some reason?
No stupidity. Are getting this when playing notes and keyswitches in, or just playing keyswitches in on already recorded phrases, or just playback of notes and phrases?
constaneum
Senior Member
Pardon my noobness. I have to set CC13 above 64 or less than that? I'm switching articulations using keyswitch CC
OP
OP
Ihnoc
Active Member
Sounds like what you want is to delay the articulation changes as well then. That's not an outrageous request and I've wondered whether it is a good idea. I will have a think about this as I adjust the script.
OP
OP
Ihnoc
Active Member
Thanks and please don't hesitate to ask.
The Delay CC (by default CC13) should be above 64 to engage the script's delay. If you are sending CC (13 and 58) to Kontakt, then the script should also be picking up those changes as well.
The best way to test whether things are working is to set CC13 to 0, set CC58 to Spicatto (11 I believe), then play some chords. The response should be immediate (the delay is bypassed). Then turn CC13 up to full and play again. The response should feel like a quarter note delay.
Also check that the MIDI channel that you are sending the CC to is set correctly in the script. The default is 1, but if your CSS instrument is on a different channel, then the script will ignore the MIDI. This is so the script only affects one channel at a time (and doesn't mess with other playback).
constaneum
Senior Member
Thanks man !
OP
OP
Ihnoc
Active Member
Update 1.5
- Script now supports keyswitches as a method of input, along with keyswitch CC or any combination. Keyswitches can be moved in octaves, set to CSS defaults or changed individually
- Updated UI with tabs to provide help, add more functions (like keyswitches) and make customisation easier
- Added auto-rebow feature for legato (regardless whether delay is on or not)
- Further improved timing of articulation switching when seeking and on articulations that trigger at the same time as a note
Henu
Dismember
EDIT: Sorry, I was too early celebrating. :/ I thought the articulations were now also delayed at first, but then after trying out some more faster switchings, I noticed they weren't. But if you can do that- and if it's not too hard, of course- I bet I'm not the only who would be really glad about it! 
Last edited:
Thanks for sharing this, but I'm finding it a little... temperamental. I had it up and running perfectly in a Pro Tools session this morning, but it seems to have bugged for me along the way. Now it only seems to offset by the fast speed when playing anything legato, regardless of the note velocities. The shorts all seem to work fine though.
I'm thinking that this is mostly likely some pilot error on my end, because for one glorious fleeting moment it worked beautifully. Any ideas?
I'm thinking that this is mostly likely some pilot error on my end, because for one glorious fleeting moment it worked beautifully. Any ideas?
OP
OP
Ihnoc
Active Member
That's literally the opposite of what 1.5 should be doing now. Are you using just keyswitches or just CC58? Also please look at the script while legato and staccato passages are playing. What does the script say it is doing?
Tempermental is certainly a word I would use for this whole script; it is more often the script thinking you are doing something else, rather than user error.
drymcore_music
New Member
I have a question: what happens with the first note in a legato line? The delay of those notes are not delayed so much as the transitions, but i guess i have to either:
- move them so they are on the grid OR
- use CC13 to disable the script for the first note, then re-enable it before the next note (now a legato transition) starts
or do i miss something here?
(did not try the script yet, but will soon)
- move them so they are on the grid OR
- use CC13 to disable the script for the first note, then re-enable it before the next note (now a legato transition) starts
or do i miss something here?
(did not try the script yet, but will soon)
+1
Would make so much more sense if the first long note is in sync with the grid!
I've tried using both keyswitches and CC58, with both the script gives the message "Playing advanced sustain note with delay of 100 (or whatever I set the fast legato value to), legato phrase length: 0".
Staccato passage all show the same message, and appear to also use the fast legato times.
Keyswitches and CC58 both give articulation updated messages though.
I'll keep digging on my end though, and let you know if I find anything.
Edit: Just got a script warning in Kontakt that reads "SCRIPT WARNING (Line 1065, Script 0): wront time parameter in wait statement!."
OP
OP
Ihnoc
Active Member
The first note in any legato phrase is offset by the same amount as fast legato (and sustains/marcato/trills/harmonics) which by default is 100ms, which sounded right to my ears. As far as I can tell it just plays a sustain note at the beginning.
So the first note in legato phrases is offset relative to the slow legato, like everything else. You should not have to move the first note, and keeping CC13 up all the time will offset everything correctly.
OP
OP
Ihnoc
Active Member
Could I ask you to PM me your script settings? While it is not impossible to get this error in theory, I have never encountered it with the default settings.
