As some of you may or may not know many bugs in the past where based on the Sonar Template.
Metronome not working, create loop will highlight and my every time there was an update the bakers would change the templates as well over writing the older ones just changing the problems.
I have been able to see this as I import *.wav files from older project templates in the course of my work flow. I used a different DIR for mine templates so they were not over written.  Depending on the system I'm on, the temples will have first installed templates on that system and different problems.
 
I've been importing all my  all my old Splat projects wavs into the last Temple and that seems to help but it's not a great template.
I believe  that may problems are hidden withing the template it self. like the [R] coming on when a new track is created. and all or some of the ProCh strips activating randomly.
 
I think that we need a solid "master" template with out issues as the foundation of the next generation of Splat and a notification on where to download it. 
 
 
Peace!
 

I've encountered a handful of issues over the years that were related to using old templates, but can't think of any that occurred only in new templates. Do you know of any issues with the current [Blank] or Basic template that are not present in some earlier version of these templates? I didn't get the reference to "Metronome not working, create loop will highlight". I also keep my templates in a different directory, and generally don't update the default set unless some issue comes up.

brundlefly
I've encountered a handful of issues over the years that were related to using old templates, but can't think of any that occurred only in new templates. Do you know of any issues with the current [Blank] or Basic template that are not present in some earlier version of these templates? I didn't get the reference to "Metronome not working, create loop will highlight". I also keep my templates in a different directory, and generally don't update the default set unless some issue comes up.

So then? I'm confused... So your point is? That you agree that we need a solid master template or that people should just use what they have and hope for the best. I actually stopped mid mix because of a template problem. One I have seen posted here in the past with a conversation with a Baker. I still feel that this "concept" is a good beginning of maybe having a "solid template foundation" for a solid working DAW...
I truly don't understand your motive.

Why did you post this if not to have some discussion about it?
 
I'm just asking what specifically is not 'solid' in current templates, if only so I can watch out for it myself.
 
And, yes, I have some doubts about the extent of the problem. I've been at this for a long time, and haven't encountered enough template-related issues to feel it's a priority. But I'm willing to be educated.
 
No biggie. Just curious.

lol. As we all know we all don't use the same tools but I use Splat every day, I still have random strange things and I don't pay much attention. As we all know, when in the zone recording or mixing... you don't stop to analyze every twitchy bugs. I shut down, reboot and move on. 
But here's the list of what I believe is because of the templates as I see the randomness in projects. Random audio dropout, Splat simply shuts down. I'm on a backup laptop running one of the last updated Templates that has randomly selecting all tracks. So its like I want to cut a wav. I select the track and if I don't catch it I will delete all waves on the same time location on all tracks. These are only examples of past templates. BUT in the past these same bugs come and go and them back again... update to update... Though we have no idea on the update deal... we still all could use an up to date master Template... 
Seeing what I posted above. But that said, my main bug on any system or template is the ProCh strips randomly turning on. Being that its ProCh buttons are well above and I have to scroll up to see them, I may not notice until I notice and have to start the mix over after I shut off the ProCh strips. I have video of this problem. All I'm saying is that just because we all don't connect issues the same or use all the tools the same we will all have different problems and it would be nice to start with a bug free template. For a logical starting point. we all need to start with a Template... So? :) 

As I said, no biggie, but I just don't see how any of that is clearly indicative of buggy templates as opposed to ordinary code bugs.
 
I'm expecting a problem description like this:
 
"When I start a project from the Cakewalk-provided Basic.tpl file with Last Modified date <x>, and perform action <y>, <z> happens. When I do the same using the Basic.tpl file with Last Modified date <n> or earlier, <z> does not happen."

it's relevant because I can open projects from past dates that have the bugs that are not present in newer templates.
like no metronome. Its still in the program but it won't work. Seems like a month before Cakewalk closed a baker was talking about templates and that they replaced them. it's not a stretch... I really thinking about doing some Splat video. I can maybe find older templates backed up and or projects and create a presentation... lol I really think "we all" (if possible) start putting up Sonar Videos... I really don't want to start looking for a new DAW again, though I already wasted cash on a few! :(
 
Still nice to talk with you BrundleFly... :)

The main cause of no metronome that I know of is changing metronome settings while FX Bypass is engaged. Toggling FX Bypass will restore it. This has nothing to do with templates; its a project-state issue that can occur in any project running under the currrent release (and last several releases IIRC) of SONAR.