• SONAR
  • [Solved] Audio Engine button keeps disabling
2014/05/05 20:56:18
DaveG74
I have a X3 template file from which all of my new projects begin. A few CSC tracks, a few TTS tracks, an SI Drums track and an SessionDrummer track. For some reason, the two Drum tracks are malfunctioning.
 
a) (In the case of both tracks) I select a kit, but the instrument does not sound. Nor does the level meter light up.
b) I delete the synth track (and the synth itself from the Rack) and insert a new one. I select a kit -- and it sounds.
c) I save the template as a new Template file. I close down Sonar and reopen it to the template.
d) Upon loading the template, the drum track is once again silent. The synth loads, but we're back to step A.
 
Can anyone tell me why the drum kits are resetting when I load the file? Any info is appreciated. Thanks!
 
EDIT, 8:40PM
 
Running the actual Sonar shortcut that opens to the Template, the drum kit sounds. I saved the file as the Template.
Running the Template file itself, sampled the drum kit bu it is quiet (per step A).
When I inserted another Drum kit track, I heard a loud drum hit (the audio of what I just tried to sample).
Drum kit(s) sounded, but went quiet again next time template was loaded (per step A).
 
In both tests, the Drum Kits only sound while the project is open. Close, reopen, they don't sound.
Any ideas?
2014/05/05 23:15:20
Cactus Music
Not sure if this will help but I  save my templates as a CWP file. Seems to make no real difference. 
 
Open your template
 
Set everything up the way you like it. 
 
Save As to Normal ( CWP ) and give it a name like  " Original template 1.CWP" 
 
Then open it, And immediately SAVE AS  and re name as the song title your about to work on.
I  browse to a new folder for the song.  
  
Al the pre sets for Session drummer, tts1 and the lexicon load up fine. 
2014/05/06 08:49:47
robert_e_bone
Well, I did some experimenting and did not seem to be able to duplicate your issues.
 
Can you please take another crack at explaining exactly what you are doing?  If there IS a way to get this to happen, I am willing to keep trying, as it might help the Cakewalk folks out in the event that there is some sort of bug.
 
I am a bit curious, though.
 
1.  You indicate that you saved things as a Template - I am assuming you mean a Project Template, and not a Track Template?
 
2.  I am wondering why you are opening the saved template again, rather than using it as the base for a new project.  Project templates are really intended to be loaded as the starting point for a new project, where you would provide some name for the new project and select one of the project templates to get your new project started.  By opening the template as the saved template, you are making it so you have extra steps when actually creating a new project, in my opinion.
 
I create Project and Track templates all the time.  To create a Project Template, I would start a new project (usually named some gibberish, since I am not actually going to save the project as a project and do not then need the project folder), and I may choose either Normal or some other template, depending on how close one of those is to what I am trying to build.  I then make all of the adjustments I want, such as loading and configuring a drum synth and its audio tracks and cell output assignments, or even inserting from track templates.  So, when I have whatever template adjustments finished, I do a Save As, change the  Type to Template, give it some meaningful template name, and navigate to the X3 Project Templates folder and hit Save.
 
To USE the new project template, I would start a new project, giving it a real project name, and select the project template I created.  Sonar then loads up that template, with whatever is inside it, and now when I do a Save, it saves it all as a regular Sonar Project file with the name of the project and a '*.cwp' extension, in a project folder, where the project file name and the project folder name are the name I gave the new project.
 
I did a bunch of testing, loading and saving project templates, using Session Drummer, and I had NO success at producing any problems with the drums sounding.  That is not to say that there isn't a problem - I just could not reproduce it, and THIS is why I would like you to provide a set of steps that you do that produce this problem.  THEN, I can also produce the problem and will have something I can work with to help you, and to help report it to Cakewalk for fixing.
 
I do believe that something is occurring in how you are doing things, that causes these issues for you, but what that might be is either not listed or I am simply missing something in what you had explained.
 
I DO think that there may be some significance in one thing you said, about hearing a single drum 'hit', but am not sure what is happening to get that to occur (it does not do that for me).
 
Please also explain what you mean by 'Sampling a drum kit'.  What I am doing is double-clicking on the Session Drummer instance that is in the synth rack, and clicking on the various kit pieces, which triggers them to produce the corresponding sound (snare, toms, etc).
 
