Notifications
Clear all

Unifying UVI Falcon 2 Libraries

72 Posts
10 Users
7 Likes
3,081 Views
Bernd@PDX
(@berndpdx)
Trusted Member
Joined: 1 year ago
Posts: 82
Topic starter  

@getdunne Additionally, what is confusing, I can "MIDI learn" a Unify macro knob to listen to my hardware controller's knob at CC 22. I twist my hardware knob on CC22 and Unify macro knob will turn. But I also mapped Unify macro knob with "assign CC" menu to CC 14. Then I assign CC 14 to plugin macro knob. Now Unify macro knob turns when I turn hardware knob. But plugin macro does not move. When I move Unify macro knob with mouse, the plugin knob also moves. That feels very counter-intuitive.


ReplyQuote
Bernd@PDX
(@berndpdx)
Trusted Member
Joined: 1 year ago
Posts: 82
Topic starter  

Upon further investigation, and to save you time with troubleshooting, I should mention that I also have a control script (*.txt file) with mappings. And the static control mappings from the script seem to take precedence over the in-app (Unify) mappings. When I disabled the control scripts, the above described dynamic does not happen.


ReplyQuote
Bernd@PDX
(@berndpdx)
Trusted Member
Joined: 1 year ago
Posts: 82
Topic starter  

@eddrake I can't tell you which one is "advantageous" for your particular situation. But I thought I'd share this insight I just gained into Falcon...

 

MIDI CC assignments to Falcon macro knobs are saved with the Falcon "Program" (the individual instrument preset). While "Host Automation" assignments are only saved at the Falcon "Multi" level (ensemble of programs). 

So depending on whether you are more likely to use Falcon ensembles, or individual programs, one might be more useful than the other. 

Personally, I have learned to use only one program per Falcon plugin instance, since Falcon seems single-threaded and bottoms out CPU performance pretty quickly with more than one program loaded in its multi. Depends of course on the program, but the VOKLM soundbank presets are particularly challenging in that regard.


ReplyQuote
getdunne
(@getdunne)
Illustrious Member Admin
Joined: 3 years ago
Posts: 3574
 

@berndpdx

The problem is that there is no "standard mapping of the Unify knob macro CC numbers". Users are free to assign CC numbers to knobs however they wish, and will typically do so, because while one user's MIDI controller might easily produce CC's 1, 2, 4, and 67 (the ones chosen by Airwave for his libraries), another user might prefer CC's 14, 15, 16, and 17 because those are what the knobs on their NI Komplete Kontrol unit sends.


ReplyQuote
Hexabuzz
(@hexabuzz)
Estimable Member
Joined: 2 years ago
Posts: 124
 
Posted by: @getdunne

@berndpdx

The problem is that there is no "standard mapping of the Unify knob macro CC numbers". Users are free to assign CC numbers to knobs however they wish, and will typically do so, because while one user's MIDI controller might easily produce CC's 1, 2, 4, and 67 (the ones chosen by Airwave for his libraries), another user might prefer CC's 14, 15, 16, and 17 because those are what the knobs on their NI Komplete Kontrol unit sends.

As I was discussing this with Bernd outside of the forum, I am so new and inexperienced at this that I'm flying a bit blind as to what is or isn't a standard practice.

I just started assigning CC's 14, 15, 16, etc. because they were part of the Init patch defaults, so I assumed that it was done for some reason that was known to the Higher Powers than me (I'm not in any way trying to put this on you, Shane, as I said, I just assumed that it was done for some reason that I should follow along with).

I fully understand that everybody has their own preferences with controllers and setups, and I guess I just assumed that at least if you assign SOMETHING, it gives the end user a starting point for having the patch ready to go just as soon as they do a few quick cc assignments on their own equipment, rather than having to start assigning cc's in Unify from scratch, especially when some patches have so many (I found some in other Falcon libraries that have 28!).

I'm going to keep doing these patches as I have been, unless someone tells me to stop... I just want to do what's best for everyone.


ReplyQuote
Bernd@PDX
(@berndpdx)
Trusted Member
Joined: 1 year ago
Posts: 82
Topic starter  

@zinct & @hexabuzz & others involved in mapping Falcon 2 to Unify macros, I think I've found a useful short cut for this...

