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

[arachnaut]

I can see where arachnaut is coming from...

I don't know how the thing is programmed, but to use pseudo object-oriented terminology and a bit of guess-work, I would describe what I want thusly:

When a keygroup inherits an oscillator, that oscillator and all similar oscillators will use the public, global properties of that oscillator.

Changing a knob on any of these global oscillators affects them all. It is not very common that one would want to change just a single instance. In other words, it looks like a single oscillator even though it is a group of oscillators. The public methods and their changes affect them all.

To make an edit of one single oscillator on one sample or keygroup, one would need to create a private instance of the knobs on a particular keygroup, say, by assigning a macro. I don't know how this should be done, it is too specific to the implementation. This would convert the public oscillator to a private oscillator and it's changes are separated from the other global oscillators.

I hope my distinction between the public/global and the private properties is clear. It is clear in my head, but I might be describing it well - it's been a few decades since I did any object-oriented design.

[arachnaut]

7) Using the Tree View to modify the topmost macro of a set of keygroups results in a random number of the macros in the group getting adjusted properly and the rest get ignored. I posted pictures of this a few posts back.

If you got some steps to reproduce, I will gladly have a look.

When I get a chance I will submit an error report.

Here is an example. Using the preset I posted a few pages ago:

http://www.arachnaut.net/Falcon/Karplan ... Falcon.zip

Step1.png

Step2.png

Step3.png

[arachnaut]

4) If you want to select a range of keygroups, you can only do so with control clicks. You can not use a mouse drag. You can do so if you move a keygroup to expose a 'hole' in the mapping area and use that hole to start the mouse click and then drag an area to lasso a group. (I'm talking about mapping areas that are totally filled - all notes, all velocities, so no holes).

Shift + click then drag

Perfect! That's what I was looking for.

My mouse must be very sensitive because I was frequently nudging these areas when I tried to control click.

[arachnaut]

5) The resolve overlapping tools work somewhat oddly. I don't know how they work, but they don't work as I expected. If I had a few overlapping velocity areas, like from an accidental nudge, I expected the resolution to automatically adjust and nudge them in place, but it did not do that at all, it totally wrecked the key sample.

This is what should happen. If you have a use case that fails, please send it to our support.

Here is an example of what confused me. Firstly, I had a few keygroups mis-aligned due to a faulty click becoming a click-drag. So I made a random few changes like below to simulate what had happened:

Step1.png

Then I selected all the keygroups and clicked 'Resolve overlapping key ranges' by accident. There are no overlapping key ranges, just overlapping velocity ranges, so nothing should change.

When I saw this, I was thoroughly confused:

Step2.png

Now I see that it is using the velocity overlaps incorrectly, but at the time I saw this originally I was just totally confused with the results.

[arachnaut]

3) It would be nice to be able to sort samples by velocity and/or key.

Click the column header corresponding to velocities in the List View and Voila !

This does not work for me. Neither column sorts.

sort.png

[mdsp]

5) The resolve overlapping tools work somewhat oddly. I don't know how they work, but they don't work as I expected. If I had a few overlapping velocity areas, like from an accidental nudge, I expected the resolution to automatically adjust and nudge them in place, but it did not do that at all, it totally wrecked the key sample.

This is what should happen. If you have a use case that fails, please send it to our support.

Here is an example of what confused me. Firstly, I had a few keygroups mis-aligned due to a faulty click becoming a click-drag. So I made a random few changes like below to simulate what had happened:

Step1.png

Then I selected all the keygroups and clicked 'Resolve overlapping key ranges' by accident. There are no overlapping key ranges, just overlapping velocity ranges, so nothing should change.

When I saw this, I was thoroughly confused:

Step2.png

Now I see that it is using the velocity overlaps incorrectly, but at the time I saw this originally I was just totally confused with the results.

It is working as expected, when 2 keygroups overlap, the split point is being defined as the center of the overlap key region. then each key group's keyrange is trimmed in order to avoid the overlap.

In your case, 'resolve overlapping velocity ranges' was the function to use.

[otristan]

