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

[EvilDragon]

In the voice, amp envelope is king. Once release is done, the voice is cut off so that it doesn't take any more CPU. Not to mention RAM load would be proportionally increased depending on number of voices, and with it CPU usage as well.

You can always do what you want with 16 monophonic patches each set to receive over its own MIDI channel...

[Echoes in the Attic]

In the voice, amp envelope is king. Once release is done, the voice is cut off so that it doesn't take any more CPU. Not to mention RAM load would be proportionally increased depending on number of voices, and with it CPU usage as well.

You can always do what you want with 16 monophonic patches each set to receive over its own MIDI channel...

Yeah I've done this with Omnisphere. It's a great side benefit of using multi-channel midi with a multi-instance plugin that receive on different channels. But I'm not sure if there's any way with Falcon to copy one program across copies like omni. I wonder if anyone has created a script that creates copies or updates copies based on a master program.

[EvilDragon]

Yikes, 500 MB per Omnisphere instance!

Scripts in Falcon cannot create copies of Falcon programs to my knowledge, so you can only do this manually.

[Caine123]

In the voice, amp envelope is king. Once release is done, the voice is cut off so that it doesn't take any more CPU. Not to mention RAM load would be proportionally increased depending on number of voices, and with it CPU usage as well.

You can always do what you want with 16 monophonic patches each set to receive over its own MIDI channel...

Yeah I've done this with Omnisphere. It's a great side benefit of using multi-channel midi with a multi-instance plugin that receive on different channels. But I'm not sure if there's any way with Falcon to copy one program across copies like omni. I wonder if anyone has created a script that creates copies or updates copies based on a master program.

yes i only do it with omnisphere still, great option and saves a lot of cpu, even with my lower specced old pc i could have 15 sounds or so from omnisphere that way!

[Echoes in the Attic]

Yikes, 500 MB per Omnisphere instance!

Scripts in Falcon cannot create copies of Falcon programs to my knowledge, so you can only do this manually.

No no, not multiple instances of the plugin. One plugin with multiple instances of the sound on different parts (1-8). I shouldn't have used the word instance since that usually refers to loading the plugin multiple times. I'm talking about plugins that can load a given sound multiple times like omni and kontakt. But Omnisphere has a command that copies part 1 to parts 2-8 which is useful for this kind of thing.

[EvilDragon]

Ah, right. Yes, Omni is 8-part multitimbral so that is definitely useful.

[David]

Just picked up Ether Fields, thanks for the discount—sounds great of course, thank you, too, Simon:)

There's some great Pluck presets in there, each targeting a bunch of interesting new samples and loops, apparently in a folder, that can be arrowed between. Is it possible to access these samples directly in some way, for loading into other osc/keygroups? Where's this folder located?

TIA!

[Sampleconstruct]

Just picked up Ether Fields, thanks for the discount—sounds great of course, thank you, too, Simon:)

There's some great Pluck presets in there, each targeting a bunch of interesting new samples and loops, apparently in a folder, that can be arrowed between. Is it possible to access these samples directly in some way, for loading into other osc/keygroups? Where's this folder located?

TIA!

You can't access the samples other than saving each sample into your user directory manually. Unlike my own libraries, UVI use an encrypted sample/assets-container.

[David]

You can't access the samples other than saving each sample into your user directory manually. Unlike my own libraries, UVI use an encrypted sample/assets-container.

Hmm, natch, thanks!

By "saving each sample…manually" do you mean selecting it and playing it via the right-click menu and recording, or is there some way to save these, in the file-saving sense?

[dangayle]

I took advantage of the sale, I wan't looking at getting Falcon any time soon, but my GAS hit me too hard.

A few notes:
- UVI's customer service is the best. They've consistently been awesome to me.
- Falcon always seemed like the greatest atmosphere and pad device, so I picked up Ether Fields and Atmospherics as my toss-ins.
- I used the $100 voucher on top of that to get Vintage Vault 2, so now I'm entirely out of hard drive space AND I have far too many sounds to work with.
- I now have redundant licenses for Mello (the freebie) and Vintage Legends. Anyone interested in a trade?

[Sampleconstruct]

You can't access the samples other than saving each sample into your user directory manually. Unlike my own libraries, UVI use an encrypted sample/assets-container.

Hmm, natch, thanks!

By "saving each sample…manually" do you mean selecting it and playing it via the right-click menu and recording, or is there some way to save these, in the file-saving sense?

Saving them as oscillator presets will do, not resampling them the hard-core way

[David]

Saving them as oscillator presets will do, not resampling them the hard-core way

Yes, of course; glad I found the hard-core door, though:)

[acYm]

Exactly, when starting a patch from scratch, there are no Macros assigned at all and their assignments will differ from patch to patch (or Macros won't be available at all, depending on the sound designer). Right clicking on a Macro let's the user assign it to automation IDs, these assignments are not stored within a patch but within the session in the user's DAW.

That's my point. It doesn't matter if a patch has zero macro controls or a hundred. You're still supposed to be able to map the macro section to automation in a fixed manner across the entire instrument. Like for example, say, every other instrument that has macros that I can think of.

Hopefully UVI realize how insanely dumb this is, if they do, they'll be $250 richer in the next sale.

[Sampleconstruct]

Exactly, when starting a patch from scratch, there are no Macros assigned at all and their assignments will differ from patch to patch (or Macros won't be available at all, depending on the sound designer). Right clicking on a Macro let's the user assign it to automation IDs, these assignments are not stored within a patch but within the session in the user's DAW.

That's my point. It doesn't matter if a patch has zero macro controls or a hundred. You're still supposed to be able to map the macro section to automation in a fixed manner across the entire instrument. Like for example, say, every other instrument that has macros that I can think of.

Hopefully UVI realize how insanely dumb this is, if they do, they'll be $250 richer in the next sale.

You still haven't understood or don't want to understand.

[SJ_Digriz]

Exactly, when starting a patch from scratch, there are no Macros assigned at all and their assignments will differ from patch to patch (or Macros won't be available at all, depending on the sound designer). Right clicking on a Macro let's the user assign it to automation IDs, these assignments are not stored within a patch but within the session in the user's DAW.

That's my point. It doesn't matter if a patch has zero macro controls or a hundred. You're still supposed to be able to map the macro section to automation in a fixed manner across the entire instrument. Like for example, say, every other instrument that has macros that I can think of.

Hopefully UVI realize how insanely dumb this is, if they do, they'll be $250 richer in the next sale.

I think there is a communications gap going on here in the usage of the word macro.

Since I primarily use Falcon in my DAW or hosted in VEP, the macro assignment issue hasn't come up often. But, it would be nice if the CC assignment for macros was saved with the patch as an option.