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

[Sampleconstruct]

Falcon is way too over-complicated, I much prefer stuff like Diversion that provides results much faster

Naaa, it's not.

[deastman]

Falcon is way too over-complicated, I much prefer stuff like Diversion that provides results much faster

Naaa, it's not.

Falcon is a sophisticated tool, no doubt about it. There are advanced users and patch designers who can really dig in and make the most of a complex synth like this. For others, a simple instrument with less functionality but great sound is going to be a better tool for the task of making music. Both have their place. Its pretty obvious which category Falcon falls into, but that doesn't mean that it isn't absolutely perfect for some people.

[Sampleconstruct]

Falcon is way too over-complicated, I much prefer stuff like Diversion that provides results much faster

Naaa, it's not.

Falcon is a sophisticated tool, no doubt about it. There are advanced users and patch designers who can really dig in and make the most of a complex synth like this. For others, a simple instrument with less functionality but great sound is going to be a better tool for the task of making music. Both have their place. Its pretty obvious which category Falcon falls into, but that doesn't mean that it isn't absolutely perfect for some people.

I think what is the most baffling for Falcon newcomers is the lack of an old-school modulation matrix approach, where you assign things in columns - A modulates B, or A modulates B via C - I much prefer the Falcon approach as assigning modulations is so much faster by simply right clicking and choosing a modulator which can then be edited at the bottom of the GUI or via right click again “ Edit Modulation“ - and it can all be monitored in Tree View as a patch grows.

And the combination of a sample-player approach with a hierarchy of Program->Layer->Keygroup->Oscillator and a synth approach can be confusing at first, after all you can theoretically map 16384 different key-zones in Falcon, each one containing a different oscillator type/synthesis form (128 Midi notes times 128 velocity zones). Maybe I should try that one day

EDIT: the maths were wrong as there are only 127 velocity zones available which reduces the number of possible zones to 16256.

[wagtunes]

Falcon is way too over-complicated, I much prefer stuff like Diversion that provides results much faster

Naaa, it's not.

Falcon is a sophisticated tool, no doubt about it. There are advanced users and patch designers who can really dig in and make the most of a complex synth like this. For others, a simple instrument with less functionality but great sound is going to be a better tool for the task of making music. Both have their place. Its pretty obvious which category Falcon falls into, but that doesn't mean that it isn't absolutely perfect for some people.

I think what is the most baffling for Falcon newcomers is the lack of an old-school modulation matrix approach, where you assign things in columns - A modulates B, or A modulates B via C - I much prefer the Falcon approach as assigning modulations is so much faster by simply right clicking and choosing a modulator which can then be edited at the bottom of the GUI or via right click again “ Edit Modulation“ - and it can all be monitored in Tree View as a patch grows.

And the combination of a sample-player approach with a hierarchy of Program->Layer->Keygroup->Oscillator and a synth approach can be confusing at first, after all you can theoretically map 16384 different key-zones in Falcon, each one containing a different oscillator type/synthesis form (128 Midi notes times 128 velocity zones). Maybe I should try that one day

EDIT: the maths were wrong as there are only 127 velocity zones available which reduces the number of possible zones to 16256.

I have to agree with this. After using I don't know how many synths, I find Falcon's modulation "matrix" the easiest to use. It's basically a couple of clicks to do just about anything and I don't have to go looking around for matrix boxes or whatever other hoops most synths make you go through to modulate something, as few as there are out there that even have so many modulation possibilities.

My only complaint about Falcon is that it is so versatile and so wide open that sometimes I sit and look at it and say to myself, "Okay, what the hell do I want to do with it today?" Yes, sometimes the choices can be overwhelming in deciding what to do. But once I stop the procrastination and make that decision, creating what I want is easier than with any other synth that I can think of, even if it's just a a simple patch.

I've created over 400 patches since getting Falcon and haven't even scratched the surface. Granular synthesis alone could keep me busy for years.

In short, I've died and gone to synth heaven.

[the3ug3reeder]

