[webif] Web Interface 1.4.x

Status
Not open for further replies.
I currently have an overrunning recording :( - must be related in some way to my attempts to set up the skipped recording of Death in Paradise

The recording is South Today on BBC 1 South that should have run from 18:30 - 19:00 still going at 19:55

rts.logs for today
Code: 
23/02/2017 08:07:47 - System booted (Scheduled event).
[RR] Thu Feb 23 08:25:01 2017:    System is in standby.
[RR] Thu Feb 23 08:25:01 2017: Persistent log starting, v2.17
[RR] Thu Feb 23 08:25:01 2017: REC icon on.
[RR] Thu Feb 23 08:25:01 2017:    Recording 1
[RR] Thu Feb 23 08:25:01 2017:    Changing to red.
[RR] Thu Feb 23 08:25:01 2017: Recording start 22:'/mnt/hd2/My Video/Justin's House/Justin's House_20170223_0825.nts'
[RR] Thu Feb 23 08:50:38 2017: REC icon off.
[RR] Thu Feb 23 08:50:38 2017:    Changing to dim blue.
[RR] Thu Feb 23 08:50:38 2017:    System is in standby.
[RR] Thu Feb 23 08:50:39 2017: Recording end 22.
[RR] Thu Feb 23 08:50:40 2017: Standby ring dim detected.
[RR] Thu Feb 23 08:50:40 2017:   Setting LED level.
23/02/2017 08:50:45 - Recorded: Justin's House/Justin's House (25 minutes - CBeebies)
Thu Feb 23 13:07:10 2017: Restoring any favourites.
Thu Feb 23 13:07:10 2017: Ignoring: no such table: fav (no such table: fav)
Thu Feb 23 13:07:10 2017: Final schedule entries: 60
Thu Feb 23 13:07:10 2017: rsvsync starting.
Thu Feb 23 13:07:10 2017: Opening /var/lib/humaxtv/rsvp.db
Thu Feb 23 13:07:10 2017: Slots:
23/02/2017 13:07:41 - System booted (Scheduled event).
[RR] Thu Feb 23 13:23:08 2017: Persistent log starting, v2.17
[RR] Thu Feb 23 13:23:08 2017: Ring going blue, full boot.
[RR] Thu Feb 23 13:27:33 2017:    Recording 1
[RR] Thu Feb 23 13:27:33 2017:    Recording 1
[RR] Thu Feb 23 13:27:33 2017: REC icon on.
[RR] Thu Feb 23 13:27:33 2017: Ring going red.
[RR] Thu Feb 23 13:39:28 2017: Recording end 45.
[RR] Thu Feb 23 13:39:28 2017: REC icon off.
23/02/2017 13:39:34 - Recorded: Twirlywoos/Twirlywoos (11 minutes - CBeebies)
[RR] Thu Feb 23 14:09:40 2017: Recording start 31:'/mnt/hd2/My Video/Countdown/Countdown_20170223_1409.nts'
[RR] Thu Feb 23 14:09:40 2017:    Recording 1
[RR] Thu Feb 23 14:09:40 2017: Ring going red.
[RR] Thu Feb 23 14:09:40 2017: REC icon on.
[RR] Thu Feb 23 14:58:52 2017: REC icon off.
[RR] Thu Feb 23 14:58:52 2017: Recording end 31.
[RR] Thu Feb 23 14:58:55 2017: Recording start 46:'/mnt/hd2/My Video/Fifteen to One/Fifteen to One_20170223_1458.nts'
[RR] Thu Feb 23 14:58:55 2017: Ring going red.
[RR] Thu Feb 23 14:58:55 2017: REC icon on.
[RR] Thu Feb 23 14:58:55 2017:    Recording 1
23/02/2017 14:58:58 - Recorded: Countdown/Countdown (49 minutes - Channel 4)
[RR] Thu Feb 23 15:59:34 2017: REC icon off.
[RR] Thu Feb 23 15:59:34 2017: Recording end 46.
23/02/2017 15:59:41 - Recorded: Fifteen to One/Fifteen to One (60 minutes - Channel 4)
[nugget]: Thu Feb 23 16:48:43 2017: schedule save starting.
Thu Feb 23 16:48:43 2017: rsvsync starting.
23/02/2017 16:48:43 - Scheduled Death in Paradise @ 1487883600
[nugget]: Thu Feb 23 16:48:43 2017: Persistent log starting, v0.97
Thu Feb 23 16:48:43 2017: Nugget is available.
Thu Feb 23 16:48:43 2017: Real-time mode.
Thu Feb 23 16:48:44 2017: Moving pending entry 0 to spare slot 47
Thu Feb 23 16:48:44 2017: Opening /var/lib/humaxtv/rsvp.db
[nugget]: Thu Feb 23 16:48:44 2017: Schedule load failed.
Thu Feb 23 16:48:44 2017: Schedule saved.
[nugget]: Thu Feb 23 16:48:44 2017: Closing database.
Thu Feb 23 16:48:44 2017: Final schedule entries: 61
[nugget]: Thu Feb 23 16:48:44 2017: NULL database handle.
[nugget]: Thu Feb 23 16:48:44 2017: Schedule failed to reload, deferring.
Thu Feb 23 16:48:44 2017: Slots: +47
[nugget]: Thu Feb 23 16:48:44 2017: schedule save complete.
[nugget]: Thu Feb 23 16:48:44 2017: Deferred thread starting for '61:+47' (attempt 1)
[nugget]: Thu Feb 23 16:48:44 2017: Re-loading schedule database (61).
[nugget]: Thu Feb 23 16:48:44 2017: schedule.stash 26 = 1
Thu Feb 23 16:48:44 2017: Loading schedule information to HumaxTV binary.
[nugget]: Thu Feb 23 16:48:47 2017:   Last Event: 0
[nugget]: Thu Feb 23 16:48:47 2017:   Death in Paradise
[nugget]: Thu Feb 23 16:48:47 2017:       Thu Feb 23 21:00:00 2017 +60m
[nugget]: Thu Feb 23 16:48:47 2017:  Wake 1487882700 - Thu Feb 23 20:45:00 2017
[nugget]: Thu Feb 23 16:48:47 2017:   Events: 1FP.BBC.CO.UK/1FN6X0|
[nugget]: Thu Feb 23 16:48:47 2017:  [0] 458900,1487883600,1487887200,41471
[nugget]: Thu Feb 23 16:48:47 2017:     - Thu Feb 23 20:44:30 2017
[nugget]: Thu Feb 23 16:48:47 2017: Deferred thread exiting.
[nugget]: Thu Feb 23 16:48:47 2017: Processing slot +47 (47)
[nugget]: Thu Feb 23 16:48:47 2017: Ready 1487882670 - Thu Feb 23 20:44:30 2017
[nugget]: Thu Feb 23 16:48:47 2017:    @ 1487883600 (Thu Feb 23 21:00:00 2017)
[nugget]: Thu Feb 23 16:48:47 2017:   CRID: 2/[FP.BBC.CO.UK/VUZABE]
[nugget]: Thu Feb 23 16:48:47 2017:   Recorded:
[nugget]: Thu Feb 23 16:48:47 2017: Adding timer(1487882670)
[nugget]: Thu Feb 23 16:48:47 2017: schedule.restore 26 = 1
[nugget]: Thu Feb 23 16:48:47 2017: slots(61, +47)
[nugget]: Thu Feb 23 16:48:47 2017: Re-loading schedule database (61).
[nugget]: Thu Feb 23 16:48:47 2017: schedule reload complete (61).
[nugget]: Thu Feb 23 16:50:24 2017: schedule save complete.
[nugget]: Thu Feb 23 16:50:24 2017: schedule reload complete (61).
[nugget]: Thu Feb 23 16:50:24 2017: schedule.restore 26 = 1
[nugget]: Thu Feb 23 16:50:24 2017: schedule save starting.
23/02/2017 16:50:24 - Scheduled Death in Paradise @ 1487883600
[nugget]: Thu Feb 23 16:50:24 2017: slots(61, +47)
[nugget]: Thu Feb 23 16:50:24 2017: Processing slot +47 (47)
[nugget]: Thu Feb 23 16:50:24 2017: Closing database.
Thu Feb 23 16:50:24 2017: Loading schedule information to HumaxTV binary.
[nugget]: Thu Feb 23 16:50:24 2017: Re-loading schedule database (61).
[nugget]: Thu Feb 23 16:50:24 2017: schedule.stash 26 = 1
[nugget]: Thu Feb 23 16:50:24 2017:   CRID: 2/[FP.BBC.CO.UK/VUZABE]
[nugget]: Thu Feb 23 16:50:24 2017:   Death in Paradise
Thu Feb 23 16:50:24 2017: Final schedule entries: 61
[nugget]: Thu Feb 23 16:50:24 2017:   Events:
[nugget]: Thu Feb 23 16:50:24 2017:  Wake 1487882700 - Thu Feb 23 20:45:00 2017
[nugget]: Thu Feb 23 16:50:24 2017:   Recorded: 1FP.BBC.CO.UK/1FN6X0|
[nugget]: Thu Feb 23 16:50:24 2017:   Last Event: 0
[nugget]: Thu Feb 23 16:50:24 2017:     - Thu Feb 23 20:44:30 2017
[nugget]: Thu Feb 23 16:50:24 2017:    @ 1487883600 (Thu Feb 23 21:00:00 2017)
[nugget]: Thu Feb 23 16:50:24 2017: Ready 1487882670 - Thu Feb 23 20:44:30 2017
[nugget]: Thu Feb 23 16:50:24 2017: Adding timer(1487882670)
Thu Feb 23 16:50:24 2017: Nugget is available.
Thu Feb 23 16:50:24 2017: Schedule saved.
Thu Feb 23 16:50:24 2017: rsvsync starting.
Thu Feb 23 16:50:24 2017: Real-time mode.
Thu Feb 23 16:50:24 2017: Setting skip on slot 47 (-1)
Thu Feb 23 16:50:24 2017: Slots: +47
Thu Feb 23 16:50:24 2017: Opening /var/lib/humaxtv/rsvp.db
Thu Feb 23 16:50:24 2017: Found slot 47 for 3/458900/0/41471
23/02/2017 16:50:59 - Scheduled Death in Paradise @ 1487883600
Thu Feb 23 16:51:01 2017: Real-time mode.
[nugget]: Thu Feb 23 16:51:01 2017: schedule save complete.
Thu Feb 23 16:51:01 2017: Schedule saved.
Thu Feb 23 16:51:01 2017: Opening /var/lib/humaxtv/rsvp.db
Thu Feb 23 16:51:01 2017: Nugget is available.
Thu Feb 23 16:51:01 2017: rsvsync starting.
[nugget]: Thu Feb 23 16:51:01 2017: schedule save starting.
Thu Feb 23 16:51:01 2017: Moving pending entry 0 to spare slot 48
Thu Feb 23 16:51:02 2017: Slots: +48
Thu Feb 23 16:51:02 2017: Final schedule entries: 62
[nugget]: Thu Feb 23 16:51:02 2017: Deferred thread starting for '62:+48' (attempt 1)
[nugget]: Thu Feb 23 16:51:02 2017: Closing database.
[nugget]: Thu Feb 23 16:51:02 2017: Re-loading schedule database (62).
[nugget]: Thu Feb 23 16:51:02 2017: Schedule failed to reload, deferring.
[nugget]: Thu Feb 23 16:51:02 2017: schedule.stash 26 = 1
Thu Feb 23 16:51:02 2017: Loading schedule information to HumaxTV binary.
[nugget]: Thu Feb 23 16:51:02 2017: NULL database handle.
[nugget]: Thu Feb 23 16:51:02 2017: Schedule load failed.
[nugget]: Thu Feb 23 16:51:05 2017: Re-loading schedule database (62).
[nugget]: Thu Feb 23 16:51:06 2017:    @ 1487883600 (Thu Feb 23 21:00:00 2017)
[nugget]: Thu Feb 23 16:51:06 2017:   CRID: 2/[FP.BBC.CO.UK/VUZABE]
[nugget]: Thu Feb 23 16:51:06 2017: schedule.restore 26 = 1
[nugget]: Thu Feb 23 16:51:06 2017: slots(62, +48)
[nugget]: Thu Feb 23 16:51:06 2017: Processing slot +48 (48)
[nugget]: Thu Feb 23 16:51:06 2017:   Death in Paradise
[nugget]: Thu Feb 23 16:51:06 2017:   Recorded:
[nugget]: Thu Feb 23 16:51:06 2017: Adding timer(1487882670)
[nugget]: Thu Feb 23 16:51:06 2017:     - Thu Feb 23 20:44:30 2017
[nugget]: Thu Feb 23 16:51:06 2017: Deferred thread exiting.
[nugget]: Thu Feb 23 16:51:06 2017: schedule reload complete (62).
[nugget]: Thu Feb 23 16:51:06 2017:       Thu Feb 23 21:00:00 2017 +60m
[nugget]: Thu Feb 23 16:51:06 2017:   Last Event: 0
[nugget]: Thu Feb 23 16:51:06 2017:   Events: 1FP.BBC.CO.UK/1FN6X0|
[nugget]: Thu Feb 23 16:51:06 2017:  [0] 458900,1487883600,1487887200,41471
[nugget]: Thu Feb 23 16:51:06 2017:  Wake 1487882700 - Thu Feb 23 20:45:00 2017
[nugget]: Thu Feb 23 16:51:06 2017: Ready 1487882670 - Thu Feb 23 20:44:30 2017
[RR] Thu Feb 23 16:59:31 2017: Recording start 43:'/mnt/hd2/My Video/Chase/New_ The Chase_20170223_1659.nts'
[RR] Thu Feb 23 16:59:31 2017: Ring going red.
[RR] Thu Feb 23 16:59:31 2017: REC icon on.
[RR] Thu Feb 23 16:59:31 2017:    Recording 1
[RR] Thu Feb 23 17:14:32 2017: Recording start 45:'/mnt/hd2/My Video/Pointless/Pointless_20170223_1714.nts'
[RR] Thu Feb 23 17:14:32 2017:    Changing to purple.
[RR] Thu Feb 23 17:14:32 2017:    Recording 2
[RR] Thu Feb 23 17:59:33 2017: Recording end 43.
[RR] Thu Feb 23 17:59:33 2017:    Changing to red.
23/02/2017 17:59:40 - Recorded: Chase/New: The Chase (60 minutes - ITV)
[RR] Thu Feb 23 17:59:48 2017: Recording start 50:'/mnt/hd2/My Video/Eggheads/Eggheads_20170223_1759.nts'
[RR] Thu Feb 23 17:59:48 2017:    Recording 2
[RR] Thu Feb 23 17:59:48 2017:    Changing to purple.
[RR] Thu Feb 23 17:59:55 2017: Recording end 45.
[RR] Thu Feb 23 17:59:55 2017:    Changing to red.
23/02/2017 18:00:02 - Recorded: Pointless/Pointless (45 minutes - BBC ONE South)
[RR] Thu Feb 23 18:00:48 2017: Recording start 44:'/mnt/hd2/My Video/Clangers/Clangers_20170223_1800.nts'
[RR] Thu Feb 23 18:00:48 2017:    Changing to purple.
[RR] Thu Feb 23 18:00:48 2017:    Recording 2
[RR] Thu Feb 23 18:12:21 2017: Recording end 44.
[RR] Thu Feb 23 18:12:21 2017:    Changing to red.
23/02/2017 18:12:28 - Recorded: Clangers/Clangers (11 minutes - CBeebies)
[RR] Thu Feb 23 18:28:47 2017: Recording start 23:'/mnt/hd2/My Video/BBC News/South Today_20170223_1828.nts'
[RR] Thu Feb 23 18:28:47 2017:    Recording 2
[RR] Thu Feb 23 18:28:47 2017:    Changing to purple.
[RR] Thu Feb 23 18:30:41 2017:    Changing to red.
[RR] Thu Feb 23 18:30:41 2017: Recording end 50.
23/02/2017 18:30:47 - Recorded: Eggheads/Eggheads (30 minutes - BBC TWO)
Thu Feb 23 18:35:50 2017: Opening /var/lib/humaxtv/rsvp.db
Thu Feb 23 18:35:50 2017: Nugget is available.
Thu Feb 23 18:35:50 2017: Schedule saved.
Thu Feb 23 18:35:50 2017: Real-time mode.
Thu Feb 23 18:35:50 2017: Moving pending entry 0 to spare slot 47
Thu Feb 23 18:35:50 2017: Slots: +47
Thu Feb 23 18:35:50 2017: rsvsync starting.
[nugget]: Thu Feb 23 18:35:50 2017: schedule.stash 30 = 2
[nugget]: Thu Feb 23 18:35:50 2017: schedule save starting.
[nugget]: Thu Feb 23 18:35:50 2017: schedule save complete.
[nugget]: Thu Feb 23 18:35:50 2017: Re-loading schedule database (61).
[nugget]: Thu Feb 23 18:35:50 2017: Deferred thread starting for '61:+47' (attempt 1)
Thu Feb 23 18:35:50 2017: Final schedule entries: 61
Thu Feb 23 18:35:50 2017: Loading schedule information to HumaxTV binary.
[nugget]: Thu Feb 23 18:35:50 2017: Schedule failed to reload, deferring.
[nugget]: Thu Feb 23 18:35:50 2017: Schedule load failed.
23/02/2017 18:35:50 - Scheduled Death in Paradise @ 1487883600
[nugget]: Thu Feb 23 18:35:50 2017: Closing database.
[nugget]: Thu Feb 23 18:35:50 2017: NULL database handle.
[nugget]: Thu Feb 23 18:35:53 2017: schedule reload complete (61).
[nugget]: Thu Feb 23 18:35:53 2017: schedule.restore 30 = 2
[nugget]: Thu Feb 23 18:35:53 2017:   Death in Paradise
[nugget]: Thu Feb 23 18:35:53 2017:     - Thu Feb 23 20:44:30 2017
[nugget]: Thu Feb 23 18:35:53 2017: slots(61, +47)
[nugget]: Thu Feb 23 18:35:53 2017: Re-loading schedule database (61).
[nugget]: Thu Feb 23 18:35:53 2017:   Events: 1FP.BBC.CO.UK/1FN6X0|
[nugget]: Thu Feb 23 18:35:53 2017:    @ 1487883600 (Thu Feb 23 21:00:00 2017)
[nugget]: Thu Feb 23 18:35:53 2017:   CRID: 2/[FP.BBC.CO.UK/VUZABE]
[nugget]: Thu Feb 23 18:35:53 2017: Processing slot +47 (47)
[nugget]: Thu Feb 23 18:35:53 2017: Ready 1487882670 - Thu Feb 23 20:44:30 2017
[nugget]: Thu Feb 23 18:35:53 2017: Adding timer(1487882670)
[nugget]: Thu Feb 23 18:35:53 2017:  [0] 458900,1487883600,1487887200,41471
[nugget]: Thu Feb 23 18:35:53 2017: Deferred thread exiting.
[nugget]: Thu Feb 23 18:35:53 2017:  Wake 1487882700 - Thu Feb 23 20:45:00 2017
[nugget]: Thu Feb 23 18:35:53 2017:       Thu Feb 23 21:00:00 2017 +60m
[nugget]: Thu Feb 23 18:35:53 2017:   Last Event: 0
[nugget]: Thu Feb 23 18:35:53 2017:   Recorded:
[nugget]: Thu Feb 23 18:37:13 2017: schedule save complete.
Thu Feb 23 18:37:13 2017: Found slot 47 for 3/458900/0/41471
Thu Feb 23 18:37:13 2017: Loading schedule information to HumaxTV binary.
[nugget]: Thu Feb 23 18:37:13 2017: Re-loading schedule database (61).
[nugget]: Thu Feb 23 18:37:13 2017: schedule save starting.
Thu Feb 23 18:37:13 2017: rsvsync starting.
Thu Feb 23 18:37:13 2017: Real-time mode.
[nugget]: Thu Feb 23 18:37:13 2017: schedule.stash 30 = 2
[nugget]: Thu Feb 23 18:37:13 2017: Closing database.
Thu Feb 23 18:37:13 2017: Opening /var/lib/humaxtv/rsvp.db
Thu Feb 23 18:37:13 2017: Nugget is available.
Thu Feb 23 18:37:13 2017: Schedule saved.
Thu Feb 23 18:37:13 2017: Final schedule entries: 61
Thu Feb 23 18:37:13 2017: Setting skip on slot 47 (-1)
Thu Feb 23 18:37:13 2017: Slots: +47
23/02/2017 18:37:13 - Scheduled Death in Paradise @ 1487883600
[nugget]: Thu Feb 23 18:37:14 2017:   Events:
[nugget]: Thu Feb 23 18:37:14 2017: schedule reload complete (61).
[nugget]: Thu Feb 23 18:37:14 2017:   Death in Paradise
[nugget]: Thu Feb 23 18:37:14 2017:    @ 1487883600 (Thu Feb 23 21:00:00 2017)
[nugget]: Thu Feb 23 18:37:14 2017:   CRID: 2/[FP.BBC.CO.UK/VUZABE]
[nugget]: Thu Feb 23 18:37:14 2017:   Recorded: 1FP.BBC.CO.UK/1FN6X0|
[nugget]: Thu Feb 23 18:37:14 2017:   Last Event: 0
[nugget]: Thu Feb 23 18:37:14 2017:     - Thu Feb 23 20:44:30 2017
[nugget]: Thu Feb 23 18:37:14 2017:  Wake 1487882700 - Thu Feb 23 20:45:00 2017
[nugget]: Thu Feb 23 18:37:14 2017: Ready 1487882670 - Thu Feb 23 20:44:30 2017
[nugget]: Thu Feb 23 18:37:14 2017: Adding timer(1487882670)
[nugget]: Thu Feb 23 18:37:14 2017: schedule.restore 30 = 2
[nugget]: Thu Feb 23 18:37:14 2017: slots(61, +47)
[nugget]: Thu Feb 23 18:37:14 2017: Processing slot +47 (47)
[RR] Thu Feb 23 19:29:43 2017: Play icon on.



>>> Ending diagnostic rts.logs

I will stop the recording shortly but anything I should look for!

Update: I noticed later that the System was in Deliquent Half Awake state refusing to fully shut down. It had booted normally earlier in the day so I don't know if this is the cause or a side effect of the over-running recording
 
Last edited:
Creating duplicate schedule entries

I have found that if you schedule a recording via RS and then schedule the same programme via webif (whilst it is still pending in RS) you will end up with two entries in the Humax schedule, the Humax only records the programme once but it would be better if there were a duplicate entry check when adding entries from the pending queue to the schedule.

Why would I do anything so stupid - sometimes I mistakenly schedule something imminent via the RS and then worry it wont get added in time so add it again via webif.
 
MymsMan said:
I have found that if you schedule a recording via RS and then schedule the same programme via webif (whilst it is still pending in RS) you will end up with two entries in the Humax schedule
Click to expand...
I've had the same effect but in a slightly different way - if an expired series link becomes active again within the 3 month window AND you have setup a scheduling action on RS for it as well (just in case the next series doesn't come back within 3 months).
The suggested duplicate check would also catch this.
 
