A Couple Q's on differences between Duo X and Dwarf

Using MOD devices Device Details
2

  1. Latency is the same for all the units, as the codec is very similar between them and we all run them with the same config.
    Likely we will add an official option for 64 frames or something that reduces latency, should be doable on Duo X and Dwarf, but on the Duo it is out of question.

  2. Well, the Duo X limited edition run had a Quad-Core 1.5GHz CPU, and production units have a Hexa-Core, 4 of 1.4GHz and 2 of 1.7GHz (the big.Little architecture thing). In comparison, the Dwarf has a Quad-Core 1.3GHz.
    So the Dwarf sits between the Duo and Duo X, but a lot closer to the Duo X than the Duo. The 4 vs 2 cores makes a lot of difference to make the entire system feel smooth.
    I know that the CPU on the Duo X can do a lot, but not all plugins are optimized the best way for it. If there is a plugin that you feel consumes a lot more CPU than it should, feel free to mention it.

  3. I did not make any tests regarding latency on USB audio mode, so I rather not comment on that. The obvious “gotcha” is that using USB for audio/midi while also actively doing stuff in the web UI leads to xruns (aka audio drop-outs). I am not sure if USB allows to prioritize data packets, something we still need to research. Using USB audio together with WiFi for the web interface gives the best results in my experience.

The big difference of Dwarf and other units is mostly hardware. The headphone is now the small jack, MIDI uses the 3-pin audio-like-mini-jack and there is only 1 screen obviously.
The Dwarf also has knob pagination, apart from the full control pagination. with 3 knob pages per knob, and 8 full control pages, you get 72 addressings (3x3x8) possible for the knobs.