UVI Falcon - v4 = 2026 released - rumors, ads, praise, kindergarden, auto-sampling and off-topic inside!

[otristan]

You are using the MPE script from the Utilities folder from Falcon factory script ?
Not the one I've sent on KvR, right ?

Well I thought I was but it turns out I wasn't. And now that I'm trying out the factory one I'm getting really odd results. My pitch shifts are different even though all else seems the same. Kinda freaking me out... Should I/could I put this all in an e-mail for you? I'd love to get this sorted out but I'm not sure I should take up the space here.

Thanks so much,
B

The pitch bend range might be different between the one in the resource and the one I have sent here.

1) I actually modified both scripts to go down to 1 semitone pitch-bend range. This is the only line I modified in the script:

local PitchBendRange = NumBox {"PitchBendRange", 1, 1, 48, false, displayName = "PB Range", tooltip = "Pitch Bend Range"}

Is this the only line I should need to modify?

2) If I use the Script Event Modulation with the depth sliders set to the same place it shouldn't matter right?

Thanks for your help!

1. No need to change the script itself, but you need to tweak the pitch bend range in the script UI according to your device. Usually 24 or 48 semi tones
2. Pitch bend range in the script is only for the hardcoded Y axis to pitch connection.

1 semitones pitch bend range do not make sense in the MPE logic as you need to do the whole keyboard range using the pitch bend.

[Sound Author]

Does anyone know of a custom script for vector synthesis? Specifically with an XY pad for fading between four samples? I really like the Vector oscillator in kv331's Synthmaster and I'm interested in developing a script for something like it if it doesn't already exist. Any ideas?

[UmFuFu]

1. No need to change the script itself, but you need to tweak the pitch bend range in the script UI according to your device. Usually 24 or 48 semi tones
2. Pitch bend range in the script is only for the hardcoded Y axis to pitch connection.

1 semitones pitch bend range do not make sense in the MPE logic as you need to do the whole keyboard range using the pitch bend.

I'm not using the MPE script with a controller (though I do sometimes), but I'm using it as a way to send pitch-bend and amplitude data to Falcon on a per-note basis using Nuendo's Note-Expression functionality. And because of the data I'm using I need it to be 1 semitone pitch-bend range... So there's a very specific reason that I'm doing that.

But going back to my earlier question: If I use the Script Event Modulation with the depth sliders set to the same place then the results should theoretically be the same right?

Thanks.

[otristan]

Yep. Be sure to use a bipolar Script Event Modulation though.

[UmFuFu]

Yep. Be sure to use a bipolar Script Event Modulation though.

I get different results.. trying to figure out why.

[otristan]

Yep. Be sure to use a bipolar Script Event Modulation though.

I get different results.. trying to figure out why.

Tried here with the Script Event Modulation and it works fine.
Just in case you didn't did it, you need to remove the pitch bend modulation already present by default in preset.

[UmFuFu]

Yep. Be sure to use a bipolar Script Event Modulation though.

I get different results.. trying to figure out why.

Tried here with the Script Event Modulation and it works fine.
Just in case you didn't did it, you need to remove the pitch bend modulation already present by default in preset.

I think I figured it out!! The new factory MPE script seems to suffer from the same affliction that some of your early MPE scripts suffered from; namely, the notes won't pick up a pitch-bend change if it happens at the very beginning of the note. It will pick up (and jump) to the first pitch-bend data after the note is already playing. In my current piece I only have one bit of pitch-bend data at the very head of each note which is why it was sounding different. When I went back and added a bit of PB data just after the note started it sounded correct again.

Some of your later MPE scripts on the forum fixed this issue, might there be a way to fix it again you think?

Thanks so much,
B

[otristan]

Could you try that ?
https://we.tl/F3fBU7UBVA

The issue probably happen only on overlapping note on the same channel.

Thx

[UmFuFu]

Could you try that ?
https://we.tl/F3fBU7UBVA

The issue probably happen only on overlapping note on the same channel.