Black Hole said:
But not, apparently, remove it where it's not required:
Click to expand...
Oops! :oops:

Turns out that I did need a reboot, despite having RTS turned on, as I found out when my bedroom HD-FOX was on the wrong channel when consciousness returned this morning. Doesn't schedule restore work with RTS yet, or is there a technical reason it can't?
 
Black Hole said:
But not, apparently, remove it where it's not required:
Click to expand...
The note you quoted relates to the bootstrap pages within the custom firmware and not the web interface. I've moved the post over to the web interface thread.
Black Hole said:
Turns out that I did need a reboot, despite having RTS turned on, as I found out when my bedroom HD-FOX was on the wrong channel when consciousness returned this morning. Doesn't schedule restore work with RTS yet, or is there a technical reason it can't?
Click to expand...
No, schedule restore does not work with RTS. That's partly because I've never done the work to make it work but also because it restores favourites too and that requires a reboot. Doing a schedule restore will actually completely disable RTS until reboot.
 
af123 said:
Doing a schedule restore will actually completely disable RTS until reboot.
Click to expand...
That explains why some recordings I added via WebIF after restore went "pending" instead of "active".

I think a note to this effect would be useful, added to the restore warnings if RTS is enabled.
 
Since moving up to webif 1.4.1 with the VFD showing the time within the currently playing programme, I was wondering how that time's obtained.
I know to use lsof to get the files accessed by the humaxtv process, and infer what's being recorded or played, but not the location within the programme.
This means if I pause and go away for a couple of hours, it can look like I was watching Sean the Sheep for hours rather than the 8 minutes it lasts.
I'd like TV Diary to be able to differentiate between watching moving video and freeze-frames.
Is it something I can cheaply spot?
 