Since the Falcon 2 macro host automations are mapped in the Multi, and not at the Program level, you can create a template Multi with a "New Program", in which you can create a bunch of dummy Macros. Then assign Host Automations to them, just within Falcon, not related to Unify yet. Save the Multi as the default one that will load when you start Falcon 2. I started with 8 Falcon macro knobs, but you should do the max number in your soundbank preset list (a lot of the UVI soundbank presets have more than 8). Once you save the default multi with its 8 or more macro knobs pre-assigned to host automations, you can actually drag soundbank programs into that "New Program" template you create (not add, but overwrite, drag the preset into/over the existing New Program). This will make the preset "inherit" the templated macro knob host automation assignments, saving you the manual effort to remap each soundbank preset's macro knobs. Now the order of assignment is still sometimes non intuitive on a per-preset level, but that's a more nuanced problem. Let's see if this lets me share the default multi template here (see attached zip file)

UPDATE: One more thing you have to do to get this working...create a Unify patch as a template, with Falcon 2 loaded with this multi. Apparently the multi only saves the Host Assignments in a DAW/VST host context. So save a Unify patch with Falcon 2 and this template multi loaded. Make your Unify macro assignments to the Falcon program template knobs. Save the Unify patch again. And now you can replace the Falcon 2 template program with the actual soundbank presets. Then save the Unify patch under different names, aligned with the Falcon preset. The Unify macros should automatically map to the Falcon macros. Trying to share the .unify patch implementing what I just described, let's see if this works, let me know...


ReplyQuote
getdunne
(@getdunne)
Illustrious Member Admin
Joined: 3 years ago
Posts: 3574
 

@hexabuzz

Unify does not (yet) have an internal facility to modify MIDI CC messages before sending them to plug-ins. Therefore, if you set up Falcon so MIDI CC#14 controls, say, filter cutoff, then only CC#14 will be able to control that parameter.

Suppose a user's MIDI controller is unable to send CC#14 at all, so they want to use CC#100 instead (I chose that number at random.) Incoming CC#100 messages will be sent on to the plug-ins, including Falcon.

  • If one of Unify's macro knobs has a link to Falcon's filter-cutoff parameter, then the user can simply set that knob to respond to CC#100, and CC#100 will control the filter cutoff.
  • Otherwise, all that will happen is that their CC#100 messages will get passed into Falcon, but Falcon will either ignore them (because you didn't assign CC#100 to control anything inside Falcon), or worse, some other parameter will change (which you did assign to CC#100 inside Falcon).

This is why using links to specific plug-in parameters is preferred, because these directly reference parameter names, as opposed to MIDI CCs which are just numbers, and must be assigned manually. The user is free to change which CC's control each of Unify's macro knobs, but doing so won't magically change CC/parameter assignments set up inside a plug-in.


ReplyQuote
Hexabuzz
(@hexabuzz)
Estimable Member
Joined: 2 years ago
Posts: 124
 
Posted by: @getdunne

@hexabuzz

Unify does not (yet) have an internal facility to modify MIDI CC messages before sending them to plug-ins. Therefore, if you set up Falcon so MIDI CC#14 controls, say, filter cutoff, then only CC#14 will be able to control that parameter.

Suppose a user's MIDI controller is unable to send CC#14 at all, so they want to use CC#100 instead (I chose that number at random.) Incoming CC#100 messages will be sent on to the plug-ins, including Falcon.

  • If one of Unify's macro knobs has a link to Falcon's filter-cutoff parameter, then the user can simply set that knob to respond to CC#100, and CC#100 will control the filter cutoff.
  • Otherwise, all that will happen is that their CC#100 messages will get passed into Falcon, but Falcon will either ignore them (because you didn't assign CC#100 to control anything inside Falcon), or worse, some other parameter will change (which you did assign to CC#100 inside Falcon).

This is why using links to specific plug-in parameters is preferred, because these directly reference parameter names, as opposed to MIDI CCs which are just numbers, and must be assigned manually. The user is free to change which CC's control each of Unify's macro knobs, but doing so won't magically change CC/parameter assignments set up inside a plug-in.

I get it... 

 