Thx

Still testing a few things but I think that did it thanks! At least it is MUCH, much closer... The initial pitch-bend values seem to be fixed (i.e. they are being read now). I'm getting some differences in the way the Pressure (Gain) info is being interpreted. Trying to figure that out...

Quick question. In the previous version of the script (before 1.1), there wasn't a drop-down for the Script Event Modulation, so if you were using S.E.M. were you supposed to select "None"? If you had "Pitch" selected and had S.E.M going (for instance) would the values double up? I think that could be the remainder of my problem if so.

Thanks!

[EvilDragon]

Script Event Modulation makes sense only if you have such a modulator modulating something in your instrument.

[UmFuFu]

Script Event Modulation makes sense only if you have such a modulator modulating something in your instrument.

Yes, but what happens (in the older script) if you have Script Event Modulation applied to Pitch, and also "Pitch" selected in the drop-down? Do they add together? Or is one ignored?

[otristan]

The same thing we did with pitch bend is used as well for pressure.
Specs is not very clear on that.
Right now I reset the initial pressure after the note off so the previous value do not "leak"
Still if you don't have overlapping note on the same channel, this will work.

Do you have more than 16 note on (without note off) at some point ?

What is S.E.M ? Cubase Note expression ?
No need to use Script Event Modulation for pitch bend to pitch, just set the right pitch bend range in the script value.
It's either hardcoded pitch mods handled using the script engine or Script Event Modulation or nothing
but pitch bend events are not passed through right now.
Still this wouldn't work as pitch bend do not handle MPE by itself.
For standard X axis behavior use "Pitch" in the combo and set the right range in the script UI.
Script Event modulation is only useful for non pitch use of the X axis.

Could you try that ?
https://we.tl/F3fBU7UBVA

The issue probably happen only on overlapping note on the same channel.

Thx

Still testing a few things but I think that did it thanks! At least it is MUCH, much closer... The initial pitch-bend values seem to be fixed (i.e. they are being read now). I'm getting some differences in the way the Pressure (Gain) info is being interpreted. Trying to figure that out...

Quick question. In the previous version of the script (before 1.1), there wasn't a drop-down for the Script Event Modulation, so if you were using S.E.M. were you supposed to select "None"? If you had "Pitch" selected and had S.E.M going (for instance) would the values double up? I think that could be the remainder of my problem if so.

Thanks!

[UmFuFu]

The same thing we did with pitch bend is used as well for pressure.
Specs is not very clear on that.
Right now I reset the initial pressure after the note off so the previous value do not "leak"
Still if you don't have overlapping note on the same channel, this will work.

Do you have more than 16 note on (without note off) at some point ?

What is S.E.M ? Cubase Note expression ?
No need to use Script Event Modulation for pitch bend to pitch, just set the right pitch bend range in the script value.
It's either hardcoded pitch mods handled using the script engine or Script Event Modulation or nothing
but pitch bend events are not passed through right now.
Still this wouldn't work as pitch bend do not handle MPE by itself.
For standard X axis behavior use "Pitch" in the combo and set the right range in the script UI.
Script Event modulation is only useful for non pitch use of the X axis.

I don't have more than 15 note on's without note off's.

S.E.M. was just my abbreviation for "Script Event Modulation". Sorry, I just got tired of typing it ;p

I think I understand everything you said. But just to be clear, in the old script, if you had "Pitch" selected and had Script Event Modulation mapped to Pitch, would the values double up, or would the Script Event Modulation be ignored in favor of the "hardwired" MPE script?

[otristan]

previous script would double up as it would do the pitch mod using the script and send Script Event Modulation.
Current script do not send Script Event Modulation if you don't have selected it in the combo.

[UmFuFu]

previous script would double up as it would do the pitch mod using the script and send Script Event Modulation.
Current script do not send Script Event Modulation if you don't have selected it in the combo.

Okay thanks. I think that accounts for the differences that I've been experiencing.

Cheers!