What's new

Navigating a large template in Logic

For years in the pre-10.4.7 era my Logic template had 240 instance of EXS24, 16x 16-channel multitimbral VI channels going to VEPro (giving an additional 256 channels of Kontakt etc.), and 64 audio tracks - all routed in 5.1 to eight stem sub-masters by way of busses, with individual front+back reverb+delay for each stem. I had four busses unused - hooray!

Since 10.4.7 my template is up to 512 instances of EXS24, 128 audio tracks, and the same 16 x 16 VEPro feeds. So, bigger but still only half of Logic's capacity.

As soon as my instrument count got beyond, say, 64 or so I've been very diligent about organizing how they stack up vertically so I already know where to look for the sound I want. Here are the salient points:

- I never use the Mixer window that can appear at the bottom of the Main window. Like, never ever.

- I pre-build all of my Instrument, Audio, Aux, and ReWire objects in the Environment window. I place them precisely, create colored ornament labels for everything, and then "Lock Positions / Hide Cables" to lock everything in place. I keep my Environment open on a second display to the right of my Main display.

- I make damn sure that "Automatic Management of Channel Strips" or whatever it's called is turned OFF. I don't want Logic spuriously making Aux objects and moving stuff around in my precious Environment.

- I use Folder Track Stacks to make collapsable bricks with 16 VI tracks per Folder Stack, and have a key command assigned to expand / collapse the Folder Stacks, and I use color-coding and icons for each Folder Stack and the tracks within so everything matches.

- I do not use Summing Track Stacks. I want to be able to re-route any single object within a Stack to a different bus / stem sub-master at any time, so I can merge or separate elements within stems WITHOUT moving the sound / MIDI to a different track. This can create routing chaos sometimes but keeps everything where I expect it to be in the track list.

- Each 16-channel Folder Stack represents 16 slots in a given category - so, Stack 1 is kick drums, taikos, etc. Stack 2 is mid-range percussion. Stack 3 is metallic clanks and stuff. Stack 4 is high percussion.

- I always leave the last 2-4 tracks within each stack empty so I can go browsing for wild-card sounds that fit within that Stack's category but weren't pre-assigned in my template.

- Each group of four Stacks represents a stem, and all elements within are routed to that stem's sub-master busses. So, 16 tracks per stack x 4 stacks per stem x 8 stems = 512 VI tracks total, with 64 per stem. Should be enough (for now!).

- I obey some in-house "rules" like putting my main low-strings patch on the first track of the first Stack in the Strings array. It used to always live on track 65, halfway through my old 128-track template. Now it's on track 257, exactly at the mid-point in the fully-expanded track list. Other instruments that I use in every template function like this, as "anchor points" that I KNOW will be right where I left them and will never be deleted from the template. Not every Stack has an anchor instrument, but almost...

- Every 16-channel stack obeys some pretty strict rules about what's going to be in there. So if I'm looking for strings harmonics, sul-pont-trems, or any thin and icy string sounds I KNOW they'll be all next to each other in a certain Stack. Likewise with almost every sound in my world - they each have a home Stack, a place where by all the rules of nature they "should be".

- Those Stack categories follow the organization of my EXS library pretty closely (and my EXS library is obsessively organized), so if I want to go browsing for another sound in the Synths>Ambiences>Atonal category, I don't just go looking for an empty track in some random Stack, I first go to one of those few empty tracks at the end of the correct category's Stack, and load the new sound THERE.

- If I haven't used any tracks within a Folder Stack I keep it collapsed, and possibly hidden until I need it. With up+down arrow keys assigned to move through the tracks list, I can often get where I'm going without using the mouse.

- As the cue progresses I make extensive use of the "Hide Track" command to reduce clutter. When I need a new sound, a quick key-command to temporarily show all tracks lets me see everything, and then I can un-collapse the correct Folder Stack if needed, un-check the little green "Hide" button on the newly-used track, and then re-enable "Hide". Almost all of this is done with key commands, very quick.

