yeah. it's nulling across latency levels, so if the output is different on the monitor (and i think it is), it isn't on the render. that's psychological.

and the bottom end simply does not appear to be there. unfortunately.

i think they overlap about 736, but i need to be playing back about 4096 with the current array of plugins..

i have to go the drugstore and get groceries. i'm going to wait until i come back before i play with anything.

but if somebody is doing this purposefully, they're really just wasting my time.

i mean, latency shouldn't matter when you're just playing back wave files. but it does seem to have an effect on the monitor out in real time when effects are being calculated, which is of course what i want recreated in the render. if i have to monitor the plugins at 4096 to prevent crackling, i'm going to get a different output. it's the kind of thing that 95% of musicians won't notice. but what i do is very intimately tied into the sound production. it's not the two note power chord riff that's of value here, it's the eight guitars i've got playing it through different effects paths.

the key thing is monitoring it at the same level it renders at, so i get what i'm hearing. i mean, there was one song a few years ago that i actually recorded out with analog instead of rendering because of the mismatch.