Bob Bone
 
2014/05/06 17:42:26
DaveG74
CACTUS MUSIC --
 
I will give your suggestion a try. My means of saving to a Template file is so that I can have Sonar load right into it than doing it manually. But I would guess it's the same as loading the template .CWP just as well.
 
BOB --
 
Thanks for your insight into this bug. I have answered your passages below...
 
robert_e_bone
Can you please take another crack at explaining exactly what you are doing?  If there IS a way to get this to happen, I am willing to keep trying, as it might help the Cakewalk folks out in the event that there is some sort of bug.

 
I've created a Sonar Template file (5 CSC, 5 TTS, 1 SesDrum, 1 SI-Drums) to build my projects from. It's saved in Windows' My Music folder as a Template (.CWT) file, named "Normal". When I build the song, I save as Project thereafter, leaving the Normal template unmodified when I close Sonar.
 
robert_e_bone
1.  You indicate that you saved things as a Template - I am assuming you mean a Project Template, and not a Track Template?
 

 
Yes -- this is a Project template called "Normal". I prefer to have Sonar set to launch directly into the template when I run the Sonar shortcut. I load my existing projects simply by clicking their filename, but when I start a new project, I either click the Sonar shortcut (which, again, loads right into "Normal") or just load the "Normal" file itself.
 
robert_e_bone
2.  I am wondering why you are opening the saved template again, rather than using it as the base for a new project.  Project templates are really intended to be loaded as the starting point for a new project, where you would provide some name for the new project and select one of the project templates to get your new project started.  By opening the template as the saved template, you are making it so you have extra steps when actually creating a new project, in my opinion.
 

 
I intend to use "Normal" as my base for all projects. The silence in the Drums bug was something I stumbled upon when accessing my Normal template. This also happened with the project file of the same build.
 
robert_e_bone
I create Project and Track templates all the time.  To create a Project Template, I would start a new project (usually named some gibberish, since I am not actually going to save the project as a project and do not then need the project folder), and I may choose either Normal or some other template, depending on how close one of those is to what I am trying to build.  I then make all of the adjustments I want, such as loading and configuring a drum synth and its audio tracks and cell output assignments, or even inserting from track templates.  So, when I have whatever template adjustments finished, I do a Save As, change the  Type to Template, give it some meaningful template name, and navigate to the X3 Project Templates folder and hit Save.
 
To USE the new project template, I would start a new project, giving it a real project name, and select the project template I created.  Sonar then loads up that template, with whatever is inside it, and now when I do a Save, it saves it all as a regular Sonar Project file with the name of the project and a '*.cwp' extension, in a project folder, where the project file name and the project folder name are the name I gave the new project.
 

 
First paragraph: exactly what I do. Second paragraph: I deviate a bit from that. I start new projects through the template (set to automatically load), draw in my content, then save to a Project. As you said, starting a new project and choosing the Template from the prompt, I could do it that way, but it's just a few extra steps I'd rather avoid.
 
The method in which a template is to be loaded unnerves and concerns me. The way Sonar loads a template shouldn't affect the operations of one of the synths therein.
 
robert_e_bone
I did a bunch of testing, loading and saving project templates, using Session Drummer, and I had NO success at producing any problems with the drums sounding.  That is not to say that there isn't a problem - I just could not reproduce it, and THIS is why I would like you to provide a set of steps that you do that produce this problem.  THEN, I can also produce the problem and will have something I can work with to help you, and to help report it to Cakewalk for fixing.

 
This template was definitely created after upgrading to Sonar, so hopefully it doesn't have any glitches embedded from my previous Music Creator 6. Just somehow I discovered yesterday that both Drum synths go silent until I add another one.
 
robert_e_bone
I DO think that there may be some significance in one thing you said, about hearing a single drum 'hit', but am not sure what is happening to get that to occur (it does not do that for me).
 
Please also explain what you mean by 'Sampling a drum kit'.  What I am doing is double-clicking on the Session Drummer instance that is in the synth rack, and clicking on the various kit pieces, which triggers them to produce the corresponding sound (snare, toms, etc).

 
Referencing the drum hit sound & "sampling a drum kit": I open up the properties of a drum synth. I select a kit and click on a few drums, and there's no sound. I exit Properties and when I insert a new drum synth, that particular drum I just hit from that kit suddenly sounds.
 