But really it's the obsessive organization of everything into 16-channel bricks (Folder Stacks) that makes this easy. I still obey my own mental rules for how sounds should be organized from top-to-bottom, much like in the old analog tape days where kick drum was always on fader #1 on the SSL and lead vocal was always on the first fader to the right of the center section on the console. So the list of Folder Stacks, tracks, stems, busses.... EVERYTHING follows that thinking of how any given sound has a "right" place it should be in the natural order of things. Even within each Folder Stack, in my mind there's always a "first" instrument that sits in the first track - it's the main / biggest / heaviest / thickest sound in that family, and the others descend from there, getting higher / lighter / thinner / more obscure in character as you move down the list.

Your rules may be different, but working from lowest to highest track / folder / bus / stem numbers my list looks like this:

Stem A / Folder Stacks 1-4 = Low Drums, Mid Drums, Metal Drums, High Drums

Stem B / Folder Stacks 5-8 = Basses, Synths+Pulses, Guitars+Blasts+Braams, Crazy Hard Noise

Stem C / Folder Stacks 9-12 = Bowed Metals, Metal Textures, Noise Textures, Glitch Shit

Stem D / Folder Stacks 13-16 = Synth Textures, Synth Ambs, Atonal Textures, Atonal Ambs

Stem E / Folder Stacks 17-20 = Low Strings, Main String Ensembles, Icy High Strings, Strings FX

Stem F / Folder Stacks 21-24 = Low Brass, Mid Brass, Woodwinds, Brass FX

Stem G / Folder Stacks 25-28 = Orch FX Short A, Orch FX Short B, Orch FX Long A, Orch FX Long B

Stem H / Folder Stacks 29-32 = Short Strings Low, Short Strings Hi, Choir+Vox, Choir+Vox FX.

I am currently building a variation on this template which is in Quad instead of 5.1, so I can fit more stems with fewer channels per stem into my 64-channel MADI output (that goes from the Logic rig to the ProTools print rig). When this is complete I'll be able to use up to 16 stems with 4 channels each, instead of my current setup of 8 stems of 6 channels each (with some left empty). This would let me basically split each of my current stems into two, each of the above categories would be split in half.

Not sure if I'll need to go this way but we'll see...

Hi Charlie
Many many thanks for taking the time to describe your set-up. I know that the careful planning of a large template is crucial. I also find myself using too much time on organizing and building - especially in Cubase - and I realized that my organizing gene are taking too much focus. I have been working on a large Lemur template, programmed set-ups in Composer Tools, hoping for the day, that Logic will have the must basic tools to solve these problems.
Your way of doing it is build on your big experience in your work I understand, and I will surely look into this!
Thanks a lot!
 
An additional tool: screensets with the Main window scrolled to different places, for example one screenset scrolled to bowed metals, another to synth textures, etc.

I don't do that, but I would if I worked with 200 - 600 tracks.

But yeah, I've seen a lot of requests for a track search function.
Hi Nick
I havn't thought of screensets in this context! That's a good idea, I will try it.
 
Another feature that is often overlooked (until logic gets full track search etc) is the Hide Group 1-32 workflow.

Meaning you can:

  • in the mixer select a channel strip
  • go to the group drop down menu and add as many groups as you need (up to 32)
  • open the group window (command+ G) and select all groups and uncheck all options (volume, pan etc)
  • Rename groups as needed
  • select tracks
  • in the group window select a group
  • use key command to add tracks to selected group
  • Create key commands for toggle hide group 1-32
Hi Samphony
Yes I use the group system to select which instruments to hide, it works well. What I have a problem with is, that hiding in the arrange also hides in the mixer, where I like to have my 16 group outs visible sometimes without having in the arrangement.
Thanks for replying!
 
You could also set up buttons in a floating Environment window as part of your main screenset.

This is a Meta button set up to recall a screenset. You'd set up more of them, and they'd probably be smaller.

I guess the screenshot isn't particularly helpful other than to show what a floating window looks like, but there are different buttons with different styles. This would be a dedicated Environment layer.

