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

[Biome_Digital]

Omni has a vast sample library, but I'd rather program Falcon than Omni. In addition Falcon seems to be more optimized in terms of CPU and RAM than many other commercial synths. You can probably load Falcon on each track if you wanted (Zebra is great too). And you can load exactly the modules and effects you want in each patch, there's no bloat. And you can load as many oscillators and modulators as you want.

That being said, I wish they had a demo so you could try it out. It's tough to make purchases without a demo.

I think Falcon struggles a bit on CPU. I don't think it's multi-core.

[Biome_Digital]

So yes, in my opinion I find Cherry Audio synths, and Vsts that do proper midi much more fun to work with. Half baked is definitely what Falcon feels like to me,as it's if they gave up on the performance aspect,when it came to assigning midi CC's for performing realtime, or made it such a task that it takes the fun away from it for me, again I'm pretty sure I'm the minority here,just my opinion. Hope that's okay for KVR and it makes sense.

It's modular. You can do things however you want, which means they can't be done for you.
Do you have any suggestion of how this should be done?

Personally I wish the Macros acted like macros do for NI etc. or the 4 XY pads in Zebra, where they keep their CC assignments across all patches. So a bank of 8, 16, 32 etc. macros that are permanently assigned to the CC's you choose to assign them to. This way you could use the control surface approach of Logic, Live, Bitwig etc. or CC approach of DP etc.

You can permanently assign and save MIDI CC's to macros in programs, but I just kinda think they dropped the ball on the idea of macros in terms of immediate gratification. It's not that bad but I could see how that would be a better front end than ever changing macros only. I would love to be proven wrong here, but it seems that there isn't a universal MIDI or track automation bank, you would have to go through all programs and create that.

It's not going to work like that because the macros are all completely different. I actually think it's pretty cool to have different macro assignments for different sounds. It keeps it interesting between patches. I can understand why you would want them more consistent, though.

[machinesworking]

But the main problem is that macros can have completely different layouts between any two patches, which means cutoff wouldn't always be cutoff etc. Also they can work differently too, the same macro (i.e. macro 3) can be continuous vs on/off toggle, unipolar vs bipolar...

It'a funny you would say that considering you do some work for NI, who put out Komplete Control, that maps disparate parameters on hundreds of plug ins from multiple manufacturers to 8 knobs and 8 buttons on Komplete hardware. The precedent is pretty simple really, a macro setup for complex synths has been a thing for a long, long time now. You 'kind of' get that with macros in Falcon. What you do not get is macros that keep the same cc or track automation.

[machinesworking]

It's not going to work like that because the macros are all completely different. I actually think it's pretty cool to have different macro assignments for different sounds. It keeps it interesting between patches. I can understand why you would want them more consistent, though.

Look to Komplete Kontrol as an example, same 8 knobs, hundreds of variations of what those macro knobs do. I'm not talking consistency of output or assignment parameter wise, but consistency of CC or track automation assignment for 8-16 knobs or faders and 8-16 buttons.

I assign the 8 parameters of the Zebra XY panels to anything I want inside Zebra, but to the outside world I can map the 8 CC's on my AKAI to those pads and it's universally controlled across all patches in Zebra. Something like this makes sense for super complex plug ins like Zebra and Falcon. I'm a little confused why this is so difficult to grasp?

[EvilDragon]

But the main problem is that macros can have completely different layouts between any two patches, which means cutoff wouldn't always be cutoff etc. Also they can work differently too, the same macro (i.e. macro 3) can be continuous vs on/off toggle, unipolar vs bipolar...

It'a funny you would say that considering you do some work for NI, who put out Komplete Control, that maps disparate parameters on hundreds of plug ins from multiple manufacturers to 8 knobs and 8 buttons on Komplete hardware. The precedent is pretty simple really, a macro setup for complex synths has been a thing for a long, long time now. You 'kind of' get that with macros in Falcon. What you do not get is macros that keep the same cc or track automation.

Don't forget that all those macros in KK were manually assigned by actual people, one by one. There's little to no automatism there. Somebody had to do the work.

[machinesworking]

But the main problem is that macros can have completely different layouts between any two patches, which means cutoff wouldn't always be cutoff etc. Also they can work differently too, the same macro (i.e. macro 3) can be continuous vs on/off toggle, unipolar vs bipolar...

