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

[Echoes in the Attic]

Unfortunately though I still can't assign parameters of my choosing to the axes. I've tried by assigning Z and Y to parameters in the preset example and also tried loading the script into factory presets. I right-click a parameter like a cutoff and select add modulation>script event processor (new one or X/Y/Z if it exists already) and it doesn't respond. I've tried just about every combination of where to put the script and here to put the modulation source...

[otristan]

You need to choose per voice parameter (aka keygroup or below level)
My issue here is that you don't use an MPE controller so do you know that you need to send note on different MIDI channel and not on the global one (by default one) ?

[Echoes in the Attic]

You need to choose per voice parameter (aka keygroup or below level)
My issue here is that you don't use an MPE controller so do you know that you need to send note on different MIDI channel and not on the global one (by default one) ?

Actually I am using an MPE controller - The bitwig touch screen keyboard operates in MPE mode (sends notes on different channels etc.). You just click "Force MPE mode" on the VST device and then the keyboard sends midi that way.

I have been choosing per voice parameters, like keygroup filters.

Edit - Actually the modulated parameters respond but they seem to respond globally to only the note sent on the channel selected in the global channel box. So for example with global channel 2 selected it seems to respond to the note modulation sent with the channel 2 note, rather than processing the note modulations separately per note. I'm unsure of what this global channel setting is supposed to mean since notes/Y/Z get sent on different channels.

Also - just to confirm. It's ok to have the MPE script on the Part level right? I like to have it there because it can be kept while changing presets (and even loaded in the default multi).

[otristan]

The global channel is used to sent events to all channel.
Like if you want to pitch bend all notes in one shot.

It is ok to use the MPE script on Part level.

I have downloaded bitwig demo but I have a hard time figuring how to use the MPE aspect.

If you can send me a simple song with Falcon set in MPE mode and with a small sequence that does send pressure, pitch and timbre for different note, I can take a look.

FWIW, The MPE script was done using the Seabord rise.

[Echoes in the Attic]

The global channel is used to sent events to all channel.
Like if you want to pitch bend all notes in one shot.

It is ok to use the MPE script on Part level.

I have downloaded bitwig demo but I have a hard time figuring how to use the MPE aspect.

If you can send me a simple song with Falcon set in MPE mode and with a small sequence that does send pressure, pitch and timbre for different note, I can take a look.

FWIW, The MPE script was done using the Seabord rise.

Cool, much appreciated. To turn on MPE, just right-click the falcon device box and select "Force MPE". Then if the device responds to MPE you can edit individual note pitch changes (on the note itself by clicking the note edit button on the left) as well as timbre and pressure (Y and Z) per note (in the modulation lane below).

How do I send you a file? Will you pm me your email?

[otristan]

Just upload something on wetransfer.com and send me the link in PM

Thanks !

[otristan]

It's either me, or Bitwig seems to not do MPE correctly.
Looks like when you draw a curve it sends only the first value and the last one, so this is not very practical do do ramps....so their actual display is wrong. This is maybe what is bothering you.

[Echoes in the Attic]

It's either me, or Bitwig seems to not do MPE correctly.
Looks like when you draw a curve it sends only the first value and the last one, so this is not very practical do do ramps....so their actual display is wrong. This is maybe what is bothering you.

Works with other MPE instruments though. And also works with Falcon with the "easy" bindings you have set up like gain > z. Maybe I could send an example of something that works with falcon and something that doesn't.

[otristan]

I have reworked the script to make it a bit more flexible
Here is the new version.
http://we.tl/rpNFqUFSgA

If you have a sequence that runs fine with other MPE synth and do not work the same in Falcon.
Please send it to me so I can have a look.

Thanks !

[Echoes in the Attic]

I have reworked the script to make it a bit more flexible
Here is the new version.
http://we.tl/rpNFqUFSgA

If you have a sequence that runs fine with other MPE synth and do not work the same in Falcon.
Please send it to me so I can have a look.

Thanks !

Nice new layout and functionality with the new script! Unfortunately it doesn't work for me though at all. If I use this one, I just can't trigger any midi. I replace it with your first or second version and midi triggers again normally.

At the same time I am investigating MPE issues in Bitwig. There definitely seems to be a problem with midi data in Bitwig where the timbre or pressure data doesn't set the correct VST parameter value until the respective automation/modulation line hits a node. This doesn't seem to be the case with built-in instruments. But I've confirmed it's an issue with u-he Diva as well which supports MPE.

So in Falcon for example if z is set to contorl gain and the initial pressure is set at 0, but the midi clip has the pressure line starting at maximum and going down, the pressure will be at initial value until it hits a node even though the automation may be descending from max. I will report this to Bitwig.

I will send you an example file with some clips in it demonstrating what works and what doesn't with Falcon. Bit tired of the testing for now though.

[DeSynthesize]

Nice new layout and functionality with the new script! Unfortunately it doesn't work for me though at all. If I use this one, I just can't trigger any midi. I replace it with your first or second version and midi triggers again normally.

