bitflipper, I totally understand what you mean. I don't disagree with anything, so thanks for the reassurance of my own understanding/knowledge.
I've already compensated for latency in the DAW, which gets me synched up to the very sample, much better than even the ASIO self-testing can measure. I do expect some ever-so-slight latency, but certainly not 50+ms. Surely some people have measured much better than that. What's got me troubleshooting and providing workarounds is that as you mentioned, you use a much older machine, and can deal with the latency. So, it must not be quite that bad. My machine is less than 3 months old, with an iCore7 4/8 thread CPU, 16 Gigs RAM, SATA drive, new Intel MB with 2033Mhz backplane, and everything else in order up to what I know, which is fairly advanced.
CueMix DSP is the method we used, because it runs directly on the MOTU PCIe-424 card giving us a mere 3ms delay in feedback. This is very workable, since it allows me to change the feedback volume of the vocal while tracking is going on without causing Drop-Outs. So, this is what MOTU expects me to do, which works very well except, I can't use a compression plug-in (even a very fast one).
I just don't think I should be hearing the singer tell me, "Yeah, this is horrible. It's throwing me off". Maybe what's changed is a setting I didn't catch, or I don't really fully understand the right approach in latency-management.
gwitz, yeah, I do run BitDefender, but I disable it completely when we track. It's been an issue before when it would attempt to read the files Sonar was writing, which was seriously dumb on BitDefender's part. They don't even recognize a DVD movie before hijacking the DVD drive to scan it. heh