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:
Are you triggering with both cc and keyswitch? Sometimes it takes both to activate exactly how you want. I think there are a few posts in this thread about it.
Click to expand...
If by this you mean using the default keyswitch of C1 and 0-5, 6-10 in CC58, then yes. I've done both simultaneously.
 
Reoreyh said:
I'm at my wit's end with this stuff (CSS, not the script.) I've been tinkering with this here and there for the better part of a year now and I've honestly gotten nowhere. In no way can I develop any workflow with this product. Using Reaper, I absolutely 100% cannot under any circumstances go from a short to a sustain keyswitch. Not with CC58 or with an actual midi note keyswitch. Everything else works fine, but to go from a short to a long I need to find some sort of sweet spot by nudging it left to right. This takes an unreal amount of time and more often then not throws off the proceeding notes articulation.

Does this issue resemble a known or common bug or problem? I just don't understand how people are able to compose with CSS. It's like, if I want to NOT manually nudge every note in place, I have to manually nudge a keyswitch in place for each and every change.

EDIT: The script tells me it's playing a long with all the relevant offset and legato data, but the CSS Instance in Kontakt itself does not change from Staccato.
Click to expand...
Honestly, if CSS had some mode where delays are uniform across the board, similar to how Audio Imperia handles it, I'd have no issue with this library. I do wish more devs did that, because I've never been able to make this type of script work elegantly or consistently.
 
Reoreyh said:
If by this you mean using the default keyswitch of C1 and 0-5, 6-10 in CC58, then yes. I've done both simultaneously.
Click to expand...
Did you confirm the keyswitch octave? Default "sustain" keyswitch is C0 (note 24) unless you've changed it. Also, it's a known issue that with Kontakt a CC message and a note coming in at the exact same time could result in the CC coming just after the note leaving your note unaffected (assuming that CC was meant to change its articulation). It may be just a matter of pulling back your CC (or the program change if your using Reaticulate) to come slightly ahead of your note. It's hard to be sure about the exact issue you're having without seeing the MIDI your passing to CSS.

In the little I've done with CSS so far, I've never had to use both a keyswitch and its matching CC58 value to trigger some articulation. I settled on using solely CC58 since I usually have some multi script in place guaranteeing the CC would come first, but I think many would advise going all keyswitch so Kontakt can respond more predictably.

