Think its time to give up on my Tascam US 1800

Have you tried to update your drivers? I see there is a new version V 2.05 since the 26-12-2014. I would try that first.

I asked this already but my post was deleted ...
 
What are your latency numbers with what machine?  I've been thinkng about buying one of these.

Pictures and all that  :)
 

Thanks

So when you say your having latency issues, Is this when you turn on input echo? 
 
With my us1641 the best I could get was about 14 Ms but at that setting it would stutter. So I always used the "normal setting which was then around 22ms. 
But I never would "hear" latency because I always monitored from the interface. 
My problem was with using VST's and Effects. My system would just crap out if I tried anything complicated. I always blamed it on my computer which was older and only a duo core 4 Gigs of RAM. 
I had to stay with my in laws for a week and I installed X3 on this HP i7 , 16 gig of RAM/ 7200 RPM drive mega computer and I had the same experience...So I got fed up and drove over to a music store and bought the Focusrite 6i6 and have never looked back. Tascam's drivers are just not great. 
But to tell the truth, the RTL of the Scarlett is not a heck of lot better than the Tascam, it's the stability that's hugely improved. 
Edit:
I see we where typing at the same time.. If your tracks are not in sync then there's something gone weird, I never had that issue with my Tascam. 

I'm glad I read this thread because of what cowboydan posted I just went to the Tascam support page and well .well they have finally updated the drivers, last update was 2011 so I never even bother looking anymore.. So this might just breath so new life into the old girl. Not overly optimistic that it's going to be earthshaking improvement but nice to be able to still carry on with Windows 8 support. 
Thank you cowpiedan 

+1 I was going to recommend testing your offset. Sonar and the drivers do this automatically and normally it's never an issue. 
So testing the function is one way to rule that out as being the issue. 
 
Just a small change to the above method. 
 
I would not change any setting first to see if the offset is being calculated correctly. This will change if you change audio buffer settings so it's best to leave it on auto if you can.
 
Use a short patch cable and connect an output back to an input and re record any transient audio track. The more visual the transient spikes the better. If you don't have one, make a audio track by bouncing a midi drum track. 
Record to a new audio track next to the original.
To check for clock drift you might want a whole 3 minutes.
Zoom in on the 2 tracks and see if there is any offset showing.
Right now your using your ears. That is flawed. You need to test the system first.
 
If the tracks line up all is good and you need to look elsewhere for what your hearing.  
 
 

Sorry - I just noticed you posted back.  I'll do some math and post tomorrow
 
What sample rate are you running?

OK, you measured 2119 (avg) sample latency.  At 48K, that's about 44.14ms.  Hearable for sure.
At the bottom of this dialog, is the total roundtrip number in agreement with your measurement?

 
At the bottom of this dialog, is the previous number listed and "Use ASIO Reported Latency" checked?  If the numbers agree, but the box isn't checked, then checking the box should set you up.  If the numbers don't agree, you leave the box unchecked and enter 2119 in the manual offset box.  NOTE:  The Device dropdown selection never stays at what I select.  It doesn't seem to matter.

 
The downside to manual offset is that changing your driver settings will require you to change this number accordingly.  It's best if you're able to use Reported Latency.
 
I hope this makes sense  :)

ftf613
Now I have my driver set as WDM, for some reason it seems ASIO doesnt work with the Tascam. I will check when I get home tonight. Thank you for all of your help.

You really should concentrate on getting your interface to use its ASIO driver.
 
Have you installed the latest Driver V2.05 for Windows from Dec. 26 ?
 
What shows up in Sonar Preferences with respect to this driver ?
Can you supply some screenshots ?
 

The new driver  ( for the us1641) was a total disappointment. No change at all for me. Still reporting a RT latency of 50ms. Lower than that I'll  get crackles.  
 
So I changed to WDM mode and ran the test and then set the buffer slider in the middle somewhere. The crackles are gone and everything seems to work fine.  
But I lost the outputs 3/4 ?? so I switched back to ASIO. 
Anyhow, we are still dealing with crappy drivers. 
The same computer has no issues at all with my Scarlett. 
 
I'll run the loop back test later. 

This is Tascam ASIO normal setting 

 

 

Johnny, I don't quite see what you're doing here so I have some questions that may or not make sense.
 
How does an interface come into the picture when you're playing a midi track ?  Are you doing a loop back or something ?
 
How can an interface react to a midi note before the note happens ?
 
The tracks using the Scarlett look more like noise than drums.  Is there supposed to be a hit like with the Tascam ?
 
 

Thanks guys for your help. Hey BobF the 2119 was way off so I guess I do something wrong in my measurements. After some fiddling I have found that around 804 seems to work, though I recorded some tracks last night that may seem to differ, but could have easily been sloppy playing. Any thing else I should be looking at?

Also i asked before but not sure anyone could answer but using offset, when I export tracks for someone to use in their DAW will this creates timing issues like with click tracks and the like?

Sorry I haven't had a chance to test if mine will swicth to 48 Michael. Once I finished the Jazz recording I had to swicth back to my Scarlett to continue with other projects. I didn't want to have Sonar freak out about the interface. It actually doesn't freak out much because both have the exact same output configuration. 1/2 - 3/4 and SPDIF. 
Might try it tonight. 
But as I said there was a huge differance in the performance when using the better computer. The RTL will not change much because that's also partly a hardware issue and those hidden buffers. So you won't get better latency no matter what. But the fact that the driver seemed more stable than before and also the reported latency was very close this time make me think they did improve it somewhat. 
 
While I had it hooked up I fired up a project with a lot of tracks and both VST's and effects. 
This was where the Tascam bombed out on me in the past. It couldn't handle big projects. I bought the Scarlett and the problems went away immediately. But now the us1641 is working just fine. So the computer must be a factor. Make double sure the new drive did install properly. 
Tascams driver install is terrible and I think this is part of the problem. Example. on the first office computer I originally did the loop back test  ( bad results), Windows 8.1 had always flagging the Tascam as not installed properly in that fix issue task bar thingy. That computer had the original 2.1? driver installed first and then I updated it to the new one. 
On the DAW where it's working properly  I never had the old driver installed, I don't have that message. 
If I have time I'll try obliterating all traces of the Tascam's drivers and re installing the new driver and see if it works better. It might be one of those issues for you too.