That's why I was doing BOTH - using the linked parameter, as well as assigning a CC to a macro knob when needed (beyond those already assigned in the Init patch. I guess at least this way the end user may have to change a CC assignment in Unify, but the link to the Falcon function being controlled will still be intact because of the Linked Parameter. Correct?


ReplyQuote
getdunne
(@getdunne)
Illustrious Member Admin
Joined: 3 years ago
Posts: 3574
 

@hexabuzz

As long as you don't do anything inside Falcon, to make it require specific MIDI CC messages, you should be fine.


Hexabuzz reacted
ReplyQuote
Hexabuzz
(@hexabuzz)
Estimable Member
Joined: 2 years ago
Posts: 124
 
Posted by: @getdunne

@hexabuzz

As long as you don't do anything inside Falcon, to make it require specific MIDI CC messages, you should be fine.

Ok, last comment, I promise...

So...

 

DO used Assign Host Automation in Falcon to connect it to Linked Parameters with the Macro Knobs in Unify.

DON'T assign any MIDI CC's inside Falcon to those controls.

Let the MIDI CC's in Unify stay in the control of the end user, and the Macro knobs will still link up fine with Falcon because of the Linked Parameter.

 

Now I think I've got it.

 

Sorry for all the trouble, and thank you for all the help. As I said, I just want to do this right...


ReplyQuote
Bernd@PDX
(@berndpdx)
Trusted Member
Joined: 1 year ago
Posts: 82
Topic starter  

@hexabuzz I think this is a useful discussion, and perhaps some day this could be illustrated in the manual or a tutorial, as people will be mapping their plugins/macros, regardless of a joint "Unification" effort. It's an important feature in Unify and if we struggle to understand it, these hard-learn lessons are worth translating into broader user base understanding. Heck, maybe I should create one of my infamous tutorial videos, LOL


ReplyQuote
getdunne
(@getdunne)
Illustrious Member Admin
Joined: 3 years ago
Posts: 3574
 
Posted by: @hexabuzz

DO used Assign Host Automation in Falcon to connect it to Linked Parameters with the Macro Knobs in Unify.

DON'T assign any MIDI CC's inside Falcon to those controls.

Let the MIDI CC's in Unify stay in the control of the end user, and the Macro knobs will still link up fine with Falcon because of the Linked Parameter.

Yes, exactly.


Hexabuzz reacted
ReplyQuote
getdunne
(@getdunne)
Illustrious Member Admin
Joined: 3 years ago
Posts: 3574
 

@hexabuzz, @berndpdx

This is indeed a very useful and important discussion. Lots of people don't understand the difference between MIDI CCs and automation, because both are ways to control plug-in parameters over time, but they are indeed very different.

The main difference is as I explained: automation provides direct access to specific parameters by name, whereas MIDI CC's are just generic messages with a number and a value, and it's up to each plug-in to set up some kind of connection between CC numbers and parameters. There are MANY other differences, and Bernd, if you were to make a really clear video explaining them some day, that would be a great community service.


ReplyQuote
Bernd@PDX
(@berndpdx)
Trusted Member
Joined: 1 year ago
Posts: 82
Topic starter  

@getdunne Alright.

All: Here's a quick video showing how to use the pre-mapped macro template for Unify-Falcon knob connections, and explanations how to use it. I might make another one showing how I created the template.

 

Unify MIDI Macro Knobs + Falcon 2 Mapping - YouTube

 


ReplyQuote
Bernd@PDX
(@berndpdx)
Trusted Member
Joined: 1 year ago
Posts: 82
Topic starter  

This video is a bit more of a technical deep dive, explaining how I created the macro mapping template in Falcon 2 for the Unification of Falcon factory presets. Might not be useful for the average Unify end-user as it is more focused on Falcon specific dynamics. But this gives more background for the team involved with Unifying Falcon 2 presets, specifically how I created and use the Falcon Program template I shared earlier here.

Unify Falcon 2 Macro Mapping Deep Dive - YouTube


ReplyQuote
JeremyH
(@zinct)
Member
Joined: 2 years ago
Posts: 497
 

@berndpdx

Hey that's a very cool discovery Bernd and thanks for the videos! That should save a lot of time.