1575663491887.png
I use Metagrid to recall that kind of things, works fine. Thanks!
 
- I use Folder Track Stacks to make collapsable bricks with 16 VI tracks per Folder Stack, and have a key command assigned to expand / collapse the Folder Stacks, and I use color-coding and icons for each Folder Stack and the tracks within so everything matches.
Hi again, can't neither find the key command for expand / collapse folder stacks nor the switch to stop Automatic Bus Assignment! ;-(
Can you help again?
 
Hi again, can't neither find the key command for expand / collapse folder stacks nor the switch to stop Automatic Bus Assignment! ;-(
Can you help again?

The key commands relating to collapsing folder stacks are in the this screenshot - search the key commands window for "stack" to show them. The ones I use are the first two in the screenshot, but note that there are many others that may be useful to you.


Stacks key commands.png


The stuff relating to Automatic Management of Channel Strip Objects is in Project Settings > Audio > Channel Strips, and is shown in the this screenshot. Note that this won't prevent Logic from creating a single Master Volume fader object when you make a Folder Stack - but it will prevent all sorts of automatic creation / deletion of Aux objects and other crap that might mess up your precisely arranged Environment window. If you don't use the Environment the way I do this might not matter to you, but I'm still working in old-school Logic v4 mode over here!

AutoManage Strips.png
 
The key commands relating to collapsing folder stacks are in the this screenshot - search the key commands window for "stack" to show them. The ones I use are the first two in the screenshot, but note that there are many others that may be useful to you.
So kind og you to help me. Thanks a lot.

Stacks key commands.png


The stuff relating to Automatic Management of Channel Strip Objects is in Project Settings > Audio > Channel Strips, and is shown in the this screenshot. Note that this won't prevent Logic from creating a single Master Volume fader object when you make a Folder Stack - but it will prevent all sorts of automatic creation / deletion of Aux objects and other crap that might mess up your precisely arranged Environment window. If you don't use the Environment the way I do this might not matter to you, but I'm still working in old-school Logic v4 mode over here!

AutoManage Strips.png
 
I just am finishing up my 2020 version of my main template. I figured out how to have nested folder stacks instead of summing stacks inside of folder stacks. Each section is a folder with several additional folders for each library.
Each library's section goes to an aux bus when I have reverb sends. I do like the idea of what Jay is using.

FYI If you want to know how to do this you create the folder outside of the one you want to insert it into and simply drag it into another folder.

That being said I haven't finalized if I am sticking to this or going back to Summing nested inside Folders yet.
 
Last edited:
  • Like
Reactions: AEF
Oh but you first must make a summing stack inside a folder stack to get it to work...it's a bit of a PITA so I think I am going to just drop the nested folders and just have each major section in a folder.
 
Oh but you first must make a summing stack inside a folder stack to get it to work...it's a bit of a PITA so I think I am going to just drop the nested folders and just have each major section in a folder.
This is a great tip though! I am so happy to have found this. But is it me, or does the folder stack only want to go to the bottom of the folder that it's in?
 
This is a great tip though! I am so happy to have found this. But is it me, or does the folder stack only want to go to the bottom of the folder that it's in?
Ok, I found a workaround, you have to move all of the non-folder tracks below the folder track, so that the folder is at the top.

I hope Apple improves folders in the next version, so it's easier to make folders-within-folders.
 
Ok, I found a workaround, you have to move all of the non-folder tracks below the folder track, so that the folder is at the top.

