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

[EvilDragon]

@oristan

I am really getting sick of updating falcon sound banks. I just purchased the ngoya harp and opened up the portal to install it.

Theres 60GB of updates waiting for me????????

When in the hell are you going to join the rest of us in the 21st century and stop just replacing huge soundbanks when there is a change and just ship a diff file.

How you can manage to code something as big and beautiful as falcon but you still insist in using up my download allowance for the month is bloody beyond me. Fix it.

Soundbank are encrypted hence the difficulty to do only partial update.
We need to find a solution for this but this is not trivial.

We hear you though.

The solution is to separate the samples from the instrument files, have only samples in the monolith, just like a number of other samplers do.

Then, considering Falcon uses single file image mounting as a procedure to use the library, you should have something like a CUE file when you create an audio CD image, which would also be mountable, and would contain references to the instrument files and sample monoliths.

In case of instrument data update you would only have to update the actual instrument files and CUE file, which is super small and fast to download. In case of sample fixes, you would have additional small monolith(s) with new samples, which doesn't require overwriting the original huge monolith, and is also smaller and faster to download. All this ends up in better user experience.


Doesn't sound that complicated to me, but you guys know your framework better than me, that goes without saying. However, does my idea here seem feasible?

[liv]

What has happened to the "edit modulation" entry for macro knob edits?

Try:
1. Right click attack knob on a envelope and choose "Assign to macro/add new macro".
2. Right click again on attack knob and see the entry "Edit modulation" is greyed out.

Bug?

Macro are program only so modulation would be only LFO and stuff like that.
Is this what you wanted to achieve ?

Using the example above:
In earlier versions you could right click the attack knob and choose "Edit modulation" and the macro knob would pop-up. Easy to access and edit the ratio, offset etc.

See?

[otristan]

@oristan

I am really getting sick of updating falcon sound banks. I just purchased the ngoya harp and opened up the portal to install it.

Theres 60GB of updates waiting for me????????

When in the hell are you going to join the rest of us in the 21st century and stop just replacing huge soundbanks when there is a change and just ship a diff file.

How you can manage to code something as big and beautiful as falcon but you still insist in using up my download allowance for the month is bloody beyond me. Fix it.

Soundbank are encrypted hence the difficulty to do only partial update.
We need to find a solution for this but this is not trivial.

We hear you though.

The solution is to separate the samples from the instrument files, have only samples in the monolith, just like a number of other samplers do.

Then, considering Falcon uses single file image mounting as a procedure to use the library, you should have something like a CUE file when you create an audio CD image, which would also be mountable, and would contain references to the instrument files and sample monoliths.

In case of instrument data update you would only have to update the actual instrument files and CUE file, which is super small and fast to download. In case of sample fixes, you would have additional small monolith(s) with new samples, which doesn't require overwriting the original huge monolith, and is also smaller and faster to download. All this ends up in better user experience.


Doesn't sound that complicated to me, but you guys know your framework better than me, that goes without saying. However, does my idea here seem feasible?

Don't worry, we do our homework.

[otristan]

What has happened to the "edit modulation" entry for macro knob edits?

Try:
1. Right click attack knob on a envelope and choose "Assign to macro/add new macro".
2. Right click again on attack knob and see the entry "Edit modulation" is greyed out.

Bug?

Macro are program only so modulation would be only LFO and stuff like that.
Is this what you wanted to achieve ?

Using the example above:
In earlier versions you could right click the attack knob and choose "Edit modulation" and the macro knob would pop-up. Easy to access and edit the ratio, offset etc.

See?

It still work. It's only enabled when there is already an available connection though.
So you need to create it first then use edit modulation if you want to edit if further.

[liv]

What has happened to the "edit modulation" entry for macro knob edits?

Try:
1. Right click attack knob on a envelope and choose "Assign to macro/add new macro".
2. Right click again on attack knob and see the entry "Edit modulation" is greyed out.

Bug?

Macro are program only so modulation would be only LFO and stuff like that.
Is this what you wanted to achieve ?