Also, after Unifying all those Falcon 2 patches at weekend (minus knob assignments), not being able to include knob assignments in the automation played on my mind a bit, so I thought I would set aside some time to investigate it further. Now seeing your discovery it might be possible to incorporate your way of inheriting the macros in Falcon in the AHK script (need to figure out how to do drag/drop in the script). The only issue is that I don't yet own Falcon 2 and my buddy might get fed up with me keep pestering him for his laptop 😀 However, I do have a few other UVI libraries including Synth Anthology 3 which I would like to Unify and I wonder whether something similar might work with the macro setups in UVI Workstation.

Incidentally, per your request in the video, all the information regarding automated Unification is inside the following forum thread

https://forums.pluginguru.com/unified-libs/autohotkey-unify-patch-browser/  

It was originally started for another purpose but rapidly became focussed on automating the Unification process. Last week I asked Shane to move the thread to where it is now and make it sticky so that people could find it more easily. The original author also changed the title of the thread to something more appropriate. 

This post was modified 1 year ago by JeremyH

ReplyQuote
thsve
(@thsve)
Member
Joined: 3 years ago
Posts: 293
 

@zinct

Drag n Drop example:

MouseMove, 147, 499
Click, Down
MouseMove, 651, 347, 5
Click, Up

Rocket science🤗

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


ReplyQuote
JeremyH
(@zinct)
Member
Joined: 2 years ago
Posts: 497
 
Posted by: @thsve

@zinct

Drag n Drop example:

MouseMove, 147, 499
Click, Down
MouseMove, 651, 347, 5
Click, Up

Rocket science🤗

Thanks Thomas! 🤣 Just tried it using a simple example.

I created a file and folder on the desktop then dragged the file to the folder in the script.

https://youtu.be/6Wk-J_oMN54  

The tricky bit in, say, Falcon 2 is going to be keeping track of where you are dragging from (the "to" should stay constant). When I did the Factory library I used the browser display, selecting the first patch, then sent "down" and "enter" from AHK (like a down cursor and Enter) to move to the next patch. This means that the current patch screen location changes until you reach the bottom of the screen and then remains there. I guess you could start with the first patch already at the bottom of the screen.

It's maybe worth adding this information to the main AutoHotKey thread.

 

This post was modified 1 year ago 5 times by JeremyH

ReplyQuote
thsve
(@thsve)
Member
Joined: 3 years ago
Posts: 293
 

@zinct

I don't own Falcon, but I tried something simular with Kontakt. See https://www.dropbox.com/s/bqormhcavpl2j1l/2021-04-27%2014-06-15.mp4?dl=0

 

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


ReplyQuote
JeremyH
(@zinct)
Member
Joined: 2 years ago
Posts: 497
 

@thsve

Yes, that's pretty much the same scenario as Falcon but it might need some fiddling to get the next patch to stay in the same location.

I'll also try something similar in UVI Workstation for Synth Anthology 3.

Unfortunately, I have problems with my car today (clutch went) so I am in the process of sorting out getting it recovered to a garage for repair and a hire car while it's away. Hopefully I'll have more time later!


ReplyQuote
thsve
(@thsve)
Member
Joined: 3 years ago
Posts: 293
 

@zinct

Isn’t that what my script in the movie does by using Wheeldown (mimics mouse scroll wheel)?

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


ReplyQuote
JeremyH
(@zinct)
Member
Joined: 2 years ago
Posts: 497
 

@thsve

Hopefully but I have no time to try it right now. 


ReplyQuote
Hexabuzz
(@hexabuzz)
Estimable Member
Joined: 2 years ago
Posts: 124
 

@berndpdx

I've been working with the Host Automation template for the last hour or so with mixed results - Here's what I've found so far, and I'd be interested if anyone can duplicate these results. FYI, I'm on Mac.

I own all 16 Falcon Expansion Libraries, so I tried the template using the instructions demonstrated by Bernd, and as I said, with mixed results.

Some libraries worked as expected, with the Host Automation being picked up and assigned. Other libraries, no Host Automation assignment occurred. In one library (Spectre), Host Automation was assigned to all parameters except one called "Room", no matter which patch I tried.

I of course didn't have the time to try this with every patch in every library, but I did try at least 5-10 from each to at least see if it appeared to be giving me consistent results.

