Reply to thread

Message: <blockquote data-quote="cybrmage" data-source="post: 219213" data-attributes="member: 51680">I was FINALLY able to duplicate this... I think I have it fixed this time.I can't duplicate this condition.It may be an X64 issue, but I can't be certain. Does configuration still hang if you Disable the ExternalDisplay plugin?When it hangs, let it sit for a minute then copy the configuration.log and post it. (IE: make a copy of the configuration.log before you forcably shut down the process)Nope. The ExternalDisplay plugin already has an IRTrans driver.The { 0xAA, 0xAA }  initialization was the only information provided to me... Although you seem to have accumulated a large amount of data, it's not all that useful, as most of it only shows a single capture. To be able to determine what is static initialization and what (if any) data is dependant on date or time or option selected, there should be multiple captures... Also... a description of what is shown on the display would be helpful. (What does the sequance { 0xAD, ...., 0x00 } do??? that's a lot of data to "decode" without knowing what options are set or what the display is doing... 8-} )try the new version...What happens when you shut down MediaPortal (without putting the machine in standby/hibernate)??? The shutdown code was provided by -Manfred- without explanation or description of what the display does on shutdown.Remember... I don't have the hardware... so I can't see what any of the commands actually do.... saying that the display doesn't act the way it does with MHC tells me absolutely nothing... I don't know how the display acts under MHC!!I didn't find any documentation (official or otherwise) that indicated that the 0x7E code was sent with every button press... But, your log shows that there are indeed two bytes sent for every button press. I have changed the driver to accomodate this behaviour.Here is the new version:I have redone the remote mapping file so that the order of the keys in the editor more closely matches the layout on the remote (from top left to bottom right) and changed the name of some keys to better match the button labels (thanks Herr R aus B for providing a readable picture of the remote!). I have also updated the default button mapping to fix some of the keys so they actually do what they are supposed to do.The driver will NOT update the existing mapping file (which will still work properly). If you want/need to get the new default mappings, you should delete the VLSYS_Mplay.xml in your MediaPortal's InputDeviceMappings\custom directory.Also changed is the Advance configuration... The "Advanced" button no longer brings up the remote mapping editor. Instead, it brings up an advanced driver configuration screen. On the advanced configuration screen you can set some driver specific options. Currently, you can disable the remote control, and you can enable use of the fan controller (experimental).Regards,CybrMage</blockquote>

Verification