It'a funny you would say that considering you do some work for NI, who put out Komplete Control, that maps disparate parameters on hundreds of plug ins from multiple manufacturers to 8 knobs and 8 buttons on Komplete hardware. The precedent is pretty simple really, a macro setup for complex synths has been a thing for a long, long time now. You 'kind of' get that with macros in Falcon. What you do not get is macros that keep the same cc or track automation.

Don't forget that all those macros in KK were manually assigned by actual people, one by one. There's little to no automatism there. Somebody had to do the work.

The paradigm is there though, and NI did the work initially on their own plug ins to start the ball rolling. It wasn’t some grand new idea or anything Automap from Novation was similar, but a plug in could have a universal fixed set of macros that could be assigned to various parameters in that plug in, it’s something IMO every complex instrument should do, but it’s not common. Previous to KK Massive v1 had this, Zebra has this etc. etc. It’s like being able to control a plug ins volume with cc7 like you can with Falcon, it shouldn’t be rare, but it is.

[rasmusklump]

I have re-downloaded and installed the latest version of Falcon today and have the problem with the VST3 version in Cubase 12, Windows 11, that there is always a loud crackle at the beginning when switching sounds, under Bitwig 8-Track there is no problem.

I am on Windows 10 and cubase 11 and don't have any problems with vst3 Falcon

[pierb]

So much nonsense in one single post.
It is funny that even after quite some time of not using it, you're still in the Falcon thread just to post your BS concepts about UX.

If my opinion bothers you you can just ignore me. Problem solved!

Edit:

Oh now I remember you. I see you're still pissed off about that conversation we had at VIC.

[digitallysane]

Oh now I remember you. I see you're still pissed off about that conversation we had at VIC.

I don't even remember whatever conversation you're talking about, but it seems you do, so not sure who's pissed.

I'm pissed off about your insistence, here, to present your misguided opinions as objective truths, that's all.

[chagzuki]

Just been on the phone to Apple support. I've been having big problems with Logic on M1, glitches in audio playback and loads of hanging notes, as have many people. Unsurprisingly their first line of attack was to focus on third party plugins as the source of the problems, which I was sceptical about. I'm pretty sure the hanging note issue isn't limited to one or two specific plugins. However, it happens that in a recent project which uses a complex Falcon patch and I get a lot of hanging notes that make using Logic near impossible. So I followed Apple's advice and replaced Falcon with a stock Logic synth. The hanging notes appear to have gone, and I don't know if it's because the Falcon patch was so complex and therefore placed a greater strain on the system, or whether there's something about the M1 Falcon build which causes problems, problems which tend to appear once the project has been open for 5 minutes or so, and persist until Logic is relaunched. The Apple support person mentioned memory leaks, which I don't properly understand as a concept, and how or whether they could be related to hanging notes. Anyhow, the same project without Falcon appears to be running without hanging notes, so I'm keen for some feedback about this from the devs.

[otristan]

This is a logic problem.
See Apple confirmation here

https://forum.juce.com/t/br-hanging-not ... r/49446/10

[Sampleconstruct]

This is a logic problem.
See Apple confirmation here

https://forum.juce.com/t/br-hanging-not ... r/49446/10

Oops, another good reason to stay away from M1s for a while...

[dayjob]

This is a logic problem.
See Apple confirmation here

https://forum.juce.com/t/br-hanging-not ... r/49446/10

thanks for that. good to be aware. hopefully apple get it sorted out quickly.

[chagzuki]

This is a logic problem.
See Apple confirmation here

https://forum.juce.com/t/br-hanging-not ... r/49446/10

Thanks, that's the info I've been hoping to find for weeks now. Though I'm confused though as to why people started experiencing these issues particularly with logic 10.7.0, if it's something to do with the hardware/OS relation (if I've understood the forum post correctly). And in my case after I had issues with 10.7.0 I renamed the logic application file and restored 10.6.3 via Time Machine, leaving two versions on my Mac. I don't understand the OS well enough to know whether this causes conflicts with dependencies, but I've found that the hanging note issue is pretty much as bad using 10.6.3, which seems odd given that I don't remember it particularly being an issue prior to 10.7.0.

[maximoog]

I have re-downloaded and installed the latest version of Falcon today and have the problem with the VST3 version in Cubase 12, Windows 11, that there is always a loud crackle at the beginning when switching sounds, under Bitwig 8-Track there is no problem.

I am on Windows 10 and cubase 11 and don't have any problems with vst3 Falcon

The problem has been solved. I uninstalled Falcon and reinstalled it again. Now the problem is gone.