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

[EvilDragon]

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

Hey, who wouldn't be?!

Stay safe, guys and girls!

[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?

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

The more I look at this... As they are two different things. Maybe add a menu option "Edit macro assignment" below "Assign to macro" is a better way to go?

[otristan]

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

Yep those are currently not modulable.

[liv]

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

Yep those are currently not modulable.

Is this possible to add?
I see endless use cases either in live performance or for automation purposes.

[otristan]

Would need to have a look.
In the meantime, I would advice to use mapped looped with MIDI file (could use the internal MIDI player) and regular AHD.

[rasmusklump]

nevermind, this guy is not worth it..

[c_voltage]

@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?

ED, if i right understand from your wrote, i don't think that it's a better idea have a bunch of little "update" files, it will add some mess.

Yes, I agree that there are some problems with server speed at times but i would prefer spend time and download them somehow, than spoil the "aesthetics" of the UFS folder, where one file = one library.

I think it will be easier (and more correct) to fix problem with the server.

[EvilDragon]

It doesn't really solve the problem of potentially huge downloads, which is an issue for people under metered connections or where flat rate is not an option...

[WatchTheGuitar]

I've got unlimited flat rate 450 Mb/s broadband and it pisses me off how long it takes so it must be brutal for people who aren't on fibre or are on metered connections. They don't even need to create a new file structure. Keep it monolithic and just make an updater available that amends the deltas. Have the UVI Portal take care of the process.

[rasmusklump]

ED, if i right understand from your wrote, i don't think that it's a better idea have a bunch of little "update" files, it will add some mess.

Yes, I agree that there are some problems with server speed at times but i would prefer spend time and download them somehow, than spoil the "aesthetics" of the UFS folder, where one file = one library.

I think it will be easier (and more correct) to fix problem with the server.

Exactly. The 1 File thing is one thing that I like about the UFS as well

[padillac]

Is there a way to “find all missing samples” across instances? I’m assuming not but thought I’d check...

Example: I have two separate falcon instances in a single DAW project. I renamed a sample folder. Now when I open the first Falcon, it shows the “find all missing samples” dialog. I locate the new samples folder and it fixes it. Then when I open the second falcon, it also shows “find all missing samples.” I would like locating the folder on the first falcon to also update the second falcon.

[Sampleconstruct]

Is there a way to “find all missing samples” across instances? I’m assuming not but thought I’d check...

Example: I have two separate falcon instances in a single DAW project. I renamed a sample folder. Now when I open the first Falcon, it shows the “find all missing samples” dialog. I locate the new samples folder and it fixes it. Then when I open the second falcon, it also shows “find all missing samples.” I would like locating the folder on the first falcon to also update the second falcon.

Unfortunately you have to do it for each program/multi.

[padillac]

k thanks for the info.

That's a bummer for me, because I like to keep project-specific samples in the DAW project folder. But I move those around a lot to reorganize things as I work on them, and it always breaks the Falcon sample references. That's not unique to Falcon of course. It would just be nice if there were a faster way to find and clean up broken references.

So far it appears that the necessary approach to audio file management is "name it, file it, and never change your mind, EVER." But I am a messy thinker, so getting the naming and filing 100% right from the very beginning is just not going to happen.

[padillac]

I may have come up with something useful... I found this tool diskDedupe to de-duplicate files on APFS volumes.

So hopefully what that means for me is, I can keep a folder for my sample library and move things around however I want. And when I save Falcon patches, save them with their samples, whatever they happened to be named at the time. And run this disk-dedupe tool to not waste a bunch of disk space saving the same samples over and over.

[otristan]

On OSX you can as well use hard links to achieve this.