Summary - is there a libavr32/USB wizard here who could help me figure out hacking ansible/trilogy device detection to use DIY usb devices?
I am working on a couple of DIY devices which speak monome serial (grid and arc clones for lack of a better term). These are based on a Teensy 3.x micro controller.
I’ve gotten these working pretty well communicating with serialosc (Max on MacOS) and libmonome (Norns on linux/raspberryPi) with minimal hacking.
So then I wonder can I also get these working with ansible or trilogy modules? Answer: nope - or at least not without some serious hacking
Which leads me to libavr32 source code and trying to figure out how its device detection works. It looks like the magic happens in
uhi_ftdi.c but a bunch of that magic looks very specific to the monome hardware and USB wizardry (usb interface-class, interface-protocol, attributes, configuring endpoints, etc.) which is a little over my head.
I’d like to find out how other devices (i.e. Teensy) could be recognized as “valid” and try to make my DIY devices show up for ansible/trilogy modules.
Any help would be greatly appreciated. Thx!