martxw said:
Since moving up to webif 1.4.1 with the VFD showing the time within the currently playing programme, I was wondering how that time's obtained.
Click to expand...
When playing anything back, the Humax software scrolls the first 10 characters of the programme name followed by the offset on the VFD. The redring package spots that in the data stream and extracts the time so it can replace the scrolling text. The time will be in /tmp/.vfd as long as redring is installed and is configured to show the playback time.
That would be a bit hit and miss though. If it would help, I could extend redring to also store the current state of the display icons and any detected offset separately. You'd be able to use those pieces of information providing the user has chosen to install redring (I don't think it should be an explicit dependency of tvdiary).
 
Last edited:
martxw - redring 2.20 is now in the beta repository. This adds a library which can be used to retrieve data like which icons are illuminated. Fairly basic so far but it should give you more information to work from.

Code: 
humax# jimsh
Welcome to Jim version 0.77
. source /mod/webif/plugin/redring/lib.jim
. ::redring::vfd
5 USA
. ::redring::offset
. ::redring::icons
TV FULL Timer {Disk Space 1} {Disk Space 2}
. ::redring::iconset Timer
1
. ::redring::iconset Pause
0

The offset method returns the last offset that was seen on the screen - or an empty string if none seen in last minute.
Happy to add/change anything that would be useful to you.
 
