I think JDSLabs has a right approach here: managing complex DSP features on a device display can be done (see RME)…but quickly becomes very complex and may be the wrong approach in the end. At the same time, there is definitely a need to balance what can be done on the device itself vs. what is only available through the app—same debate as cars “information system”, touch screen vs. buttons, knobs, and dedicated sub-displays. The Element IV may be lacking a few useful on-board control, or a way to expand/overload the knob functions (short press, long press, double press, triple press, etc.) via settings in the app.
What John Seaber does not cover in his blog is what can and can’t be done with the XU316….
See the Neutron HiFi DAC V1 review thread
https://www.audiosciencereview.com/forum/index.php?threads/neutron-hifi-dac-v1-review.56647/ for reference.
I know it’s ‘just’ a dongle… but the architecture is not that different, and Neutron is already fine-tuning the balance between adding more DSP features and how many of those can run concurrently vs. the available processing power of the embedded ARM processor.
The XU316 appears to be a fairly powerful (specialized) MCU, but it ain’t specialized DSP, that was my all point!