Request: Teensy pins for user-input

[bit-9]

Context
When using a Headless M8, it is necessary to have the M8's front-end window to be in the foreground to receive user input. I often have other programs running in tandem when using my Headless M8 (i.e. DAW, browser, audio player/recorder, screen-capture, etc.), which consistently interrupts workflow.

Request
Allow Firmware to receive dedicated inputs via the Teensy 4.1's input pins for user-input.

Request Details
Allow 8 pins, of the Developer's choosing, to receive a digital-HIGH input to be interpreted analogously to the buttons on a non-Headless M8 (UP, RIGHT, DOWN, LEFT, SHIFT, OPTION, EDIT, PLAY). Conceptually, the user would solder switches (i.e. Cherry MX, momentary ON) between a power-output pin and each of the aforementioned digital-inputs.

Optional Request Details
Given the multitude of I/O pins on the Teensy 4.1, there may be a similar possibility to include user I/O for: MIDI IN/OUT, Audio IN/OUT, keyboard notes/octave/velocity (as per TouchDesigner's settings).

[Monoend]

I think everyone wants this and its just an unspoken thing that people don't address often that adding all the hardware functionality intentionally not inthe headless cannibalizes a lot of people who would buy an m8. I want to get one but I wouldnt order it if everything was available gpio. also midi already exists and was swapped for a midi interface or something and only at that point was it documented as not officially supported. everyone would love it but it doesnt make sense

[trash80]

Headless is not available to make a half-baked M8. It is intended to be used with a computer for either an affordable option or serve as a backup to hardware M8. It will not support any GPIO / MIDI or Audio. If it works, it works out of chance as I am not testing for it.

Adding support for hardware pins has many drawbacks:

1. Even if every function was exposed there are still limitations in terms of SD card performance and SD card presence detection due to the SD card connector and layout of the Teensy 4.1, there are other limiting factors that may leave a bad impression of the physical hardware without ever trying it first hand.

2. I cannot support, for free, a non-testable amount of hardware configurations, nor can I answer / support questions around the matter without spending significant time on the matter.

3. People would abuse this and sell inferior M8 knock-offs at a scale to which I could not afford to stop easily, which could cut into my ability to continue operations. This is a small project which is currently fully funded by hardware sales. If that happens to change in the future, or development stops etc, than things will become more open and hacker friendly.

The current lack of hardware support was never to discourage single user at-home tinkerers or enthusiasts, it is stemmed from the concerns of supporting unknown hardware, fielding user support requests, and discouraging others from selling/profiting from the project without permission.