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

Echoes in the Attic wrote:
otristan wrote:There was a typo in my latest MPE script.

Here is a fixed version
http://we.tl/LTl2QhB9YD

@Echoes in the Attic
This should fix your issue.

Thanks for your demo project.
Working great now, thanks!
Whats about pitch range? Is 24 semitons (by default in script) do not match with bitwig piano roll pitch envelope. Seems bitwig bisects value of pitch range. In this way pitch range value should be is 48 semitones. I've already sent a bug report to bitwig. Correct me if I'm wrong.

Post

mrfrenkie wrote:
Echoes in the Attic wrote:
otristan wrote:There was a typo in my latest MPE script.

Here is a fixed version
http://we.tl/LTl2QhB9YD

@Echoes in the Attic
This should fix your issue.

Thanks for your demo project.
Working great now, thanks!
Whats about pitch range? Is 24 semitons (by default in script) do not match with bitwig piano roll pitch envelope. Seems bitwig bisects value of pitch range. In this way pitch range value should be is 48 semitones. I've already sent a bug report to bitwig. Correct me if I'm wrong.
There is pitch bend range setting on the falcon script GUI. By default it is 24, but it can be changed to 48, which is necessary for bitwig's touch screen note grid to pitch bend correctly. But it's good to send the request to bitwig to allow other pitch bend ranges since that is very limiting for other synths that can'tg o up to 48.

Post

Falcon 1.0.7 is up.

Official announcement will follow later today.

Here is the changelog
- fix regression with legato multi point envelope introduced in 1.0.4
- fix issue with Guitar Boxes under Reaper
- allow edit of oscillators in multi selection
- fix possible crash when deleting mapper
- fix noise when activating filters in UVI Drive and Double Drive
- fix crash when adding Granular oscillator using Tree view
- fix crash when adding MIDI player in Edit view
- fix sample start handling in Sample oscillator
- allows right click on module tab to change their type (similar to long press behavior)
- fix potential crash in script processor when launching lots (100000+) of asynchronous commands
- fix possible issue with Mono Retrigger mode
- rotary FX improvements
- fix for scala keyboard mapping (.kbm) with 0 size

Enjoy !
Olivier Tristan
Developer - UVI Team
http://www.uvi.net

Post

:tu:

Thanks Olivier!

Cheers,

Tom
"Out beyond the ideas of wrongdoing and rightdoing, there is a field. I’ll meet you there." · Rumi
UrbanFlow.art · Instagram · YouTube

Post

Thanks, do I need to run the REX installer in the extras folder? What is it for?

Post

REX installer is not mandatory but allows to support REX file
(The loop format from propellerheads Recycle https://www.propellerheads.se/recycle)
Olivier Tristan
Developer - UVI Team
http://www.uvi.net

Post

Okay, thanks.

Post

New video: Stretch, Scrub and Granular Tutorial

Olivier Tristan
Developer - UVI Team
http://www.uvi.net

Post

Thanks for the update, and thanks also for that new tutorial movie. The voice is much better understandable now and boy, he knows his stuff!
I learned a lot (will have to watch it again...)
Windows 7, Cubase 9.5 and some extra plug-ins | Takamine EN-10C and PRS Mira

Post

Thanks for the update and tutorial..
waves break, but somehow it all makes sense.

Post

Nice update and video.

I have to mention one thing that I find quite confusing about the falcon layout, which is that in the edit view and the tree view, effects are at the top and the oscillators below so the signal flow is generally upwards. However in the tree view this is only true for the program and layer levels and then when you get to the keygroup level it goes oscillator and then effects underneath. The inconsistency just kind of throws me off. Does anyone else feel this way?

Post

Hello

Having a touch of trouble with v1.0.7, thought someone might shed some light on the situation. I am getting a warning in Logic upon loading a project with Falcon 1.0.6 in the project.
Logic Falcon.jpg

The AU is indeed installed correctly, the standalone functions correctly and Live 9.6 "sees" and loads the AU correctly. Any Ideas would be appreciated.
Restarted Logic , reinstalled the plugin and restarted the mac...no change.

Regards
Krzysztof
You do not have the required permissions to view the files attached to this post.

Post

krzys wrote:Hello

Having a touch of trouble with v1.0.7, thought someone might shed some light on the situation. I am getting a warning in Logic upon loading a project with Falcon 1.0.6 in the project.
Logic Falcon.jpg

The AU is indeed installed correctly, the standalone functions correctly and Live 9.6 "sees" and loads the AU correctly. Any Ideas would be appreciated.
Restarted Logic , reinstalled the plugin and restarted the mac...no change.

Regards
Krzysztof
I'm using logic X (latest version) on Yosemite, I don't have the same issue..
waves break, but somehow it all makes sense.

Post

krzys wrote:Hello

Having a touch of trouble with v1.0.7, thought someone might shed some light on the situation. I am getting a warning in Logic upon loading a project with Falcon 1.0.6 in the project.
Logic Falcon.jpg

The AU is indeed installed correctly, the standalone functions correctly and Live 9.6 "sees" and loads the AU correctly. Any Ideas would be appreciated.
Restarted Logic , reinstalled the plugin and restarted the mac...no change.

Regards
Krzysztof
Did you re-scan your plug-ins?

Post

bradkvr wrote:
krzys wrote:Hello

Having a touch of trouble with v1.0.7, thought someone might shed some light on the situation. I am getting a warning in Logic upon loading a project with Falcon 1.0.6 in the project.
Logic Falcon.jpg

The AU is indeed installed correctly, the standalone functions correctly and Live 9.6 "sees" and loads the AU correctly. Any Ideas would be appreciated.
Restarted Logic , reinstalled the plugin and restarted the mac...no change.

Regards
Krzysztof
Did you re-scan your plug-ins?


Thanks, that did it>>>!
Thanks.

Post Reply

Return to “Instruments”