Import Logic projects from a template hijacks existing buses, despite different import settings (keep bus number, i/o etc)

[GCritchley]

Messing with importing from the Logic version of the Andrew Scheps mix template INTO the song I recorded and am ready to mix. However, I'm confused by a few things in the import logic projects process. In the Scheps template, his buses are contained in the bank from 1 - 32. I already have some buses assigned for various things, and they are in that first bank too. His buses end up merging (despite a bus by bus dialogue box for assigning), and hijacking my existing buses, so now my bus one (kick bus) is ALSO a guitar busm since that's he template Bus 1. Does this mean that I should always use buses above 32 from now on, so I CAN import the template and it won't have any conflicts? Is there a way around this for existing songs? any tutorials that get into a similar process? I'd like to find a way, that when the tracks are ready, and even though I've already mixed as I went, while producing., I have some go to template info i can pull in and re-distribute the audio tracks. This will be helpful especially with a record I'm mixing now, where most of the same instruments can be treated similarly. Thanks for any help, pointers, and or tutorials on this topic.

[fuzzfilth]

Generally speaking, you import the simpler project into the more complicated one and import only what's absolutely necessary. More specifically, if you intend to use a Mix Template, you import only the naked tracks+content, without their routing.

Once imported, you either change routing and set up Sends for any selection of tracks, or, more streamlined, you move the content of the imported tracks to already prepared, empty tracks in the Mix Template, which reduces routing-time and -hassles to zero.

Edited June 9, 2022 by fuzzfilth

[GCritchley]

Thanks. I would have thought the same, but in the Sheps method, (which i have been curious to try), he imports his templates into the sessions he's sent. I know it's Pro Tools, and the wave files are delivered with very few, if any busses being used,, but in my case I've been producing in Logic, I'm 50% to a mix, some things are still in the MIDI realm for last minute tweaking, and then I'd love to jump to the template options and sort of make a hybrid process out of it.  which leads me to ask - is there no way to have Logic bump either my existing or the template routing so it's not hijacked and shared? 

[fuzzfilth]

In the few occasions where I had to merge Logic projects, I haven't encountered such problems, and in the thousands of times I had to merge ProTools sessions, I always always always made sure I only ever import tracks+content without routings or sends. The less stuff you do in the source project, the less you have to manage or redo in the merged version.

[GCritchley]

Actually - this is a head smack moment. If I import from the logic file I'm working on INTO the template, I can just import without routing. Duh, I think this is what you were getting at. OK, gonna try that. Thanks

[fuzzfilth]

Great.