Something is awry with my template, even as a project file of that same build. Upon opening that template, the drum track is silent. No meter light-up either. (I actually haven't tested CSC and TTS tracks to see if they do this also.) I insert a new drum synth and I get the sound back. (At this point, doesn't seem to matter whether I save or not.) I close Sonar, reopen, and the drums are again silent.
 
As I await your follow-up, I may actually rebuild my template from scratch. I'm so frustrated that I've been using the Cakewalk software for almost a year and barely got any work done in favor of experimenting and troubleshooting. I hope to get this worked out...
 
Thanks again for your input in this boggling matter.
 
2014/05/07 16:16:13
DaveG74
EDIT, 5:06PM:
 
When I load this Template, NONE of the inserted synths sound (not just the drums track).
Furthermore, when I insert ANY new synth track, I hear the drum hit of that last piece I struck in the kit preview window.
2014/05/08 10:15:44
robert_e_bone
I responded to your PM, by sending you my email address for you to send me your project template.
 
I will post any findings back here in the post.
 
Bob Bone
 
2014/05/14 10:27:58
robert_e_bone
OK - check your PM's.  I am about to test out what you sent me.
 
I would have done it yesterday, but our entire sub-division lost power for several hours, twice.
 
Bob Bone
2014/05/14 11:36:31
robert_e_bone
OK - I was sent a copy of the Cakewalk Project Template that this issue is about, and this morning I was finally able to carve out some time to test some things out with it.
 
I first downloaded it into the default location for templates on my computer, which is at: D:\\Cakewalk Content\SONAR X3 Producer\Project Templates, and gave it a new name, so as not to disturb my Normal template.
 
I then launched X3, and told it to create a new project, using the newly-saved project template.
 
The project consisted of 5 simple instrument tracks, each pointing to an instance of the Cakewalk Sound Center in the synth rack, all of which had the default sound loaded.  Then, there were 5 midi tracks, each pointing to the same single instance of TTS-1 in the synth rack.  Each midi track was assigned to a midi output channel (1-5), and there was a single audio track labelled to pick up output from TTS-1.  Then there was another simple instrument track, for SI Drums, and one more simple instrument track for Session Drummer 1.  
 
PLEASE NOTE that there was NO loaded preset for the instance of Session Drummer 1 in the synth rack.  Sounds were loaded for all other synths in the rack.
 
PLEASE ALSO NOTE that the audio track, labelled TTS1 Output, had NO assigned Input, so there was no chance of hearing any of the TTS-1 synth sounds, using the project template I had received.
 
OK, so I then opened up each synth instance in the rack, and triggered notes, using the virtual keyboard for the CSC synth instances, the 'preview' button for the tracks of the TTS-1 instance, and the virtual drum kits for both SI Drums and Session Drummer 1.
 
All synth instances in the rack produced sound, EXCEPT for TTS-1 and Session Drummer 1.
 
1.  TTS-1 pressing the Preview buttons OR triggering notes from one of my midi controllers both failed to produce sound.  Upon closer examination, triggering notes from my controller DID generate midi activity, but no sound, and as indicated clicking the preview produced no sound (and no midi activity, but I think that is expected, since it is the internal preview button).  Anyways, the problem, as noted earlier, was the Audio track Input for TTS1 Output was NOT assigned.  Once I set that to pick up output from TTS-1 Output 1 Stereo, then hitting Preview worked, as did triggering note events from my midi controller.  So, that was the problem with TTS-1.
 
2.  Session Drummer 1.  As noted earlier, the instance of Session Drummer 1 had NO loaded preset, and as expected, produced no sound.  As soon as I loaded a preset into its synth rack instance, the kit sounded just fine, when triggered from either the virtual kit in the UI, or from midi controller notes.
 
3.  There were no problems with any triggered notes for any of the instances of the Cakewalk Sound Center synths - they all played just fine.
 
4.  Saving the project, closing and reopening it, I had NO problems playing sounds for all tracks.
 
PLEASE NOTE that for reasons I TRULY do not understand, every single track sent its output directly to output channels of my audio interface, rather than to a Master or Sub Bus.
 
I REALLY don't get that.  There were NO buses present in the project.
 
