UACC

Spitfire Audio has created a new articulation switching method, known as the UACC (Universal Articulation Controller Channel), to be used as a standard across their libraries.

It's currently at v2 (as of May 2014).

For more information on the nuts and bolts of how it works, and the philosophy behind it, please see these links:

UACC - A New Proposed Standard

Tutorials - Spitfire Audio - Changing Articulations

Current UACC spec v2

TouchOSC

TouchOSC is an app for iOS and Android that relays OSC or MIDI values to a host DAW (via TouchOSC Bridge) over WiFi or USB.

Users may make various templates for their instruments/projects via a desktop program (TouchOSC Editor), and upload them to the mobile device that will be used as a controller.

For more information on how to setup TouchOSC, TouchOSC Editor and the TouchOSC Bridge applications, please see:

Hexler TouchOSC

Template v1.0

With that out of the way, here is a template I've created for the iPad using the latest UACC spec and TouchOSC version to control Spitfire libraries.

Here are a couple of images of the template with some explanatory notations...

Please use the above links as reference to how to properly load/utilize TouchOSC templates.

I am providing a download of the template below for anyone who is interested in controlling their Spitfire templates/instruments this way.

Please be sure you select "Locked to UACC" preference in the Kontakt performance view window (as seen below).

Kontakt Performance View - Select "Locked to UACC" for proper functioning.

I hope you find this tool useful and helpful in efficiently managing your Spitfire Audio workflow!

Download Template v1.0

11 Comments

For a while now, I've kind of struggled with the idea of DAW templates.

I understand the draw of it; the ability to load everything at once and then pick an instrumental color on the fly as you're working.

But, I hate clutter. And, I don't always want to wait for huge templates to load when inspiration (or a deadline) hits.

So what are the other options?

What I've usually done to date, is start with a blank slate, and I then add my instruments as needed.

Obviously this type of workflow requires at least some semblance of foresight or musical need, as you are sort of making-it-up-as-you-go. The advantage to this approach is that you have your basic set of instrumental colors established and in place for subsequent cues/songs/etc for a given project. This can help keep within a nice set of aural boundaries when working on a linear project that could otherwise sway towards disparate elements, even if accidentally.

So here's an idea using Logic X User Patches.

This is an approach to creating a template in Logic X that can be as complex or simplistic as you need/desire. I'm sure I am not the first to think of this or to implement this type of system, but in the event anyone reading this has struggled with the concepts or process of "templating"...

I hope this helps.

First, select a new instrument. Check the multi-timbral box as to use one instance of Kontakt to load up to  16 patches. — First, select a new instrument. Check the multi-timbral box as to use one instance of Kontakt to load up to 16 patches.

As above, make sure to select Multi-timbral - 1 part and 1 track.

Next, instantiate an instance of the Multi Output Kontakt plugin.

After adding Kontakt, look in the mixer. You should now have a little "+" button on your newly creating multi-timbral instrument track.

Click the "+" button on the mixer channel strip shown above and create 15 Aux channels. Then, select all of those tracks you've just created and right click, then select Create Track.

You should now have a track available for each of the 16 Kontakt patch slots like below:

Here, you can see the tracks we've created for the 16 Kontakt patches we will now add.

Alright, now add the Kontakt patches you want in this particular instrument. In this example, I'm creating this Kontakt instance as my default Albion 1 Synth Pads.

Here you can see the 16 patches I've loaded for this particular Kontakt instance.

In order to send the audio from each Kontakt patch to the appropriate Logic channel, on each Kontakt patch, select subsequent output pairs as below.

Notice how each patch is routed to sequential stereo pairs.

Next, in the Output menu of Kontakt, select the first option to "Clear output selection and create one individual channel..." (you can go back and select the second option afterward if you want the output names to match the patch names).

Alright, now name your tracks in the Logic arrange window if you'd like. After naming, I like to create a Summing Track Stack and name it accordingly (in this case - Albion 1 Pads).

Tracks in Logic named and Track Stacked.

So that's the hard part.

Now for the more rewarding part of this.

You can now select your Track Stack and open the library drawer in Logic. Click the Save... button in the bottom right corner and name it accordingly (in this case - Albion 1 Pads - again. See a pattern here?).

Saving this Kontakt instance as a user patch in Logic X.

Now, anytime I want to bring in my Albion 1 Pads into a Logic project, I can just select this User Patch within the Logic X library.

To do this, you just create a new software instrument (it doesn't need to be multi-timbral) in Logic X, and then select your user patch in the library pane.

As you can see with this approach, it takes a bit to set up up front. But, once you've created all of your user patches for all the most commonly used aspects of what would be your larger overall template, you can pick and choose them as needed. Thus, the modular aspect of this whole thing.

These steps I've illustrated are just the basics, but the sky is limit, as while you are creating your user patches, you can route various sends and instantiate whatever plugins you'd like on each instrument aux channel (or the summing stack as a whole). You can also purge your Kontakt patches if you wish to create an even more speedy recall when loading user patches.

These methods can also be used with Vienna Ensemble, etc. for other instrument families, or I even have one for a blank instance of Kontakt, just because it's faster to load this way than selecting from the plugin list.

The settings will all be remembered when saving and recalling the user patch in Logic X.

I know, right!? Awesome.

Anyone else got any interesting alternative template methods?

-B

6 Comments

Journal

spitfire audio / touchosc | uacc v2 template