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

[spnc]

Okay this time I'm pretty sure UVI Falcon and Ableton together don't work well in macOS Monterey/M1 and are the culprit.

I updated to 2.8.1 and it still crashes immediately when loading certain presets.

Sending the crash report to support but with not much hope.

I made sure to remove the midi device so this is not the issue.

Of course if I load an instance of Falcon alone in a empty project it will work (so far no crash) but that's pointless.

As soon as I get busy in a project it will crash sooner or later, making it unworkable.

I have 700 other vsts and none of them do that.

I'm thinking of moving to Logic if Ableton will never work properly with Falcon but that's an extreme solution. I'm not ready to throw years of getting used to a DAW just for a plugin.

Maybe I should give it another try when macOS Ventura is out next month? Stability issue related to Apple perhaps?

[spnc]

One other really minor thing, which is minor, but since I haven't really dug into falcon programming yet, using it to understand a little:

On the new texture presets, if I click 'modwheel', the preset stops responding to notes outside of C4-C5 (everything gets remapped into that range). Unclicking doesn't help. Using the preset immediately after loading responds normally. Obviously a little weird for basses Even just going into the script seems to trigger this behaviour. I am on M1 Mac, with the latest update, running under live 11.2 M1 native... any ideas?

More investigation: if I open any preset (tried with a couple Devinity presets, go to Edit, everything fine. Then click on a note in the keyboard - now it's clamped to C4-C5 again.

Also, I also have Logic, so I tried it there as well - no issues in Logic, works fine, this appears to be limited to Ableton Live. I did try both 11.2 and 10.1.3 (I have both installed for a few things that only work in Rosetta and/or live 10 - alchemy, liquid music, BFD, jamstix) and both had the same issue, so it doesn't look like a recent break.

For this there are ways around it (just don't do those two things when used as a preset player, but maybe it affects other things too.

Oh yeah man this is so annoying I've noticed that too since an update ago. Driving me nuts!

[spnc]

When using the native mac Keyboard of a M1 MBP to play the notes, in Ableton 11.2 and Falcon 2.8.1, the notes get stuck on C4/C5, regardless of the notes range you select while an instance of Falcon is loaded and armed. For instance, you select C1 octave range, yet, it will keep playing C4/C5 range only in Falcon. Very annoying.

I guess this is related to the previously reported bug.

[shonky]

Can anyone tell me if there’s an issue with Live 11 and Falcon on Win 10 or is it just a MAC issue. Thinking of buying but quite costly if it’s unusable

[otristan]

Okay this time I'm pretty sure UVI Falcon and Ableton together don't work well in macOS Monterey/M1 and are the culprit.

I updated to 2.8.1 and it still crashes immediately when loading certain presets.

Sending the crash report to support but with not much hope.

I made sure to remove the midi device so this is not the issue.

Of course if I load an instance of Falcon alone in a empty project it will work (so far no crash) but that's pointless.

As soon as I get busy in a project it will crash sooner or later, making it unworkable.

I have 700 other vsts and none of them do that.

I'm thinking of moving to Logic if Ableton will never work properly with Falcon but that's an extreme solution. I'm not ready to throw years of getting used to a DAW just for a plugin.

Maybe I should give it another try when macOS Ventura is out next month? Stability issue related to Apple perhaps?

What is your ticket number ?

Thanks

[chroma]

I tried to reproduce this again last night, and after a reboot, was not able to. It does seem minor, and maybe only happens occasionally… will file a ticket if I can make it reproducible

[spnc]

Okay this time I'm pretty sure UVI Falcon and Ableton together don't work well in macOS Monterey/M1 and are the culprit.

I updated to 2.8.1 and it still crashes immediately when loading certain presets.

Sending the crash report to support but with not much hope.

I made sure to remove the midi device so this is not the issue.

Of course if I load an instance of Falcon alone in a empty project it will work (so far no crash) but that's pointless.

As soon as I get busy in a project it will crash sooner or later, making it unworkable.

I have 700 other vsts and none of them do that.

I'm thinking of moving to Logic if Ableton will never work properly with Falcon but that's an extreme solution. I'm not ready to throw years of getting used to a DAW just for a plugin.

Maybe I should give it another try when macOS Ventura is out next month? Stability issue related to Apple perhaps?

What is your ticket number ?

Thanks

Thanks. So actually I'm holding off, since it only seems to happen with the usual culprit librairies (Program 24, Super 7...) which I already filed a ticket for a couple months ago, and as a result support sent me an update which they later implemented in the UVI Portal too. I really didn't use Falcon afterwards so I thought they had fixed it, but it looks like it's still an issue on M1 Macs.

I suspect these librairies are an issue because they have drum sequencers in it, which Ableton doesn't seem to be able to manage. Maybe it's an internal midi signal conflict or smth inside of the Ableton code (Max?) vs. Falcon one - I don't know I'm not a developer it's just an intuition.

Or maybe it's an issue with Ableton not liking librairies on an external hard drive. But that can't be true because a couple months ago I already had the issue with the librairies on my internal SSD MacBook drive. So I think no relationship here.

So I just deleted/reinstalled these one culprit librairies I'm suspecting - again, one more time - to make sure it's a very clean install. So far today I had no conflict in new projects but these are simple projects with just one instance of Falcon in it. Maybe if I load another Falcon instance in it, it will crash - probably because of the internal Midi issue related to Ableton/UVI not understanding each other with multiple UVI sequencers conflicting.

I'm scared of adding more than one instance in my new projects, because when it crashes I can't open my projects anymore, and they're gone. My only hope then is to go to > Archive and find the latest working project without a Falcon-corrupted instance in it. Lots of time wasted in my creative process, but at least Ableton keeps the last 10 auto-saved copies thankfully. Now I immediately bounce audio with UVI instances, because it made me paranoid to lose the sound I'm developing.

Today I have downloaded all the latest librairies, some of which I had not downloaded yet previously, so I guess I will keep myself busy with the new librairies and avoid the culprit librairies mentioned above, a bit frustrating, but at least I seem to avoid the crashes this way.

I kept a copy of the last crash report in Word from 2 days ago just for archive purpose, and will write a new ticket shall their be a conflict arising. So far so good, fingers crossed, let's hope it holds...

[Fleer]

Falcon updated to 2.8.1 on Monterey with Bitwig and all’s well.

[chroma]

I did play with mine some more - it looks like it's that falcon intercepts the (laptop) keyboard when doing certain things - i can reproduce it pretty readily when using the laptop keyboard to enter notes, but piano roll notes don't have the same behaviour. That seems pretty minor, not sure what it is but it's not something that affect much normal use.

[collider]

Granulizer FX:

It would be nice if the Density value could go below 1.00 something like 0.10 would be great.

[otristan]

@spnc
What is the ticket id of your soundbank issue ?
If you want me to get to the bottom of this, you need to give me some info.

[spnc]

@spnc
What is the ticket id of your soundbank issue ?
If you want me to get to the bottom of this, you need to give me some info.

Like I said I'm not writing a new ticket yet, since I've not been working in projects where there could potentially be a crash these last couple days. But thank you this is well noted, shall there be a new crash in the near future I will send the Ableton crash report in Word to support and will notify you here.

Also, a minor thing: since 2.8.1, SoundCloud previews of each bank don't show up in UVI Portal > detail of each soundbank > SoundCloud > it's just the SoundCloud logo. Would be nice to fix. Cheers.

[rasmusklump]

You wrote that you have opened at least two tickets and you can't provide a ticket number?

[spnc]

You wrote that you have opened at least two tickets and you can't provide a ticket number?

No. That was a long time ago.

[otristan]

You wrote that you have opened at least two tickets and you can't provide a ticket number?

No. That was a long time ago.

I meant the one where you say
I updated to 2.8.1 and it still crashes immediately when loading certain presets.
Sending the crash report to support but with not much hope.

<-- do you have that one ?