If anyone else has tried the template, I'd like to hear if you had similar findings.

Here are the libraries, and if they worked for me:

Kinetics - No

LoFi Dreams - No

Plurality - Yes

Vokim - No

Savage - No

Titanium - No

Eernal Funk - Yes

Pulsar - No

Divinity - Yes

Digital Motion - No

Analog Motion - Yes

SubCulture - No

Cinematic Shades - Yes

Atmospherics - Yes

Ether Fields - Yes

Spectre - Yes*


ReplyQuote
Bernd@PDX
(@berndpdx)
Trusted Member
Joined: 1 year ago
Posts: 82
Topic starter  

@hexabuzz yes, as you saw me stumbling in my last video, Falcon's behavior seems unpredictable regarding the macro knob mapping. I could not even reproduce the macro knob creation in Falcon that I showed in the video. There seem some other dynamics under the cover that influence things. It seems to depend on the last preset loaded, which seems to leave some residual configuration in the Multi or the Program shell if you just "Empty" program. This makes Unifying it rather complicated - I guess John had a hunch that it might be harder than it originally seemed, based on experiences with its (Falcon's) competitor Kontakt. I suppose the more capable an instrument, the more complex it becomes to handle and integrate. Let's hope this never happens with Unify 😉

 

EDIT: just to not make Falcon 2 look bad - it is a very complex and capable program, with a very deep and programmable user interface and sound design logic. I am not a Falcon expert, so far much of what puzzled me at first was in the end a result of me not understanding how it works. You could spend your whole electronic music career just in Falcon, as diverse and flexible as it is. But it has quite a learning curve and I have only been at it for a few months.

 


ReplyQuote
Hexabuzz
(@hexabuzz)
Estimable Member
Joined: 2 years ago
Posts: 124
 

@berndpdx I tried to be very careful and have a fresh start every time - I always did an Init patch before loading the template, and only loaded the Falcon patch once - I never replaced it in the multi other than to drag it over your initial template - I never tried to reuse it, or load a second Falcon preset to see if it might work, so at least with what I was doing, I don't think there was any residual information...

I don't really know what to say at this point - If my findings stay consistent, at least it can help speed up SOME libraries, and maybe in the meantime we will find out the root cause of the inconsistencies - Hopefully it's something simple...


ReplyQuote
Bernd@PDX
(@berndpdx)
Trusted Member
Joined: 1 year ago
Posts: 82
Topic starter  

Okay, Friends... here's a cleaner version of the deep-dive Falcon 2 Unify macro knob mapping video - no talk, just action 🙂

Falcon 2 Unify Macro Mapping SILENT - YouTube

I figured out what I was missing, why I couldn't reproduce yesterday's process. I had to add "New Program" into the "Part" box, within the "Multi" in Falcon - important step, or you cannot add macros in the Falcon UI. 

Also included something I learned from @Hexabuzz , at 1:36 into the video, the preconfiguring of the Linked Parameter mapping in Unify, with a button press instead of having to drag the mapping curve upwards in the graph, as I have been doing. This is less work. Thank you David for that insight!


ReplyQuote
Lu_
 Lu_
(@lu_)
Active Member
Joined: 8 months ago
Posts: 11
 

Appears i'm a bit late for the Falcon Party.

Unify user for a few months now and also looking to Unify a few of my VST's. 

I’ve done Rapid manually yesterday (for personal use).

Attached my owned Falcon Libraries and i also own Vintage Vault/Keysuite

Thanks Bernd@PDX for the instruction video's and how to set up controls regarding Falcon in an template.

I made an template with 8 knob assignments, done a few manual patches and reading a bit more now about loadmax and other things to incorporate into this template.

@Hexabuzz, one observation:

When i loaded up the 8 knob template and loading in like a LoFi Dreams patch i noticed instead of the 8 assigned Host Automations there are only 4 left (and working) over here.

On this patch i went to Info / Script and added an 5th macro, this one was automatically assigned again to Host automation 5.

Would someone care to share their Falcon AutoHotKey routine, I might try to do Vintage Vault and Keysuite after getting a bit more familiar with AHK unifying things. I've atached my owned libraries.

Thanks.


ReplyQuote
Page 2 / 2
Share: