(2014-02-09, 17:49)Rorwin Wrote: i got

Code:

<tvshow>
<line>$INFO[LCD.TimeWide22]</line>
    </tvshow>

in my config. it shows again a half part of the Digit. The first liine is empty and on the second line there is a half digit display.
i also noticed the it does the same in the screensaver mode. only half of the digits

(2013-06-14, 08:41)herrnst Wrote: @ALL: Did anyone else also experience such problems especially with HD44780-type displays?

(2014-02-11, 12:52)Cyberdyne_de Wrote: First thing I noticed was that the brackets around the progressbar were gone. LCD/VFD uses brackets without the <progressbarsurroundings>on</progressbarsurroundings> tag. Than I notices that the this progressbar was much better - it shows the progress pixel by pixel. I started testing everything again but found a few new problems:

(2014-02-11, 12:52)Cyberdyne_de Wrote: 1. "LCD.PlayIcon" works but a "LCD.ProgressBar" in a line below does not work. If you use "LCD.ProgressBar" in a line befor "LCD.PlayIcon" everything is fine (does not have to be the first line when using a 4 line display).

(2014-02-11, 12:52)Cyberdyne_de Wrote: 2. I have a 20x4 HD44780 display and "LCD.TimeWide21" and "LCD.TimeWide22" (and "LCD.Time21" and "LCD.Time22") always show a fullscreen clock using all 4 lines.

(2014-02-11, 12:52)Cyberdyne_de Wrote: 3. I use the progressbar for video-playback. When I pause a film XBMC will start the screensaver after a few minutes and the display is configured to show the big clock in screensaver mode. Now only houres and minutes are shown and it is frozen (shows only the time the screensaver started). I understand why a big clock and the progressbar can't be used at the same time (in different lines) but here it switches from showing a film with progressbar to only showing a clock and nothing more. I think it is a bug.

(2014-02-11, 12:52)Cyberdyne_de Wrote: 4. In some submenus the display gets darker. I still have to check if it is always the same menu or menu-level but right now I am not at home. All I can say right now is, that in some menus the display gets darker and going up a menu-level makes it brighter again. This never happened with LCD/VFD.

(2014-02-11, 12:52)Cyberdyne_de Wrote: Update:
I did some testing and I can reproduce the problem (only tested it with Confluence skin):
When I go to "System"->"Settings" and then to anything but "Add-ons" (because this menu looks different) I get to a menu with main options on the left and all the parameters on the right. When I go to the parameters on the right, the letters on the LCD get darker and it stays like this even when the navigation-screen changes to the general-screen and even the big clock of the screensaver-screen is darker (less contrast). As soon as I go back to the left side everything thing is back to normal.
I also found one other way to dim the letters (lower the contrast): When I go to "Videos" and thumbnail-view is active the letters get darker when I reach the most right thumbnail. Here the letters stay dark (even when I go to the left again) until I click a thumbnail or go back to the main menu.
Do you need pictures or can you understand what I try to say?

(2014-02-11, 12:52)Cyberdyne_de Wrote: Please excuse my poor english. It is not my mother tongue.

(2014-02-11, 21:31)herrnst Wrote: Well, that option and it's behaviour is wanted by some users, that's why it's there ;-) (could probably be moved to the GUI settings, though).

(2014-02-11, 21:31)herrnst Wrote: Honestly I don't have a clue why this happens especially on RPi, I also don't have any such hardware at hands to test and/or reproduce (nor even fix) the problem.

(2014-02-11, 21:31)herrnst Wrote: As I understand: It doesn't matter where the PlayIcon thingy and the following ProgressBar is placed. If the PlayIcon is placed _somewhere_ above the ProgressBar (e.g. Icon at Line 1, Bar at 4), the bar disappears. Is that right?

(2014-02-11, 21:31)herrnst Wrote: This is intended. script.xbmc.lcdproc doesn't draw any special text chars from the ROM charset (like "Has LCD/VFD" does).

(2014-02-11, 21:31)herrnst Wrote: Rather, it utilises LCDproc's "num" widgets so that LCDproc takes care of putting the digits onto the display (it can do it best and automatically as it obviously knows best how to drive the attached display). This greatly improves compatibility with all sorts of display hardware regarding the bigdigit display (rather than having only garbage on non-HD44780 character rom displays). The (rather little) draw-back is that LCDproc "num"'s can't be mixed with something else.

