Menu
What's new
By:
Filters

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

@kpmuzik and @aka70
Thanks gentlemen. Applying both your comments makes the script function well.

Reducing the note overlap (as kpmuzik suggested) did improve things, but there was still an odd delay. Then I played G#0 (as aka70 suggested) and that put everything right on the grid.

What puzzles me is why nudging my fader (set to CC58), so that it triggers the legato/sustain articulation didn't work like the keyswitch. I recorded that automation into the beginning of the region, and always had the playhead pass over that, and I did see something changing in the script as it would pass over that point. Furthermore, I mistakenly started the screen recording a bit late so that you didn't see that happening, but it did happen.

Anyway, playing the G#0 made it work, so although don't get why it works and not the fader, I'm happy that it does.

Does this mean the script won't work with using articulation sets to trigger the different articulations (you know, where the choice of articulation is "baked" into the note); i.e. it needs to be a traditional keyswitch?
 
JM Composer said:
What puzzles me is why nudging my fader (set to CC58), so that it triggers the legato/sustain articulation didn't work like the keyswitch. I recorded that automation into the beginning of the region, and always had the playhead pass over that, and I did see something changing in the script as it would pass over that point. Furthermore, I mistakenly started the screen recording a bit late so that you didn't see that happening, but it did happen.
Click to expand...
Maybe you did move it but cc58 has many articulations, maybe you have selected pizzicato or who knows (from your video I would suggest you had selected marcato because it was algorithm 3). Anyway the script needs to know both CC58 and the keyswitch to initiate.

In Studio One I just use the sound variation so I never bother to move or not the fader (cc58). As soon as I pick up an articulaton the script is already good to go, because sound variations includes both information required by the script to know what delay to use
 
@aka70
Ah, I see, this is good to know. I'm guessing that this fact - that both CC58 and keyswitch must be set for the script - was probably stated somewhere, so I appreciate you took the time to re-clarify this.

Those of you wandering into this thread, take note!
 
***Edited as I made some obvious errors in my articulation map***

Hi again, so I'm redoing this post as I caught some an obvious error in my articulation map where I had the wrong legato vs sustain keyswitch interfering with VDC.

So the only remaining problem I have is something is interfering with Logic switching between shorts and longs (or CSS/kontakt's response). Frequently the longs drop out (or have CC#1 at 0 possibly) if they were preceded by a short. The only solution I've found so far is to use separate tracks. I was wondering if anyone else has had this difficulty with Logic, it seems like Cubase had a similar issue, but it interferes with the ideal workflow of using VDC to use multiple articulations in a single track.

Here are my corrected articulation maps, I didn't put anything in the switches tab. The issue only occurs when going from a short to a long. Going from a long to short works as expected, and I am drawing in CC1 data after the short to make sure the value is not 0. Additionally, the behavior isn't consistent. Sometimes it works.
Screenshot 2024-01-14 at 11.49.20 AM.png Screenshot 2024-01-14 at 11.50.14 AM.png
 
Last edited:
Dr Bensmir said:
View attachment 2024-01-14 15-36-31.mp4
Hey, any idea what the problem might be with the script here with csw?
Click to expand...
I'm noticing that there isn't any info between "Alg 1:" and the "- Leg. 220ms" in the status panel (center-top of UI). It's the sign that it's not fully initialized. Furthermore, it demonstrates that you haven't sent any keyswitch MIDI to it yet (it should display which rules got matched, but none are displaying).

It's stuck in Alg 1 until it gets a both CC58 and a G#0 (default legato on/off switch) to initialize it (assuming the CSW preset is analogous to how my CSS preset is designed). It's what the two comments above yours are discussing, in fact.

VSTHero said:
***Edited as I made some obvious errors in my articulation map***

Hi again, so I'm redoing this post as I caught some an obvious error in my articulation map where I had the wrong legato vs sustain keyswitch interfering with VDC.

So the only remaining problem I have is something is interfering with Logic switching between shorts and longs (or CSS/kontakt's response). Frequently the longs drop out (or have CC#1 at 0 possibly) if they were preceded by a short. The only solution I've found so far is to use separate tracks. I was wondering if anyone else has had this difficulty with Logic, it seems like Cubase had a similar issue, but it interferes with the ideal workflow of using VDC to use multiple articulations in a single track.

Here are my corrected articulation maps, I didn't put anything in the switches tab. The issue only occurs when going from a short to a long. Going from a long to short works as expected, and I am drawing in CC1 data after the short to make sure the value is not 0. Additionally, the behavior isn't consistent. Sometimes it works.
Screenshot 2024-01-14 at 11.49.20 AM.png Screenshot 2024-01-14 at 11.50.14 AM.png
Click to expand...
Might need some MIDI (with the Logic-produced keyswitches) to go with this one. What you've shown looks alright to me, but bear in mind that I'm not experienced with Logic.

Or you can investigate yourself if you're savvy with a MIDI monitor (there's one in Kontakt as a factory multi script). Placing one before and after the script to compare what's going into the VDC (aka from Logic) and out of the VDC (aka into the instrument) should reveal everything we'd need to know.
 
kpmuzik said:
I'm noticing that there isn't any info between "Alg 1:" and the "- Leg. 220ms" in the status panel (center-top of UI). It's the sign that it's not fully initialized. Furthermore, it demonstrates that you haven't sent any keyswitch MIDI to it yet (it should display which rules got matched, but none are displaying).

It's stuck in Alg 1 until it gets a both CC58 and a G#0 (default legato on/off switch) to initialize it (assuming the CSW preset is analogous to how my CSS preset is designed). It's what the two comments above yours are discussing, in fact.


Might need some MIDI (with the Logic-produced keyswitches) to go with this one. What you've shown looks alright to me, but bear in mind that I'm not experienced with Logic.

Or you can investigate yourself if you're savvy with a MIDI monitor (there's one in Kontakt as a factory multi script). Placing one before and after the script to compare what's going into the VDC (aka from Logic) and out of the VDC (aka into the instrument) should reveal everything we'd need to know.
Click to expand...
Thanks KP, I'll give it a go. Most likely it's a Logic to Kontakt / CSS issue rather than VDC itself but figured since most VDC users are CSS users someone might have already run into this.
 
