131 replies to this topic

[bacicciosat]

Just implementing a 'feature abort' after every unhandled message doesn't work. There would be too much replies. Some message are just sending status and don't request anything from the box. Such message don't need a feature abort reply.

True.
And how are going your tests ?
I was wondering about the performance of the current code. I was a little surprised when pieterg decided to move the code on python side because i though that cec communication is slow and i don't love all this use of signals and resources in the jumps between c++ and python. But maybe i am wrong and there is not significative impact on performance.
I have a doubt about the function "sendMessages" too. I was wondering if it is a good idea to send a sequence of cec messages without a timing. I remember in my tests that the destinator is not always in ready state and could ignore the message or reply with a feature abort breaking the sequence.

[pieterg]

I was wondering about the performance of the current code. I was a little surprised when pieterg decided to move the code on python side because i though that cec communication is slow and i don't love all this use of signals and resources in the jumps between c++ and python. But maybe i am wrong and there is not significative impact on performance.

don't be fooled by the abstract nature of 'signals', it's just a few lines of c++ code, in fact it's the same as calling a (blocking) function. signals just help to break object oriented constraints, in such a way that it is more or less accepted (at least by the people that use them)

And hdmi-cec is so low-rate that it could never really have an effect on on the e2 performance IMHO

[plnick]

It is not that hard. Only thing you'll need in python is a keyrelease event.

Sorry for late reply,

At the moment I implement the volume control for A/V receivers without changing C++ part and do it only at python/plugin side. For this I take this from InfoBarGenerics.py to catch key events

eActionMap.getInstance().bindAction('', -0x7FFFFFFF, volumekeyPressed)

Sending vol up/down/mute commands is done by this

def volumekeyPressed(key, flag):
    if config.hdmicec.avvolumecontrol.value:
	   if key == 113 or key == 114 or key == 115:
		  address = int("5",16)
		  cecmessagesendkey = int("44",16)
		  cecmessagekeyevent = None
		  if flag == 1:
			 cecmessagekeybreak = int("45",16)
			 cmd = struct.pack('B',cecmessagekeybreak)
		  else:
			 if key == 113:
				cecmessagekeyevent = int("43",16)
			 elif key == 114:
				cecmessagekeyevent = int("42",16)
			 elif key == 115:
				cecmessagekeyevent = int("41",16)
			 if cecmessagekeyevent:
				cmd = struct.pack('BB',cecmessagesendkey,cecmessagekeyevent)
		  if cmd:
			 eHdmiCEC.getInstance().sendMessage(address, len(cmd), str(cmd))
		  return 1
    return 0

I know, it is not nice but it works (tested with Yamaha A/V receiver) /images/smiley/smile.gif

Is there a TV which accepts volume control ? My Samsung does not accept the 0x44 CEC messages.

[Sjaaky]

Ah, nice one, didn't know that. It is a nicer method than my current implementation. This way you don't need to explicitly disable the normal VolumeControl.

I don't know of a tv which does accept 0x44. No positive feedback yet. I read cec was designed to let you control all devices with the tv remote. So a tv would never need to accept keypresses over cec, whereas an av receiver would. So I guess chances are slim.
Maybe something can be done with the vendor specific commands.

Edited by Sjaaky, 13 May 2013 - 12:43.

[bacicciosat]

I have a stupid question pieterg.
Why have increased rc to +2 ?

eAutoInitP0<eHdmiCECInit> init_hdmicec(eAutoInitNumbers::rc + 2, "Hdmi CEC driver");

[pieterg]

+2 was not actually necessary, +1 would have been enough.
At that time I was thinking about connecting an eRCInputEventDriver (and eInputDeviceInit is initialised at rc + 1).
But we only need eRCInput to be initialised, so +1 would have been enough it turns out.

[bacicciosat]

Thanks for explanation.
Indeed i have setup it to +1 in my file so i was wandering if it was wrong.

[Dimitrij]

@pieterg
You can add the option "Handle deepstandby to zap timers".
This is when the timer is not recording, and zap.
Then you can use the tuner as an alarm clock/images/smiley/smile.gif .

HdmiCec.py
...
if config.hdmicec.handle_deepstandby_zap_timers.value:
if getFPWasTimerWakeup():
????????? in the next 360 seconds = zap timer: ?????
self.wakeupMessages()

[Dimitrij]

Does not work HdmiCEC "Forward volume keys".

File "/usr/lib/enigma2/python/mytest.py", line 432, in <module>
    from Components.VolumeControl import VolumeControl
  File "/usr/lib/enigma2/python/Components/VolumeControl.py", line 7, in <module>

[Sjaaky]

Can you post the error message? Your excerpt is 'on spot' but too small.

[Dimitrij]

Can you post the error message? Your excerpt is 'on spot' but too small.

Sorry, wrong.

[Dimitrij]

Can you post the error message? Your excerpt is 'on spot' but too small.

Sorry, wrong.

@pieterg
You can add the option "Handle deepstandby to zap timers".
This is when the timer is not recording, and zap.
Then you can use the tuner as an alarm clock/images/smiley/smile.gif .

Added function to enable zap timer.
Added Russian translation.

Edited by Dima73, 8 October 2011 - 16:47.

[arneande]

Hi
this plugn are not for 8000 because we have dvi -hdmi is that right?

regard
arneande

[hemertje]

all DMM boxes do NOT support HDMI-CEC!

[bigroma]

I have a little problem with my Philips 40PFL9705 and et9000. If one device switched on another one via HDMI-CEC in my TV doesn't work "Auto zoom". if I switch to another HDMI device(PC) on my TV and back to et9000 autozoom works fine. It isn't big problem and may be it's TV problem, but i hope OpenPLI team will find solution

[ims]

D Q: some as HDMI-CEC does not work on DM800SE ?

[WanWizard]

I don't think any of the DM boxes has support for CEC...

[daddelfalk]

Hi,

right, yes all Dreamboxes have still no HDMI-CEC Support in their Closed Source drivers.

[chant]

Hello,

I have a Sony Bravia KDL-40X3500 and it does switch of when I switch of my ET9000. I tried all the different settings for my tv to wake up when I switch on the ET9000 but nothing seems to work.
When I switch on my TV de ET9000 switches on. But I want my tv to switch on when I switch on my ET9000. Is there anything I can do to get it work? Or does somebody else have a Sony tv that does switch on? If yes, what are the settings?
Hopefully somebody can help me with this becase I tried every option that seems logical to me (and more...)

Thanks,

Chant

Edited by chant, 1 November 2011 - 23:15.

[pieterg]

maybe your tv closes down cec when it goes to standby? Do you have settings to control what is disabled in standby?
(my panasonic for instance has settings to enable/disable 'viera link' in standby / normal operation)