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

[Echoes in the Attic]

For the MPE folks out there.

I have improved the script to offer a quick binding between Y axis and Poly Aftertouch which is usually found in more presets.
http://we.tl/rc6DHoAMvH

I'm confused again.

The Z component of MPE is polyphonic aftertouch. It's the downward pressure on the keys or pads.

Y is the vertical up/down motion along the length of the keys or the square of the linnstrument or Bitwig keyboard for example.

See the description of the linnstrument axes here:
http://www.rogerlinndesign.com/linnstrument.html
(under the what is it? section - It describes the different axis movements, Y being timbre on the diagram).

Timbre/Y axis with MPE is controlled by CC74.

By the way, on a side note, I could not get the example preset to work at all from the previous script installer. To use your MPE scripts I have to load them into the part level, but the preset provided has it in the program level, which doesn't work for me. Also, is it not possible to drag a module from one level to another? I was surprised that I couldn't drag the module out of the program level to the part level.

[otristan]

My intention was not to sound sarcastic, it was a genuine question. I asked for corrections if my assumptions are wrong - not sarcasm in return

Sarcasm implies some truth as well. So yes, your assumptions are right.
Even if voices were dependent you could do some dependency graph and resolve this.
Still, this do not implies that the solution is trivial even if doable.

[Echoes in the Attic]

For the MPE folks out there.

I have improved the script to offer a quick binding between Y axis and Poly Aftertouch which is usually found in more presets.
http://we.tl/rc6DHoAMvH

I'm confused again.

The Z component of MPE is polyphonic aftertouch. It's the downward pressure on the keys or pads.

Y is the vertical up/down motion along the length of the keys or the square of the linnstrument or Bitwig keyboard for example.

See the description of the linnstrument axes here:
http://www.rogerlinndesign.com/linnstrument.html
(under the what is it? section - It describes the different axis movements, Y being timbre on the diagram).

Timbre/Y axis with MPE is controlled by CC74.

By the way, on a side note, I could not get the example preset to work at all from the previous script installer. To use your MPE scripts I have to load them into the part level, but the preset provided has it in the program level, which doesn't work for me. Also, is it not possible to drag a module from one level to another? I was surprised that I couldn't drag the module out of the program level to the part level.

Actually, slight correction to what I wrote.

Technically, the MPE standard uses channel aftertouch for z (not polyphonic aftertouch), since it is channel per note (each note goes on a different channel).

See the section here under continuous per note chanel pressure:
https://docs.google.com/document/d/1-26 ... nn1nkjz3b6

The Z axis is described under the Continuous Per-Note Control Change Message 74 section.

[otristan]

Binding Y axis to polyAT is just quick way to bind existing preset using poly AT to the MPE script.
While this limits the possibility, this could be useful, hence the addition.

You probably need to load it in the part because Program events are loaded from the Program and scratch existing one.
You cannot indeed drag modules form one level to another.

[Echoes in the Attic]

Binding Y axis to polyAT is just quick way to bind existing preset using poly AT to the MPE script.
While this limits the possibility, this could be useful, hence the addition.

Oh I get it. So it's a way to use polyphonic aftertouch, which has already been assigned in a patch, but instead use it with the Y axis movement. That's cool. Wouldn't it make even more sense though to allow quick binding of polyphonic aftertouch to the Z axis? This way, MPE users could use the same gesture as was intended by the patch designer (which was key pressure). Right now it looks it looks like there is only a quick binding to gain from Z.

You probably need to load it in the part because Program events are loaded from the Program and scratch existing one.

I don't understand. Shouldn't the example patch work? It doesn't. Until I turn off the script. However in the example patch, I do see the X/Y/Z events as modulation sources under program when I click to add modulation. In order to add those myself after adding the script to the Part level, am I correct that I just go Add New modulation > Script Event processor, then rename the modulation to X/Y/Z and give it Event ID of 0/1/2 respectively?

[Sound Author]

Looks like the same issue still exists in the updated v1.0.6. When auditioning samples in the file browser, WAV files arbitrarily "stick" and you have to press the play button. Not a really big deal, I was just wondering if anyone else noticed?

[otristan]

Binding Y axis to polyAT is just quick way to bind existing preset using poly AT to the MPE script.
While this limits the possibility, this could be useful, hence the addition.

Oh I get it. So it's a way to use polyphonic aftertouch, which has already been assigned in a patch, but instead use it with the Y axis movement. That's cool. Wouldn't it make even more sense though to allow quick binding of polyphonic aftertouch to the Z axis? This way, MPE users could use the same gesture as was intended by the patch designer (which was key pressure). Right now it looks it looks like there is only a quick binding to gain from Z.

Make sense. Will remove my Y > PolyAT and offer a Z > PolyAT instead.

You probably need to load it in the part because Program events are loaded from the Program and scratch existing one.

