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

[Echoes in the Attic]

Here's a more simple and useful test:
http://we.tl/S9eI3BEw7T

This one is comparing your V2 MPE script (where you added an easy binding for PolyAT to the Y axis) to your latest MPE script (calling it V3)
There are 3 falcon tracks.
-First one has your V2 script with a parameter (phasedist) modulated by polyAT and midi data sending Timbre (Y) automation. This seems to correctly modulate phase dist by the Y automation going through polyAT.
-Second one has your V2 script with the same parameter (phasedist) modulated by the script Y axis (index 1) directly instead of going through polyAT (PolyAT binding turned off). I thought this wouldn't work as I thought I tried this before, however it does work, which is great! I'm not sure if I did something wrong before when testing V1 script or if V2 fixed it.
-Third track uses your V3 script, which the new flexible bindings for polyAT to either Z or Y. I'm using the same clip as the others and same patch, however it just doesn't work. No notes are triggered.

So it appears that if you can get the V3 script to work like the V2 one then it'll be a winner. Having a lot of fun playing with the touch screen keyboard with the Y axis modulation controlling parameters in Falcon (with V2 script)

[otristan]

Will check this on Monday.
I haven't tested thoroughly script v3 so I have maybe introduced a bug.
Still easy to fix if V2 worked

Thanks !

[Sampleconstruct]

Five Falcons and a limiter on the master out, slightly bombastic:

https://soundcloud.com/sampleconstruct/ ... capes-vol1

[ErikH]

Nice one indeed.

======================================

Question: I have .wav samples from a NI Kontakt instrument. Can I, using those wavs create a similar instrument in Falcon?
My idea is yes, but if so: what do I have to pay special attention to?
I hope I do not have to load each and every sample to one key....

[Sampleconstruct]

You can try converting the nki to sfz with an app from chickensystems and then load the sfz into Falcon, then you don't have to remap all the samples. Or if you have MachFive, load the nki in there, save and reload in Falcon.

[ErikH]

I haven't got MachFive, and Chicken Systems is either $150 for everything, or 80 for all-to-soundfonts.
Mmmm>Will have to muse on this, and first have adeeper look into my UVI's grand piano.

Thanks!

[otristan]

@EricH if the sample are well named, you can try the Alt + DnD in order to get the custom sample DnD which can use sample names in order to map them automatically

[ErikH]

Thanks.
Indeed, yes: the drag'n'drop menu...
There's so much to remember in Falcon, so many doors leading to entirily new wings of the palace, and each wing has so many doors leading to ... (da capo).

[ErikH]

Pretty impressed. As a test I loaded an instrument via Alt-DnD that has pp, mf and ff samples, , and Falcon organised them neatly in vertical velocity keygroups for me.
Wow.

[c_voltage]

I watched "groove3" video, accidentally noticed about "Trigger Mode" (especially cycle) in osc section, I do not was attach any importance to what it is before, damn, not fit in the head what available to get via this. radical addition, how to better to say a breakthrough but in "horizontally" (among stack) , a special thank for this.

[mcpersso]

Damm I love Falcon. I have been sampling The eminent 310U. It is so great to work with. Love it.
It will be a give away thing in a few weeks time.

Here is a quick made demo:

http://mcpersso.dk/eminent/demo310U.wav /24bit/ Beware of your speakers. The bass is heavy.



BUT, many times it loose the connections to div. macro i made. Thats very irritating. The macro seams to be there, but nothing happens. You have to disconnect and reconnect them. It happens after either of a new Program start or a Multi with equal midi channel setting.

More options like Serum in wavetables, please.

It also have trouble with Root keys of the samples. The root nearly ever be in the sampled root key.
And the Phaser sucks. Please make a better phaser with some stages. 2-4-6-8 and so on.
Let the Bigrock vst phaser be the measurement.

But i love it any way.

Best regards

Peter Persson

[ThomasHelzle]

Here's a more simple and useful test:
http://we.tl/S9eI3BEw7T

This one is comparing your V2 MPE script (where you added an easy binding for PolyAT to the Y axis) to your latest MPE script (calling it V3)
There are 3 falcon tracks.
-First one has your V2 script with a parameter (phasedist) modulated by polyAT and midi data sending Timbre (Y) automation. This seems to correctly modulate phase dist by the Y automation going through polyAT.
-Second one has your V2 script with the same parameter (phasedist) modulated by the script Y axis (index 1) directly instead of going through polyAT (PolyAT binding turned off). I thought this wouldn't work as I thought I tried this before, however it does work, which is great! I'm not sure if I did something wrong before when testing V1 script or if V2 fixed it.
-Third track uses your V3 script, which the new flexible bindings for polyAT to either Z or Y. I'm using the same clip as the others and same patch, however it just doesn't work. No notes are triggered.

So it appears that if you can get the V3 script to work like the V2 one then it'll be a winner. Having a lot of fun playing with the touch screen keyboard with the Y axis modulation controlling parameters in Falcon (with V2 script)

Do you happen to have Aalto? That supports MPE rather well (menu in the upper right) and worked great in my tests with BWS and the LinnStrument I boroughed a while ago.
But like u-he support said, MPE is still up in the air and not implemented the same everywhere yet, so be sure to report your findings to Bitwig Support as well.

Cheers,

Tom

[Echoes in the Attic]

Here's a more simple and useful test:
http://we.tl/S9eI3BEw7T

This one is comparing your V2 MPE script (where you added an easy binding for PolyAT to the Y axis) to your latest MPE script (calling it V3)
There are 3 falcon tracks.
-First one has your V2 script with a parameter (phasedist) modulated by polyAT and midi data sending Timbre (Y) automation. This seems to correctly modulate phase dist by the Y automation going through polyAT.
-Second one has your V2 script with the same parameter (phasedist) modulated by the script Y axis (index 1) directly instead of going through polyAT (PolyAT binding turned off). I thought this wouldn't work as I thought I tried this before, however it does work, which is great! I'm not sure if I did something wrong before when testing V1 script or if V2 fixed it.
-Third track uses your V3 script, which the new flexible bindings for polyAT to either Z or Y. I'm using the same clip as the others and same patch, however it just doesn't work. No notes are triggered.

So it appears that if you can get the V3 script to work like the V2 one then it'll be a winner. Having a lot of fun playing with the touch screen keyboard with the Y axis modulation controlling parameters in Falcon (with V2 script)

Do you happen to have Aalto? That supports MPE rather well (menu in the upper right) and worked great in my tests with BWS and the LinnStrument I boroughed a while ago.
But like u-he support said, MPE is still up in the air and not implemented the same everywhere yet, so be sure to report your findings to Bitwig Support as well.

Cheers,

Tom

No I don't have Aalto. But it seems the only thing in Bitwig that doesn't work quite right is that in MPE mode, pressure doesn't register until the automation line encounters a node, unlike in non-MPE mode (where pressure still controls polyphonic aftertouch), where the pressure line value is sent immediately. And of course it stinks that Bitwig doesn't allow any pitch bend range, it requires an instrument to have +/-48, which kills the ability to use per note pitch automation in most synths (lots of synths can operate with note per channel even though not technically MPE, like u-he stuff, synplant, Oddity, Omnisphere with copied parts).

Falcon's script is especially great in Bitwig (or rather it will be when the latest version is fixed) because of the ability to have polyAT received by either the Y or Z axis, meaning patches that normally respond to polyAT on normal keyboards that send it, can also be controlled with the Bitwig touch screen linnstrument like note grid gliding up or down, which is especially useful when you don't have velocity as an expressive type of input.

[otristan]

There was a typo in my latest MPE script.

Here is a fixed version
http://we.tl/LTl2QhB9YD

@Echoes in the Attic
This should fix your issue.

Thanks for your demo project.

[Echoes in the Attic]

There was a typo in my latest MPE script.

Here is a fixed version
http://we.tl/LTl2QhB9YD

@Echoes in the Attic
This should fix your issue.

Thanks for your demo project.

Working great now, thanks!