Had an OXI for over a year and a half before selling it off in frustration and replacing it with Hapax.
Number one reason? The firmware development is a mess. This is also the reason I won’t be considering OXI One MKII or any of their other gear.
Constant workflow-breaking tweaks, constant regressions, a promise of an all-powerful app with every major version that never materialized (promised again for 5.0), etc. Firmware versioning was a mess. You’d find yourself running a certain release FW number and find that the beta for the next version was a lower version number. Or updates would be posted over a short period of time without updating version numbers. Or the betas would be fed to the release stream and the updater app would notify you of a new version number without indicating it’s a beta, and you’d find yourself with a buggy, regressive device when you thought you were getting a tested, polished update.
Mutes kept getting broken then fixed then broken then fixed. The UI pages for saving, loading and arrangement look identical, so it’s easy to accidentally lose what you just changed or accidentally reload or overwrite when you intended to do something else. LSB/MSB to this day don’t work properly, making program changes on some devices impossible or needing a mod lane workaround, in addition to the fact that the settings for each are split across UI pages. (This is promised to be fixed in 5.0. It was also promised to be fixed in 4.0 when I brought it up before selling the ONE.)
Fixes and feature tweaks/additions are not separated, so a new FW update might have a really cool feature, change a feature you depend on, a bad regression, and/or fixes to important things all at once and you’re forced to cross-reference which of those will affect you and weigh if it’s worth it.
THAT BEING SAID…
The OXI ONE hardware is amazing. It has double the CV/Gates as Hapax and has some unique generative ideas that are fun and musical. And obviously the size and battery and build quality are stellar. (Though the size does limit the amount of UI real estate, causing a lot more dependence on shift combos and UI paging. This is understandable and a fair price to pay for the smaller size.)
My advice to any potential OXI ONE owner is to first dig through their Discord and see if any issues might affect you. And then, if you are on a firmware that’s stable for your given use case, to not update without doing a ton of research.
To OXI’s credit the team is super responsive, but they take the implementation of community-requested features to an extreme that causes all sorts of problems. If they were more disciplined with the development and split fixes and feature changes/additions to alternate release cycles, or spent a LOT more time testing between releases, I think it would be a lot easier to recommend.
Overall, the Hapax’s biggest strength is the size. The simple fact that it has more room for a much more thought-out set of controls makes it simultaneously more intuitive and fun to use. Going to Hapax from OXI felt like it gave me room to breathe. OXI felt cramped, and the layers upon layers and fear of loss of work stoked constant anxiety.