Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - franklinoffner

#1
Thanks Peter, that gives me a better understanding of the eight bytes against the 3 glyphs  ::).  I guess we will just have to hope that the resources are eventually allocated to find and fix.  If it is changing over time, then even a lookup table of "find this pattern, replace it with that" approach is going to fail.
#2
Yes, it is clearly an issue at the IceTV end.  I'd started to write up a query in the BeyonWiz forum, but then thought to check further up the food chain and found that the same issue presents in Windows browsers, Mac browsers and in the IceTV iPad app.

I tried looking at the bytes to see if I could find a rational correlation to some UniCode glyph but without success.  I am perplexed to see how a expected single glyph ended up as 8 bytes.

I raised it here as an issue (although minor), such that it might trigger somebody in IceTv to chase it down.
#3
I am noticing strange character sequences showing up the epg descriptions.  For instance, from the web display of the upcoming War of the Worlds.
QuoteBill explains his plan to infect the aliens with a virus to Ethan, Dominic and Michael but can’t bring himself to support
You would expect a single quote/apostrophe.  It there an issue ? I see the same sequence on my recorder and the web.

When I dig into the PVR storage of the description, I find the strange characters are coming from a sequence of 8 bytes (decimal) 195,162,226,130,172,226,132,162, in the midst of the text.

Alan.
#4
I can confirm working.  EPG and timers now loaded on our U4.

Many thanks for such quick response.

Alan.
#5
Incase that it is relevant the U4 is running current beta

System OE:          OE-Alliance 4.3
Firmware version:   beyonwiz 19.3.20201011 (19.3-346-g6461e3a)
Kernel / Drivers:   4.9.51 / 180411-16.4
#6
OK, had a look into the Wiz log file and find this

{868}<    39.497> Unhandled Error
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
   
  File "/usr/lib/python2.7/threading.py", line 754, in run
   
  File "/usr/lib/python2.7/site-packages/twisted/_threads/_threadworker.py", line 46, in work
   
  File "/usr/lib/python2.7/site-packages/twisted/_threads/_team.py", line 190, in doWork
   
--- <exception caught here> ---
  File "/usr/lib/python2.7/site-packages/twisted/python/threadpool.py", line 250, in inContext
   
  File "/usr/lib/python2.7/site-packages/twisted/python/threadpool.py", line 266, in <lambda>
   
  File "/usr/lib/python2.7/site-packages/twisted/python/context.py", line 122, in callWithContext
   
  File "/usr/lib/python2.7/site-packages/twisted/python/context.py", line 85, in callWithContext
   
  File "/usr/lib/enigma2/python/Plugins/SystemPlugins/IceTV/plugin.py", line 517, in doWork
   
exceptions.OverflowError: Python int too large to convert to C long

Trust that is might help

Alan
#7
Not getting updates and getting this entry in the ice log after attempting a manual fetch and update.

This is on a Beyonwiz U4 which has been rebooted.

Tried enable/disable to no avail.

Any ideas what to try next?

IceTV version 20191013

Alan
#8
Maybe I am going nuts, but I think :-\, that when I added from the guide via the iOS app it picked up all the ABC News... programs, now, futzing around, I added it from the ice web page and it is picking up just the 7pm edition.

Anyway, solved for now ::)
#9
Making very few changes to my recordings, I missed that the useful qualifiers to series recording had been dropped some months ago.  Can anyone suggest how to set up a recording to record just the 7pm ABC News? Previously I simply qualified it with at 7pm, once a day...all good. 

I have experimented with favourites, but cannot see anyway of limiting it to just the 7pm edition and avoiding picking up News Breakfast, News update, News overnight, and numerous other programs that begin with "ABC News".  Am I missing some bleeding obvious action somewhere?  At the moment the only option I can see is that of adding umpteen exclude qualifiers which seems a decidedly backward step.

TIA Alan.
#10
General Discussions / Re: iOS 9 bug ?
September 22, 2015, 06:07:54 PM
Must have been some sever side issue as its come good now.
#11
General Discussions / Re: iOS 9 bug ?
September 20, 2015, 01:35:45 PM
So I just tried a delete the app and reload with no change.  The app is consistently showing 10 pm as the "day" start time.  I withdraw my UTC suspicion, that was simple coincidence.  However, some simple playing around has revealed a consistent 1 day offset, pick Tuesday as the time in the guide and it displays 10 pm Monday, so the App knows the date and time, it looks like the db query is up the creek.

Weird that it is OK for some users.
#12
General Discussions / iOS 9 bug ?
September 20, 2015, 08:25:16 AM
Despite doing app reset, etc after iOS 9 upgrade, the TV guide opens at the wrong time. That is, several hours in the past.  Very annoying.  This morning the penny dropped.  With the "Now" setting is opening at the UTC time.  As I sit here this morning, 8 am Sunday  in Sydney, the guide opens at 11 pm Saturday, which is the time in London.

Is it just me?

Alan

Ah yes, this is ver 2.22 on an ipad air2 in case it is relevant.