af123 said:
martxw - redring 2.20 is now in the beta repository. This adds a library which can be used to retrieve data like which icons are illuminated. Fairly basic so far but it should give you more information to work from.
Click to expand...
Thanks - I'll give that a try to see if I can improve the data I collect.
Cheers.
 
Am I missing an extension to Jim?
/mod/webif/plugin/redring/lib.jim includes a couple of [file read path] calls, but I get errors saying there isn't a read function in file.
I changed it to add a quick file_read function that opens, reads and closes, and that works for me.

Also, the test for the mtime of .offset being more than 60 seconds old prevents the position within a paused live programme being reported.

I think using offset to determine the time for live programmes will be the most easily used. I'd use it instead of the current time, and stop identifying the wrong programme.
The iconset Pause seems very responsive, while offset can be a few seconds behind what's showing on screen, possibly as it's scrolling?
I'll play around with it to see if I can extract playback behaviour, or at least a broad brushstroke approximation.
Cheers.
 
martxw said:
Am I missing an extension to Jim?
Click to expand...
As long as you source /mod/webif/lib/setup you should have {file read}
martxw said:
Also, the test for the mtime of .offset being more than 60 seconds old prevents the position within a paused live programme being reported.
Click to expand...
Yes, I wasn't sure about that one.. happy to tweak it as necessary.
I would try and use the Pause icon as far as possible.
 
