triangles are too large..

[drewg]

On my HD300, the pointer/triangle things on the home screen became too large recently. The lower 1/4 of the triangle is clipped off. Similarly, the pointer/triangle on the timeline when playing a video or recording is now too large, and the lower 1/4 of it is clipped off.

Also, when the HD300 first connects in extender mode, the lower 1/3 of the screen is corrupt (multicolor, stretched letters, stripes, etc) for just a split second (just long enough to say "what the heck is that???").

I'm running the latest (7.0.22) beta and the latest HD300 beta firmware (10/29 vers). I'm running my TV at 1080p in full pixel mode, with no overscan on the TV, and no overscan compensation in sagetv.

The problem started either when I updated from the 10/26 to the 10//27 firmware, or when I updated from the previous RC to 7.0.22. I'm not sure which. I updated to the 10/29 f/w this morning, and it didn't fix the issue. If nobody has any ideas, I'll try reverting to the release f/w to see if that fixes it..

BTW, I've uploaded my server & hd300 logs, both are running with debug logging enabled. See gallatin/triangle.zip on the ftp server.

Drew

[drewg]

Originally Posted by drewg

On my HD300, the pointer/triangle things on the home screen became too large recently. The lower 1/4 of the triangle is clipped off. Similarly, the pointer/triangle on the timeline when playing a video or recording is now too large, and the lower 1/4 of it is clipped off.
<...>
BTW, I've uploaded my server & hd300 logs, both are running with debug logging enabled. See gallatin/triangle.zip on the ftp server.

As an update, I've confirmed that this goes away if I revert to the production firmware on the HD300, so it seems like a bug in the beta firmware. I just opened a bug report on it.

Drew

[drewg]

The resolution us that my server had:

ui/enable_hardware_scaling_cache=true

set in the its properties file. Disabling this (setting ui/enable_hardware_scaling_cache=true=false) fixes this issue. I had this setting enabled to try to speed up an ancient HD100 that is no longer in service.

Thanks to SageTV support for an almost instant fix once I'd opened abug.


Drew