kpmuzik said:
I'm noticing that there isn't any info between "Alg 1:" and the "- Leg. 220ms" in the status panel (center-top of UI). It's the sign that it's not fully initialized. Furthermore, it demonstrates that you haven't sent any keyswitch MIDI to it yet (it should display which rules got matched, but none are displaying).

It's stuck in Alg 1 until it gets a both CC58 and a G#0 (default legato on/off switch) to initialize it (assuming the CSW preset is analogous to how my CSS preset is designed). It's what the two comments above yours are discussing, in fact.


Might need some MIDI (with the Logic-produced keyswitches) to go with this one. What you've shown looks alright to me, but bear in mind that I'm not experienced with Logic.

Or you can investigate yourself if you're savvy with a MIDI monitor (there's one in Kontakt as a factory multi script). Placing one before and after the script to compare what's going into the VDC (aka from Logic) and out of the VDC (aka into the instrument) should reveal everything we'd need to know.
Click to expand...
Hey, in fact I am using single track articulation, not multi KS patches. So is there a simple way to make the script behave correctly when using only one articulation, therefore only one algo
 
Dr Bensmir said:
Hey, in fact I am using single track articulation, not multi KS patches. So is there a simple way to make the script behave correctly when using only one articulation, therefore only one algo
Click to expand...
Sure!

Make sure the configuration you want is in Alg 1 as that's what the VDC will default to. You could either 1) edit the existing Alg 1 to behave like the algorithm you wanted to target, or 2) make a preset from scratch and program the first and only algorithm as desired.

Alternatively, you could switch to "Channel = Alg" mode (using channel selector in lower-right) and send your MIDI through the channel with the same number as the desired algorithm.
 
Can't open VDC in Kontakt 6. When I select it in Presets, nothing happens. It's exactly the same as what Nando reported here:

Nando Florestan said:
I put it in the right directory (presets / Multiscripts / Nando). It appears in Kontakt as a choice. But when I click it, it doesn't load. Nothing happens. If I click Edit, the editor is empty. I restarted Reaper, same thing.

Kontakt 6.7.1 on Reaper on Windows 10.
Click to expand...

I'm on Windows, Cubase 13.
 
muk said:
Can't open VDC in Kontakt 6. When I select it in Presets, nothing happens. It's exactly the same as what Nando reported here:



I'm on Windows, Cubase 13.
Click to expand...
As of v1.6, Kontakt 6.8.0+ is required. It's probably that you're still using 6.7.1.
 
Does anyone have a Dorico expression map for CSS that works with the default VDC CSS preset?

(Sorry if the answer to this is somewhere in this 14 page thread. I tried searching.)
 
You must log in or register to reply here.
Top Bottom