I've made good progress using the ::redring::eek:ffset.
For live viewing, instead of getting the EPG entry for the current time, if there's an offset I convert that into the time and get the EPG entry for then.
I adjust for day rollovers, and luckily I'm developing it at the perfect time to test the DST adjustment.

I now say you're watching what's actually on screen, rather than what's being broadcast, which the webif dropdown status still says.

I did have to tweak the proc though to handle the fact that the offset file gets stale while you're paused:
Code: 
proc my_redring_offset {} {
  if {![file exists /tmp/.offset]} {
    return ""
  }
  if {[clock seconds] - [file mtime /tmp/.offset] > 60 && ![::redring::iconset Pause]} {
    return ""
  }
  return [file read /tmp/.offset]
}
TV Diary now builds a histogram of which part of the programme you've watched and how long for. I can then do some Netflix-esque analytics on it. So while it may look like you watched a film for 2 hours, you might have missed the start, hit pause, gone away and forgotten about it, then given up after only seeing 5 minutes of the actual film.

One thing I was wondering was, can we detect when the screensaver is in operation. I could then tell when it's paused but you're not seeing anything.
 
Not too sure where to post this, but here goes

Just started watching Vera on chase play. Display on front of box showing
19:17 > 0:05. Same in box at top of webif page.

The time stamp for the recording shows the correct start time of 20:03.

Obviously connected to clocks changing, but is it webif, redring or native Humax getting confused.


Sent from my iPad using Tapatalk
 
Suggestion: if ir is installed, clicking the "watching" flag produces a drop-down channel list to choose from.
 
Suggestion: on the individual channel EPG page, where the current selected channel is shown have a quick-pick list to switch the view to another channel.
 
Suggestion: where there is a display option (eg single channel EPG list view or grid view) that has a user-defined default in Settings, provide a button where it applies to "set this as default".

Incidentally, I configured grid view as default, and it worked when I went back to the EPG on one channel but not another!
 
Status
Not open for further replies.
Back
Top