papawiz
...if i turn on the input echo so an artist or myself wants a little reverb coming in, or to add some compression in real-time on the input signal, there are serious delays,  the only one way is when i turn down the master fader so I don't hear the echo delay, But by doing so i cant here the reverb , there's a 2-3- second delay, and also in cakewalk notes they explain it but does no good,  i have tried all the latency , and interface trouble shoots...

 

scook
There is a Mix knob on the UR-22 to control the ratio of input (IOW direct signal) to DAW signal sent to the interface outputs. Since the direct signal goes directly to the interface outputs SONAR cannot control that feature of your interface.

So if you turn this knob all the way to "DAW" you won't hear any of the input foldback from the UR-22. Then you can enable input echo in SONAR and add a little reverb for your singer. The UR-22 should deliver <15 Msec latency (probably better), which in my opinion is fast enough.

Cactus Music
Chuck, this is not possible. 
 

 
To eliminate the echo from input monitoring
1. Open the Windows Volume Control window:            
Windows 7: Click the Windows Start button and go to Control Panel > Hardware and Sound > Volume Control. The Volume Control window appears.
 
2. In the Play Control window of the mixer, check the Mute check box in the Line-In column, or in the column of whatever jack your instrument is plugged into, and close the mixer window.
Now you can hear only the processed sound when you use input monitoring. Using WDM or ASIO drivers for your sound card keeps latency to a negligible amount.

That seems to be instructions for using on board audio, right? 
That has nothing to do with using an interface, You cannot control an ASIO interface in Windows control. that can only be done with the interface GUI. 
 

Ya, Im not going to be debating anyone's ideas here. That's only confusing the OP and not helping.
I am however just taking an estimated guess (like you are).
 
This right here
 

papawizwell i have tried 4 interfaces on 3 different computers, and the issue is still there

 
It sounds like he is using the inputs of these 4 interfaces but not using the correct driver, instead he is using onboard audio driver.
Possibly the OP new to this and doesn't understand the set up process in preferences and that's okay, we all start somewhere.
 

chuckebaby
Ya, Im not going to be debating anyone's ideas here. That's only confusing the OP and not helping.
I am however just taking an estimated guess (like you are).
 
This right here
 

papawizwell i have tried 4 interfaces on 3 different computers, and the issue is still there

 
It sounds like he is using the inputs of these 4 interfaces but not using the correct driver, instead he is using onboard audio driver.
Possibly the OP new to this and doesn't understand the set up process in preferences and that's okay, we all start somewhere.
 

I get what you meant to say, I assume. 
 
To clarify the terminology, I think you meant he may be using the Windows audio drivers (e.g., WDM/MME/Direct Sound/WASAPI, etc.) rather than the onboard audio drivers (e.g, Realtek).  Those are usually OEM hardware specific and wouldn't work with an audio interface from another brand.
 
The ASIO drivers that come with the interface are the only drivers that should be configured in Sonar.
 
I agree the OP should start at the beginning of the setup process and describe EXACTLY the steps taken with each interface, and the driver settings used with each, in detail.  Otherwise we are all guessing here, and it could just be a matter of a simple assumption or oversight causing the issue. 
 
Blaming a DAW for following the laws of physics is not going to solve anything.

This is really an old topic, the OP is asking about the best way to record "what u hear" and get his/her what u hear to be a signal without latency.....the only answer is what scook and cactus have been explaining. That no matter what daw, if one uses the AI monitoring as it's designed with it's onboard basic effects (if any, some don't have any) there's no or the absolute minimum RTL because it's before the daw. Often there's reverb, to give vocal artists some support, that's the most common.

If monitoring after daw effects, there will be some RTL in every daw. The more familiar a User is with his tools the better his results in setting up monitoring/recording.

It may be the OP will use all the good info here and solve his own questions. That's what most do, when trying out different settings, effects, etc.

RSMCGUITAR

papawiz
all i was trying to do was see a way to record vocals in realtime with a little reverb already on the input audio track (vocal) by using the reverb on the input track inside sonar, ( i turned down / muted the master fader and the delay went away but cant hear the reverb,
well i have tried 4 interfaces on 3 different computers, and the issue is still there, wish they write a new algorithm just for this issue, 

If you're hearing ANYTHING with the master fader turned down that could ONLY be because you are directly monitoring from your interface.

Just to be clear, are you turning this knob all the way to DAW??
 

That's a very good point, and should be the first step if you wish to monitor your DAW output (with reverb FX).
 
The second step is to get your computer and DAW latency as low as your interface and driver can handle.  Properly configured, many users are happy with the results they can get with Sonar.
 
The bottom line here is that it should be a case of monitoring all one source or the other, but not both at the same time. You are obviously going to always have more latency running the signal round trip through the computer processing, and that will never sync up with the direct input real-time monitoring of what you hear in the room.

papawiz - Thousands of SONAR users are monitoring through the DAW, with effects and low latency. Has any of the advice here helped you?

As long as the premise is "well i have tried 4 interfaces on 3 different computers, and the issue is still there, wish they write a new algorithm just for this issue" it will never be possible to find the source of the problem because it has nothing to do with the input echo algorithm. An input echo button simply passes audio through the computer to the output. As Larry Jones has pointed out, thousands of musicians are using input echo with SONAR to monitor with low latency through effects. I am one of those thousands. If you are getting extreme latency, the issue is either how the system is set up, or the operator. These are beyond the control of the manufacturers who make the gear we use.
 
If you're using Thunderbolt, who knows what's going on with your system - very few PCs are Thunderbolt-friendly, and you need a very specific chip set. Also, 6 GB RAM is hardly enough for Windows to even wake up in the morning.
 
As to monitoring through reverb, the effect itself typically has more milliseconds of pre-delay than most people ever experience with an interface. As detailed in this thread, there are other ways to record with reverb in the voice. Given the basic attributes of an Apollo interface, there should be no detectable latency problems recording vocals while monitoring through reverb. The only latency is due to A/D and D/A conversion, which is unavoidable with digital gear and is less than 2 ms.
 
I don't want to come across as snarky, because I know how difficult it is to get Windows-based systems operating properly, and I sympathize. Regardless, when people look in the wrong place for a solution, they will not find a solution. Somewhere in the system - and it could be a SONAR preference - something is not set correctly.
 

Latency-free hardware monitoring

The UR22 features latency-free hardware monitoring and an intuitive Mix knob that allows you to blend between the direct signal and the output of your host.