I have always used a "project template" - ie opening a new file using a pre-made template - which had all of my tracks, track folders, "go to" softsynths, busses, routing, parallel compression, fx etc. etc. set up
 
This seemed to work really well as I could just dive in and get creating
 
However, I am finding that my projects are getting "cluttered" with unused tracks
 
I have just started using "Track Templates" for some drum set-ups that I use a lot and it dawned on me today that I could turn my normal "template" into a series of "Track Templates" that I can load on a project by project basis so that I am less "cluttered"
 
Before I embarked on this route I wondered what others do?
 
Cheers
 
Boydie

 Unless one does the same thing every time, somewhere in between a fully configured project template and track templates would be the ideal. I mostly use the default Normal project then add a mix custom track templates, audio and midi tracks to it.

I avoid templates. Not because they are not a good way to work its just as Scook points out no two projects are similar enough.  
 
What I do is use an empty project and go from there. This is not from a template but a project with nothing in it that is saved as a empty project. 

I made this tutorial on templates (project and track)
I love project templates.
 
http://www.youtube.com/watch?v=sJmu4pqZthU

For me, the main reason I use projects templates is to setup Superior Drummer or Steven Slate drums with multi outs and for all the buses that I use (about ten or fifteen). Always seem to forget about track templates. Might not be a bad idea to have some project templates made with my drums and buses and leave everything else blank and use track templates to fill it as needed.

Project templates always. I have several versions of different types. From simple tracking to full orchestral, mixing or mastering.
I have many track templates derived from sections of the project templates so if needed I can import those sections when needed.
A great feature in Sonar.
 

Not one OR the other, but both. Project templates allow you to set up project settings to your liking. Track templates then let you easily setup different types of tracks and groups of tracks.
 
Scott

--
Scott R. Garrigus - http://garrigus.com - SONAR X2 Power! - http://garrigus.com/?SonarX2Power
* Author of the Cakewalk Sonar and Sony Sound Forge Power book series: http://garrigus.com/?PowerBooks
* Author of the Cakewalk Sonar ProAudioTutor video tutorial series: http://garrigus.com/?ProAudioTutor
* Publisher of the DigiFreq free music technology newsletter: http://digifreq.com/?DigiFreq
* Publisher of the NewTechReview free consumer technology newsletter: http://newtechreview.com/?NewTechReview

I use both... I have a template project with my screensets/layout all ready to go
 
Then I use track templates to drag in what I need.  I have templates for softsyths, analog input for my bass, drumkits and hardward synths. Its really nice with the hardware because I can pre-route the midi and audio.
 
Really they are both pretty awesome.
 
George

I've never used a project template. I use track templates all the time. I have all different kinds. One for an entire set of instruments, sets of individual instruments and others that come up from time to time. All the inputs, outputs and the PC modules I use. Of course where effects are concerned, they are always subject to change so very few are in the templates unless they are a mainstay.

imagine a project template as every track template you want to use.
the cool thing about project templates is they save I/O setting, preferences, screensets and a slew of other things.
 
in that video I made it goes through some of the things that are saved and some that are not.
at the end of the vid there's a list.
 
I used to just use track templates but once I seen the powerful fortunes to be had I only use project templates now and occasionally add a track template when necessary.