• SONAR
  • Possible PatchPoint Bug: Silent Aux Track? [Solved - input echo required]
2015/11/29 21:30:58
stickman393
I've been working all day with SONAR Platinum Kingston and I can't work this one out.... I've got an aux tracks in my project, acting as a "sub-bus" for several guitar tracks:
 
GtrA1 ---.
            +----Aux 1 --.
GrtA2 ---'                 |
                              +----- GtrBus ---- Master
GtrB1 ----------------'
 
 The problem is - no audio is coming out of the Aux 1. It's silent.
I know it's not a problem with the GtrBus because i can hear GtrB just fine. 
 If I feed either GtrA1 or GtrA2 directly to GrtBus, I can hear them fine.
 
Has anyone else experienced this? Is there an obvious solution?
 
UPDATE: See below... Aux Tracks need Input Echo to be enabled in order for them to forward their audio input down the chain.
2015/11/29 22:31:27
Mosvalve
Is the input echo on on the aux track? I believe it needs to be on to hear it. Just a guess.
2015/11/29 22:32:34
stickman393
Mosvalve, it's not a monitoring problem; it's a playback/mixing problem.
2015/11/29 22:37:00
gswitz
Please, use the cakewalk problem reporter. Try giving them the project. Or call support.

I'm glad someone is using the aux tracks. Truthfully, I haven't spent any time with them yet.

I'd love it if you get all the bugs worked out before I use it!
2015/11/29 23:40:58
stickman393
Sure, I'll create a problem report if I can get this down to a reproduceable scenario... in the meantime, I just wondered if anyone else had encountered this, and possibly solved it.
2015/11/30 00:26:52
mixmkr
I set it up as drawn above ...and indeed the input echo needs to be on for the aux track.  I even routed the Gtr B1 into the Aux 1 as well....also worked...WITH the input echo on.  Sent Gtr B1 to the gtr buss...worked as desired.    I'm not sure I'm understanding the monitoring versus playback/mixing differentiation though.  ???
2015/11/30 01:09:07
stickman393
@MosValve - you were on the right track. I'm sorry I didn't "get it" when you suggested it.
Thanks, @MixMkr... your additional notes enabled me to see the problem.
 
It is counter-intuitive to me that input echo should be needed. This actually explains some weird stuff I was hearing as I was recording the guitars. I've often used the blue "disable input echo" on the Command Bar to turn off input echo on all tracks, in order to clarify where sounds are being fed whilst recording.
 
Now, if you use Aux tracks, you can't do that. In fact, unless you're 'printing' or 'bouncing' every aux track to a recorded WAV, you absolutely can't disable input echo on all tracks without dropping parts out of the mix.
 
I'm not sure I like this. I get that it's partly my own fault...
 
Darn. Repeat after me: Aux Tracks are not Buses.
 
but I really wish they were.
 
2015/11/30 01:49:19
msorrels
They may not be buses, but they shouldn't have to share the same input echo system as everything else.  They should have their own.
2015/11/30 08:24:49
gswitz
@stickman

You can group the input echo buttons as a permanent group and toggle them all together. This way you could toggle input echo on all but a few tracks.
2015/11/30 13:49:05
Kylotan
This is exactly my problem with aux tracks, which I mentioned in this thread. I understand why they are implemented as an input - because they're basically a real-time audio source rather than coming from clip data - but it breaks my common workflow action of clicking the the 'switch all input monitoring off' button. Hopefully Cakewalk will think of a practical fix soon!
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account