Reply to thread

Message

<blockquote data-quote="cybrmage" data-source="post: 222825" data-attributes="member: 51680">Yes, it was helpful... but not complete...The logs show that there are slight differences between the MR300 that the driver was based on (via logs provided by Herr R aus B) and the M.Play Blast... (mainly, the MR300 has 2 fans, the Blast has 3)...But the logs do not show MHC controlling the fans or displaying custom characters or processing Remote buttom presses.Can you please provide logs of MHC displaying the digital clock and controlling the fan speed and processing button presses? (I also need the mediaportal log from when MediaPortal is executed and controling the display.) Thanks!Here is a new EXPERIMENTAL version of the driver.There is added support for differences in the different versions of the M.Play devices... In the advanced configuration, you will find an additional option for &quot;Device Type&quot;... If not set, the device type will default to &quot;AUTOMATIC&quot;, and the driver will try to detect the device from the ID reply from the display. If the driver can't automatically detect the display type, it will revert to using &quot;MZ4&quot; (MR300) as the device. You can override the automatic detection by selecting the specific ID string that your device returns (or that describes your device).I also fixed an error that caused the driver to throw an exception when &quot;Manage MHC&quot; is selected and the driver tries to restart MHC. I also added an additional delay after MHC is terminated to allow for the resources used by MHC (specifically the comm port) to be released.Please remember, when you post regarding problems with the driver, I need the mediaportal.log (and the configuration.log if the problem is with the driver setup).Regards,CybrMage</blockquote>

[QUOTE="cybrmage, post: 222825, member: 51680"] Yes, it was helpful... but not complete... The logs show that there are slight differences between the MR300 that the driver was based on (via logs provided by Herr R aus B) and the M.Play Blast... (mainly, the MR300 has 2 fans, the Blast has 3)... But the logs do not show MHC controlling the fans or displaying custom characters or processing Remote buttom presses. Can you please provide logs of MHC displaying the digital clock and controlling the fan speed and processing button presses? (I also need the mediaportal log from when MediaPortal is executed and controling the display.) Thanks! Here is a new EXPERIMENTAL version of the driver. There is added support for differences in the different versions of the M.Play devices... In the advanced configuration, you will find an additional option for "Device Type"... If not set, the device type will default to "AUTOMATIC", and the driver will try to detect the device from the ID reply from the display. If the driver can't automatically detect the display type, it will revert to using "MZ4" (MR300) as the device. You can override the automatic detection by selecting the specific ID string that your device returns (or that describes your device). I also fixed an error that caused the driver to throw an exception when "Manage MHC" is selected and the driver tries to restart MHC. I also added an additional delay after MHC is terminated to allow for the resources used by MHC (specifically the comm port) to be released. Please remember, when you post regarding problems with the driver, I need the mediaportal.log (and the configuration.log if the problem is with the driver setup). Regards, CybrMage [/QUOTE]

Verification