guys....guys....
we use libxine directly! Xine_Player is NOT xine-ui.
Xine_Player is literally a native DCE player. Please look at the source code. There is no key mapping going on of any kind.
-Thom
Thank you Thom! That helps in narrowing down the search. Looking in Xine_Player.cpp there is some keyboard handling (up, down, left, right, & return) but then it looks like it doesn't do anything.
But knowing it is Xine_Player and DCE, I played in pluto_admin, My Devices, CORE, the core/hybrid, OnScreen Orbiter, Xine_Player. I was able to "send command to device" to pause playback using the "Pause Media" command. The neat feature here is that "send command to device" shows the MessageSend command line:
/usr/pluto/bin/MessageSend localhost 0 22 1 39 41 ""
Which shows up nicely in DCERouter.log as:
Received Message from 0 (unknown / ) to 22 (Xine Player / Living Room), type 1 id 39 Command:Pause Media, retry none, parameters: <0xa5fe9b90>
Parameter 41(StreamID): <0xa5fe9b90>
To find out which device is handling the keyboard, I then went back to tailing the DCERouter.log and pressed one of the keys that works (goto previous chapter) and saw this:
Received Message from 20 (OnScreen Orbiter / Living Room) to 10 (Media Plug-in / Living Room), type 1 id 65 Command:Jump Position In Playlist, retry none, parameters: <0x82f8ab90>
Parameter 5(Value To Assign): -1
which then resends the command to the Xine_Player with a stream id:
Received Message from 20 (OnScreen Orbiter / Living Room) to 22 (Xine Player / Living Room), type 1 id 65 Command:Jump Position In Playlist, retry none, parameters: <0xa97f0b90>
Parameter 5(Value To Assign): -1
Parameter 41(StreamID): 1001 <0xa97f0b90>
So it's looking like the OnScreen Orbiter needs to be investigated next...
Thank you,
Roy