Shot-in-the-dark (as I've done this), make sure you haven't changed any keyswitches by mistake by leaving open (or opening) the keyswitch display during playback. It's in "learn" mode while its open, so it'll reassign the keyswitch of whatever articulation you shift-clicked to the first note it gets. That would break your articulation management, obviously.
 
does it support the 1.7 css update ? (150ms for low latency and 50ms for marcato

Why the marcato and fast legato are grouped ? even in 1.5 css marcato are 40 ms and fast leg are 100 ms
 
This script is super helpful, however the 1st note detection seems to only work for me some of the time. When it's not working, then it reads the first note as any other legato note, which messes with the timing and the attack. Does anyone have any tips on getting that to work properly? Do the KS need to be hit at a certain time/order?
 
It could have something to do with CC values and delays - I've had to be careful in general about when I create a CC change vs inserting note offsets (using Dorico), sometimes causes the note to start prior to the CC change because I didn't offset the CC as well.. Just one possibility that might be messing with order of midi info getting to the KSP script.
 
Hi,

in the attachment you'll find a script based on the one from @Ihnoc that I've written for myself. Note that the UI is quite different, it does not implement everything from the other script and it may also behave a bit differently. But it should work just fine with 1.7 (at least it does for me) and maybe it also helps with the Legato problem @infinitejester0?

Hope it also works well for you! Let me know if it does or doesn't or if you have any questions :)
 

Attachments

  • csscontrolpanel.txt
    47.4 KB · Views: 109
Last edited:
I noticed that it started behaving again after hitting Midi/Reset. So I think something about the script or CSS is holding the information of a note, and therefore all the first notes read as being legato from something else.
 
Dot said:
Hi,

in the attachment you'll find a script based on the one from @Ihnoc that I've written for myself. Note that the UI is quite different, it does not implement everything from the other script and it may also behave a bit differently. But it should work just fine with 1.7 (at least it does for me) and maybe it also helps with the Legato problem @infinitejester0?

Hope it also works well for you! Let me know if it does or doesn't or if you have any questions :)
Click to expand...
Hi, thank you so much!! Works wonderfully
 
  • Like
Reactions: Dot
Dot said:
Hi,

in the attachment you'll find a script based on the one from @Ihnoc that I've written for myself. Note that the UI is quite different, it does not implement everything from the other script and it may also behave a bit differently. But it should work just fine with 1.7 (at least it does for me) and maybe it also helps with the Legato problem @infinitejester0?

Hope it also works well for you! Let me know if it does or doesn't or if you have any questions :)
Click to expand...
Hey there - how do I install this .txt file? Thanks very much!
 
artomatic said:
Have you figured out how to install this?
Click to expand...
1. Open Kontakt and click the 'KSP' button on the right of the Rack panel (pic. 1).
2. Click the 'Edit' button (pic. 2-1).
3. Paste the content of the .txt file into the editor panel (pic. 2-2).
4. Click the 'Apply' button (pic. 2-3).

Now the script is loaded and ready to use.

To be able to use it in future save it as a preset:
1. Click the 'Preset' button.
2. In the dropdown menu select 'Save preset...'. In the opened window name this preset and save it. On Windows, it would usually open such a directory where you should save your scripts: "...\Kontakt\presets\Multiscripts".
 

Attachments

  • 1.jpg
    1.jpg
    40.1 KB · Views: 24
  • 2.jpg
    2.jpg
    95.4 KB · Views: 32
OatMeal said:
1. Open Kontakt and click the 'KSP' button on the right of the Rack panel (pic. 1).
2. Click the 'Edit' button (pic. 2-1).
3. Paste the content of the .txt file into the editor panel (pic. 2-2).
4. Click the 'Apply' button (pic. 2-3).

Now the script is loaded and ready to use.

To be able to use it in future save it as a preset:
1. Click the 'Preset' button.
2. In the dropdown menu select 'Save preset...'. In the opened window name this preset and save it. On Windows, it would usually open such a directory where you should save your scripts: "...\Kontakt\presets\Multiscripts".
Click to expand...

Thank you for sharing this detailed info. Truly appreciate it!
 
I've been trying to get this thing to work for a while now (using FL Studio doesn't help) and was so close to building the template of my dreams. Is it possible to assign the Legato mode into a CC instead? Using the keyswitch is causing some inconsistencies in the legato mode with BRSO Articulate when switching from short to long articulations. I'd prefer to have it glued to Advanced legato.
 
PromotedLurker said:
I've been trying to get this thing to work for a while now (using FL Studio doesn't help) and was so close to building the template of my dreams. Is it possible to assign the Legato mode into a CC instead? Using the keyswitch is causing some inconsistencies in the legato mode with BRSO Articulate when switching from short to long articulations. I'd prefer to have it glued to Advanced legato.
Click to expand...
Sure this should be possible. If I understand you correctly you want Legato on for Advanced Legato and off otherwise and you are using Keyswitches to switch between Articulations?
If so, the Keyswitches for Sustain are processed in the script in lines 1006-1019. There you would just have to set %legatoIsEnabled[$MIDI_CHANNEL] := 1 or := 0 and send the respective MIDI event to CSS to turn it on or off there (similar to what is done for Trills in lines 1103-1111).
 
Is there a step by step guide on this for logic? I am just now getting back into scoring and just composed my first film score this past weekend and CSS was unusable for me because of the latency. I don’t get why this library is so off. Great sounding, but off. Tech support is like “it’s not a problem, it’s a feature, read the manual.” How about get the latency to a usable and playable level?
 
Hey guys, I was hesitant to comment here to plug my script in the thread of a somewhat "competing" script, but considering the development inactivity (save the contributions by members other than the OP), perhaps I can be forgiven.

I've created the VDC some time ago to handle this case while allowing for tweaking and configuring for other libraries as well. If you're interested, check out that thread, the multi script (with an included CSS preset), and the PDF manual I made. I can answer any questions in that thread.

The Variable Delay Compensator (v1.6): Another multi script for CSS...but for any others, too!

As the developer of Section Leader, I now present a multi script far less ambitious but hopefully far more usable: the Variable Delay Compensator (VDC). Before I continue, I want to shout-out the currently available solutions for making "laggy" libraries easier to work with: @Ihnoc's CSS...
vi-control.net vi-control.net
 
You must log in or register to reply here.
Top Bottom