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

[Sampleconstruct]

But, it would be nice if the CC assignment for macros was saved with the patch as an option.

You can hard-wire CCs in the modulation assignment, that way they will be saved with the patch (in opposition to assigning CCs to Macros via right click).

[acYm]

hold on. from what I can see in the manual, the 128 automation parameters that Falcon displays to the host are all un-wired, to be freely assigned by the user. to automate a macro knob, even the main 8, the same right click procedure to assign an ID as all other controls applies. is that correct or?

[padillac]

You can right-click on a macro knob and then "assign to host automation". Then if you select a different patch, the corresponding macro knob in the new patch will still be assigned to the same host automation.

[SJ_Digriz]

But, it would be nice if the CC assignment for macros was saved with the patch as an option.

You can hard-wire CCs in the modulation assignment, that way they will be saved with the patch (in opposition to assigning CCs to Macros via right click).

Right, I think I said that earlier on that you can assign CC to automation didn't I? I probably explained it poorly. I'm simply saying that it would be nice if you could do that with the macros somehow like Halion QC. It's not life/death. And, it may even be too much abstraction to the control. One of those things that sounds good until you actually try to do it.

EDIT: And, since I work primarily in Cubase and VEP, doing automation mapping to my controller has not been a huge issue, other than the macro configurations being slightly annoying.

[aMUSEd]

yeah that wasn't clear, I edited.
if you can't assign the macro section to a controller via automation

this part you can do

(in a way that remains fixed throughout the library)

This part you would have to do yourself based on the patches you want to use for a set.

So it isn't useless IMO, it just means you have to do some work once you find the patches you want to use. Again, it's the price we pay for a very, very flexible architecture.

The one ask would be a mapper system similar to Halion .. heck it may be hidden in there somewhere and I just don't know it. But, we still would need the authors to do the "default" map like they did for NKS.

However, I still think it's worth it to just map your own controller to the patch macros you want to use. The thing is, the macros aren't necessarily the same from patch to patch like they are on a synth. So, the idea of a "default" controller map is not viable.

Maybe not but at the moment there's not even any consistency to how automation params are assigned to macros. For example I can assign param 1 to the first knob in a macro page only to find in the next preset I open it is somewhere in the middle. At least they need to give some thought to making the links between hardware controllers and the plugin more reliable. At the moment it's only really possible to create controls on a patch by patch basis which would take a very long time. I do understand that it is flexible but I also think they could have given this aspect more attention and thought, Alchemy was also flexible but performance was built into the design of the plugin from the start, as it should be in the design of any instrument really.

[EvilDragon]

For example I can assign param 1 to the first knob in a macro page only to find in the next preset I open it is somewhere in the middle.

That's all a matter of how macros are positioned on the interface, no?

Also, sometimes macro 1 can be a knob, sometimes it's a button. It all depends.

[jancivil]

But, it would be nice if the CC assignment for macros was saved with the patch as an option.

You can hard-wire CCs in the modulation assignment, that way they will be saved with the patch (in opposition to assigning CCs to Macros via right click).

It's not life/death.

And, since I work primarily in Cubase and VEP, doing automation mapping to my controller has not been a huge issue, other than the macro configurations being slightly annoying.

So it exposes all automatable parameters to VE Pro?

[EvilDragon]

No, it's like in Kontakt or Reaktor, you first need to decide which parameters will be exposed to the host. You have up to 128 available slots for that.

[acYm]

Maybe not but at the moment there's not even any consistency to how automation params are assigned to macros. For example I can assign param 1 to the first knob in a macro page only to find in the next preset I open it is somewhere in the middle. At least they need to give some thought to making the links between hardware controllers and the plugin more reliable.

Does it update the parameter names of the macro knobs when you change presets by any chance?

[aMUSEd]

Don't know - I kindof gave up in frustration.

[jancivil]

No, it's like in Kontakt or Reaktor, you first need to decide which parameters will be exposed to the host. You have up to 128 available slots for that.

Well, Kontakt and Reaktor (and Absynth and...) automatically expose all automatable parameters to VE Pro.
It may be that everything that has automatable parameters is seen by VE Pro, but I don't know for certain.

[padillac]

Does it update the parameter names of the macro knobs when you change presets by any chance?

No, at least not in Renoise. And I don't think in Falcon either. Here's an example:

* load a preset
* right-click a macro (called e.g. "Grain Speed" and choose "assign to host automation 1"
* Renoise's instrument automation device will show "Grain Speed" in the first slot
* Falcon VST's tree view will show "Grain Speed" in Master/Automation
* Change your patch, and Falcon / Renoise will both still show "Grain Speed", even though the automation will affect a macro knob with a different name.

[acYm]

well darnit. that's too bad. I'd be willing to accept the freeform nature of the macro section and the resulting random mess with automation controller assignments if at least you could see the params...

[SJ_Digriz]

But, it would be nice if the CC assignment for macros was saved with the patch as an option.

You can hard-wire CCs in the modulation assignment, that way they will be saved with the patch (in opposition to assigning CCs to Macros via right click).

It's not life/death.

And, since I work primarily in Cubase and VEP, doing automation mapping to my controller has not been a huge issue, other than the macro configurations being slightly annoying.

So it exposes all automatable parameters to VE Pro?

Like ED said, you use the host mapper function of VEP.

[SJ_Digriz]

@otristan hey, I've been playing with the new envelope and I'm getting a consistent crash on some MIDI snippets. For example I have a Blues Drums library that has a variations on shuffle folder. Some of the files cause a crash every time I drop them in. Others from the same set have no problem. I can't see a difference. Is there some limitation you know about?

EDIT: This is just stand alone .. haven't tried it in a host yet.