hi list
i am using j.sarlos joystick object, but recently i thought about using multiple joystick-devices at the same machine, so i would have to "hack" the external a bit, as it's fixed to /dev/js0.
before this i wanted to give hid a try. so far i just realised that it uses eventX, which gives me no input. how can i map js0 to event0, js1 to event1? first thought was to just symbolically link them, but it seems this was an idea without unterstanding the situation, at least it ended with segfaulted pd.
any tips how to configure the hid external correctly.
lg m
before this i wanted to give hid a try. so far i just realised that it uses eventX, which gives me no input. how can i map js0 to event0, js1 to event1?
I have the same problem. the joystick on my usb port is mapped to /dev/input/js0 and not /dev/input/event0
any ideas how to change this/get around it?
-august.
I have the same problem. the joystick on my usb port is mapped to /dev/input/js0 and not /dev/input/event0
any ideas how to change this/get around it?
hmmm. just found the rawjoystick external under rawhid/
seems to work....wonderfully.
might help to have a README somewhere with the files.
best -august.
On Apr 1, 2005, at 12:35 PM, august wrote:
I have the same problem. the joystick on my usb port is mapped to /dev/input/js0 and not /dev/input/event0
any ideas how to change this/get around it?
hmmm. just found the rawjoystick external under rawhid/
seems to work....wonderfully.
might help to have a README somewhere with the files.
best -august.
Crazy... I wrote [rawjoystick] and I don't think I ever saw it
working... I think Olaf Matthes was the one who got it working...
Anyway, that is defunct, as are [linuxevent] and [linuxjoystick]. All
of this has been wrapped into [hid].
As for /dev/input/event?, you just need to have the 'evdev' module
loaded to get those devices.
.hc ________________________________________________________________________ ____
¡El pueblo unido jamás será vencido!
your joystick probably won't end up on /dev/input/event0, since your other devices like keyboard/mouse probably get detected first. on my machine, the joystick that is at /dev/js0 also appears as /dev/input/event4.
$ evtest /dev/input/event4 Input driver version is 1.0.0 Input device ID: bus 0x3 vendor 0x46d product 0xc216 version 0x125 Input device name: "Logitech Logitech Dual Action" Supported events: ...
pix.
On Fri, Apr 01, 2005 at 07:25:13PM +0200, august wrote:
before this i wanted to give hid a try. so far i just realised that it uses eventX, which gives me no input. how can i map js0 to event0, js1 to event1?
I have the same problem. the joystick on my usb port is mapped to /dev/input/js0 and not /dev/input/event0
any ideas how to change this/get around it?
-august.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://iem.at/cgi-bin/mailman/listinfo/pd-list
/dev/input/js? are created by the "joydev" and use a data struct
specific to joysticks. The /dev/input/event? devices are created by
"evdev" and use a data struct designed to be general to all human
interface devices.
So you need to "modprobe evdev" and find which /dev/input/event? device
your joysticks are on. I am planning on making this much easier in
future versions of [hid], with device names like: [hid joystick1], [hid
mouse2], etc.
.hc
On Apr 1, 2005, at 7:55 AM, metafor wrote:
hi list
i am using j.sarlos joystick object, but recently i thought about using multiple joystick-devices at the same machine, so i would have to
"hack" the external a bit, as it's fixed to /dev/js0.before this i wanted to give hid a try. so far i just realised that it
uses eventX, which gives me no input. how can i map js0 to event0, js1 to event1?
first thought was to just symbolically link them, but it seems this was an idea
without unterstanding the situation, at least it ended with segfaulted pd.any tips how to configure the hid external correctly.
lg m
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://iem.at/cgi-bin/mailman/listinfo/pd-list
"The arc of history bends towards justice."
Dr.
Martin Luther King, Jr.