• SONAR
  • Auto Mute on Armed Tracks during Recording Only - Sonar X1
2018/02/06 17:18:09
Voda La Void
Struggling to figure out if Sonar X1 has the option to mute the record path playback on armed tracks during recording only.  I need to monitor at the interface, so I will be hearing my recorded instrument playback at the interface and do NOT want it played back out through the DAW, creating that slap back effect due to the latency.  But, I also need to be able to hear my record path coming out of the DAW to set levels and sound and etc.  
 
The easiest way would be an auto setting to mute the playback of the recording path during "record" only.  Some articles I've read seemed to suggest some DAWs have this feature.  
2018/02/06 18:49:07
Cactus Music
Don't use input echo on the track you are recording if it is audio. You only use input echo while recording midi tracks so you can hear the instrument. 
2018/02/06 18:56:21
mettelus
You can also manually mute an armed track, it still records, but you do need to set gains first. This is almost required when doing any type of loopback recording.
2018/02/06 20:26:27
Voda La Void
Cactus Music
Don't use input echo on the track you are recording if it is audio. You only use input echo while recording midi tracks so you can hear the instrument. 




Doesn't input echo mix your input signal with your processed input signal?  I am looking to mute the input signal altogether. 
 
mettelus
You can also manually mute an armed track, it still records, but you do need to set gains first. This is almost required when doing any type of loopback recording.



Yeah see I will need to be able to play back a recording to review it.  And, I will need to hear the previous parts of what I'm punching in on.  That's why muting the input signal from playback is the best option.  That still lets you hear the last little bit of whatever you played just before the part you're punching in on, and you can quickly check your recording to make sure it's ok.  To manually mute on and off would be tedious and time consuming.  But I appreciate the response. 
2018/02/06 21:34:55
chuckebaby
what kind of interface are you using ?
I hear both processed within DAW and RAW sound from my interface at the same time unless I set it to DAW Recording.
2018/02/06 22:04:10
Voda La Void
chuckebaby
what kind of interface are you using ?
I hear both processed within DAW and RAW sound from my interface at the same time unless I set it to DAW Recording.




Right now I'm using Mackie i1620 Mixer/Interface with a firewire 800 connection, soon to be upgrading to the Soundcraft MTK 22 with USB connection.  Both handle audio the same way.  I have instruments and mics plugged into the mixer for the record path, and I have been just putting up with the relatively low latency and just listening to all input signals coming out of the DAW's sound card.  
 
Now, I want to start direct monitoring at the mixer for zero latency monitoring and circumvent the DAW sound card altogether.  Shouldn't be too big of a deal, really, just need the record signal to *not* come back from the DAW.  
 
Basically, it's just a direct monitoring scenario for any interface.  Anytime you monitor at the interface you are not going to want to hear your input signal come back again from the DAW.  It will be delayed and distracting, at the very least and impossible to record with at worst.  
2018/02/06 23:57:58
Cactus Music
You do not activate input echo if you DON't want to hear your incoming signal go back out the other end. 
You turn off input echo to stop hearing the input at the output of your interface. Other wise you will hear a small delay depending on the driver. Mackie's driver is not the greatest so you probably have 20-30 ms of delay. 
 
You do not have to mute the tracks. 
Direct monitoring is defiantly the way to go and all you do is mix the output of the all ready recorded playback from your DAW with your input signals. There is no latency this way. 
The minute you activate input echo that track will pass through to the outputs and you will soon find out how much round trip latency your system produces. 
Only top quality audio drivers like RME/Motu  at low buffer settings can go low enough to not be noticed. 
2018/02/07 03:15:35
Voda La Void
Awesome, thanks Johnny V.  
2018/02/07 12:32:58
chuckebaby
The last driver for the Mackie Firewire was for Windows 7. Are you still using Windows 7 ?
If you are using the Windows/ or a compatible driver for the Mackie, you shouldn't be hearing any latency.
 
Voda La Void
Doesn't input echo mix your input signal with your processed input signal?  I am looking to mute the input signal altogether. 

 
Not necessarily. But as I mentioned in my previous comment, unless your interface is set up to only hear processed data.
You can turn off input echo but you wont be able to hear any FX, Amp Sims, EXC while recording.
Just the dry signal.
2018/02/07 13:53:26
Voda La Void
chuckebaby
The last driver for the Mackie Firewire was for Windows 7. Are you still using Windows 7 ?
If you are using the Windows/ or a compatible driver for the Mackie, you shouldn't be hearing any latency.
 

 
Right now I have a round trip latency of around 20 ms, on this current old system.  But I have a new DAW built and ready for the Soundcraft mixer purchase which uses USB 2.0.  It will have even more latency due to the nature of USB.  So, it's not just the Mackie, it's also the gear I'm planning for.  
 
The way I approach problems is to shoot for the most practical solution that eliminates the problem altogether.  I could play all these buffer setting games, spend a billion dollars on amazing computer parts and audio gear and maybe when I'm done I'm down to a low latency recording chain.  But there's still latency...so I've gone broke just to mitigate a problem that could be eliminated altogether with a more practical solution: direct monitoring at the mixer.  You can't beat the speed of light for latency, that's for sure.  
 
chuckebaby
Voda La Void
Doesn't input echo mix your input signal with your processed input signal?  I am looking to mute the input signal altogether. 

 
Not necessarily. But as I mentioned in my previous comment, unless your interface is set up to only hear processed data.
You can turn off input echo but you wont be able to hear any FX, Amp Sims, EXC while recording.
Just the dry signal.



Yes, just the dry signal as it hits my mixer is exactly what I'm after.  I don't use Amp Sims really at all, and any FX I use are applied to a dry signal.  My whole studio set up is about capturing instruments and performances so dry signals are all I'm ever going to hear when laying tracks anyway, whether out of the DAW or right at the mixer.  
 
I ran out of time last night to test out the input echo, so I'm hoping to get the time tonight to see if that's the solution for me.  
 
12
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account