I don't understand. Shouldn't the example patch work? It doesn't. Until I turn off the script. However in the example patch, I do see the X/Y/Z events as modulation sources under program when I click to add modulation. In order to add those myself after adding the script to the Part level, am I correct that I just go Add New modulation > Script Event processor, then rename the modulation to X/Y/Z and give it Event ID of 0/1/2 respectively?

The example patch should work. With what are you testing it ?

[otristan]

Looks like the same issue still exists in the updated v1.0.6. When auditioning samples in the file browser, WAV files arbitrarily "stick" and you have to press the play button. Not a really big deal, I was just wondering if anyone else noticed?

Maybe a matter of looped sample ?
as far as I know this has been removed.
Is this always reproducible with one of your sample ?
If yes, can you upload it somewhere so I can have a look ?

Thanks

[Echoes in the Attic]

Binding Y axis to polyAT is just quick way to bind existing preset using poly AT to the MPE script.
While this limits the possibility, this could be useful, hence the addition.

Oh I get it. So it's a way to use polyphonic aftertouch, which has already been assigned in a patch, but instead use it with the Y axis movement. That's cool. Wouldn't it make even more sense though to allow quick binding of polyphonic aftertouch to the Z axis? This way, MPE users could use the same gesture as was intended by the patch designer (which was key pressure). Right now it looks it looks like there is only a quick binding to gain from Z.

Make sense. Will remove my Y > PolyAT and offer a Z > PolyAT instead.

I would actually encourage you to offer both! The reason for this is that someone may want to use it as pressure, however, it would be cool to be able to quickyl switch that over to timbre/Y as you have it set up here! For example I sometimes use the bitwig touch screen keyboard, which can't do pressure with fingers. However it can do timbre with up/down movements, so if I can quickly switch polyAT functionality over to Y axis that is great! But of course someone with a physical MPE keyboard would probably want to use pressure and assign Y to something else.

You probably need to load it in the part because Program events are loaded from the Program and scratch existing one.

I don't understand. Shouldn't the example patch work? It doesn't. Until I turn off the script. However in the example patch, I do see the X/Y/Z events as modulation sources under program when I click to add modulation. In order to add those myself after adding the script to the Part level, am I correct that I just go Add New modulation > Script Event processor, then rename the modulation to X/Y/Z and give it Event ID of 0/1/2 respectively?

The example patch should work. With what are you testing it ?

With Bitwig touch keyboard or even just regular DAW midi. Loading the MPE script into the part level allows normal keyboard triggering (for example CPS lock keyboard). But loading the example preset does not respond to track/DAW midi.

Do I have the general logic right though for assigning script modulation? X/Y/Z = Script index 0/1/2?

[Sound Author]

Looks like the same issue still exists in the updated v1.0.6. When auditioning samples in the file browser, WAV files arbitrarily "stick" and you have to press the play button. Not a really big deal, I was just wondering if anyone else noticed?

Maybe a matter of looped sample ?
as far as I know this has been removed.
Is this always reproducible with one of your sample ?
If yes, can you upload it somewhere so I can have a look ?

Thanks

No, it's hit and miss. Sometimes the sample will play all the way through; sometimes it will play just a millisecond then stop. However, I am browsing a folder of my own custom sequences, all of which have been looped. Is the loop data causing the problem?

[otristan]

X is 2, y is 1 and Z is 0.

When you talk about the example preset, you mean the older one that worked for others ?
The issue here is maybe that the Y is bound to a filter cutoff, and if you don't send it, then you don't hear a thing.

[otristan]

No, it's hit and miss. Sometimes the sample will play all the way through; sometimes it will play just a millisecond then stop. However, I am browsing a folder of my own custom sequences, all of which have been looped. Is the loop data causing the problem?

It's maybe streaming related.
Will have to take a look tomorrow

[Sound Author]

No, it's hit and miss. Sometimes the sample will play all the way through; sometimes it will play just a millisecond then stop. However, I am browsing a folder of my own custom sequences, all of which have been looped. Is the loop data causing the problem?

It's maybe streaming related.
Will have to take a look tomorrow

Thanks, and like I said it's no big deal, but a fix would make sample browsing a little smoother

[Sound Author]

Also, I think it would be nifty if we could hold down a note before clicking on the "Map" button in the Slice oscillator in order to map the slices to a specific key range instead of them being sent to C3 by default. I'm not sure if there's a feature suggestion thread I should know about, but I thought I'd just throw that out there

[Echoes in the Attic]

X is 2, y is 1 and Z is 0.

When you talk about the example preset, you mean the older one that worked for others ?
The issue here is maybe that the Y is bound to a filter cutoff, and if you don't send it, then you don't hear a thing.

Figured it out. With the example preset, the initial pressure is set to zero and the gain map is set to z^2. However when loading the script initially, the gain map is set to 20db, which I guess allows some volume at lowest pressure levels. And playing midi without any pressure leaves the pressure at zero, so I wouldn't hear anything unless I either turn off the z > gain or change the GainMap to 20db. Or changing the initial pressure made it work as well. Of course this was only an issue for me because I happen to be using something that didn't have pressure/aftertouch response.

Thanks!