Is there a way to adjust the amount of reverb when using the Input Echo Button for audio data?

You probably mean the echo that is caused by what is called latency. The delay caused by the conversion of analogue to digital and back again put very simply.
This is a result of how large your audio buffers are set.
What audio device do you have and do you know what size the buffers are?
Check Sonar preferences, audio, devices, and the 2 pages underneath for a complete view of your system audio properties.

Its not reverb. Its called latency. Input Echo is not a reverb effect. It just enables you to monitor the signal live, in real time through Sonar.
 
to reduce latency, you need to lower your audio interface/sound card ASIO buffers or lower the WDM slider position, depending on what driver mode you are using. If your using MME driver mode, do not use it anymore and use ASIO or WDM, as htese drivers modes are better and your audio interface has drivers written for ASIO and/or WDM, Not MME. If you are using an onboard sound chip, your $hit out of luck, as you need a semi professional interface with a profession program, like Sonar.
 
CJ

Hi gang,
 
I'm using the Fireface UFX for my interface.
My driver mode is set to ASIO, and my buffer size is set to 1024 samples.
Did notice an ASIO report of latencies which says:
 
Input:  21.9 msec. 1051 samples
Output:  22.8 msec  1092 samples
Total Roundup:  44.6 msec,  2143 samples
 
Was primarily using this Input echo button which Scott Garrigus talks about in his book Sonar X2 Power pg. 60 which he mentions using this button while recording an audio track and monitoring to get reverb from dry signal.  But when I enable the Input Echo button, I get way too much reverb than I need. 

RTFM!
 
http://forum.cakewalk.com/Input-Echo-Button-for-Audio-Data-m2931165.aspx
 

Rick5
Hi gang,
 
I'm using the Fireface UFX for my interface.
My driver mode is set to ASIO, and my buffer size is set to 1024 samples.
Did notice an ASIO report of latencies which says:
 
Input:  21.9 msec. 1051 samples
Output:  22.8 msec  1092 samples
Total Roundup:  44.6 msec,  2143 samples
 
Was primarily using this Input echo button which Scott Garrigus talks about in his book Sonar X2 Power pg. 60 which he mentions using this button while recording an audio track and monitoring to get reverb from dry signal.  But when I enable the Input Echo button, I get way too much reverb than I need. 

When youre recording set your buffers on the UFX to 96. Only go up to 1024 when youre mixing a project that's has a high track and plugin count.

Sigh...
 
The Fireface UFX offers onboard reverb and echo fx for monitoring (see p.67 in the UFX manual) and thus there really is no need to rely upon monitoring path latency difference gimmicks or even to use Sonar's input echo function at all.

When tracking (recording), I set the ASIO buffer low (like 64 or 128) so there is no delay and I just live with any little crackles I hear.  After recording and while mixing, I set it back to 1024 so there are no crackles, pops, or audio drop outs.
 
On my system, which is a fairly powerful custom audio PC, I cannot record a singer at 1024 because the slap-back echo is horribly confusing.  Trying to record from a keyboard is equally trying.  At 64, the problem goes away.  (64 is pretty low, but it works for me.)  Just don't forget to go back to the higher setting before mixing or you will face a different set of issues.
 
This is a little annoyance but not too serious.  In a year or two, our PCs will be powerful enough that we will laugh at this and be surprised we put up with it.
 
And, may I add, that compared to drop-outs, lack of editing, and other issues with tape, I am willing to live with this.  

Thanks everyone!