-
Notifications
You must be signed in to change notification settings - Fork 26
Description
Hello there,
I am trying to get the Logitech Extreme 3d Pro to work as a controller using the great Modality toolkit, but Supercollider crashes as soon as I try to initialize it. When I run:
MKtl.find(\hid);
The extreme 3d Pro shows up as:
/*** Possible MKtls for HID devices: ***/
// [ product, vendor, (serial#) ]
// [ "Extreme 3D pro", "Logitech", "00000000002A" ]
// Unknown - Create from lookupName and explore
// (or match with a generic desc):
MKtl('hid_0_extrem', 'hid_0_extreme_3d_pro');
When I then run:
MKtl('x', 'hid_0_extreme_3d_pro' );
It seems to briefly start polling the 3d Pro:
open device 0x562bb67477b0
start polling thread for -1233881168
HID: Opened device: a HIDInfo(Logitech, Extreme 3D pro, IDs:1133, 49685, /dev/hidraw4, 00000000002A, 22289, 0)
// MKtl('x') : opened device without desc file.
// Maybe you want to explore this device?
MKtl('x').explore;
-> MKtl('x')
But then 3 seconds later it crashes:
Interpreter has crashed or stopped forcefully. [Exit code: 11]
Other HID and MIDI devices work perfectly with Modality or the other HID and MIDI classes.So the problem seems to be specifically related to the 3D Pro. When I try to initialize the 3D pro like this, I get the same interpreter crash.
~myhid = HID.open( 1133, 49685);
When I test the 3D Pro outside of SuperCollider inside the jstest-gtk, the joystick works perfectly.
My udev rules for /dev/hidraw4 are set up like this:
KERNEL==“hidraw*”, SUBSYSTEM==“hidraw”, MODE=“0664”, GROUP=“plugdev”
Does anyone have any idea how to solve this issue?
Many thanks for any hints in the right direction!