(2014-02-11, 21:31)herrnst Wrote: Reproducable. From two text lines in <video> via pressing pause to the screensaver kicking in, it shows the (paused) playback time as big digits. Might need to take a look at the "isscreensaveractive+isplayingvideo" determination logic.

(2014-02-11, 21:31)herrnst Wrote: Now THAT one sounds extra-strange. Especially since a LCDproc client simply just can not - in no documented way - dim the display backlight "just a little". Backlight control from within a LCDproc client is binary - on or off (if interested, see the LCDproc dev guide regarding "screen_set -backlight").

(2014-02-11, 21:31)herrnst Wrote: A video showing the XBMC screen and the display when toggling that effect would be very interesting.

(2014-02-11, 21:31)herrnst Wrote: However (see above), I don't have a clue what could cause this or even be fixed (would really need such hardware to reproduce). Also, this is the first time I get a report of such an issue. Are you sure this ain't some sort of power issue?

(2014-02-11, 21:31)herrnst Wrote: Interpolating from your forum nick: "Kein Problem, alles gut" ;-)

(2014-02-12, 12:26)Cyberdyne_de Wrote:

(2014-02-11, 21:31)herrnst Wrote: Honestly I don't have a clue why this happens especially on RPi, I also don't have any such hardware at hands to test and/or reproduce (nor even fix) the problem.

I do have some more HD44780 displays and I could make you a cabel with poti and GPIO connector but I only have one RPi and that is in daily use. Let me know if you need the LCD.

(2014-02-12, 12:26)Cyberdyne_de Wrote:

(2014-02-11, 21:31)herrnst Wrote: This is intended. script.xbmc.lcdproc doesn't draw any special text chars from the ROM charset (like "Has LCD/VFD" does).

It's strange that "LCD.Time2x" and "LCD.TimeWide2x" and so on didn't work at all when I used the build in LCD/VFD. Is it an RPi only problem? Again: Driver problem?

(2014-02-12, 12:26)Cyberdyne_de Wrote:

(2014-02-11, 21:31)herrnst Wrote: Reproducable. From two text lines in <video> via pressing pause to the screensaver kicking in, it shows the (paused) playback time as big digits. Might need to take a look at the "isscreensaveractive+isplayingvideo" determination logic.

Updated:
Four text lines not two but yes, your are right! I now tested pausing a film, a series and music. The file is playing, I press pause, wait (I think) 3 minutes and when the screensaver starts (the tv-screen gets dimmed) the LCD shows the paused playback time as big digits. When the file is longer than an houre it shows the time like this: 00:01:30 and when it is less than an houre it shows it like this: 01:30 followed by three BIG blanks. Does this help? Is it a RPi problem only again?

(2014-02-12, 12:26)Cyberdyne_de Wrote:

(2014-02-11, 21:31)herrnst Wrote: However (see above), I don't have a clue what could cause this or even be fixed (would really need such hardware to reproduce). Also, this is the first time I get a report of such an issue. Are you sure this ain't some sort of power issue?

To make it short: Yes, it was the power supply!
I tested an other PSU just to be sure and the effect is gone or at least only a very very tiny effect can still be seen.
Updated:
I tested LCD/VFD again and it shows the same effect. I will try to deactivate the dynamic overclocking (with overvoltage). Maybe the RPi thinks that it has to overclock in these menus?! ;o)

(2014-02-12, 12:26)Cyberdyne_de Wrote: How can I determine the version of the hd44780 driver? I took the driver from the tutorial and there was no info about it. Are there different drivers and which one should I use?

(2014-02-13, 19:58)herrnst Wrote:

(2014-02-12, 12:26)Cyberdyne_de Wrote:

(2014-02-11, 21:31)herrnst Wrote: Honestly I don't have a clue why this happens especially on RPi, I also don't have any such hardware at hands to test and/or reproduce (nor even fix) the problem.

I do have some more HD44780 displays and I could make you a cabel with poti and GPIO connector but I only have one RPi and that is in daily use. Let me know if you need the LCD.

Thanks, but I would also need a RPi for this (so basically the full package ). But I think this would rather be something for someone more into low-level hardware access things, since the problem can safely be reproduced outside of the addon.