At the same time I am investigating MPE issues in Bitwig. There definitely seems to be a problem with midi data in Bitwig where the timbre or pressure data doesn't set the correct VST parameter value until the respective automation/modulation line hits a node. This doesn't seem to be the case with built-in instruments. But I've confirmed it's an issue with u-he Diva as well which supports MPE.

So in Falcon for example if z is set to contorl gain and the initial pressure is set at 0, but the midi clip has the pressure line starting at maximum and going down, the pressure will be at initial value until it hits a node even though the automation may be descending from max. I will report this to Bitwig.

I will send you an example file with some clips in it demonstrating what works and what doesn't with Falcon. Bit tired of the testing for now though.

Sorry to jump in here, but Diva doesn't support MPE. Here is a quote from an email exchange from U-he

" There's a difference between Multi-Channel MIDI and MPE, our plugins currently only support Multi-Channel MIDI.

The problem is that MPE is only a draft at the time, not a finished and agreed-upon standard. If we started implementing unfinished and experimental standards into our software "just because they exist", we'd probably spend a lot of time updating that functionality because of unforeseen changes. "

I just felt that was important to point out.

[Echoes in the Attic]

Nice new layout and functionality with the new script! Unfortunately it doesn't work for me though at all. If I use this one, I just can't trigger any midi. I replace it with your first or second version and midi triggers again normally.

At the same time I am investigating MPE issues in Bitwig. There definitely seems to be a problem with midi data in Bitwig where the timbre or pressure data doesn't set the correct VST parameter value until the respective automation/modulation line hits a node. This doesn't seem to be the case with built-in instruments. But I've confirmed it's an issue with u-he Diva as well which supports MPE.

So in Falcon for example if z is set to contorl gain and the initial pressure is set at 0, but the midi clip has the pressure line starting at maximum and going down, the pressure will be at initial value until it hits a node even though the automation may be descending from max. I will report this to Bitwig.

I will send you an example file with some clips in it demonstrating what works and what doesn't with Falcon. Bit tired of the testing for now though.

Sorry to jump in here, but Diva doesn't support MPE. Here is a quote from an email exchange from U-he

" There's a difference between Multi-Channel MIDI and MPE, our plugins currently only support Multi-Channel MIDI.

The problem is that MPE is only a draft at the time, not a finished and agreed-upon standard. If we started implementing unfinished and experimental standards into our software "just because they exist", we'd probably spend a lot of time updating that functionality because of unforeseen changes. "

I just felt that was important to point out.

Fair enough but it does support the polyphonic pressure part of it (same as polyAT but called pressure in the modulation sources). So in effect it responds to the X and Z axes of MPE messages so I am able to test against it in Bitwig with the note pitch and pressure automation lane.

[DeSynthesize]

Well I guess that's because the MIDI CC is available in DIVA and thus represented in Bitwig? I'm ASSUMING that's what Multi-Channel MIDI is.. TBH I'm not well versed in this sort of stuff... I'm still learning. Hence I emailed Diva because I read something somewhere that lead me to believe that they do infact support MPE. Please correct me if I've misunderstood something

[Echoes in the Attic]

Well I guess that's because the MIDI CC is available in DIVA and thus represented in Bitwig? I'm ASSUMING that's what Multi-Channel MIDI is.. TBH I'm not well versed in this sort of stuff... I'm still learning. Hence I emailed Diva because I read something somewhere that lead me to believe that they do infact support MPE. Please correct me if I've misunderstood something

I'm still learning myself and yeah there is a different between multi-channel midi and MPE since the first is simply allowing each note to go on a different channel whereas MPE is a standard (what messages are sent by what gestures etc.). For example timbre (Y axis) is to be controlled by cc 74 on each note channel. I'm not sure if assigning a parameter in Diva to cc74 would mean that timbre would then control it per note. Haven't tried. And actually I just realized something. Pressure/PolyAT is not the correct MPE control for Z axis, that actually is supposed to use channel aftertouch (each note is on a different channel), but I see no channel aftertouch control in Diva.

It's impossible to test this stuff because I can't tell whether a plug-in is at fault or whether the DAW is at fault. I know the latest falcon script doesn't work and the first two do as far as triggering midi and pitch bends and as far as z mapping to gain. So it seems like if the z works to gain, then it should work when z is modulating other parameters, but I don't think it does. I will send my test file to our friendly neighborhood UVI support guru.

[Echoes in the Attic]

I have reworked the script to make it a bit more flexible
Here is the new version.
http://we.tl/rpNFqUFSgA

If you have a sequence that runs fine with other MPE synth and do not work the same in Falcon.
Please send it to me so I can have a look.

Thanks !

Here is a link to a project with falcon loaded on a couple tracks:
http://we.tl/ThvN8uF4XH

Falcon_MPEV1 has your first script which responds to pressure by adjusting gain (z>gain is on).
Falcon_MPEV3 is your recent script which doesn't trigger midi. Playing the same clip.

The other tracks are just a bitwig internal synth and Diva where I tested the pressure automation which showed me that bitwig's synth responded to the pressure level right away whereas VSTs (in MPE mode) only trigger pressure once a node is hit in the pressure automation.

cheers