I hope Apple improves folders in the next version, so it's easier to make folders-within-folders.
I am re-redoing my template and this still works. I was still using summing nested inside stacks but now that I am breaking out stems with multi-output VIs (I don't do one track per articulation) summing stacks bus routing can get confusing so I'm going back to either this workaround or one stack per instrument group (Woodwinds, Brass, etc.).
 
I still use old school folders. I put my whole orch stuff in one, still. Inside that folder are track folders for sections etc, no summing folders.

What I discovered recently is that they changed LPX in 10.5.1 ( or was it 10.5?) where you now must have at least one track with midi/ audio on it or you can’t open the folder from outside it. Screenshots pointing to inside the folder still works, so I was able to get inside and make a small midi sequence and mute it. Now I can click on the folder and open it and get inside. Strange. Hopefully they are not thinking of doing away with folder tracks?
 
Last edited:
I am re-redoing my template and this still works. I was still using summing nested inside stacks but now that I am breaking out stems with multi-output VIs (I don't do one track per articulation) summing stacks bus routing can get confusing so I'm going back to either this workaround or one stack per instrument group (Woodwinds, Brass, etc.).
A couple of months ago I bought Cubase...I wanted to be able to work in both. It took me like a week to rebuild my template, but I really like having as many folders as I want. This is a feature Logic needs to add. That being said, there are things Cubase can't do that Logic does that I miss. I guess there's no such thing as a perfect DAW.
 
A couple of months ago I bought Cubase...I wanted to be able to work in both. It took me like a week to rebuild my template, but I really like having as many folders as I want. This is a feature Logic needs to add. That being said, there are things Cubase can't do that Logic does that I miss. I guess there's no such thing as a perfect DAW.
I have Cubase as well and you are right, pros and cons to each.
 
A couple of months ago I bought Cubase...I wanted to be able to work in both. It took me like a week to rebuild my template, but I really like having as many folders as I want. This is a feature Logic needs to add. That being said, there are things Cubase can't do that Logic does that I miss. I guess there's no such thing as a perfect DAW.
Yes I did the same, I am trying to like Cubans but it’s a bit cluttered to me..but we’ll see what the future holds!
 
A couple of months ago I bought Cubase...I wanted to be able to work in both. It took me like a week to rebuild my template, but I really like having as many folders as I want. This is a feature Logic needs to add. That being said, there are things Cubase can't do that Logic does that I miss. I guess there's no such thing as a perfect DAW.
Replying again to you. I’ve always had Cubase but been 90 in Logic. that may change for this project. I agree Apple need to do something about the folders issue. I found a bug too when rearranging stacks that caused them to combine no matter what you do. Got annoying quickly. I’ve got a small project to work on so I’m going to get my base template made including stem busses and see how it goes.
 
Replying again to you. I’ve always had Cubase but been 90 in Logic. that may change for this project. I agree Apple need to do something about the folders issue. I found a bug too when rearranging stacks that caused them to combine no matter what you do. Got annoying quickly. I’ve got a small project to work on so I’m going to get my base template made including stem busses and see how it goes.
Yes after the initial first week getting used to stuff, I’ve taken a liking to Cubase. I feel like the key editor/piano roll is easier to work in and that helps get better performances by fine tuning the CCs and velocities.
 
I use track stacks (and minify whenever possible). I also use the HIDE feature and only unhide the tracks I need.
 
Great thread. I built my first large template in Logic somewhere around 2008, and have been modifying it ever since. Back then it was based on old school folders, each its own instrument category, with a different screen set for each, triggered by a MIDI CC. So when I wanted to work with violins, I’d hit the “violins” button on my dedicated controller.

However, there are huge downsides to working in folders - primarily that you can never see the whole context of the project. There was also a nasty bug that existed forever where offline bounces of sub channels of a multi instrument would randomly include audio from other instruments.

Then after 25 years of begging, track stacks and hide groups finally came along and changed everything. So now, my template of around 900 tracks is what I always wanted. It collapses into just what I want to see, with each instrument group made visible at the touch of a color-coded and specifically-labeled button in my TouchOSC panel. That combined with screen sets makes it a breeze to see just what I want, and any combination thereof.

One other little tidbit that helps me: Every track has an empty region at bar 1 that I use for random notes (patch info for external synths, for example), and there are 2 side benefits to this aside from the notes themselves:

1. Color coding helps me stay visually organized

2. If I want to render that track by itself, I include that region so it will start at bar 1 no matter where the actual data is.

In 27+ years of hard core Logic use, I’ve never been happier!
 
Top Bottom