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

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS
Falcon

Post

Watch tutorials by Dan Worrall!

Post

Thanks dragon man

Post

plexuss wrote: Fri Oct 25, 2019 11:37 pm Strange thing with MPE. I am not a Falcon expert so I am not sure what is going on here: When I fire up Falcon and load a non-MPE patch, but with my Rise connected and sending MPE, I get no sound out of Falcon. But if I load an MPE patch, it works. Then, I re-load the previous non-MPE and patch and now I can play it with the Rise. Any idea whats going on here? I assume something gets loaded with the MPE patch that is carried over when other patches are loaded later?
MIDI channels.
MPE script switch the part to omni while it's only a single channel by default.
Most MPE device only send on channel 2-16 while general command are on channel 1 hence the behavior you are seeing
Olivier Tristan
Developer - UVI Team
http://www.uvi.net

Post

EvilDragon wrote: Sat Oct 26, 2019 3:07 pm When you open Falcon, press Ctrl+N to create a new keygroup, or right-click in the grid area to create one. Use the Synth template.
You can also make a new Default Part and save it so if you are experimenting with wavetable then that's the default new Part (patch). Or try saving your favorite LFO configuration.
I have a new default Multi that contains a new default Part as my starting place.
Use "Save as default Multi" on the main menu.
Falcon user since 2015

Post

How much control do you have inside of Falcon of the UVI vintage vault libraries? can you further tweak the patches? because in the UVI workstation you are limited to the parameters presented by the developer.

Post

Yes, you can further tweak stuff from Vintage Vault.

Post

EvilDragon wrote: Sun Oct 27, 2019 8:52 pm Yes, you can further tweak stuff from Vintage Vault.
Is it possible to use the samples in other patches? or are they locked?

Post

You could copy the keygroup(s) over to another patch, at least. Samples themselves are monolithed in the .ufs file and you cannot get to them any other way.

Post

EvilDragon wrote: Sun Oct 27, 2019 9:24 pm You could copy the keygroup(s) over to another patch, at least. Samples themselves are monolithed in the .ufs file and you cannot get to them any other way.
Correct me if I'm wrong but from what I understand Monolithed means I can use them in falcon but not in other applications?

Post

You can save oscillator presets which include the samples but for large multi sampled instruments that's not a realistic option.

Post

Lucastyle wrote: Sun Oct 27, 2019 9:38 pm
EvilDragon wrote: Sun Oct 27, 2019 9:24 pm You could copy the keygroup(s) over to another patch, at least. Samples themselves are monolithed in the .ufs file and you cannot get to them any other way.
Correct me if I'm wrong but from what I understand Monolithed means I can use them in falcon but not in other applications?
For example can I load a UVI vintage vault sample in the granular engine?

Post

Sure.
Lucastyle wrote: Sun Oct 27, 2019 9:38 pmCorrect me if I'm wrong but from what I understand Monolithed means I can use them in falcon but not in other applications?
Correct.

Post

EvilDragon wrote: Sun Oct 27, 2019 9:57 pm Sure.
Lucastyle wrote: Sun Oct 27, 2019 9:38 pmCorrect me if I'm wrong but from what I understand Monolithed means I can use them in falcon but not in other applications?
Correct.
Evil do you think it's worth the extra money for extra flexibility with the libraries?

Post

It's probably more worth it if you're gonna do your own stuff with it rather than just mess about with the libraries.

Post

EvilDragon wrote: Sun Oct 27, 2019 10:46 pm It's probably more worth it if you're gonna do your own stuff with it rather than just mess about with the libraries.
you mean like sampling my own instruments ?

Post Reply

Return to “Instruments”