Use a gamepad to control Supercollider.

This is simply the help file.

GeneralHID			A uniform class to access HID devices 	

Inherits from: Object

GeneralHID is a cross platform wrapper for accessing HID devices. Currently the MacOSX and Linux HID support has been wrapped. Some of the code is inspired by the GUI wrapper.

It is advised to use this class instead of the platform specific classes: HIDDeviceService (on MacOSX) and LID (on Linux)
There are intermediate "bridge" classes MXHID (on MacOSX) and GLID (on Linux), which should not be used directly, but their names will show up in the output of some of the methods of GeneralHID.

Some outstanding issues

This class is not completely finished yet. Common slot numbers across platforms are not yet guaranteed. On Windows there is not yet a proper implementation available.

Creation / Class Methods

	*scheme , *current
		Get the current scheme
	
	*scheme.id , *current.id
		Get the current scheme ID
	
	*buildDeviceList
		Look for all connected devices and build a device list. This returns the devicelist as an Array.
	
	*deviceList
		Returns the device list if it has already been built before.
	
	*postDevices
		Posts a readable list of devices.
	
	*postDevicesAndProperties
		Posts a readable list of devices and their properties.
	
	*startEventLoop( arg rate=0.005 )
		Start the eventloop with a update rate (or rather update time in seconds). (Note: this is only really needed on MacOSX, but for crossplatform code you should include it in your code).
	
	*stopEventLoop
		Stop the eventloop.
	
	*eventLoopIsRunning
		Check status of eventloop.
	
	*findBy( vendorID, productID, locID, versionID )
		Find a device by its vendorID (manufacturer), productID (product identifier as given by manufacturer), locID (identifier for the physical connection to your computer, and versionID (a version of the product, as given by the manufacturer).

Further information:
See GeneralHIDDevice for a documentation of the methods to access an HID device.
See GeneralHIDSpec for a documentation of how to access slots by name, instead of numbers.
Example

// General structure to access a device
// Look for the devices that are attached:
GeneralHID.buildDeviceList;
// Get the list of devices:
d = GeneralHID.deviceList;
// Check which devices have been found:
GeneralHID.postDevices;
// Pick the 3rd device and open it and create an instance of it:
a = GeneralHID.open( d[2] )
// Get info on the device:
a.info;

// Load the buffer (10)
s.sendMsg(\b_allocRead, 10, "sounds/a11wlk01.wav");

(
GeneralHID.action_({arg productID, vendorID, locID, cookie, val;
	var mykey;
//	[doc, key, modifiers].postln;
//	mykey = num;
	[cookie, val].postln;
	if(cookie == 18,
	{
		{EnvGen.kr(Env.perc([0.05,0.001,0.01].choose, [0.1,0.2,0.01].choose, 1, -4), doneAction:2) * SinOsc.ar(val*10, 0, 0.5)}.play;
		"bong".postln;
	});
	
	if(cookie == 19,
	{
		{EnvGen.kr(Env.perc([0.05,0.001,0.1].choose, [0.1,0.2,0.1].choose, 1, -4), doneAction:2) * TGrains.ar(2, Impulse.ar(val), 10, Dseq([10, 1, 1, 0.5, 0.5, 0.2, 0.1], inf), val, 0.04, Dseq([-1, 1], inf), 0.1, 2);}.play;
		"apollo".postln;
	});
})
)

// if you want to automatically find the device when you restart you can use the GeneralHID.findBy method. To get the arguments you should use for this function, you can use:
a.info.findArgs;
// this outputs for my Impact gamepad:
[ 1973, 786, usb-0000:00:1d.0-1/input0, 272 ]
// close the device, as we will reopen it in the next lines
a.close;
// if we know which device we want, we can find it:
b = GeneralHID.findBy( 1973, 786, "usb-0000:00:1d.0-1/input0", 272 );
b = GeneralHID.findBy( 1973, 786, 438304768, 272 );
// if you do not care about the version or the location, you can also do:
b = GeneralHID.findBy( 1973, 786 );
// or if you do not even care about the productID
b = GeneralHID.findBy( 1973 );
// you can then open it by:
a = GeneralHID.open( b )
// Start eventloop:
GeneralHID.startEventLoop
// Get the capabilities of the device in a readable format:
a.caps;
// there are different types of slots: // button (type 1), has only on/off (1/0) states // relative (type 2), counts up or down (scrollwheel for example) // absolute (type 3), continuous value between 0 and 1 // some other may show up on Linux ( Syn (type 0) and Miscellaneous (type 4), but these are generally not very useful).
// See if data is coming in:
a.debug_( true );
// Stop it:
a.debug_( false );
// Debugging can be turned on for each slot individually, if necessary: //(IBM trackpoint)
a.slots[1].at( 272 ).debug_( true );
// (external mouse on macbook pro)
a.slots[3][1].debug_(true);
(external mouse on ibm thinkpad)
a.slots[2][1].debug_(true);
// Turn it off again: // (IBM trackpoint)
a.slots[1].at( 272 ).debug_( false );
//(external mouse on macbook pro)
a.slots[3][48].debug_(false);
//(external mouse on ibm thinkpad)
a.slots[3][1].debug_(false);

// You can also create a generic gui to see what is coming in:
a.makeGui;

// The current value of a slot can be checked:
a.slots[1].at( 272 ).value; a.slots[2].at( 1 ).value; a.slots[3][1].value
//If the slot is an LED, you can set the value:
a.slots[11][0].value = 1; a.slots[11][0].value = 0;

// Actions can be mapped to each slot individually.
a.slots[1].at( 272 ).action_( { "hello".postln; } ); a.slots[1].at( 273 ).action_( { "hi".postln; } ); a.slots[3].at( 1 ).action_( { "hi".postln; } );
with an input to the function
a.slots[3].at( 1 ).action_( { |v| "hi, my value is ".post; v.value.postln; } ); a.slots[1].at( 272 ).action_( { |v| "hi, my value is ".post; v.value.postln; } );

To stop the action, assign it to an empty function.
a.slots[1].at( 272 ).action_( {} ); a.slots[1].at( 273 ).action_( {} ); a.slots[3].at( 1 ).action_( {} );

// you can access slots, by giving them a key:
a.add( \lx, [3,0] );
a[\lx].debug_( true );
// the last item in the output array, now shows the key
a[\lx].debug_( false );
// save the spec for future use:
a.spec.save( "Impact_help" );
// find a spec defined previously for this device:
c = a.findSpec;
// set it:
a.setSpec( c[0] );
// more info on this in the [GeneralHIDSpec] helpfile
// If the server is running you can create a control bus for the HID data to go to, so that a synth can immediately read the data:
s = Server.local.boot;
// To create the bus:
a.slots[1].at( 272 ).createBus( s ); a.slots[2].at( 8 ).createBus( s );

SynthDef( \hidbus_help, { |out=0,amp=0| Out.ar( out, SinOsc.ar( 300, 0, 0.01*amp.abs ) ); }).load( s ); )
x = Synth.new( \hidbus_help ); x.map( \amp, a.slots[2].at( 8 ).bus ); x.free;

( // a nicer version: SynthDef( \hidbus_help, { |out=0,amp=0,amp2=0| Out.ar( out, SinOsc.ar( 300, 0, 0.01*amp.abs.lag( 0.1 ) * amp2.lag(0.01,0.99) ) ); }).load( s ); )
x = Synth.new( \hidbus_help ); x.map( \amp, a.slots[2].at( 8 ).bus ); x.map( \amp2, a.slots[1].at( 272 ).bus ); x.free;

( // an even nicer version: SynthDef( \hidbus_help, { |out=0,freqadd=0,amp=0| Out.ar( out, SinOsc.ar( 300 + (freqadd.lag(0.2,1)*40), 0, 0.2*amp.lag(0.01,0.99) ) ); }).load( s ); )
x = Synth.new( \hidbus_help ); x.map( \freqadd, a.slots[2].at( 8 ).bus ); x.map( \amp, a.slots[1].at( 272 ).bus ); x.free;

// To free the bus:
a.slots[1].at( 272 ).freeBus; a.slots[2].at( 8 ).freeBus; 
// Close the device after use:
a.close;
GeneralHID.stopEventLoop