Reply to thread

Message: <blockquote data-quote="Herr R aus B" data-source="post: 220108" data-attributes="member: 62807">I am afraid that is a little bit too complicated. I finally found that <a href="https://forum.team-mediaportal.com/showpost.php?p=136531&postcount=16" target="_blank">article by dero </a>which even is in english. Furthermore I made some tests using Hyper Terminal - see attached snapshot, where '~' is 0x7E and 'T' is 0x54 as defined for the LEFT button. You can see the unpredictable behaviour of these remote buttons. I marked the two situations where I held the button pressed. All other 0x7E where randomly occurring. And as you can see, touching them "the right" way really makes the remote just send one single poor and lonely byte... <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink    ;)" loading="lazy" data-shortname=";)" /> I guess they used cheap contacts... Maybe these terrible slide contacts...Facit: 0x7E definately is JUST a repeat indicator but NO button pressed indicator! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin    :D" loading="lazy" data-shortname=":D" />So my suggestion would still be as follows:<ol> <li data-xf-list-type="ol">receiving a valid remote code immediately results in sending it to MP</li> <li data-xf-list-type="ol">the last valid remote code is being rememberd / cached until the next valid remote code comes around</li> <li data-xf-list-type="ol">subsequent 0x7E receivings are translated to sending the cached valid remote code to MP</li> <li data-xf-list-type="ol">after receiving a valid remote code the mnext 4-5 directly following 0x7Es are being ignored to produce a reasonable delay</li> </ol>YEAH! *applause*You don't think these were random delays?Well - either we didn't discover the biggest secret of all yet or the MHC software is just the result of quick and dirty coding... I assume the latter is more likely... Maybe the coder has children or a wife who usually don't pay much attention to him, so that he has to repeat everything several times before he gets heard - so maybe he (or she) thinks, communication always has to be like that - who knows? <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink    ;)" loading="lazy" data-shortname=";)" /> Or it's maybe just another interpretation of the mass effect law - much helps much... or something like that...Pardon me... a what??? Got me...HEy! That is MY rock! Go, lookfor your own rock! (Reminds me of Monty Python - but in Life of Brian it was a bush... And no flat jokes about George Walker now!)I fully understand why <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile    :)" loading="lazy" data-shortname=":)" />Indeed!And as for the new version - I can't complain so far. Repeats work well, remote works, standby works - but I doubt, that these artificial delays are necessary... Hard to say...Anyway here are the logs and the screenshot from Hyper Terminal...</blockquote>

Verification