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

[ThomasHelzle]

mixer... its a little too easy to delete a part... I accidentally deleted a part by using the minus button next to the master, which I thought was going to remove the FX I put on it , no warning, bang it was gone (unsaved) ... I didn't mind as i was still just experimenting...
I would say, if you try to delete a part which is not saved, you should be warned

+1 on this.

But the bigger issue that I think should be addressed is that this thread is too long and unwieldy to be an effective place to log feature requests. In fact, given how enthusiastic the community clearly is about Falcon, isn't it time for UVI to have its own KVR subforum? If so, then a moderated feature request sticky thread could be of benefit to all, especially UVI.

+1+1

+1 for both!

[Sampleconstruct]

Instant incense sticks - combining multi-granular with the pluck synth, both oscillators use the same long harmonic drone derived from vocal harmonics, I was just hitting some random notes while demonstrating the controls and modulators, so it's not a musical piece as such.

[Sampleconstruct]

quick question cos i am a bit thick today:

when assigning macros
how can i adjust the range to each target control?

dave

Here is a little quick and dirty tutorial (no voice-over) on setting Macro values:

[JonSolo]

I don't know if this has been asked, but has anyone been able to map Falcon in Ableton Live?

[evilantal]

I'm having an issue with the patch "Granular Ebow".

I'll have a look what I programmed there tomorrow morning. Sounded fine when it left the house.

Maybe it's the aftertouch assigned to grain position as I often do, so if you trigger the aftertouch with high velocities you will hear a glitch.

I didn't realise it was one of yours, Simon. It's a great sound, that's why I'd like to play it click-free

I don't think it's to do with aftertouch, because I was playing with a board without aftertouch capabilities.

[otristan]

this script and others (e.g. invert pitch) give me the error (in lua console)

Code: Select all

[string "uvi.wrapper"]:121: input should be in the range [0;3]

after playing a few notes and then the midi stream appears to be dead.
(well at least no more notes play without removing/reloading script)

EDIT: in fact pretty much every script gives me errors after playing a couple of notes

Do you just play or have you made a script that feed another one ?

[otristan]

Found a very interesting bug in the organ module.

Assign mod wheel to the percussion harmonic. Set the initial value to 16' set mod wheel so that moving it to the max position changes value to 4'. Play with mod wheel at lowest position. Percussion harmonic is at 16'. Move mod wheel up to top and play and percussion harmonic is now at 4'. Now, take the mod wheel and bring it back down to the bottom and play. The percussion harmonic does not go back down to 16'. It stays at 4'.

And this continues with each move of the mod wheel until eventually the percussion harmonic just gets stuck at 1'.

All other parameters, as far as I can tell, when the mod wheel is brought back down to its lowest value, the parameter also goes down to its original value, i.e. filter cutoff.

Either percussion harmonic doesn't work the same way or this is an odd bug.

Fixed in next version

Thanks for the report.

[otristan]

mixer... its a little too easy to delete a part... I accidentally deleted a part by using the minus button next to the master, which I thought was going to remove the FX I put on it , no warning, bang it was gone (unsaved) ... I didn't mind as i was still just experimenting...
I would say, if you try to delete a part which is not saved, you should be warned

+1 on this.

But the bigger issue that I think should be addressed is that this thread is too long and unwieldy to be an effective place to log feature requests. In fact, given how enthusiastic the community clearly is about Falcon, isn't it time for UVI to have its own KVR subforum? If so, then a moderated feature request sticky thread could be of benefit to all, especially UVI.

+1+1

+1 for both!

Sorry guys but this won't happen.

You guys can talk about Falcon, I will try to answer when I can, but KvR is not an official support channel.
We have a proper support channel and it's done trough our website.
If there was an UVI subforum, people would expect to get support from it, and we don't have time to do that on top of our official support.

Sorry about that.

[thetechnobear]

this script and others (e.g. invert pitch) give me the error (in lua console)

Code: Select all

[string "uvi.wrapper"]:121: input should be in the range [0;3]

after playing a few notes and then the midi stream appears to be dead.
(well at least no more notes play without removing/reloading script)

EDIT: in fact pretty much every script gives me errors after playing a couple of notes

Do you just play or have you made a script that feed another one ?

Just play, using any of your scripts.

Note: often I don't get any console output , it just gets a red border and whole part stops playing

[ThomasHelzle]

mixer... its a little too easy to delete a part... I accidentally deleted a part by using the minus button next to the master, which I thought was going to remove the FX I put on it , no warning, bang it was gone (unsaved) ... I didn't mind as i was still just experimenting...
I would say, if you try to delete a part which is not saved, you should be warned

+1 on this.

