I’m curious why track presets still don’t include audio in and out routings for audio tracks; and midi in and out routings or midi and instrument tracks. I can’t find any way to have these routing requirements included in a track preset. Am I missing something?
I’ve replaced my use of track presets with importing tracks from template projects or simply older projects. This enables and keeps more of the track’s configuration than the Track Presets. It’s a bit slower than track presets, but it’s a lot more powerful.
p.s. I’ve not heard of the track presets going away, but I also don’t recall seeing them improved for quite a while. It wouldn’t be the first time that Steinberg builds a better new feature rather than improving an older one. – I assume, that there are software architectural reasons for doing so, even if those reasons aren’t always obvious from our user perspective.
I have taken a similar approach to @Nico5.
I use “Export Selected Tracks” and “Import Track Archive” in lieu of Track Presets if I want to create a new track. It works similar to “Import Tracks from Project”.
For copying channel settings such as inserts and sends, I use Track Presets if the source and destination channels are in different projects. (I’m not a fan of this approach but I don’t know of any other way.)
1 Like
Hi @mlib ,
does “Import Track Archive” work reliably?
I tested track archives at one point and decided to not follow that approach any longer. TBH, I am not sure what exactly put me off back then but if you say it’s working just fine I might give it another try 
It is working reliably for me, yes.
As far as I can tell, Import Track Archive works pretty much the same (identical?) to Import Tracks from Project. You get the same Import options.
What I like about this feature is that I can export one or multiple tracks and use them as a form of track template. This leaves my project template free of any tracks used for recording in the session. For example, I have a couple of track archives with multiple drum mic tracks saved as “Drum Kit, 5 mics”, “Drum Kit, 10 mics” and so on. The real beauty, and this is also true for importing tracks from an existing project, is that all sends and direct routing is intact upon import. This does however require that any routing destination, such as group and FX channels, need to match the project you initially saved the tracks from. But since I use the same project template and all those channels live there, it’s not an issue.
I love the workflow of only using one project template for recording and mixing and adding tracks from my saved archives as needed as opposed to having multiple project templates for different scenarios.
1 Like
Thanks @mlib !
I will give it another go then. Sounds promising - no idea why I gave up on using it. I’ll report in case I come across anything in particular but I guess it was workflow-related.
Thanks again 
1 Like
I appreciate everyone taking the time to respond. I actually didn’t know about track archives and it may be helpful with other things, but maybe not in my particular use case. I’m using Raven 4 on Windows and trying to get my old batch commands to work. I built some very extensive commands (basically macros) that allow me to open individual selections of tracks with all routing and patching configured. I’ll try rewriting them to use the import archives and make the correct selections and report back. Thanks again!