Using the example above:
In earlier versions you could right click the attack knob and choose "Edit modulation" and the macro knob would pop-up. Easy to access and edit the ratio, offset etc.

See?

It still work. It's only enabled when there is already an available connection though.
So you need to create it first then use edit modulation if you want to edit if further.

Formerly when you right click and choose "Assign to macro/add new macro" this automatically enabled the connection.

To make that possible now you need an extra assignment procedure. Go through the menu twice. And then the third time you have access to pop-up the macro knob.

1. Right click attack knob, select "Assign to macro/add new macro".
2. Right click attack knob, select "Add modulation/Program/Attack [MACRO]

3. Right click attack knob, select "Edit modulation". Now it pops up and you can do the direct edits ratio, offset etc.

[otristan]

The rationale was to avoid confusion with an Edit modulations option although there was none.

[EvilDragon]

Don't worry, we do our homework.

I did not imply that you don't

Though, it's great that you're on the case of solving this pain point, at last!

[otristan]

Dear Mario,

I could use less advice and snarky comments from you.

Thanks !

[EvilDragon]

Sorry if you misunderstood me, I wasn't even trying to be snarky at all. :/ If something came out that way, my apologies, but this wasn't the intention.

[liv]

The rationale was to avoid confusion with an Edit modulations option although there was none.

Thanks. I see the logic, but the workflow in this case got worse.
Any chance bringing it back? Or any other suggested approach?

[otristan]

Sorry if you misunderstood me, I wasn't even trying to be snarky at all. :/ If something came out that way, my apologies, but this wasn't the intention.

The think is that you tend to imply that all those stuff are a simple matter of programming as you have come up with the idea in 5 min but the issue is more complex as you need to handle the server code side that does the update in a rsync style and all kind of funny stuff that thinking about it 5 minutes would not reveal.
So this implies that we are either stupid, lazy or whatever. As a CS student yourself you should know better, so please refrain yourself (and this is not the first time)

You seemed more nice with N.I stopping to authorise their old product. That shouldn't be hard either and there are plenty of employees there, right ?

Anyway...

[otristan]

The rationale was to avoid confusion with an Edit modulations option although there was none.

Thanks. I see the logic, but the workflow in this case got worse.
Any chance bringing it back? Or any other suggested approach?

Yep. Sure. Will remove it from the next build.

[EvilDragon]

The think is that you tend to imply that all those stuff are a simple matter of programming

Everything in software is a matter of programming, but of course nothing is ever too simple! I did not use the word "simple" anywhere in my post, and I also deferred to you guys knowing your framework better than me (which is of course obvious and beyond questioning - nor did I attempt to question that!) - I did not imply at all that this is a 1 hour job. Really sorry if it turned out that way - I am indeed aware there's a server-side to this all, and those things are usually much worse than just straight out making a program work.

So this implies that we are either stupid, lazy or whatever.

Well, no, to me this sounds like you read way too much into my post, because I did not imply any of that whatsoever. Again really sorry if it turned out that way, but that was not my intention in the slightest.

EDIT: I see now that I wrote "doesn't seem that complicated to me", and I can see how that could have spurred you on. Well, I won't backtrack on what I said, as it was an honest mistake, I will just own it like a battle scar and apologize. Again, nothing is ever really easy, I am well aware of that (you wouldn't believe what REALLY lies beyond NI's old products activation situation...)

Come on, Oli, there is no need for this sort of back and forth here, I would've thought you knew me better by now. While my allegiance is pretty obvious and has been known for years, this does NOT mean I don't adore and use the hell out of many other virtual instruments, a number of which is yours, too (and also you can see that I'm not at all chasing NFRs either, I'm also a buyer of your stuff)! Which is to say, as always I wish you guys the best and if anything can ultimately improve user experience regarding your product update procedures, I welcome it!



(I would have used a beer cheers emoticon, but this is on another forum )

[otristan]

Don't worry. No hard feeling.
I'm probably pissed off a bit as well because of corona virus lockdown in my area...

[liv]

Just noticed Slice module, envelope AHDS faders cannot be assigned to macro or modulation.
Is this by design?