But the bigger issue that I think should be addressed is that this thread is too long and unwieldy to be an effective place to log feature requests. In fact, given how enthusiastic the community clearly is about Falcon, isn't it time for UVI to have its own KVR subforum? If so, then a moderated feature request sticky thread could be of benefit to all, especially UVI.

+1+1

+1 for both!

Sorry guys but this won't happen.

You guys can talk about Falcon, I will try to answer when I can, but KvR is not an official support channel.
We have a proper support channel and it's done trough our website.
If there was an UVI subforum, people would expect to get support from it, and we don't have time to do that on top of our official support.

Sorry about that.

Well, you could do it like Bitwig: Have a forum here, drop in every now and then but make it clear in a sticky that the forum is intended for interaction between users first and foremost and that all bug reports and feature requests should go to the tech support form on the website.

In my view UVI enters a new state of being ATM.
From a mostly sample library based company with a free player, you now turn into a major software vendor. Sparkverb and Relayer were already great, but didn't need much inter-user-communication.

Falcon on the other hand - in my recognition - is a major player in the plugin world.
It has huge depth, tons of features, is extremely flexible and allows the same things to be done in a dozen ways. For the beginner it can be overwhelming and some areas aren't exactly obvious. Users will create presets, want to share ideas, scripts, sounds etc.

- Having a healthy community surrounding the plugin will be as important for it's long-term-success as constant development, quick bugfixing, good library support etc.

- A forum can take away a lot of stress from support, when users can solve common problems within the community. Like in this thread, certain questions will come up over and over. A sticky FAQ thread can help a lot there.

- Good tech-support is great, but not creative. So while it can solve "how do I save programs with samples" it can't solve "what are the best ways to use the grain sampler" or "look what I did this morning".
Sure you can offer tutorials etc. but if you don't grow a community for a sound-creation-workstation like Falcon, you miss out on a huge potential.

- And yes, forums are messy and can get bad without a certain amount of moderation, but at the same time, many users thrive on forums for inspiration, questions and communication and neither standard support nor videos can offer that.

