I'm new to CEC and just got a Pulse Eight USB adapter that I hooked up to my PC and to my Onkyo TX-SR3100 receiver in order to use the media buttons on the remote of the receiver to control playback on my PC. The PC's graphics card and CEC adapter are connected to each one HDMI connector of the receiver (as recommended here: If you're using 4K resolution, then the current model may not work, but you can work around it by not connecting the CEC adapter in-line).
The backward / forward buttons work perfectly fine, so far so good. I run cec-client like this (full log file attached):
$ cec-client --type p --log-file log.txt
When I click the forward (or backward) button on the remote, it registers as a key pressed and released:
TRAFFIC: [ 17499] >> 54:44:4b
DEBUG: [ 17499] >> Audio (5) -> Playback 1 (4): user control pressed (44)
DEBUG: [ 17499] SetCurrentButton forward (4b) D:0ms cur:4b
DEBUG: [ 17499] key pressed: forward (4b) current(ff) duration(0)
DEBUG: [ 17499] Changed key forward (4b) D:0ms cur:ff
DEBUG: [ 17499] key pressed: forward (4b, 0)
DEBUG: [ 17499] CheckKeypressTimeout T:125812.406
DEBUG: [ 17499] Key forward: idle (duration:0) (4b) timeout:500ms (rel:500,rep:0,prs:1,rel:0)
TRAFFIC: [ 17577] >> 54:45
DEBUG: [ 17578] >> Audio (5) -> Playback 1 (4): user control release (45)
DEBUG: [ 17578] key released: forward (4b) D:79ms
That looks just fine as far as I can tell, everything seems to work just as it should there. (But I guess that someone who's actually familiar with CEC might find something in the full log file that doesn't look fine, even though this particular part happens to work.)
But when I click the play (or pause) button on the remote, it only registers as a key released, without any information about what key it was:
TRAFFIC: [ 23383] >> 54:45
DEBUG: [ 23383] >> Audio (5) -> Playback 1 (4): user control release (45)
I'm at a loss about how to debug this further. I edited USBCECAdapterMessage.cpp and added some logging in PushReceivedByte() just to verify that there weren't any received bytes dropped somewhere, but the ff 05 54 fe : ff 86 45 fe bytes that in the log are shown decoded as >> 54:45 is really all that's being received there.
Does anyone have any idea about what might be going on here?
Is my receiver really not just sending the necessary data for two out of four of these buttons? If that's the case, might there be something that'd be possible to do to get it to start doing that?
Has anyone here encountered something similar before?
log.txt
I'm new to CEC and just got a Pulse Eight USB adapter that I hooked up to my PC and to my Onkyo TX-SR3100 receiver in order to use the media buttons on the remote of the receiver to control playback on my PC. The PC's graphics card and CEC adapter are connected to each one HDMI connector of the receiver (as recommended here: If you're using 4K resolution, then the current model may not work, but you can work around it by not connecting the CEC adapter in-line).
The backward / forward buttons work perfectly fine, so far so good. I run
cec-clientlike this (full log file attached):When I click the forward (or backward) button on the remote, it registers as a key pressed and released:
That looks just fine as far as I can tell, everything seems to work just as it should there. (But I guess that someone who's actually familiar with CEC might find something in the full log file that doesn't look fine, even though this particular part happens to work.)
But when I click the play (or pause) button on the remote, it only registers as a key released, without any information about what key it was:
I'm at a loss about how to debug this further. I edited
USBCECAdapterMessage.cppand added some logging inPushReceivedByte()just to verify that there weren't any received bytes dropped somewhere, but theff 05 54 fe : ff 86 45 febytes that in the log are shown decoded as>> 54:45is really all that's being received there.Does anyone have any idea about what might be going on here?
Is my receiver really not just sending the necessary data for two out of four of these buttons? If that's the case, might there be something that'd be possible to do to get it to start doing that?
Has anyone here encountered something similar before?
log.txt