Mini client and sagetv 64 bit

[krbaugh]

I recently moved to 64 bit sagetv and now my Android mini client looks like this

[Tiki]

There was at least one other post about something like this here:
https://forums.sagetv.com/forums/sho...1&postcount=20

[krbaugh]

Not the same problem mine works fine with the 32-bit version of Sage TV

[tvmaster2]

Originally Posted by krbaugh

I recently moved to 64 bit sagetv and now my Android mini client looks like this

oh, that’s Klingon.

[Tiki]

Originally Posted by krbaugh

Not the same problem mine works fine with the 32-bit version of Sage TV

I also seem to remember someone else having some sort of font caching problem when upgrading versions. I don’t remember what they had to do to clear the cache. I’m not sure the symptoms were the same either (I think they just had parts of the letters clipped off). Sorry that’s all I’ve got.

[wnjj]

Originally Posted by Tiki

I also seem to remember someone else having some sort of font caching problem when upgrading versions. I don’t remember what they had to do to clear the cache. I’m not sure the symptoms were the same either (I think they just had parts of the letters clipped off). Sorry that’s all I’ve got.

Yes, it had to do with the updated version of Freetype font source code I had to compile for 64-bit which apparently had change from the previous stuff. There was also plenty of code built into SageTV to tweak the spacing and sizes so I know it's kind of an artform. Deleting the cache was the solution there.

I wonder if once again there is some external dependency that the Freetype code leans on that is different on krbaugh's machine. We never understood why Java wasn't happy with what seemed to be a good install of VC++ runtimes before he uninstalled and reinstalled.

krbaugh, have you done a 'repair' install with the 64-bit SageTV installer already or at least after getting the VC++ runtimes installed again?

[JustFred]

Originally Posted by wnjj

We never understood why Java wasn't happy with what seemed to be a good install of VC++ runtimes before he uninstalled and reinstalled.

I don't think the problem here is related to the VC Runtime issue. I've stumbled into the VCRuntime pit with other non-Sage applications, too. Microsoft has acknowledged that's a bug in their VCR installer. Feel free to correct me if I've got this backwards, but I recall that MS's installer fails if a newer release was already installed, and then you try to install an older release of the same version (2010, 2008, etc).

[jpwegas]

To rule out the freetype libs as an issue try disabling the freetype fonts as described here by wnjj:

https://forums.sagetv.com/forums/sho...23&postcount=2


--John

[wnjj]

Originally Posted by JustFred

I don't think the problem here is related to the VC Runtime issue. I've stumbled into the VCRuntime pit with other non-Sage applications, too. Microsoft has acknowledged that's a bug in their VCR installer. Feel free to correct me if I've got this backwards, but I recall that MS's installer fails if a newer release was already installed, and then you try to install an older release of the same version (2010, 2008, etc).

Agreed but just looking for another reason why his system has a more unique font failure than others. I don’t know if there is another external dependency causing an issue. I can’t think of what it might be.

[stuckless]

Fonts on SageTV miniclient are rendered on the server and then sent to the client as bitmaps and then rendered to the screen. Because there are lots of font artifacts that are reused in a UI these are cached on the client. Normally when I've seen this it's because the client font cache is corrupted. So the first thing I'd try is to clear the data caches on the miniclient. If you don't know how to do that, then you can uninstall and re-install it on your phone/tv, etc.

[Wakecrash]

Originally Posted by krbaugh

Not the same problem mine works fine with the 32-bit version of Sage TV

I have 32 bit sage and I get stuff that looks like that sometimes. I am a new user of the new version of nvidia shield tv. I have to exit sage miniclient then start sage again and it clears. I can get shield to act up by resuming a video, then immediately trying to skip back from where I resumed.