Again, from your side it may seem as if not so much is changing since you developed Mach Five already and Falcon isn't that different, but from the outside, UVI suddenly is a major player on a level with some of the biggest companies in the industry.
Mach Five never really took off as far as I could see (not to it's full potential at least) and Falcon has the ability to change that.
But this will also change how UVI is seen and what UVI has to think about.

Relayer for instance was hot on KVR for a relatively short time, then it didn't show up much anymore.
An UVI subforum here would get it back into everybody's view every now and then, people could post examples or patches they did for it etc.
For Falcon, multiply this by 500

I hope you will change your mind

Cheers,

Tom

[otristan]

Just play, using any of your scripts.

Note: often I don't get any console output , it just gets a red border and whole part stops playing

This happens when there is an error.
Does this happens when used in a DAW ?
What is your MIDI keyboard ?

I suspect something very specific in your configuration but don't understand yet what it is.

Thanks !

[otristan]

Well, you could do it like Bitwig: Have a forum here, drop in every now and then but make it clear in a sticky that the forum is intended for interaction between users first and foremost and that all bug reports and feature requests should go to the tech support form on the website.

In my view UVI enters a new state of being ATM.
From a mostly sample library based company with a free player, you now turn into a major software vendor. Sparkverb and Relayer were already great, but didn't need much inter-user-communication.

Falcon on the other hand - in my recognition - is a major player in the plugin world.
It has huge depth, tons of features, is extremely flexible and allows the same things to be done in a dozen ways. For the beginner it can be overwhelming and some areas aren't exactly obvious. Users will create presets, want to share ideas, scripts, sounds etc.

- Having a healthy community surrounding the plugin will be as important for it's long-term-success as constant development, quick bugfixing, good library support etc.

- A forum can take away a lot of stress from support, when users can solve common problems within the community. Like in this thread, certain questions will come up over and over. A sticky FAQ thread can help a lot there.

- Good tech-support is great, but not creative. So while it can solve "how do I save programs with samples" it can't solve "what are the best ways to use the grain sampler" or "look what I did this morning".
Sure you can offer tutorials etc. but if you don't grow a community for a sound-creation-workstation like Falcon, you miss out on a huge potential.

- And yes, forums are messy and can get bad without a certain amount of moderation, but at the same time, many users thrive on forums for inspiration, questions and communication and neither standard support nor videos can offer that.

Again, from your side it may seem as if not so much is changing since you developed Mach Five already and Falcon isn't that different, but from the outside, UVI suddenly is a major player on a level with some of the biggest companies in the industry.
Mach Five never really took off as far as I could see (not to it's full potential at least) and Falcon has the ability to change that.
But this will also change how UVI is seen and what UVI has to think about.

Relayer for instance was hot on KVR for a relatively short time, then it didn't show up much anymore.
An UVI subforum here would get it back into everybody's view every now and then, people could post examples or patches they did for it etc.
For Falcon, multiply this by 500

I hope you will change your mind

Cheers,

Tom

I understand your point and in a a perfect world, I would agree plenty.
The problem is that most people do not read sticky thread and some would
wait for proper support there and bitch about it if there none. We don't want that.

[sugo]

Well, you could do it like Bitwig: Have a forum here, drop in every now and then but make it clear in a sticky that the forum is intended for interaction between users first and foremost and that all bug reports and feature requests should go to the tech support form on the website.

In my view UVI enters a new state of being ATM.
From a mostly sample library based company with a free player, you now turn into a major software vendor. Sparkverb and Relayer were already great, but didn't need much inter-user-communication.

Falcon on the other hand - in my recognition - is a major player in the plugin world.
It has huge depth, tons of features, is extremely flexible and allows the same things to be done in a dozen ways. For the beginner it can be overwhelming and some areas aren't exactly obvious. Users will create presets, want to share ideas, scripts, sounds etc.

- Having a healthy community surrounding the plugin will be as important for it's long-term-success as constant development, quick bugfixing, good library support etc.

- A forum can take away a lot of stress from support, when users can solve common problems within the community. Like in this thread, certain questions will come up over and over. A sticky FAQ thread can help a lot there.

- Good tech-support is great, but not creative. So while it can solve "how do I save programs with samples" it can't solve "what are the best ways to use the grain sampler" or "look what I did this morning".
Sure you can offer tutorials etc. but if you don't grow a community for a sound-creation-workstation like Falcon, you miss out on a huge potential.

- And yes, forums are messy and can get bad without a certain amount of moderation, but at the same time, many users thrive on forums for inspiration, questions and communication and neither standard support nor videos can offer that.

Again, from your side it may seem as if not so much is changing since you developed Mach Five already and Falcon isn't that different, but from the outside, UVI suddenly is a major player on a level with some of the biggest companies in the industry.
Mach Five never really took off as far as I could see (not to it's full potential at least) and Falcon has the ability to change that.
But this will also change how UVI is seen and what UVI has to think about.

Relayer for instance was hot on KVR for a relatively short time, then it didn't show up much anymore.
An UVI subforum here would get it back into everybody's view every now and then, people could post examples or patches they did for it etc.
For Falcon, multiply this by 500

I hope you will change your mind

Cheers,

Tom

I understand your point and in a a perfect world, I would agree plenty.
The problem is that most people do not read sticky thread and some would
wait for proper support there and bitch about it if there none. We don't want that.

Please trust the communitiy, especially here on kvr.
I know a lot cases here in the forum, where other users told these special-ones you talk about, to write there issues to the developers support directly.
I agree with Tom, it would be a really big, more than 500, multiplier.
And i think you don`t have to be afraid about bitching, because you can`t prevent you from those in this digital unperfectly world, anyway.
For me it would be fine to know a forum where i can trade my experience, especially about such a complex software.
Please think about it.
best wishes and thanks for this amazing work

[thetechnobear]

Just play, using any of your scripts.

Note: often I don't get any console output , it just gets a red border and whole part stops playing

This happens when there is an error.
Does this happens when used in a DAW ?
What is your MIDI keyboard ?

I suspect something very specific in your configuration but don't understand yet what it is.

Thanks !

Yes, it appears if an LUA script fails, it puts a red border around module, and stops any further processing (of midi I assume?) - Im a bit confused as to why sometimes when this happens there are no messages in the console.

Happens if I send midi in from either my Virus, Push.
Only tested with Standalone (I assumed easier for you to test, less factors),
but I'll have a go with DAW now...

Other thing I will test is, if its due to me putting the part into omni... (which I do all the time, and need to)

fyi: Mac OSX 64 bit, 10.10.5

Note: forum, I think would be a good idea, and whilst I agree about the support/sticky comment, I suspect its not much different from peoples 'expectations' on a thread here. also I personally don't mind, if its here at KVR or on your own server (later will probably have more support expectation) I think a forum is a valuable addition for a more complex product, to allow users to share ideas.

[thetechnobear]

@oristan
odd Ive run up Falcon again today, and Im not getting the errors at all, Ive tried everything and all the things I did yesterday, and nothing breaks it.

my only 'guess' is that some how (and I don't know how) the LUA 'engine' got into a bad state and then this meant any script loaded caused the issue... this perhaps also explains why, initially I got console errors, and then later these also stopped (so perhaps that was affected by the corrupt state) - I thought I restarted Falcon, to see if the issues persisted but I cannot guarantee this (could just be in hindsight would have been a good idea )

anyway, all good now... if I manage to get into that state again, I will try to figure out what provokes it, as obviously until we have a reproducible scenario, going to be difficult for you to fix it