Lewis Wolstanholme

I am working on a patch that uses a USB numpad with the hi object. My problem is that my Mac, running macOS High Sierra, continues to recognise the USB numpad as a keyboard input, creating conflicting commands with the ones produced in Max. Is there anyway I can bypass this and run the hardware directly through Max at all times, even when Max is a background window? I've looked into using alternative drivers, but ideally I want to keep my use of third party apps to a minimum. It should be noted that the numpad is a generic unbranded model, and doesn't need a driver to function as a keyboard device.

I am working on a patch that uses a USB numpad with the hi object. My problem is that my Mac, running macOS High Sierra, continues to recogn

problem-using-a-usb-keyboard-as-a-hid

Have almost the same setup - am using a generic Onn usb numpad as a audience-facing control surface.

Is there a way to tell the OS to simply ignore the usb numpad ( while still letting max access it ? )

Memory seems to recall the keyboard input patch in Quartz Composer had a toggle to ensure the patch had exclusivity for a specific input device... don't remember if it kept the OS away from it tho' ...

Bump : )

Have almost the same setup - am using a generic Onn usb numpad as a audience-facing control surface.

Is there a way to tell the OS to simply ignore the usb numpad  ( while still letting max access it ? )

Memory seems to recall the keyboard input patch in Quartz Composer had a toggle to ensure the patch had exclusivity for a specific input device...          don't remember if it kept the OS away from it tho' ...

thanks for any ideas/hints gang!
cheers
jd



Problem using a USB Keyboard as a HID