Allowing custom key switched instruments in unify

@ibanez

Our forum software doesn't allow users to post links until they have been members for a while, and made several other posts.

Please specify the name of the specific plug-in you found at x42-plugins.com, so I can go have a look at it, and get a better understanding of what you're asking.

UPDATE: If you've been trying to log in, it may be because the Forum software "banned" you for using links. I just un-banned you.

I didn't realize there was a link restriction so apologies for that.  Also a bit of a delay in responding since I was on holiday :).  The name of the plugin is midi keysplits and it's part of the x42 MIDI Filter Collection.  It looks like all of this is open source.  Unfortunately there is no VST version of the plugin they created since they chose the LV2 plugin format and it seems like it would take a lot of weird set up to get it working in a DAW / unify.

@ibanez1

You may be able to use multiple instances of Unify's built-in MIDI Filter plug-in, possibly together with ComboBox, to achieve what you need. However, I can't advise in any detail unless I understand exactly what you need. Just saying "allows key switched multis for libraries which otherwise don't support multi articulation patches" is too generic.

There are many libraries which only have single articulation patches to play in kontakt.  This forces multi track use in the DAW and having midi for multiple articulations spread between different tracks.  Unify has the ability to have one instance host multiple kontakt, spitfire player, sine player instances so technically it could be an indirect host for a "multi articulation" instance by having multiple instruments in unify where each instrument is a single articulation patch for a virtual instrument.

The problem becomes in how to isolate to only one active articulation at a time which is equivalent to saying only one instrument is receiving midi at a given time.  Ideally this should be controlled by a keyswitch.  Press C0 and all incoming midi is only sent to midi channel 1 which is the only channel that instrument 1 in unify is receiving.  Press C#0 and all incoming midi is only sent to midi channel 2 which is the only channel that instrument 2 in unify is receiving.  Instrument 1 has a short articulation for violin and instrument 2 has a legato articulation for violin in this example.

I can't seem to find any way in unify to do this directly in the midi plugins hence why I was searching online and found that x42-plugin which seems to describe the functionality I want.

that's a great suggestion. Effectively unify that can operate 24 layers, it would be very powerful to be able to assign the MIDI Switch input or mute Switch from one layer to a Key Switch including the aux layer. In this way we could pass from one instrument to another by a simple note

@ibanez1

Unify can't switch MIDI among layers by note messages, but it can do so with CC's, using carefully crafted parameter links, and then you can use a free MIDI-effect plug-in called midiNotesToCC to achieve the result you're after. This is a bit intricate, but it works.

The attached zip file contains two patches. (Unzip and drag/drop each .unify file into Unify, then hit Save to save to your User Library.)

The first patch (TEMPLATE - 4 layer knob switcher) shows how to use a Macro knob to effectively switch input MIDI among four layers. The first Macro knob selects layers 1, 2, 3, then 4 as the knob is turned (which can be done using DAW automation or a MIDI CC assignment).

The trick is to connect each INST layer's midiEnable parameter, and to use the Step-N-of-4.xml macro-link curve presets (where N is 1, 2, 3, or 4) to create precisely non-overlapping curves, so exactly one layer is enabled at a time.

The second patch (TEMPLATE - 4-way MIDI key switcher) takes this a step further, putting the TEMPLATE - 4 layer knob switcher patch in to an embedded Unify layer with Macro Knob 1 assigned to MIDI CC#20, then preceding this with an instance of the midiNotesToCC MIDI-effect plug-in from the free PizMidi plug-ins collection. Note this patch requires the midiNotesToCC plug-in, and won't work properly until you download the collection, install and scan/register it into Unify's Known Plug-Ins List. As with all MIDI effects, you will need to add midiNotesToCC to a MIDI-effects subset in order to be able to select them for use in MIDI-effect slots when creating your own patches.

I realize this may not be easy to follow. If there is sufficient interest, I can ask John to create a one-tip topic video showing the steps.

@getdunne 

Thanks so much for this!  It is intricate but I think I get the need for 2 patches since one instance of unify is embedded to accept the CC setting to switch between the layers and the other acts as the parent unify instance to host the midiNotesToCC plugin as a midi modifier plugin.

Also, if I understand your explanation, this CC controlled midi switch macro effectively stops sending midi to all other instrument layers beside the one in that is active in that cc range correct?

I'll give this as shot in the next few days and let you know how it goes.  I might also relay this to others on VI control as this is becoming a common ask for various libraries.  Nashville Scoring Strings and Performance Samples Pacific Strings are just 2 libraries that come to mind where keyswitching is not supported by the developer.  I think publicizing this support will get even more people interested in unify as it effectly makes mixing and matching any articulations from any libraries possible.  Like the legato from library A but want the spiccato from library B?  Set it up in unify :).