it would be very cool to add a record button to Falcon.
play MIDI and press to record audio output...
then be able to select what you want from the recorded output and copy that into your oscillator.

[EvilDragon]

That's why you have DAWs. Record the output of Falcon then put that into Falcon as a sample...

[the3ug3reeder]

yes in theory...

though in practice recording a sample to a file, then making sure it's not currently reffenced by your daw
(in live, i need to first delete a recording from my track before i can reffence it anywhere else),
then again dragging that into your sampler is tedious.
and also, it's messy.

i think recording to a buffer, and then selecting just the section you want to actually use is much better.

have you tried renoise redux?
there is something extremely slick about being able, first of all, to record audio into a buffer...
and then by simply highlighting a selection of the waveform and hitting 'ctrl+shift+C' you immediatly have a new edited sample.
nothing gets saved to disk before you actually save the patch.

[Shabdahbriah]

have you tried renoise redux?
there is something extremely slick about being able, first of all, to record audio into a buffer...
and then by simply highlighting a selection of the waveform and hitting 'ctrl+shift+C' you immediatly have a new edited sample.
nothing gets saved to disk before you actually save the patch.

I'd spaced on trying this... Thanks for the heads-up. "slick" ~ indeed!

[Cinebient]

I also find the modulation in Falcon really great and fast. For such a complex thing it works good.

That said, Equator has for me the best and most intuitive way to add modulation plus the best UI ever.

[Sampleconstruct]

Whoever is fed up always using a calculator when using the step sequencer to create pitch sequences, here is a first table with a 2-octave range, so if you e.g. assign oscillator pitch to “Step Envelope“, set the slider to “24 Semitones“, then type in the numbers into each step numerically, if you are using a bipolar stepper just use negative values for the lower pole:

+1 semitones 0,04167
+2 semitones 0,0833
+3 semitones 0,12501
+4 semitones 0,1668
+5 semitones 0,20835
+6 semitones 0,25002
+7 semitones 0,29169
+8 semitones 0,33336
+9 semitones 0,375
+10 semitones 0,4167
+11 semitones 0,45837
+12 semitones 0,5
+13 semitones 0,5417
+14 semitones 0,58338
+15 semitones 0,625
+16 semitones 0,667
+17 semitones 0,7083
+18 semitones 0,75
+19 semitones 0,79167
+20 semitones 0,833
+21 semitones 0,875
+22 semitones 0,9167
+23 semitones 0,9583
+24 semitones 1

[EvilDragon]

I think a better/simpler way could be using a modulation mapper. You set the step envelope amount to 1 semitone, add the mapper, set size to 48, range -24 to 24, disable Interpolated, enable Integer Output. Voila.

[Sampleconstruct]

I think a better/simpler way could be using a modulation mapper. You set the step envelope amount to 1 semitone, add the mapper, set size to 48, range -24 to 24, disable Interpolated, enable Integer Output. Voila.

And then you would have to type in semitone values in the mapper and edit the steps in the stepper too, which doubles the amount of work. A ramp-up LFO via Mapper would do the trick though.

[EvilDragon]

No need to type semitone values in the mapper at all. Integer Output rounds to semitones when the mapper is set as above. Then you could freehand draw interesting patterns in the step envelope without concerning yourself with which note is going to play, but they will always snap to semitones...

Of course, if you need a SPECIFIC sequence going on, then just using the table you listed is probably faster, yeah.

[Sampleconstruct]

No need to type semitone values in the mapper at all. Integer Output rounds to semitones when the mapper is set as above. Then you could freehand draw interesting patterns in the step envelope without concerning yourself with which note is going to play, but they will always snap to semitones...

Of course, if you need a SPECIFIC sequence going on, then just using the table you listed is probably faster, yeah.

But I was referring to a “pitch sequence“ as in a “repeating rhythmical melodic motif“ as in pitch sequence

[Sampleconstruct]

A split Falcon patch with e-bowed and amped electric guitar flageolet transitions meets a granulated vocal texture:

https://soundcloud.com/sampleconstruct/ ... falcon-air