• The forum software that supports hummy.tv has been upgraded to XenForo 2.3!

    Please bear with us as we continue to tweak things, and feel free to post any questions, issues or suggestions in the upgrade thread.

Flexview duration times wrong

Wildebeest

Wildebeest

Member
Is it just me or is anyone else getting incorrect runtimes (duration column) shown in the Flexview display? For example 30 minute programmes showing as 1h30. This seems to happen with different channels and with both standard definition and high definition. I've only noticed it recently but I've no idea how long it's been happening.
 
Is it just in the column display or also on detailed view? All programmes or just some? Does standard browse show the same problem? Was paddig used in recording?
 
MymsMan said:
Is it just in the column display or also on detailed view?
Click to expand...
Both; see attached screenshot.
MymsMan said:
Does standard browse show the same problem?
Click to expand...
Doesn't seem to - duration is not displayed in the main file list but in the detail view that comes up on a double click it seems ok - see second screenshot.
MymsMan said:
Was paddig used in recording?
Click to expand...
No - I just use the default, which is AR I believe?Humax screenshoot.jpgHumax screenshoot2.jpg
 
Ooo, you've got lots of the files that I've lost in my HD crash... (have you got Yes PM as well?)

Anyway, I think I spy the potential problem - duration of Ep. 1 on the Media Browser is 30:20; duration on Flexview is 1:30:20. I bet all the others are consistently out by an hour. I wonder if there isn't a DST problem here.
 
Ooh, good spot. Yes, I think I've seen a longer programme somewhere that was listed as an hour longer than it should have been.

Interesting thought about DST, but if, when calculating durations, that was applied to just one of the times - either start or finish - and not the other, causing an hour's discrepancy, you'd expect that either during summer or winter but not both, but purely speculation at this stage I guess. It's not a big deal, I just spotted it and found it curious.

I have most of the YPM episodes but not quite a full set unfortunately! (and none of the 2013 series, I'm not even sure I've ever seen any of those). Over the years I've occasionally spotted YM / YPM being played on radio 4, it's a bit strange listening to them knowing it's really a television programme but it does work in an odd kind of way; it's not a very visual programme other than Eddington and Hawthorne's sublime facial expressions.
 
This is a browser Javascript problem. I don't know if it has ever worked (I guess it must have done), but currently at least FF, Chrome and Edge all behave the same.
All days from 1-Jan-1970 (day 0 in Unix epoch time values) to 30-Oct-1971 seem to generate a timezone offset of -60 minutes (in the UK at least). This is quite bizarre.
After that they behave as you would expect - 0 from end of October to end of March and -60 when DST is in effect.
The way Flexview generates its durations effectively uses a timestamp on day 0, which generates this 1 hour offset.
I think I've worked out a fix which shouldn't upset anything else it does (as real recordings from the early 1970s are somewhat unlikely to exist on a Fox T2) but it means bodging the jquery.jqGrid library.

Possibly a better way of doing it would be to generate the duration (and similar) fields in the JSON as text strings and not have any of this JS Date malarkey in the browser, but that's beyond my pay grade.

I've worked out why the channel icons don't work as well:
Code: 
--- script.js~
+++ script.js
@@ -736,7 +736,7 @@
 {
     // Add Channel icon to channel name
     var name = cellvalue;
-    var icon = '<img class="fvIcon" src="/img/channels/out/'+name+'.png"> ' ;
+    var icon = '<img class="fvIcon" src="/img/channels/'+name+'.png"> ' ;
     var fmtStr= icon + name;
     return fmtStr;
 }
 
Ah, I think it's because of this (from Wikipedia): "An inquiry during 1966–1967 led the government of Harold Wilson to introduce the British Standard Time experiment, with Britain remaining on GMT+1 throughout the year. This took place between 27 October 1968 and 31 October 1971, when there was a reversion to the previous arrangement."

I'm not sure it's especially worth spending time fixing it but nice that you've spotted the cause of the broken icons too!
 
Ah, I'd forgotten this:
"In the 1960s, the Government decided to test the support for continuous summertime. A three year experiment was introduced from 1968-1971 when summertime (GMT+1) applied throughout the year."
which explains it.
This just goes to show that a duration is not a date and shouldn't be considered as such.
 
prpr said:
That's up to MM.

That was the easy bit.
Click to expand...
My ToDo list got disrupted by discovering that not only had the Humax hung while we were on holiday but something has also broken the aerial connection and we have no TV signal at all except in one bedroom :dunno:
 
Ideally that would be with the 'FOX in standby, and even better to coincide with the 0430 OTA wake-up. However, a mechanical time-switch does not account for GMT/BST whereas the 'FOX schedules do.
 
SemiRamis said:
All you need is one of them, plug your humax in it and set it to go off at 4 on at 4.15. And Bob's your


Essential holiday buy
Click to expand...
I thought had set the time switch :dunno: but failed and for some reason the powered amplifier/splitter in the loft chose the same week to fail :( so nothing would have recorded anyway!
A few hours in the loft to discover this and bypass the splitter which is now not required since the kids have flown the nest, a few more hours to set up the only other TV still using the splitter output to use the HDHomerun app to receive live TV via wifi rather than from aerial.
I have bought a TP-Link Tapo P105 Mini Smart Wi-Fi Plug to allow for remote rebooting but of course that will take a bit of time to learn how to set it up and the family will soon be descending for Christmas (it was supposed to be quiet)
 
MymsMan said:
TP-Link Tapo P105 Mini Smart Wi-Fi Plug to allow for remote rebooting but of course that will take a bit of time to learn how to set it up
Click to expand...
Ya just install the app. on your phone. It's fairly intuitive. You can set schedules or just control it as and when.
If you tie both the Humax and the Tapo to something like Home Assistant &/or Node-RED you can even get it to auto-power cycle it when it dies. I'm just about to do this with my set.
Anyway, this is rather off-topic for this thread now. Back to fixing the code!
 
You must log in or register to reply here.
Back
Top