(2014-02-13, 19:58)herrnst Wrote:

(2014-02-12, 12:26)Cyberdyne_de Wrote:

(2014-02-11, 21:31)herrnst Wrote: This is intended. script.xbmc.lcdproc doesn't draw any special text chars from the ROM charset (like "Has LCD/VFD" does).

It's strange that "LCD.Time2x" and "LCD.TimeWide2x" and so on didn't work at all when I used the build in LCD/VFD. Is it an RPi only problem? Again: Driver problem?

I'd rather suspect some sort of charmap setting in LCDd.conf. For the way bultin did things to work, charmap=none should be the way to go.

(2014-02-13, 19:58)herrnst Wrote:

(2014-02-12, 12:26)Cyberdyne_de Wrote:

(2014-02-11, 21:31)herrnst Wrote: Reproducable. From two text lines in <video> via pressing pause to the screensaver kicking in, it shows the (paused) playback time as big digits. Might need to take a look at the "isscreensaveractive+isplayingvideo" determination logic.

Updated:
Four text lines not two but yes, your are right! I now tested pausing a film, a series and music. The file is playing, I press pause, wait (I think) 3 minutes and when the screensaver starts (the tv-screen gets dimmed) the LCD shows the paused playback time as big digits. When the file is longer than an houre it shows the time like this: 00:01:30 and when it is less than an houre it shows it like this: 01:30 followed by three BIG blanks. Does this help? Is it a RPi problem only again?

Nope, I reproduced this on my dev system using the x11-osd pseudo-driver, and clearly is caused by script.xbmc.lcdproc.

(2014-02-13, 19:58)herrnst Wrote:

(2014-02-12, 12:26)Cyberdyne_de Wrote: How can I determine the version of the hd44780 driver? I took the driver from the tutorial and there was no info about it. Are there different drivers and which one should I use?

You're probably looking for the output of (example)

Code:

# LCDd -h
LCDd - LCDproc Server Daemon, 0.5.5

but that information can also be retrieved from xbmc.log (debug level):

Code:

17:14:52 T:140703385917184   DEBUG: ### [XBMC LCDproc] - Open 127.0.0.1:13666
17:14:52 T:140703385917184   DEBUG: ### [XBMC LCDproc] - Reply: connect LCDproc 0.5.5 protocol 0.3 lcd wid 16 hgt 2 cellwid 6 cellhgt 8

Some display drivers also deliver more details which are retrieved using the info command (those details are e.g. used to enable support for iMon/mdm166a extra display elements) which in some cases also can contain a driver version. That information is also written to xbmc.log (notice-level). Example:

Code:

17:14:52 T:140703385917184  NOTICE: ### [XBMC LCDproc] - Driver information reply: SoundGraph iMON LCD driver v0.6 : 15c2:ffdc and 15c2:0038

(2014-02-16, 17:29)delinend Wrote: But I always use a LCD (HD44780/display) via RPi/GPIO (Raspberry Pi), and always replays the hd44780.so driver, in my openELEC/Gotham test builds.

(2014-02-16, 17:29)delinend Wrote: Regarding LCDproc in many XBMC Gotham test builds....

(2014-02-16, 19:03)Cyberdyne_de Wrote:

(2014-02-16, 17:29)delinend Wrote: But I always use a LCD (HD44780/display) via RPi/GPIO (Raspberry Pi), and always replays the hd44780.so driver, in my openELEC/Gotham test builds.

Which driver do you use (size and version if you know it)? Do you have the same problem with the right and wrong order of "PlayIcon" and "ProgressBar" mentioned in this thread? As you say that Gothem builds use the same LCDproc version (0.5.6) an update from Frodo will not change this problem but maybe it's the driver. Could you try the hd44780-driver I use and tell us if there is a difference to the driver you use.

(2014-02-16, 17:29)delinend Wrote: Regarding LCDproc in many XBMC Gotham test builds....

Are there new Gothem builds without LCDproc? I think about testing a version patched by Milhouse. Do they have LCDproc included?

(2014-02-13, 22:27)Cyberdyne_de Wrote: 3. Play/Pause/Scrennsaver-Clock -> It's a bug and hopefully you will fix it.