View Single Post
Old 03-01-2018, 02:21 PM   #1
Jason Lyon
Human being with feelings
Join Date: May 2016
Posts: 709
Default Orch template with Reaticulate File

I've finally fixed my MIDI-chasing issue, and I thought I'd share the fruits of my labours. The attached template uses GPO5 as a basis and augments it with CSS, Kirk Hunter Concert Brass 2 and CineWinds Core.

It's unlikely most people will have precisely all of those, of course. You could always delete the tracks pertaining to the ones you don't. Or you could substitute in ones you do, but then you'll have to do some work on the MIDI note names and Reaticulate banks. The former task is boring rather than difficult and the latter isn't half as terrifying as it first seems.

I hope people will get some kind of use out of this, even if they just pick up on some of the methodology.


Reaticulate Reabank File:


- - -

Reaticulate Version

This is a mid to late Romantic-era orchestra, not a kitchen sink epic job.



GPO is limited by modern standards (for instance the legato and portamento are scripted not sampled, and most instruments have vibrato baked in) but you can't fault it on sheer value. It's more a "concertish" sound than a "filmic" one, but it makes a very good bedrock for any project. Meat and potatoes, and its auto handling of long-short is very intuitive. It also fills in a lot of less common auxiliaries.

It involves quite a few compromises, but it's comprehensive, practical and has a minimal hit to resources. It's ideal for sketching and even full productions, especially if you really get under the hood.


CSS is a more advanced string library, allowing for more natural sounding sampled legato (among many other things). Its inclusion here is primarily for layering purposes. The workhorse legato and articulation approach of GPO5 can be augmented by doubling the GPO MIDI content in the nested CSS MIDI tracks, creating an overlay for far more realistic performance, as well as variety of tone and more density.

I've used the older Classic Legato patches since they seem to combine with other libraries with less angst over timing.

CSS has generally brighter and more aggressive performances (a little more in the "filmic" direction). Experimenting with the relative feeds of GPO and CSS (from the purple "container" tracks - see below) can give interesting and different results. For instance, to stay "concertish", dial in just enough of CSS to give the increased realism. To get brighter and tighter, alter the balance more in favour of CSS. You could of course simply mute out one or the other entirely.

I find the CSS basses "cut" and "dig" a little too much in this context, so they aren't included.


All instruments but the bass trombone are doubled in nested tracks. As opposed to the string sections, I feel these are best used as either/or, but I suppose you could double up (or more) your brass up if you wished.

Again, the advantage to using these samples is primarily for more sophisticated legato handling and much greater control over articulations. KHCB is brighter and punchier than GPO, but not enough to trouble the overall balance too much.


All major woods are doubled in nested tracks. Again these can be either/or/and. The advantages are the same as with KHCB. Again, this library is punchier than GPO, but combines well with it.


Jason Tackaberry's solution to articulation management - flexible, visually appealing and auto-chasing. You'll need to add the packaged text file to the Reaticulate file in REAPER/Data.

This version of the template retains the default KS mapping for all libraries. I've left them in the MIDI Editor as named notes - they can be useful for translating previous projects to Reaticulate. You can use traditional KSes in conjunction with Reaticulate, but the former won't always chase properly.

In general, if you want to simply copy over MIDI items from one library track to another you'll probably have to do some editing. It shouldn't be too bad if you use Reatic events though - all but the most unusual map across different sample players, using Spitfire's UACC standard.


The layout philosophy is simple - when you're above the line (track panel) you're a musician, when you're below (mixer panel) you're an engineer.

The template compromises total flexibility in favour of what I've found to be practical workflow. For instance, it's better to control instrument volume in MIDI by sample cross-fades rather than volume, so envelopes for audio tracks aren't displayed.


The Track Panel Master at the top (the real Master) is acting as a sort of "Conductor" track, with visible control over global tempo and volume envelopes.

The MIDI tracks have preroll items in them to send setup info to the VSTis. These items also include MIDI note name info to display only in-range notes and KSes for each library in MIDI Editor.

The top control lane clearly displays Reatic bank and program changes. The Editor windows also include cc lanes for cc2 vibrato (where applicable), cc20 portamento (for GPO instruments only), mod wheel and velocity. You can add many more lanes for detailed control, but I've found these are the most frequently used.

Every available instrument is displayed by default, but they can be hidden or deleted if you wish. All Kontakt libraries are pre-purged, so a clean load should come in at a little under 8GB.

The sections are laid out in traditional score order, but you can move them around. (Note that the MIDI tracks above and Audio tracks below are different entities, so you'll need to hide, delete or move them in both panels.)


The "MASTER FX" track serves as the mix master and contains flat-set EQ and multiband compressor. (The top Master track has the final say over volume, however.) While you can put FX on the Master, this seems to have a bad effect on CPU usage on some systems and "premastering" like this won't hurt anyway.

The five blue section tracks labelled "CTRL" (in blue) simply bulk-handle the M, S and fader trim controls of all section audio tracks. The summed audio outputs of all instruments in each section are displayed for visual monitoring purposes.

The audio track M, S and R controls are master-slaved to the related MIDI tracks. The audio tracks themselves are record-disabled to prevent inadvertent doubling.

The individual instrument audio tracks contain instances of ReaPitch randomly knocked a few cents sharp and flat (helps with realism and phasing). Second rank instruments (woods and FHs) also have a slight high EQ cut, Third rank instruments (other brass and percussion) have a slightly stronger high EQ cut.

There are three reverbs - Room, Preverb Rank 2 and Preverb Rank 3 (in black). The instrument tracks are bussed in combination to these to create spacial depth in combination with the per-track EQ cuts.

The "engine room" is the VSTi "container" tracks (in purple). Instruments are banked here, set to auto-legato, centred and dry. Relative output from all "container" tracks can be faded to taste.

There is an extra "container" track called GPOFrontDesks. This receives MIDI from the GPO VlnsI, VlnsII, Vlas and Cellos tracks and outputs small sections. It can be faded up to add a little variety and bite to the strings.

All instruments are sent mono except the General Percussion and String Sections. The strings, although stereo, are centred so you can pan your sections in-DAW while retaining their individual spreads.

All FX used are stock REAPER ones, for maximum compatibility. You can swap in your favourites, of course.

Comments, suggestions and bug reports to:

Last edited by Jason Lyon; 03-05-2018 at 01:52 AM.
Jason Lyon is offline   Reply With Quote