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

[SJ_Digriz]

Pray for multicore.

Not that sure it would bring the gains that people are projecting.

For a true multi it could

[machinesworking]

Pray for multicore.

Not that sure it would bring the gains that people are projecting.

For a true multi it could

I don't really get the desire here? Only some plug ins can use more than one core when instantiated and Kontakt for instance isn't one of them. I've had DAW developers tell me outright that in order to even the load, instead of loading 16 heavily scripted libraries into a single Kontakt plug in, it's best to instantiate multiple plugins on several tracks. At leas on Mac here, NI explicitly state that multi core support for Konakt is not meant to be used when it's instantiated as a plug in, in a DAW etc. Even Diva is hit or miss with multi core, there are times and DAWs where it doesn't work.

[Jorisma]

A mí todo lo contrario, no me gustó para nada el sound factory y los sonidos preestablecidos, y mucho menos los que trajo la v2.5

[rasmusklump]

Upl glll grnft mpfuflmot rnnntz wqtfghjv zhbznüüph

[trusampler]

Dear UVI,
Is there still no option to assign a midi controller to switch/change presets? Do we really have to use a mouse and keyboard to sort thru the thousands of presets you sell..

[WatchTheGuitar]

Efff eff efff eff heth efff eff eff Chris Waddle

[ChamomileShark]

Efff eff efff eff heth efff eff eff Chris Waddle

Shouldn't that be "Efff feff fefff feff heth fefff feff feff Chris Waddle"?

Let's not butcher the language here.

[otristan]

- Random modulator from different "seed". Currently all random modulator affect same
level.

The new Smooth Random should help you to do that. Just use a 0 hz freq

- ADSR with curve control (concave and convex).

You can already change it on the UI of the regular ADSR

[otristan]

Not sure, whether this is possible already, I would love to see improvements in preset managment:

- Show only favorites, best would be a separate main tree node

Just click the favorite column so favorite are listed first.

[EvilDragon]

Only some plug ins can use more than one core when instantiated and Kontakt for instance isn't one of them.

Yes it is, Kontakt supports up to 16 core multiprocessing, in standalone and in plugin mode. Now of course, some DAWs will be fussy about it, while others will work just fine with it. In general, it does help across the board, from my experience.

[WatchTheGuitar]

Efff eff efff eff heth efff eff eff Chris Waddle

Shouldn't that be "Efff feff fefff feff heth fefff feff feff Chris Waddle"?

Let's not butcher the language here.

You're probably right. Long time since I spoke it, in a hole, with an owl!

[machinesworking]

Only some plug ins can use more than one core when instantiated and Kontakt for instance isn't one of them.

Yes it is, Kontakt supports up to 16 core multiprocessing, in standalone and in plugin mode. Now of course, some DAWs will be fussy about it, while others will work just fine with it. In general, it does help across the board, from my experience.

So it always pops up with this warning on any DAW here: "Please note that enabling multi-processor support in both your host and Kontakt can lead to audio problems."

Then there's this recent thread.
https://www.native-instruments.com/foru ... kt.446111/

Almost all threads on it recommend not having multi processor support on both your DAW and Kontakt. Seems to me that multiple instances is much safer for most people than multiple applications trying to distribute to multiple cores etc.

So it seems to me to be something that works for some people on some systems. It's definitely a case where I wish NI would name and shame, or better laud the DAWs/configurations that do work with multiprocessor support instead of it being trial and error. So it's still basically a feature that only certain configurations are using without issues from my perspective.

[EvilDragon]

Sure, as I said some DAWs are more fussy than others. Never had issues with that option in Reaper, FWIW - it does reduce RT CPU usage, which is good on the whole.

[rasmusklump]

In Cubase there also are no problems with multicore plugins

[sircuit]

Pray for multicore.

Not that sure it would bring the gains that people are projecting.

With multicore enabled I can run quite a bunch of Divas without clicks and pops. As soon as I disable the multi option, everything cracks and pops. It may not help a huge lot, but is enough to have a clean audio so it worth having a properly implemented multicore option. That is, if they manage to do it as uhe did