OK - so I do not know what else to test.  Once I fixed the routing assignments and loaded a preset into Session Drummer 1, everything triggered just fine, and I also had NO trouble saving off a project created from the template, then reopening it and triggering sounds.  It all just worked.
 
Please review the above and let me know what else you would like me to do.
 
ALSO, please explain to me why in the world you would want to skip the use of buses entirely and go directly to audio interface output ports.
 
Lastly, I myself NEVER EVER use simple instrument tracks for anything, whatsoever.  I use separate midi and audio tracks, period.  I am not saying using simple instrument tracks is problematic/wrong, I just find I can do anything at all I wish to with using separate audio and midi tracks.
 
So, I will look for a response from you on the above, and am happy to do any additional testing you wish done.
 
Bob Bone
 
 
2014/05/14 16:53:29
DaveG74
robert_e_bone
PLEASE ALSO NOTE that the audio track, labelled TTS1 Output, had NO assigned Input, so there was no chance of hearing any of the TTS-1 synth sounds, using the project template I had received.
 
1.  TTS-1 pressing the Preview buttons OR triggering notes from one of my midi controllers both failed to produce sound.  Upon closer examination, triggering notes from my controller DID generate midi activity, but no sound, and as indicated clicking the preview produced no sound (and no midi activity, but I think that is expected, since it is the internal preview button).  Anyways, the problem, as noted earlier, was the Audio track Input for TTS1 Output was NOT assigned.  Once I set that to pick up output from TTS-1 Output 1 Stereo, then hitting Preview worked, as did triggering note events from my midi controller.  So, that was the problem with TTS-1.
 

 
I assigned the TTS-1 Output track to the correct input. The meter lit up, but I heard no sound, even after selecting another instrument through the Mixer and the Patch button.
 
robert_e_bone
2.  Session Drummer 1.  As noted earlier, the instance of Session Drummer 1 had NO loaded preset, and as expected, produced no sound.  As soon as I loaded a preset into its synth rack instance, the kit sounded just fine, when triggered from either the virtual kit in the UI, or from midi controller notes.

 
For some reason, even after choosing a Session Drummer program, I heard no sound.
 
robert_e_bone
3.  There were no problems with any triggered notes for any of the instances of the Cakewalk Sound Center synths - they all played just fine.

 
I am not able to hear sound (or get the meter to light for any of the five Sound Center tracks.
 
robert_e_bone
PLEASE NOTE that for reasons I TRULY do not understand, every single track sent its output directly to output channels of my audio interface, rather than to a Master or Sub Bus. I REALLY don't get that.  There were NO buses present in the project.
 
ALSO, please explain to me why in the world you would want to skip the use of buses entirely and go directly to audio interface output ports.

 
Honestly -- I haven't learned how to use buses or become aware that they would be the smarter alternative.
 
robert_e_bone
Lastly, I myself NEVER EVER use simple instrument tracks for anything, whatsoever.  I use separate midi and audio tracks, period.  I am not saying using simple instrument tracks is problematic/wrong, I just find I can do anything at all I wish to with using separate audio and midi tracks.
 


Please pardon, but...would you elaborate?
 
I am grateful for your assistance on this! :) When I received your response, I was excited to learn that I had simply ignored a minor oversight that some instruments merely weren't selected. But after examining these solutions and trying them myself, I cannot get any of my tracks to sound.
 
However, my sound comes back for ALL tracks when I insert a new synth track of any kind. I am stumped.
 
Please advise. Thanks again for your assistance! :)
2014/05/14 19:35:07
robert_e_bone
I would suggest you go through the tutorials, to help you get up to speed on X3.
 
I do not know why you cannot get sound - I literally used the same template you sent me, with only making the changes of loading a preset into Session Drummer 1 and setting the Input routing for TTS Output to pick up the stereo output.
 
I use separate midi tracks and audio tracks as a matter of personal choice, I work with multi-timbral instruments, like Kontakt 5, and want to have multiple midi tracks associated with a given instance of it, so I do that with separate midi tracks.  I also will have separate audio tracks - either a left and right for each loaded instrument, or sometimes i single stereo track for each loaded instrument.
 
I frequently have different effects on one side or the other of a stereo output, so I tend to use a separate left and right audio track.
 
Bob Bone
 
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account