Re: [Freevo-users] Using a wireless presenter to control Freevo
Michel Hoogervorst wrote: > Hi, > > > When you press a button on you presenter do you see any messages > from dmesg? > > If you do then you need to map the unknown events to an event using > "applykeymap" > > > > Nope... nothing about this in dmesg|tail... > > > You can also try "input-events 2" or "input-events 3" and press some > keys, it you see something then it's working and will work with either > the event driver or lircd. > > > > That indeed is the reason I'm sure it does work ;-) > This thing has a switch for switching between presenter mode, and mouse > mode. > When I put it in mouse mode, I see events for event device 3, and when I > put it in presenter mode, it gives events for event device 2. > > Problem is, that the stick in presenter mode, only returns a "KEY_M", no > matter what side I push it. > Other thing is, that while in mouse mode, it returns "KEY_M" on every > key I press on device 2. > > Could this be my problem? That device 2 also returns a keypress when > using the thing as device 3? > I added USE_SDL_KEYBOARD = 0 in local_conf.py to stop it from pushing up > the volume on every key I press :-P > If I remove that, the thing still doesn't work (I then only see the > mouse pointer move around my screen). I would evpect that you see, something like: grabbed input device waiting for events 20:42:12.552117: EV_KEY KEY_LEFT pressed 20:42:12.552121: EV_SYN code=0 value=0 20:42:12.754057: EV_KEY KEY_LEFT released 20:42:12.754060: EV_SYN code=0 value=0 20:42:13.763784: EV_KEY KEY_DOWN pressed 20:42:13.763788: EV_SYN code=0 value=0 20:42:13.965727: EV_KEY KEY_DOWN released 20:42:13.965730: EV_SYN code=0 value=0 20:42:14.369619: EV_KEY KEY_RIGHT pressed 20:42:14.369623: EV_SYN code=0 value=0 20:42:14.571558: EV_KEY KEY_RIGHT released 20:42:14.571561: EV_SYN code=0 value=0 20:42:15.076425: EV_KEY KEY_UP pressed 20:42:15.076429: EV_SYN code=0 value=0 20:42:15.177394: EV_KEY KEY_UP released 20:42:15.177397: EV_SYN code=0 value=0 timeout, quitting released input device You can try evtest /dev/input/event[23], this gives me: Input device ID: bus 0x18 vendor 0x0 product 0x0 version 0x0 Input device name: "i2c IR (Hauppauge)" Supported events: Event type 0 (Sync) Event type 1 (Key) Event code 0 (Reserved) Event code 1 (Esc) Event code 28 (Enter) Event code 71 (KP7) Event code 72 (KP8) Event code 73 (KP9) Event code 75 (KP4) Event code 76 (KP5) Event code 77 (KP6) Event code 79 (KP1) Event code 80 (KP2) Event code 81 (KP3) Event code 82 (KP0) Event code 103 (Up) Event code 105 (Left) Event code 106 (Right) Event code 108 (Down) Event code 113 (Mute) Event code 114 (VolumeDown) Event code 115 (VolumeUp) Event code 116 (Power) Event code 120 (?) Event code 121 (KPComma) Event code 122 (Hanguel) Event code 123 (Hanja) Event code 128 (Stop) Event code 132 (Front) Event code 139 (Menu) Event code 142 (Sleep) Event code 148 (Prog1) Event code 163 (NextSong) Event code 164 (PlayPause) Event code 165 (PreviousSong) Event code 167 (Record) Event code 168 (Rewind) Event code 207 (Play) Event code 208 (Fast Forward) Event code 218 (Connect) Event code 224 (Brightness down) Event code 225 (Brightness up) Event code 354 (Goto) Event code 363 (Channel) Event code 368 (Language) Event code 370 (Subtitle) Event code 375 (Screen) Event code 377 (TV) Event code 392 (Audio) Event code 393 (Video) Event code 395 (List) Event code 402 (ChannelUp) Event code 403 (ChannelDown) Event type 20 (Repeat) Testing ... (interrupt to exit) Event: time 1185734798.210091, type 1 (Key), code 105 (Left), value 1 Event: time 1185734798.210095, -- Report Sync Event: time 1185734798.412028, type 1 (Key), code 105 (Left), value 0 Event: time 1185734798.412031, -- Report Sync Event: time 1185734799.724673, type 1 (Key), code 108 (Down), value 1 Event: time 1185734799.724677, -- Report Sync Event: time 1185734799.926610, type 1 (Key), code 108 (Down), value 0 Event: time 1185734799.926613, -- Report Sync Event: time 1185734800.330505, type 1 (Key), code 106 (Right), value 1 Event: time 1185734800.330509, -- Report Sync Event: time 1185734800.532444, type 1 (Key), code 106 (Right), value 0 Event: time 1185734800.532447, -- Report Sync Event: time 1185734800.835368, type 1 (Key), code 103 (Up), value 1 Event: time 1185734800.835373, -- Report Sync Event: time 1185734801.037303, type 1 (Key), code 103 (Up), value 0 Event: time 1185734801.037307, -- Report Sync >From my /etc/ivtv/ir_kbd_i2c.pvr350.conf, there is: # cursor keys 0x0014 = 103 # KEY_UP 0x0015 = 108 # KEY_DOWN 0x0016 = 105 # KEY_LE
Re: [Freevo-users] Using a wireless presenter to control Freevo
Hi, When you press a button on you presenter do you see any messages from dmesg? > > If you do then you need to map the unknown events to an event using > "applykeymap" Nope... nothing about this in dmesg|tail... You can also try "input-events 2" or "input-events 3" and press some > keys, it you see something then it's working and will work with either > the event driver or lircd. That indeed is the reason I'm sure it does work ;-) This thing has a switch for switching between presenter mode, and mouse mode. When I put it in mouse mode, I see events for event device 3, and when I put it in presenter mode, it gives events for event device 2. Problem is, that the stick in presenter mode, only returns a "KEY_M", no matter what side I push it. Other thing is, that while in mouse mode, it returns "KEY_M" on every key I press on device 2. Could this be my problem? That device 2 also returns a keypress when using the thing as device 3? I added USE_SDL_KEYBOARD = 0 in local_conf.py to stop it from pushing up the volume on every key I press :-P If I remove that, the thing still doesn't work (I then only see the mouse pointer move around my screen). Michel - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
Re: [Freevo-users] Using a wireless presenter to control Freevo
Michel Hoogervorst wrote:
> I tried some, but can't get it to work at all :-(
>
> Because my distro (Mandriva) had no 'lsinput' in the input-utils
> package, I downloaded and compiled the utils from the package
> mentioned in the wiki (in the Linux event interface page).
>
> When I do ./lsinput, I get those two wich belong to my presenter:
> /dev/input/event2
>bustype : BUS_USB
>vendor : 0x5fe
>product : 0x1010
>version : 16641
>name: "USB Device USB Device"
>phys: "usb-:00:02.0-1/input0"
>uniq: ""
>bits ev : EV_SYN EV_KEY EV_LED EV_REP
>
> /dev/input/event3
>bustype : BUS_USB
>vendor : 0x5fe
>product : 0x1010
>version : 16641
>name: "USB Device USB Device"
>phys: "usb-:00:02.0-1/input1"
>uniq: ""
>bits ev : EV_SYN EV_KEY EV_REL EV_ABS
>
When you press a button on you presenter do you see any messages from dmesg?
If you do then you need to map the unknown events to an event using
"applykeymap"
You can also try "input-events 2" or "input-events 3" and press some
keys, it you see something then it's working and will work with either
the event driver or lircd.
Duncan
> The event3 part is the mouse-function on this thing, and the event2
> part is the presenter-part.
> When I do ./input-events 3, and push the mouse up, I get this:
>
> 02:40:51.407932: EV_REL REL_Y -7
>
> Where the -7 is a number between -1 and -7
> Pushing it down, gives a positive number between 1 and 7
>
> So, me happy, and I put this in local_conf.py:
> EVENT_DEVS = [ '/dev/input/event3' ]
> EVENTMAP['REL_Y'] = ('UP', 'DOWN')
> EVENTMAP['REL_X'] = ('LEFT', 'RIGHT')
>
> But, nothing happens when I push the stick up, down, left or right...
> I also tried putting lines in like:
> EVENTMAP['REL_Y -7'] = 'UP'
> EVENTMAP['REL_Y 7'] = 'DOWN'
>
> And I even tried putting it like this:
> EVENTMAP['EV_REL REL_Y 3'] = 'DOWN'
>
> But, nothing works... :-(
>
> Just to be sure, I tried putting this in local_conf.py:
> EVENT_DEVS = [ '/dev/input/event0' ]
> EVENTMAP['BTN_TL2'] = 'DOWN'
>
> which is mapped to a key on my joystick device... and that works, so
> the communication between the event interface and Freevo works fine...
> but I still can't use the presenter to control Freevo. :-(
>
> Any ideas left?
>
>
> Michel
>
> 2007/7/26, Duncan Webb <[EMAIL PROTECTED] >:
>
> > Hi,
> >
> > Just got to the last bit there where you mention the wiki and that's
> >> where I was going to say to check. Freevo doesn't natively
> support mouse
> >> navigation
> >
> >
> >
> > I understand, but I was thinking, maybe there's a way of fooling
> the Linux
> > OS in thinking that mouse-down is the same as the down button on a
> > keyboard
> > or joystick? :-) The mouse on this thing is a sort of joystick
> anyway...
> > it
> > only identifies itself as a mouse.
> >
> > An imap search just found a posting in
> >> freevo-users from 2004 that doesn't look encouraging - see Re:
> Plans for
> >> mouse input?
> >
> >
> >
> > I found that one too, but hey, it's three years later.. a lot
> could have
> > happened in the mean time ;-)
> >
> >
> > Wait, just found this -
> >> http://studio.kyperjokki.fi/engine/FreevoPointerInput. Doubt
> that diff
> >> will apply now though :)
> >
> >
> >
> > I found that one as well... but the latest change on the page is
> already a
> > year old, and I'm pretty sure I won't be able to apply this to
> Freevo
> > 1.7.2:-D
> > If I only understood Python... *sigh*
> >
> >
> > A google for 'freevo mouse patch' might help,
> >> patches welcome
> >
> >
> >
> > Yeah, did that but couldn't find anything, that's why I
> asked the
> > list... hoping somebody knows more than I have found so far.
>
> Does your remote have an event interface under Linux?
>
> You can tell by using lsinput (package input-utils)
>
> If it does then you can use the lircd with dev/input driver
>
> See http://freevo.sourceforge.net/cgi-bin/doc/LircDevInput
> for a guide,
> which I wrote for the PVR-350 but should be relevant to any event
> driver.
>
> Duncan
>
>
>
>
> -
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
>
>
> ___
> Freevo-users mailing list
> Freevo-users@lists.sourceforge.net
> http
Re: [Freevo-users] Using a wireless presenter to control Freevo
I tried some, but can't get it to work at all :-(
Because my distro (Mandriva) had no 'lsinput' in the input-utils package, I
downloaded and compiled the utils from the package mentioned in the wiki (in
the Linux event interface page).
When I do ./lsinput, I get those two wich belong to my presenter:
/dev/input/event2
bustype : BUS_USB
vendor : 0x5fe
product : 0x1010
version : 16641
name: "USB Device USB Device"
phys: "usb-:00:02.0-1/input0"
uniq: ""
bits ev : EV_SYN EV_KEY EV_LED EV_REP
/dev/input/event3
bustype : BUS_USB
vendor : 0x5fe
product : 0x1010
version : 16641
name: "USB Device USB Device"
phys: "usb-:00:02.0-1/input1"
uniq: ""
bits ev : EV_SYN EV_KEY EV_REL EV_ABS
The event3 part is the mouse-function on this thing, and the event2 part is
the presenter-part.
When I do ./input-events 3, and push the mouse up, I get this:
02:40:51.407932: EV_REL REL_Y -7
Where the -7 is a number between -1 and -7
Pushing it down, gives a positive number between 1 and 7
So, me happy, and I put this in local_conf.py:
EVENT_DEVS = [ '/dev/input/event3' ]
EVENTMAP['REL_Y'] = ('UP', 'DOWN')
EVENTMAP['REL_X'] = ('LEFT', 'RIGHT')
But, nothing happens when I push the stick up, down, left or right...
I also tried putting lines in like:
EVENTMAP['REL_Y -7'] = 'UP'
EVENTMAP['REL_Y 7'] = 'DOWN'
And I even tried putting it like this:
EVENTMAP['EV_REL REL_Y 3'] = 'DOWN'
But, nothing works... :-(
Just to be sure, I tried putting this in local_conf.py:
EVENT_DEVS = [ '/dev/input/event0' ]
EVENTMAP['BTN_TL2'] = 'DOWN'
which is mapped to a key on my joystick device... and that works, so the
communication between the event interface and Freevo works fine... but I
still can't use the presenter to control Freevo. :-(
Any ideas left?
Michel
2007/7/26, Duncan Webb <[EMAIL PROTECTED]>:
>
> > Hi,
> >
> > Just got to the last bit there where you mention the wiki and that's
> >> where I was going to say to check. Freevo doesn't natively support
> mouse
> >> navigation
> >
> >
> >
> > I understand, but I was thinking, maybe there's a way of fooling the
> Linux
> > OS in thinking that mouse-down is the same as the down button on a
> > keyboard
> > or joystick? :-) The mouse on this thing is a sort of joystick
> anyway...
> > it
> > only identifies itself as a mouse.
> >
> > An imap search just found a posting in
> >> freevo-users from 2004 that doesn't look encouraging - see Re: Plans
> for
> >> mouse input?
> >
> >
> >
> > I found that one too, but hey, it's three years later.. a lot could have
> > happened in the mean time ;-)
> >
> >
> > Wait, just found this -
> >> http://studio.kyperjokki.fi/engine/FreevoPointerInput. Doubt that diff
> >> will apply now though :)
> >
> >
> >
> > I found that one as well... but the latest change on the page is already
> a
> > year old, and I'm pretty sure I won't be able to apply this to Freevo
> > 1.7.2:-D
> > If I only understood Python... *sigh*
> >
> >
> > A google for 'freevo mouse patch' might help,
> >> patches welcome
> >
> >
> >
> > Yeah, did that but couldn't find anything, that's why I asked the
> > list... hoping somebody knows more than I have found so far.
>
> Does your remote have an event interface under Linux?
>
> You can tell by using lsinput (package input-utils)
>
> If it does then you can use the lircd with dev/input driver
>
> See http://freevo.sourceforge.net/cgi-bin/doc/LircDevInput for a guide,
> which I wrote for the PVR-350 but should be relevant to any event driver.
>
> Duncan
>
>
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/___
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users
Re: [Freevo-users] Using a wireless presenter to control Freevo
> Hi, > > Just got to the last bit there where you mention the wiki and that's >> where I was going to say to check. Freevo doesn't natively support mouse >> navigation > > > > I understand, but I was thinking, maybe there's a way of fooling the Linux > OS in thinking that mouse-down is the same as the down button on a > keyboard > or joystick? :-) The mouse on this thing is a sort of joystick anyway... > it > only identifies itself as a mouse. > > An imap search just found a posting in >> freevo-users from 2004 that doesn't look encouraging - see Re: Plans for >> mouse input? > > > > I found that one too, but hey, it's three years later.. a lot could have > happened in the mean time ;-) > > > Wait, just found this - >> http://studio.kyperjokki.fi/engine/FreevoPointerInput. Doubt that diff >> will apply now though :) > > > > I found that one as well... but the latest change on the page is already a > year old, and I'm pretty sure I won't be able to apply this to Freevo > 1.7.2:-D > If I only understood Python... *sigh* > > > A google for 'freevo mouse patch' might help, >> patches welcome > > > > Yeah, did that but couldn't find anything, that's why I asked the > list... hoping somebody knows more than I have found so far. Does your remote have an event interface under Linux? You can tell by using lsinput (package input-utils) If it does then you can use the lircd with dev/input driver See http://freevo.sourceforge.net/cgi-bin/doc/LircDevInput for a guide, which I wrote for the PVR-350 but should be relevant to any event driver. Duncan - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
Re: [Freevo-users] Using a wireless presenter to control Freevo
Hi, Just got to the last bit there where you mention the wiki and that's where I was going to say to check. Freevo doesn't natively support mouse navigation I understand, but I was thinking, maybe there's a way of fooling the Linux OS in thinking that mouse-down is the same as the down button on a keyboard or joystick? :-) The mouse on this thing is a sort of joystick anyway... it only identifies itself as a mouse. An imap search just found a posting in freevo-users from 2004 that doesn't look encouraging - see Re: Plans for mouse input? I found that one too, but hey, it's three years later.. a lot could have happened in the mean time ;-) Wait, just found this - http://studio.kyperjokki.fi/engine/FreevoPointerInput. Doubt that diff will apply now though :) I found that one as well... but the latest change on the page is already a year old, and I'm pretty sure I won't be able to apply this to Freevo 1.7.2:-D If I only understood Python... *sigh* A google for 'freevo mouse patch' might help, patches welcome Yeah, did that but couldn't find anything, that's why I asked the list... hoping somebody knows more than I have found so far. Michel - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
Re: [Freevo-users] Using a wireless presenter to control Freevo
Michel Hoogervorst wrote: > Hi, > > I just bought a Targus Wireless 2.4Ghz Presenter, which will have two > functions: > 1. Make my cat do some exercise (kinda cool to see how she reacts on > the laser light :-P) > 2. Hope to control Freeo with it. > > I bought this one, because it has a button to switch between presenter > mode, and mouse mode. > Kinda hoped that switching it in presenter mode, would make the middle > stick function as a joystick... but it doesn't :-( > > So now, the only way I can use this this to control Freevo, it putting > it in presenter mode, and just map de 4 buttons on it. > What I would like to know, is if there is a solution to trick > Linux/Freevo into thinking that mouse-down is the same as pressing the > down butten, and the same for up left and right, controlling Freevo > like that :-) > > Is this somehow possible? > Or is there another way of using a mouse with Freevo? > > I thought there used to be a Wiki page about using a mouse with Freevo > under tips and tricks... but I can't seem to find it anymore... > Does anyone have a clue? > > > Michel Just got to the last bit there where you mention the wiki and that's where I was going to say to check. Freevo doesn't natively support mouse navigation but there was someone who had posted to the wiki a patch that they had developed to allow use of a mouse. It was actually to allow freevo to be used with a touchscreen which was what they were using in a museum or somewhere like that. The touchscreen emulated a mouse hence the need for the mouse support. An imap search just found a posting in freevo-users from 2004 that doesn't look encouraging - see Re: Plans for mouse input? Wait, just found this - http://studio.kyperjokki.fi/engine/FreevoPointerInput. Doubt that diff will apply now though :) A google for 'freevo mouse patch' might help, patches welcome John - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
