I note that the [hi] human interface object does not appear to pick up all USB devices. For example, my M-Audio Oxygen 8 MIDI keyboard is not recognised as a USB device (tho’ its MIDI information is, of course, available via objects like [midiin]).
Is this because of the driver that accompanies such a device? Is there anything that can be done about this in Max to make such devices ‘visible’ to [hi]? Or is there another object that allows access to the raw data coming from the keyboard without it being parsed as MIDI?
I would also love this for the Emotiv headset. Man could you do some fun stuff in Max with that…
There is someone who made a mini-app that translates the Emotiv’s signals into OSC, which Max could then pick up. Can be found on the Emotiv forums under "Mind your OSC’s".
But a [hi] method would be more straightforward, if it’s possible.
The [hi] object is designed to work with HID class devices, which is a special subset of the USB spec. HID was designed originally for input devices like mice, keyboards, and joysticks so that new devices would not require special crossplatform drivers. MIDI USB devices use a whole different specification.
Ah, so it would be up to the Emotiv folks to make it HID-class compliant. Or they could change their output from the wireless receiver to spit out OSC, MIDI, or the data via UDP, etc. Thanks for the clarification.
now I just need to scrape up the money to buy one…ach
C74 RSS Feed | © Copyright Cycling '74