I've been having all kinds of issues with timing as I record that I've basically realized are latency issues. (Using Reaper and an M-Audio Profire 610) So I measured my latency as follows: 1. Inserted a click source in my DAW 2. Sent that signal through the output of my interface looped back into my input and recorded it 3. I then measured the distance between the click source and my recorded click source (in sample units) and determined what my round trip latency was/is. 4. In my DAW I override the internally reported latency from my interface to set it manually the number of samples I measured as my latency. Now if I'm right about this, it captures and accounts for roundtrip latency - that is to my ears from inside the DAW then through my interface, and the latency involved in my guitar signal going through my interface and being recorded by the DAW. If I wanted to more specifically account for any specific latency caused by plugins etc I could do that same loopback test but run the click through those plugins as well to see what they might be adding to the issue. I also guess that if I'm listening to my instrument through live record monitoring, my brain would be dealing with an additional bit of difference between the click source in my ear and the recorded monitored output of my guitar and could account for some performance issues.... Where I get less clear is with things like midi-tracks etc... Does latency on midi also get compensated for by my DAW ? Is midi latency different than my other audio interface latency measurements. With respect to midi -- (like a sequence or a drum beat) - should I always send it to a bus to be rendered/recorded as an audio track. If so -- wont this audio only have half the latency of the tracks (given they are not dealing with the return leg of the latency equation)? Thanks guys -- just really trying to get my head around this and really tighten up my workflow so I can get better recordings in the can.