FlexASIO VS RESTinio

I had a similar issue with my setup, I suggest using FLEXASIO. Youll need to download flexasio and the gui component to use it. https://github.com/dechamps/FlexASIO

The problem I have with FlexASIO is that it only supports having 1 input while the katana requires multiple. See: https://github.com/dechamps/FlexASIO/issues/147

The UMC-22 has a budget Midas-type pre-amp which is hard to beat under $200. That said, the UMC-22 also has terrible ASIO4ALL based drivers which can partially be worked around by using something like FlexASIO. Ultimately though, the drivers won't matter unless you are using heavier VST plugins for your voice/audio input.

FlexASIO allows none exclusive mode but it does it in a different way to regular ASIO drivers. You will have to give it a try to see if it can provide a latency that is acceptable. It is meant to work with more hardware than regular ASIO drivers. I suspect that latency might be compromised somewhat but give it a try to see if it works okay for you. It does explain how it works compared to other ASIO drivers on the github page.

FlexASIO

https://github.com/dechamps/FlexASIO/releases

FlexASIO is the modern and IMO better alternative to ASIO4ALL, just sayin.

You could try https://github.com/dechamps/FlexASIO It's a universal asio driver that allows non-exclusive mode

flex asio - https://github.com/dechamps/FlexASIO/tree/flexasio-1.9 and https://github.com/flipswitchingmonkey/FlexASIO_GUI

In my past job, we used https://github.com/Stiffstream/restinio and absolutely loved it. It's not as active but it honestly didn't need much.

Here's a C++ REST framework for you to use too: https://github.com/Stiffstream/restinio

I had a good experience using restinio for a small ASIO HTTP server recently.

It uses restinio https://github.com/Stiffstream/restinio with great success ;)

For networking, pick a networking library. Restinio is a fair choice for HTTP. But, again, feel free to pick others.

You may find this worthwhile: https://github.com/Stiffstream/restinio/issues/101 FWIW, I used Restbed successfully for 3.5 years before switching personal projects to Restino. I've left the job that used Restbed, but I think they are still using it.

Contrary to the direction most people go, I've been writing REST APIs as C++ servers using two different fairly full featured C++ REST frameworks: first using https://github.com/Corvusoft/restbed and more lately using https://github.com/Stiffstream/restinio. These can be peers with any other server, while living on embedded and/or high compute devices for video encode/decode/analysis, deployed ML models, encryption for and remote process communications, model data collection and similar expensive or in-field processing. In both high compute and in-field-no-internet situations creating REST APIs in C++ enables speed and system controls not present in the majority of the mainstream REST frameworks. It's a big world, and here comes ubiquitous high compute...

If you need an embedded C++ HTTP server then there are plenty of libraries/frameworks (in random order): Crow, RESTinio, Boost.Beast, cpp-httplib, http_backend, Pistache, RestBed, served, proxygen, Simple-Web-Server, drogon, oat++.