11-04-2021, 01:49 AM
(11-03-2021, 07:00 PM)Tim Curtis Wrote: I don't think its as low level as a HAL but more like a class definition or function set that allows the custom, device-specific switching code to plug into.
If I were a dev that wanted to code a device into the existing input switching sections of moOde I'd just do it directly rather than writing both an interface mechanism and the custom device specific code. Even directly coding a device is very time consuming because there are a lot of moving parts that have to be created/updated. I stopped after two devices because it became too time consuming (for me).
The good thing about it is that the interface (and instantiation mechanism) is, ideally, only written once, and it makes it a lot easier to extend with new cards. This also allows distributing the burden of testing/maintaining, as long as the maintainer of moOde is willing to trust contributed interface implementation code
![Wink Wink](https://moodeaudio.org/forum/images/smilies/wink.png)