mettelus
LOL, 96K is "cheating" I never record at that, but finally have the system back online so can give you quick numbers, 96K/256 buffer is 733 samples total (8.3ms), 44.1/128 is 367 (also 8.3ms), and 44.1/64 is 239 (5.4ms). It will go down to 32 "supposedly" but never tried it. As Jim Roseberry mentioned, I assume there is a "wall" at around 5ms anyway (and the CPU load is unnecessary).
From Johnny's thread on offsets, it seems the Focusrite products are more optimized to the 48K spec. Another thing to bear in mind is my offset is 76 samples - it seems this is "built-in" to accommodate loopback functionality inside the box.
I may have missed it in the thread, but which amp sims are you running?
Your one comment made me chuckle. Personally if it isn't broke, I don't try to fix it (but planning is good). You are "banking" on impending doom, but worry like that is best dealt with when the time comes.
mettellus - Yeah, I've been cheating since the beginning. I got into Sonar by myself, and my whole learning process was setting it up (by myself) and recording & mixing (by myself), so I had no one to tell me that 24/96 was "too much." After all, the sound card is actually
called "Audiophile 2496." How was I to know? But it has worked well for me: Until I started shopping for a replacement, I didn't even know latency was an issue.
As for worrying too far in advance, Part B of my plan is to start using my laptop for recording on location, so that's what got me started looking for a new interface. Worrying about drivers for Windows 10 was just a fun bonus.
Thank you so much for all your help!
PS: I use Guitar Rig 3 (that came with an earlier version of Sonar), TH2 Producer and various guitar FX chains by Craig Anderton. I just don't want to mic an amp and make a whole bunch of noise, and most of my music doesn't really require that sound anyway.