Pd-vanilla 0.47.1, hid 0.7 external on debian jessie, no output from usb controller [SOLVED]

Reply to Pd-vanilla 0.47.1, hid 0.7 external on debian jessie, no output from usb controller [SOLVED] on Sun, 23 Apr 2017 04:05:18 GMT

ephemerides — Sun, 23 Apr 2017 04:05:18 GMT

Hello, I've added the hid external from the "find external"/deken function in pd-vanilla, running on debian jessie. I can see when adjusting sliders and knobs on my usb controller that it affects values and channels in [ctlin] under "Test Audio and Midi". However, when I try something as simple as:

[print]--[hid]

I only see in the console:

info: open 0
info: device 0

No other information is printed as I adjust sliders or knobs. All the tutorials I see use this object under pd-extended, so I'm not sure if I'm missing some other necessary external, or if something else is the issue. If there's a better workaround, I'm basically just trying to map a usb controller for use with pd.

Reply to Pd-vanilla 0.47.1, hid 0.7 external on debian jessie, no output from usb controller [SOLVED] on Sat, 22 Apr 2017 08:11:50 GMT

whale-av — Sat, 22 Apr 2017 08:11:50 GMT

@ephemerides So the device is working. But your computer has found it and connected it as a midi device.
The usb controller is sending midi control change messages. Maybe it can be told to send the messages that you want....... midi notes, program change, nrpn, sysex etc.?

The messages in terminal show that "a device" was found. Device numbering starts at 0. But which device was found? Maybe your mouse?
If you can use the data that you are receiving..... as it is....... then just put a [ctlin] object in your patch and use the data received. You will be able to scale it to your requirements in your patch.
David.

Reply to Pd-vanilla 0.47.1, hid 0.7 external on debian jessie, no output from usb controller [SOLVED] on Sun, 23 Apr 2017 01:55:04 GMT

ephemerides — Sun, 23 Apr 2017 01:55:04 GMT

My usb controller is alive now and great fun. Thank you for the prompt and patient reply, David. I thought I needed to rely on the [hid] object to map the device as I saw in some tutorials, but as you suggested (and if I had just read the manual):

"When you create the ctlin object without arguments, it´s listening to all cc´s and to all channels. This is useful as an analysis tool to know which cc and channel sends each fader/ knob of your controller. " http://write.flossmanuals.net/pure-data/using-midi/

This gives me a good deal to work with before I get into trouble again.