Matt,
Some explanation: there is a list of JRiver's convolver features summarized in the first post. Two of the features mentioned as being supported are 1) input channel weights and 2) partitioned implementation.
On 1) mattkhan and I haven't been able to get input channel weights working.
On 2) Both mattkhan and I have measured latency for the convolver and the latency we measured seems consistent with an unpartioned implementation. We both measured delay equal to ((filter taps/2)/samplerate). That's the delay that one would expect with an unpartitioned implementation.
The questions are:
1) Is channel weighting/scaling in config files supported (whether input or output)?
2) Is the convolution implementation partitioned, and if so why is it showing latencies consistent with an unpartioned implementation?
3) Is the feature list in the first post accurate? Are there additional features, or alternatively are some features on that list no longer supported.
I have a few other questions as well about MC's automatic resampling of filters (I've never gotten it working, but it obviously works for some people), but I'll wait to get those answered until mattkhan's issues are sorted.
EDIT: ninja'd, but I'll leave this here.
Honestly I don't even know what a partitioned implementation is. And I wrote our convolution engine!
Here's a link to some discussion of another partitioned convolver and the i/o latency reductions anticipated:
http://www.ludd.luth.se/~torger/brutefir.html#bruteconv_3