3) It would be nice to be able to sort samples by velocity and/or key.

Click the column header corresponding to velocities in the List View and Voila !

This does not work for me. Neither column sorts.

sort.png

Fixed in 1.0.2
I forgot that we didn't implemented the one with two values in one column.

Thanks !

[arachnaut]

3) It would be nice to be able to sort samples by velocity and/or key.

Click the column header corresponding to velocities in the List View and Voila !

This does not work for me. Neither column sorts.

sort.png

Fixed in 1.0.2
I forgot that we didn't implemented the one with two values in one column.

Thanks !

Great! There are other hidden column headers that can also be enabled, like 'key fade'. I suppose those are fixed as well?

[arachnaut]

I have thought a little about handling the global sample controls better and came up with this suggestion.

Imagine this scenario:

1) Load a bunch of samples into a new keygroup and set up all the velocity and key ranges.
2) Select all the keygroups
3) Now the instrument oscillators show 'Multiple Selection', so use the Batch button to select one, say 'Granular', for example.
4) Currently, the display will still show 'Multiple Selection', suppose instead it showed the initial state for all the sampler controls. If one were to change any of these controls, ALL the keygroups selected get changed. The instrument panel color would be the keygroup color to show it is global.
5) Now suppose we want to change just one oscillator or another group, so we select them. They show the current controls, which are still the global defaults. Changing any of these will change only these oscillators and not the rest. These instrument panels will now be the standard instrument color, not the keygroup color.
6) Changing the global settings will make changes on all the instrument controls that have not been changed - all the so-called global controls. But any instrument with local, private changes, retain those private settings. So in other words, there are global and private controls for each sampler, or in OO terminology, the public and private data.
7) The Batch menu could have a new item that says: 'Reset to global' which will remove the private settings for the selected keygroups and revert to the current global settings.
8 There should be some way to show which parts of an oscillator are global and which are private. The button colors could take on the keygroup color for global settings and the normal color for private settings.

I have not thought this out in detail, there are probably a lot of issues, but I think this is a good start to adding a really useful feature. And I don't think it would interfere very much with the current implementation architecture, but that is just my guess.

[otristan]

Great! There are other hidden column headers that can also be enabled, like 'key fade'. I suppose those are fixed as well?

Nop. just Vel and Key.
You will need to find me a good use case for that before

[arachnaut]

Great! There are other hidden column headers that can also be enabled, like 'key fade'. I suppose those are fixed as well?

Nop. just Vel and Key.
You will need to find me a good use case for that before

I can't give you one, I was just curious. I probably will never even enable those other columns.

[UmFuFu]

Hi All,
Really enjoying Falcon. Great work.

I have a quick question about the Pluck oscillator. Is there a way to make it stereo (besides unison)? It seems like it should be as the waveform shows both channels of a stereo file, but I only ever hear it playback in mono.

Let me know thanks.
I love the way the pluck osc sounds btw!

[Sampleconstruct]

Hi All,
Really enjoying Falcon. Great work.

I have a quick question about the Pluck oscillator. Is there a way to make it stereo (besides unison)? It seems like it should be as the waveform shows both channels of a stereo file, but I only ever hear it playback in mono.

Let me know thanks.
I love the way the pluck osc sounds btw!

There is a switch in the inspector labelled “Stereo“, you have to be in dual string mode though for this to have an effect, try Bridge mode then the strings will be panned in the stereo field.

Unison (I know you weren't asking for this but I still mention it for others to read): you can also set the layer to 2+ voices and apply unison modulation to keygroup pan position (and a bit of pitch to enhance the stereo effect).

[UmFuFu]

Ah, amazing thank you!
I never would've found that. Are there a lot of "hidden" features to modules in the inspector view? I'll have to keep looking there.

[Sampleconstruct]

Ah, amazing thank you!
I never would've found that. Are there a lot of "hidden" features to modules in the inspector view? I'll have to keep looking there.

Yes, there are - e.g. in the delay FX module, you can modulate frequency - notch or peak - by assigning e.g. monophonic LFOs to the frequency and q-parameters which makes for some nice effects.