I've lately been busy hacking on an LCDproc Python addon. The addon handles communication to LCDd more cleanly (reacts properly on any responses and only sends update when really needed, without spamming the socket) and improves on many other things (e.g. no more character translation table for any display type required, special chars handled via native LCDproc widgets etc.). While the addon runs very stable at least for me and can fully replace the code currently present in XBMC's core, it definitely requires testing by more users (different platforms, different displays, different LCD.xml configurations and so on). So I'd like to kindly ask anyone using a LCD or VFD driven by LCDproc to test this
The addon can be found at my GitHub repo at https://github.com/herrnst/script.xbmc.lcdproc.
The repo has been reorganized a bit lately: Base functionality has been branched as version 1.1.0, and will receive bugfixes only from now on.
The "imonmdm" branch is now merged to master and will eventually become version 1.2.0. So, master now contains the additional functionality to drive the extra icons surrounding the text area of the display. @SoundGraph iMON LCD/Futaba mdm166a users: Please report back any problems you see with this. Especially mdm166a users should report back if the stuff works at all, as this support has been implemented blindly without any testing (no hardware). Everyone else: No harm or instability should be caused by this, please report if it unfortunately does.
For notes, instructions and so on, please check https://github.com/herrnst/script.xbmc.lcdproc/wiki (updated for version information etc.).
Would love to receive any feedback on this, and don't hesitate to ask questions or report problems
Thanks to XBMC Team member Memphiz for the base implementation and letting me use it
Following up on the PR-discussion from PR#1482 here:
Memphiz Wrote:The only thing i found is that "$INFO[LCD.TimeWide21]" should show the clock not the player.time (when screensaver is on there is no player running).
I found out that the screensaver mode also gets active at least while music is playing, thus getting the LCD.TimeXX being drawn, but the output was scrambled due to special chars being directly posted. Haven't looked at the core code at that time, so it felt like a good idea to print the player.time at that point However, looking afterwards it indeed states "systemtime" in core. What about leaving "player.time" when playing media, and showing "systemtime" when screensaver gets active without anything playing?