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

[otristan]

Just a remark: the benefit of using several ocs within the same keygroup is to share e.g. the same envelopes and filters, especially layering several independent keygroups which e.g. use the Xpander filters can be quite demanding on the CPU as those filters are somewhat hungry, so instead of using 3 filters for 3 synths in 3 keygroups, use one filter for 3 synths in one keygroup, you can still control their volumes independently on oscillator level and even assign LFOs/Macros to each for volume/pitch control.

That - and also round robin features.

But round robins in Falcon happen on layer level (not on keygroup level), so I'm not sure what you're referring to.

There are two different round robin feature.
Oscillator ones using Trigger Mode and Layer ones using Layer Rules

[Sampleconstruct]

As demonstrated in the above video and mentioned by Greg before that.

Indeed. I guess i missed that somehow as the post/question of nrosko was not quoted in those replies.

Anyway this was one of the main issues i had when starting with Falcon but found the solution quite fast (actually without checking this in the manual).

When we come back to this thread it's always helpful to read at least the last posts which were made since you left the thread, otherwise we're going to parrot each other for the next 200 pages

[Sampleconstruct]

Just a remark: the benefit of using several ocs within the same keygroup is to share e.g. the same envelopes and filters, especially layering several independent keygroups which e.g. use the Xpander filters can be quite demanding on the CPU as those filters are somewhat hungry, so instead of using 3 filters for 3 synths in 3 keygroups, use one filter for 3 synths in one keygroup, you can still control their volumes independently on oscillator level and even assign LFOs/Macros to each for volume/pitch control.

That - and also round robin features.

But round robins in Falcon happen on layer level (not on keygroup level), so I'm not sure what you're referring to.

There are two different round robin feature.
Oscillator ones using Trigger Mode and Layer ones using Layer Rules

True, I forgot.

[nkurence]

Pretty easy to get lost in this stuff, here's a few patches from last week (all single part/instance).

Couple Pluck oscillators (using drum samples for the exciter) and a simple WT:
https://soundcloud.com/nkurence/151102- ... pluck-test

Granular and Scrub oscillators using some samples from the film Ladyhawke^^, a pluck and simple WT:
https://soundcloud.com/nkurence/151103- ... nular-test

Noodling with effects, a lot of them (multiple Aux w/Beat Repeat):
https://soundcloud.com/nkurence/151104- ... at-grinder

Multi-granular, Pluck, FM and WT (Beat Repeat again):
https://soundcloud.com/nkurence/151105- ... uck-and-wt

[PatchAdamz]

Here are a couple single presets from "Bird in Flight" expansion for Falcon.

PAD/Atmosphere:
https://soundcloud.com/vintage-synth-pa ... uvi-falcon

Ebow Guitar:
https://soundcloud.com/vintage-synth-pa ... uvi-falcon

[el-bo (formerly ebow)]

Multi-granular, Pluck, FM and WT (Beat Repeat again):
https://soundcloud.com/nkurence/151105- ... uck-and-wt

[PatchAdamz]

Some nice stuff by all - and all so different.

Speaks well for Falcons design!

[Ingonator]

I had just imported a few wavetables including my own ones craeted with Audio Term and also a few of teh Codex factory wavetables. Then i had saved those as preset files for the wavetable oscillator module.
Importing, saving as a preset file and re-loading it so far seems to work nicely.

Anyway what is strange IMO is that the preset files have a size that is smaller than 1 KB. So is the full imported wavetable saved in those or is that stored at another location? So far i have no idea wher that other location could be.

If in Falcon a full table with 64 or more waves is stored in less than 1 KB it would be indeed very efficient.
In PPG Wavemapper 2 a full 256 waves wavetable uses up to 65 KB (less with a smaller amount of waves).
In DUNE 2 wavetable files (*.wt format) even go up to a few MBs in size.

[otristan]

If in Falcon a full table with 64 or more waves is stored in less than 1 KB it would be indeed very efficient.
In PPG Wavemapper 2 a full 256 waves wavetable uses up to 65 KB (less with a smaller amount of waves).
In DUNE 2 wavetable files (*.wt format) even go up to a few MBs in size.

Falcon presets do not contains wavetable data but link to this external resource using relative path.

[Ingonator]

If in Falcon a full table with 64 or more waves is stored in less than 1 KB it would be indeed very efficient.
In PPG Wavemapper 2 a full 256 waves wavetable uses up to 65 KB (less with a smaller amount of waves).
In DUNE 2 wavetable files (*.wt format) even go up to a few MBs in size.

Falcon presets do not contains wavetable data but link to this external resource using relative path.

Hi,

thanks for the fast reply. I just found that when moving the WAV file that was used for the wavetable import to another place would I get an error message. You then get the option to search for the related WAV file.

If i copy the WAV file back to the original place the oscillator preset works nicely again.

UPDATE:
If i save a patch/program that uses a custom wavetable with "Save Program and Sample As..." a new sub-folder with the related WAV file seems to be automatically created at the folder where the patch/program file is saved (the new sub-folder has the same name as the patch/program).
Would be nice if when importing a wavetable and saving a preset file it could work the same way (saving a copy of the WAV file in a sub-folder at the oscillator preset folder).

[fmr]

If i save a patch/program that uses a custom wavetable with "Save Program and Sample As..." a new sub-folder with the related WAV file seems to be automatically created at the folder where the patch/program file is saved.
Would be nice if when importing a wavetable and saving a preset file it could work the same way (saving a copy of the WAV file in a sub-folder at the oscillator preset folder).

I second this request. I had this marked, but forgot to send the request. This is important, IMO, because saving with a relative pointer may cause troubles if/when we get back to the saved presente after a while, in case we had forgotten, and deleted the file. The solution, then would be to either have the option to save the file together with the preset, as it happens with the sample files, or embed the data in the preset.

Of course the best option would be to save the new wavetables in a directory where they would be scanned and presented in the list of available wavetables, together with the factory ones. Having a visual display representation would help when we are choosing, because sometimes just the name may be insuficient, but this may be asking too much

[otristan]

We don't want any data duplicate unless you ask explicitly for it, which is what is "Save Program and Sample As..."


List custom wavetable in the popup menu is another issue though. Need to check how this could be done.

[Ingonator]

We don't want any data duplicate unless you ask explicitly for it, which is what is "Save Program and Sample As..."


List custom wavetable in the popup menu is another issue though. Need to check how this could be done.

So maybe like with the programs a menu entry like e.g. "Save Preset with Samples" could be helpful at the wavetable oscillator module. This could then create a new sub-folder with a copy of the WAV file like it is done with the "Save Program with Sample" feature.
That way you could only create a copy of the WAV file if you really want it.

[ThomasHelzle]

We don't want any data duplicate unless you ask explicitly for it, which is what is "Save Program and Sample As..."


List custom wavetable in the popup menu is another issue though. Need to check how this could be done.

So maybe like with the programs a menu entry like e.g. "Save Preset with Samples" could be helpful at the wavetable oscillator module. This could then create a new sub-folder with a copy of the WAV file like it is done with the "Save Program with Sample" feature.
That way you could only create a copy of the WAV file if you really want it.

+1

[wagtunes]

Here is the issue that I've run into.

I created one patch with a wavetable and saved the program with sample.

I then created another patch with a different wavetable but also used the wavetable from the previous patch. I have to save the program with the new wavetable or it won't be found. But now that's also going to save a copy of the wavetable from the other patch so we're getting duplicate waves which take up extra space which is not necessary.

I wonder if there is a way we can make this work a little more elegantly.