Heh... No technobabble here, sir. There's a known issue where D&M products erroneously use 1ft=1ms that MultEQ-X corrects for, but that you can sort out yourself by multiplying distances in feet x 0.889 (or 0.875 for metric). Plugging in physical distances would, in that case, give you slightly incorrect delays.