The problem with any processing is that you have an output that has a larger bit depth - in the case of Hugo 2 its internal processing is at 48 bits for the cross-feed. This needs to be converted back to 24 bits for the next stage processing; and I can do this very aggressively with maintaining small signal accuracy via noise shaping at 705/768 kHz so that depth perception is not degraded. But doing it via a PC means the OP truncation to 32 or 24 bits is via dither as you are limited to the original SR; and my tests with dither shows that it is not as good in preserving depth as doing it at 768k with noise shaping.
We are not talking about vast changes though. But one potential problem is whether the software coder is significantly aware of the essential importance of small signal accuracy. IIR design to ensure absolute small signal accuracy is not trivial. Now I am not saying that EQ apps sound poor; I am just making the point that it is not as easy as it might appear, and there is considerable potential to mess up transparency.
Rob
Thanks for sharing Rob. With my Mojo I definitely prefer to use it (with my PC software, for obvious reasons).
But since it's a built in feature of the Hugo 2 I will definitely leave it to the expertise of the Dac.
I had a look at my PC software. DSP is done at 64 bits (obviously a good thing) but indeed it looks like the original sample rate is maintained. I need to ask them if noise shaping is done at higher SR (for cross feed) - for my Mojo.