[RS] Problems skipping F1 episodes.

peterworks · Apr 23, 2017

I have tried but cannot skip 'episodes' for next weeks Russian Grand Prix. Using RS I only wanted the qualifying and race to be recorded. It showed that it worked but they all reappeared.
I have attached the Device Logs from RS and the nugget log if that helps

~~Edit: Not sure if this should be a new thread as it is not just the last episode - perhaps a mod could make up my mind for me !~~ - Moderator comment: New thread created.

Trev · Apr 23, 2017

I think it's because now it's all on CH4, all the 'episodes' have the same CRID or whatever it's called, whereas before when it was split BBC2/BBC1, they were differeent

MymsMan · Apr 25, 2017

peterworks said:
I have tried but cannot skip 'episodes' for next weeks Russian Grand Prix. Using RS I only wanted the qualifying and race to be recorded. It showed that it worked but they all reappeared.
I have attached the Device Logs from RS and the nugget log if that helps

Edit: Not sure if this should be a new thread as it is not just the last episode - perhaps a mod could make up my mind for me !

I don't think it is the Last Episode problem because that was specifically related to how the Humax handled recordings with no future episodes in the EPG

However there definitely is a problem because I saw similar problems with skipping the practice sessions for last weeks Bahrain GP and again for this weeks Russian GP.

Today I skipped the 3 practice sessions and F1 meets but only the first practice showed up as skipped. I then rebooted the Humax and practice 2 is now also shown as skipped but practice 3 and F1 meets are still scheduled even after another reboot.

So I surmise that RS/RTS has a problem when trying to handle multiple skips for the same series in quick succession.
The rsv.db only stores five episode so there would always be a problem if trying to skip more episode but I deliberately only skipped 4 and only 2 are shown as skipped

I note that all of the episodes have different titles but all of the skip events use "F1 Russian GP Practice 1 Live" rather than the actual title but I presume matching should be by CRID rather than name

rts.logs diag output:

Code:

[RR] Tue Apr 25 00:25:46 2017: Recording end 29.
[RR] Tue Apr 25 00:25:46 2017:    System is in standby.
[RR] Tue Apr 25 00:25:47 2017: Standby ring dim detected.
25/04/2017 00:25:52 - Recorded: Have I Got a Bit More News for You/Have I Got a Bit More News for You (43 minutes - BBC ONE South)
Tue Apr 25 10:13:34 2017: Restoring any favourites.
Tue Apr 25 10:13:34 2017: rsvsync starting.
Tue Apr 25 10:13:34 2017: Slots:
Tue Apr 25 10:13:34 2017: Final schedule entries: 48
Tue Apr 25 10:13:34 2017: Ignoring: no such table: fav (no such table: fav)
Tue Apr 25 10:13:34 2017: Opening /var/lib/humaxtv/rsvp.db
25/04/2017 10:14:12 - System booted (Remote control handset).
25/04/2017 10:51:26 - Scheduled F1 Russian GP Practice 1 Live @ 1493366100
25/04/2017 10:51:32 - Scheduled F1 Russian GP Practice 1 Live @ 1493380500
25/04/2017 10:51:38 - Scheduled F1 Russian GP Practice 1 Live @ 1493456100
25/04/2017 10:51:44 - Scheduled F1 Russian GP Practice 1 Live @ 1493461500
Tue Apr 25 10:51:46 2017: Nugget is available.
[nugget]: Tue Apr 25 10:51:46 2017: schedule save starting.
Tue Apr 25 10:51:46 2017: rsvsync starting.
[nugget]: Tue Apr 25 10:51:46 2017: Persistent log starting, v0.97
Tue Apr 25 10:51:46 2017: Real-time mode.
Tue Apr 25 10:51:47 2017: Found slot 0 for 3/262243/0/17032
Tue Apr 25 10:51:47 2017:  - next event skip (262243:17345:1493380500)
[nugget]: Tue Apr 25 10:51:47 2017: Closing database.
[nugget]: Tue Apr 25 10:51:47 2017: schedule reload complete (48).
Tue Apr 25 10:51:47 2017: Setting skip on slot 0 (262243:17345:1493380500)
[nugget]: Tue Apr 25 10:51:47 2017: Re-loading schedule database (48).
Tue Apr 25 10:51:47 2017: Schedule saved.
Tue Apr 25 10:51:47 2017: Opening /var/lib/humaxtv/rsvp.db
[nugget]: Tue Apr 25 10:51:47 2017: slots(48, +0,+-1,+-1,+-1)
[nugget]: Tue Apr 25 10:51:47 2017: schedule save complete.
[nugget]: Tue Apr 25 10:51:47 2017:  [1] 262243,1493456100,1493461500,17068
[nugget]: Tue Apr 25 10:51:47 2017:       Sat Apr 29 09:55:00 2017 +90m
[nugget]: Tue Apr 25 10:51:47 2017:  [0] 262243,1493380500,1493386500,17345
[nugget]: Tue Apr 25 10:51:47 2017:       Sat Apr 29 11:25:00 2017 +30m
[nugget]: Tue Apr 25 10:51:47 2017: Processing slot +0 (0)
[nugget]: Tue Apr 25 10:51:47 2017:   F1 Russian GP Practice 1 Live
[nugget]: Tue Apr 25 10:51:47 2017:  [2] 262243,1493461500,1493463300,17069
[nugget]: Tue Apr 25 10:51:47 2017:   CRID: 2/[WWW.CHANNEL4.COM/C4EI0170325162113199]
[nugget]: Tue Apr 25 10:51:47 2017:   Recorded: 1www.channel4.com/66350/012|1WWW.CHANNEL4.COM/66350/011|1WWW.CHANNEL4.COM/66350/009|1WWW.CHANNEL4.COM/66350/008|1WWW.CHANNEL4.COM/66171/001|1WWW.CHANNEL4.COM/66350/007|
[nugget]: Tue Apr 25 10:51:47 2017:       Sun Apr 30 12:35:00 2017 +155m
[nugget]: Tue Apr 25 10:51:47 2017:  [6] 262243,1493561400,1493566200,17394
[nugget]: Tue Apr 25 10:51:47 2017:       Sun Apr 30 15:10:00 2017 +80m
[nugget]: Tue Apr 25 10:51:47 2017:  Wake 1493379600 - Fri Apr 28 12:40:00 2017
[nugget]: Tue Apr 25 10:51:47 2017: Ready 1493379570 - Fri Apr 28 12:39:30 2017
[nugget]: Tue Apr 25 10:51:47 2017: Adding timer(1493379570)
Tue Apr 25 10:51:47 2017: Could not get slot.
Tue Apr 25 10:51:47 2017: Setting skip on slot -1 (0)
[nugget]: Tue Apr 25 10:51:47 2017:  [3] 262243,1493463300,1493472600,17070
[nugget]: Tue Apr 25 10:51:47 2017:       Sat Apr 29 11:55:00 2017 +155m
[nugget]: Tue Apr 25 10:51:47 2017:    @ 1493380500 (Fri Apr 28 12:55:00 2017)
[nugget]: Tue Apr 25 10:51:47 2017:       Sun Apr 30 12:00:00 2017 +35m
Tue Apr 25 10:51:47 2017: Slots: +0,+-1,+-1,+-1
Tue Apr 25 10:51:47 2017: Final schedule entries: 48
Tue Apr 25 10:51:47 2017: Loading schedule information to HumaxTV binary.
[nugget]: Tue Apr 25 10:51:47 2017:   Events: 1WWW.CHANNEL4.COM/66350/012|1WWW.CHANNEL4.COM/66350/013|1WWW.CHANNEL4.COM/66350/014|1WWW.CHANNEL4.COM/66171/002|1WWW.CHANNEL4.COM/66350/015|1WWW.CHANNEL4.COM/66350/016|1WWW.CHANNEL4.COM/66350/017|1WWW.CHANNEL4.COM/66350/018|
[nugget]: Tue Apr 25 10:51:47 2017:     - Fri Apr 28 12:39:30 2017
[nugget]: Tue Apr 25 10:51:47 2017:       Fri Apr 28 12:55:00 2017 +100m
[nugget]: Tue Apr 25 10:51:47 2017: Invalid slot, '+-1'.
[nugget]: Tue Apr 25 10:51:47 2017: Invalid slot, '+-1'.
[nugget]: Tue Apr 25 10:51:47 2017:  [4] 262243,1493550000,1493552100,17086
[nugget]: Tue Apr 25 10:51:47 2017: Invalid slot, '+-1'.
[nugget]: Tue Apr 25 10:51:47 2017:  [5] 262243,1493552100,1493561400,17393
[nugget]: Tue Apr 25 10:51:47 2017:   Last Event: 16620
Tue Apr 25 10:51:47 2017: Setting skip on slot -1 (0)
Tue Apr 25 10:51:47 2017: Setting skip on slot -1 (0)
Tue Apr 25 10:51:47 2017: Could not get slot.
Tue Apr 25 10:51:47 2017: Could not get slot.
[RR] Tue Apr 25 11:07:23 2017: Standby VFD dim detected, overriding.
[RR] Tue Apr 25 11:07:23 2017: Persistent log starting, v2.20
[RR] Tue Apr 25 11:07:23 2017: Standby ring dim detected.
[RR] Tue Apr 25 11:07:23 2017: Standby ring dim detected.
[RR] Tue Apr 25 11:07:24 2017: Ring trying to go amber.
[RR] Tue Apr 25 11:07:24 2017:   Changing to dim blue.
[RR] Tue Apr 25 11:07:26 2017: Standby ring dim detected.
Tue Apr 25 11:12:26 2017: Restoring any favourites.
Tue Apr 25 11:12:26 2017: rsvsync starting.
Tue Apr 25 11:12:26 2017: Opening /var/lib/humaxtv/rsvp.db
Tue Apr 25 11:12:26 2017: Final schedule entries: 48
Tue Apr 25 11:12:26 2017: Ignoring: no such table: fav (no such table: fav)
Tue Apr 25 11:12:26 2017: Slots:
25/04/2017 11:13:01 - System booted (Remote control handset).
[RR] Tue Apr 25 11:26:04 2017: Persistent log starting, v2.20
[RR] Tue Apr 25 11:26:04 2017: Standby VFD dim detected, overriding.
[RR] Tue Apr 25 11:26:04 2017: Standby ring dim detected.
[RR] Tue Apr 25 11:26:04 2017: Standby ring dim detected.
[RR] Tue Apr 25 11:26:05 2017: Ring trying to go amber.
[RR] Tue Apr 25 11:26:05 2017:   Changing to dim blue.
[RR] Tue Apr 25 11:26:07 2017: Standby ring dim detected.
Tue Apr 25 11:28:54 2017: rsvsync starting.
Tue Apr 25 11:28:54 2017: Opening /var/lib/humaxtv/rsvp.db
Tue Apr 25 11:28:54 2017: Slots:
Tue Apr 25 11:28:54 2017: Final schedule entries: 48
Tue Apr 25 11:28:54 2017: Restoring any favourites.
Tue Apr 25 11:28:54 2017: Ignoring: no such table: fav (no such table: fav)
25/04/2017 11:29:34 - System booted (Remote control handset).

RS Device log

Code:

Device Logs
Time    Message
25/04/2017 11:30:36    System booted (Remote control handset).
25/04/2017 11:14:03    System booted (Remote control handset).
25/04/2017 10:51:45      Successfully scheduled skip for recording.
25/04/2017 10:51:44      F1 Russian GP Practice 1 Live
25/04/2017 10:51:41    Processing command 'skip 8384.17069'
25/04/2017 10:51:39      Successfully scheduled skip for recording.
25/04/2017 10:51:38      F1 Russian GP Practice 1 Live
25/04/2017 10:51:35    Processing command 'skip 8384.17068'
25/04/2017 10:51:33      Successfully scheduled skip for recording.
25/04/2017 10:51:32      F1 Russian GP Practice 1 Live
25/04/2017 10:51:29    Processing command 'skip 8384.17345'
25/04/2017 10:51:27      Successfully scheduled skip for recording.
25/04/2017 10:51:26      F1 Russian GP Practice 1 Live
25/04/2017 10:51:24    Processing command 'skip 8384.17032'
25/04/2017 10:22:23    Updated disk contents.
25/04/2017 10:15:05    System booted (Remote control handset).
25/04/2017 00:25:53    Recorded: Have I Got a Bit More News for You/Have I Got a Bit More News for You (43 minutes - BBC ONE South)

MymsMan · Apr 27, 2017

peterworks said:
I have tried but cannot skip 'episodes' for next weeks Russian Grand Prix. Using RS I only wanted the qualifying and race to be recorded. It showed that it worked but they all reappeared.
I have attached the Device Logs from RS and the nugget log if that helps

Edit: Not sure if this should be a new thread as it is not just the last episode - perhaps a mod could make up my mind for me !

Bump,

Any thoughts on this problem af123
It seems to be a reproducible problem.
I tried again to skip Practice 3 and F1 Meets - but this time it deleted Practice 3 and Qualifying leaving F1 Meets in place

af123 · Apr 28, 2017

I'll have a look, thanks for the nudge!

Trev · Apr 28, 2017

I suspect af is up to his armpits in Foxsat at the mo.

af123 · Apr 28, 2017

More like paid work : )

Code:

[nugget]: Sat Apr 22 22:12:00 2017: slots(8, +6,+6,+6,+6)

This doesn't look good though!

af123 · Apr 28, 2017

Here's a patch to try for those happy to modify the file directly. I'll package up the changes tonight.

Code:

humax# diff -ru /mod/sbin/rs_process~ /mod/sbin/rs_process
--- /mod/sbin/rs_process~
+++ /mod/sbin/rs_process
@@ -389,7 +389,8 @@
        # First check to see if there is already a pending skip for this
        # event and, if so, update that one.
        set table pending
-       set crid "[$event get channel_crid][$event get series_crid]"
+       set crid [string toupper "[$event get channel_crid][$event get series_crid]"]
        set ev [rsv fetch $table $ersvtype $hsvc 0 $usevtid $crid]
        if {$ev == 0} {
                log "*No pending event"

af123 · Apr 29, 2017

rs 1.4.9-2 was released last night including this fix which should solve this problem, at least for F1.
The next version of webif will include a more general fix but please can you test the updated RS?

peterworks · Apr 29, 2017

The next F1 scenario which matches the one that highlighted the problem is not until 26th/27th/28th May. Will try and find another set of programs/episodes to test the fix.

MymsMan · Apr 29, 2017

I am not sure!
Practice 3 was recording when I started testing so a few too many things going on simultaneously
I cancelled F1 Meets, Buildup and Reaction via RS leaving just Quali and the race scheduled and the RS displays show that as happening, F1 Meets has not recorded
However the webif Schedule and crucially the Humax schedule shows only the race scheduled via the series recording so I added Quali as a oneof recording via the remote just in case!

Code:

593    [nugget]: Sat Apr 29 11:21:19 2017:     - Sat Apr 29 11:39:30 2017
592    [nugget]: Sat Apr 29 11:21:19 2017: Adding timer(1493462370)
591    [nugget]: Sat Apr 29 11:21:19 2017: Ready 1493462370 - Sat Apr 29 11:39:30 2017
590    [nugget]: Sat Apr 29 11:21:19 2017:  Wake 1493462400 - Sat Apr 29 11:40:00 2017
589    [nugget]: Sat Apr 29 11:21:19 2017:       Sun Apr 30 12:35:00 2017 +155m
588    [nugget]: Sat Apr 29 11:21:19 2017:  [1] 262243,1493552100,1493561400,17393
587    [nugget]: Sat Apr 29 11:21:19 2017:       Sat Apr 29 11:55:00 2017 +155m
586    [nugget]: Sat Apr 29 11:21:19 2017:  [0] 262243,1493463300,1493472600,17070
585    [nugget]: Sat Apr 29 11:21:19 2017:   Events: 1WWW.CHANNEL4.COM/66171/002|1WWW.CHANNEL4.COM/66350/015|1WWW.CHANNEL4.COM/66350/016|1WWW.CHANNEL4.COM/66350/017|1WWW.CHANNEL4.COM/66350/018|
584    [nugget]: Sat Apr 29 11:21:19 2017:   Last Event: 17068
583    [nugget]: Sat Apr 29 11:21:19 2017:   Recorded: 1www.channel4.com/66350/018|1www.channel4.com/66350/016|1www.channel4.com/66171/002|1WWW.CHANNEL4.COM/66350/014|
582    [nugget]: Sat Apr 29 11:21:19 2017:   CRID: 2/[WWW.CHANNEL4.COM/C4EI0170325162113199]
581    [nugget]: Sat Apr 29 11:21:19 2017:    @ 1493463300 (Sat Apr 29 11:55:00 2017)
580    [nugget]: Sat Apr 29 11:21:19 2017:   F1 Meets... Daniel Ricciardo
579    [nugget]: Sat Apr 29 11:21:19 2017: Processing slot +0 (0)
578    [nugget]: Sat Apr 29 11:21:19 2017: slots(48, +0)
577    [nugget]: Sat Apr 29 11:21:19 2017: schedule.restore 0 = 1
576    [nugget]: Sat Apr 29 11:21:19 2017: schedule reload complete (48).
575    [nugget]: Sat Apr 29 11:21:19 2017: Closing database.
574    [nugget]: Sat Apr 29 11:21:18 2017: schedule.stash 0 = 1
573    [nugget]: Sat Apr 29 11:21:18 2017: Re-loading schedule database (48).
572    [nugget]: Sat Apr 29 11:21:18 2017: schedule save complete.
571    [nugget]: Sat Apr 29 11:21:18 2017: schedule save starting.
570    [nugget]: Sat Apr 29 11:16:00 2017:     - Sat Apr 29 11:16:05 2017
569    [nugget]: Sat Apr 29 11:16:00 2017: Adding timer(1493460965)
568    [nugget]: Sat Apr 29 11:16:00 2017: Skipping lead-in.
567    [nugget]: Sat Apr 29 11:16:00 2017: In the past.
566    [nugget]: Sat Apr 29 11:16:00 2017: Ready 1493460931 - Sat Apr 29 11:15:31 2017
565    [nugget]: Sat Apr 29 11:16:00 2017:  Wake 1493460961 - Sat Apr 29 11:16:01 2017
564    [nugget]: Sat Apr 29 11:16:00 2017: Good EPG data, retaining.
563    [nugget]: Sat Apr 29 11:16:00 2017:    @ 1493461500 (Sat Apr 29 11:25:00 2017)
562    [nugget]: Sat Apr 29 11:16:00 2017:   F1 Meets... Daniel Ricciardo
561    [nugget]: Sat Apr 29 11:16:00 2017: Processing slot 0 (0)
560    [nugget]: Sat Apr 29 11:16:00 2017: slots(48, 0)
559    [nugget]: Sat Apr 29 11:16:00 2017: schedule.restore 0 = 1
558    [nugget]: Sat Apr 29 11:16:00 2017: schedule reload complete (48).
557    [nugget]: Sat Apr 29 11:16:00 2017: Closing database.
556    [nugget]: Sat Apr 29 11:16:00 2017: schedule.stash 0 = 1
555    [nugget]: Sat Apr 29 11:16:00 2017: Re-loading schedule database (48).
554    [nugget]: Sat Apr 29 11:16:00 2017: schedule save complete.
553    [nugget]: Sat Apr 29 11:15:59 2017: schedule save starting.
552    [nugget]: Sat Apr 29 11:15:59 2017: Persistent log starting, v0.97
551    +++++++++++++++++++++++++++++++++++++++++++++++++++++++

I will attempt to find on of those back to back series marathons to try some less rushed testing

MymsMan · Apr 29, 2017

MymsMan said:
I will attempt to find on of those back to back series marathons to try some less rushed testing

Great British Railway Journeys on Yesterday has 4 episodes today, 10 tomorrow and 10 Monday! So good for testing but one does wonder who they are aimed at with each epsisode repeated 3 times a day - you have to be a massive fan of railways, Michael Portillo and bad colour combinations to want to record/watch them all :eek:

I set up the series record for Sunday and then skipped 5 alternate episodes SCRID:/OGYMC9
The resulting schedule is

Code:

19
Yesterday     Great British Railway Journeys    
Sun 30 Apr 2017 14:30
Sun 30 Apr 2017 16:30
Mon 01 May 2017 13:00
Mon 01 May 2017 14:00
Mon 01 May 2017 15:00
Mon 01 May 2017 15:30
Mon 01 May 2017 16:00
Mon 01 May 2017 16:30
Mon 01 May 2017 17:00
Mon 01 May 2017 17:30

MymsMan · Apr 30, 2017

Another test using Come Dine With Me
Schedule before attempted skips of Mon 01 May 2017 15:00 and 16:30

Code:

47 4seven     Come Dine with Me  
Mon 01 May 2017 14:30
Mon 01 May 2017 15:00
Mon 01 May 2017 15:30
Mon 01 May 2017 16:00
Mon 01 May 2017 16:30

Code:

Time     Message
30/04/2017 10:51:47      Successfully unscheduled recording.
30/04/2017 10:51:47      New: Bigheads
30/04/2017 10:51:45    Processing command 'unschedule live'
30/04/2017 10:51:44      Successfully scheduled skip for recording.
30/04/2017 10:51:43      Come Dine with Me
30/04/2017 10:51:41    Processing command 'skip 27168.20461'
30/04/2017 10:51:40      Successfully scheduled skip for recording.
30/04/2017 10:51:39      Come Dine with Me
30/04/2017 10:51:36    Processing command 'skip 27168.20458'
30/04/2017 10:46:14    Updated disk contents.
30/04/2017 10:41:28    System booted (Remote control handset).

Has actually skipped Mon 15:00, 15:30, 16:30 and Tue 15:00

Code:

47 4seven     Come Dine with Me  
Mon 01 May 2017 14:30 
Mon 01 May 2017 16:00 
Tue 02 May 2017 14:30 
Tue 02 May 2017 15:30 
Tue 02 May 2017 16:00 
Tue 02 May 2017 16:30

Code:

1010    [nugget]: Sun Apr 30 10:51:49 2017: Removing timer for slot 46
1009    [nugget]: Sun Apr 30 10:51:49 2017: Processing slot -46 (46)
1008    [nugget]: Sun Apr 30 10:51:49 2017:     - Mon May  1 14:14:30 2017
1007    [nugget]: Sun Apr 30 10:51:49 2017: Adding timer(1493644470)
1006    [nugget]: Sun Apr 30 10:51:49 2017: Ready 1493644470 - Mon May  1 14:14:30 2017
1005    [nugget]: Sun Apr 30 10:51:49 2017:  Wake 1493644500 - Mon May  1 14:15:00 2017
1004    [nugget]: Sun Apr 30 10:51:49 2017:       Thu May  4 16:30:00 2017 +30m
1003    [nugget]: Sun Apr 30 10:51:49 2017:  [17] 327802,1493911800,1493913600,20530
1002    [nugget]: Sun Apr 30 10:51:49 2017:       Thu May  4 16:00:00 2017 +30m
1001    [nugget]: Sun Apr 30 10:51:49 2017:  [16] 327802,1493910000,1493911800,20529
1000    [nugget]: Sun Apr 30 10:51:49 2017:       Thu May  4 15:30:00 2017 +30m
999    [nugget]: Sun Apr 30 10:51:49 2017:  [15] 327802,1493908200,1493910000,20528
998    [nugget]: Sun Apr 30 10:51:49 2017:       Thu May  4 15:00:00 2017 +30m
997    [nugget]: Sun Apr 30 10:51:49 2017:  [14] 327802,1493906400,1493908200,20527
996    [nugget]: Sun Apr 30 10:51:49 2017:       Thu May  4 14:30:00 2017 +30m
995    [nugget]: Sun Apr 30 10:51:49 2017:  [13] 327802,1493904600,1493906400,20526
994    [nugget]: Sun Apr 30 10:51:49 2017:       Wed May  3 16:30:00 2017 +30m
993    [nugget]: Sun Apr 30 10:51:49 2017:  [12] 327802,1493825400,1493827200,20507
992    [nugget]: Sun Apr 30 10:51:49 2017:       Wed May  3 16:00:00 2017 +30m
991    [nugget]: Sun Apr 30 10:51:49 2017:  [11] 327802,1493823600,1493825400,20506
990    [nugget]: Sun Apr 30 10:51:49 2017:       Wed May  3 15:30:00 2017 +30m
989    [nugget]: Sun Apr 30 10:51:49 2017:  [10] 327802,1493821800,1493823600,20505
988    [nugget]: Sun Apr 30 10:51:49 2017:       Wed May  3 15:00:00 2017 +30m
987    [nugget]: Sun Apr 30 10:51:49 2017:  [9] 327802,1493820000,1493821800,20504
986    [nugget]: Sun Apr 30 10:51:49 2017:       Wed May  3 14:30:00 2017 +30m
985    [nugget]: Sun Apr 30 10:51:49 2017:  [8] 327802,1493818200,1493820000,20503
984    [nugget]: Sun Apr 30 10:51:49 2017:       Tue May  2 16:30:00 2017 +30m
983    [nugget]: Sun Apr 30 10:51:49 2017:  [7] 327802,1493739000,1493740800,20484
982    [nugget]: Sun Apr 30 10:51:49 2017:       Tue May  2 16:00:00 2017 +30m
981    [nugget]: Sun Apr 30 10:51:49 2017:  [6] 327802,1493737200,1493739000,20483
980    [nugget]: Sun Apr 30 10:51:49 2017:       Tue May  2 15:30:00 2017 +30m
979    [nugget]: Sun Apr 30 10:51:49 2017:  [5] 327802,1493735400,1493737200,20482
978    [nugget]: Sun Apr 30 10:51:49 2017:       Tue May  2 15:00:00 2017 +30m
977    [nugget]: Sun Apr 30 10:51:49 2017:  [4] 327802,1493733600,1493735400,20481
976    [nugget]: Sun Apr 30 10:51:49 2017:       Tue May  2 14:30:00 2017 +30m
975    [nugget]: Sun Apr 30 10:51:49 2017:  [3] 327802,1493731800,1493733600,20480
974    [nugget]: Sun Apr 30 10:51:49 2017:       Mon May  1 16:00:00 2017 +30m
973    [nugget]: Sun Apr 30 10:51:49 2017:  [2] 327802,1493650800,1493652600,20460
972    [nugget]: Sun Apr 30 10:51:49 2017:       Mon May  1 15:30:00 2017 +30m
971    [nugget]: Sun Apr 30 10:51:49 2017:  [1] 327802,1493649000,1493650800,20459
970    [nugget]: Sun Apr 30 10:51:49 2017:       Mon May  1 14:30:00 2017 +30m
969    [nugget]: Sun Apr 30 10:51:49 2017:  [0] 327802,1493645400,1493647200,20457
968    [nugget]: Sun Apr 30 10:51:49 2017:   Events: 1WWW.CHANNEL4.COM/50270/006|1WWW.CHANNEL4.COM/50270/007|1WWW.CHANNEL4.COM/50270/008|1WWW.CHANNEL4.COM/50270/009|1WWW.CHANNEL4.COM/50270/010|1WWW.CHANNEL4.COM/50270/011|1WWW.CHANNEL4.COM/50270/012|1WWW.CHANNEL4.COM/50270/013|1WWW.CHANNEL4.COM/50270/014|1WWW.CHANNEL4.COM/50270/015|1WWW.CHANNEL4.COM/50270/016|1WWW.CHANNEL4.COM/50270/017|1WWW.CHANNEL4.COM/50270/018|1WWW.CHANNEL4.COM/50270/019|1WWW.CHANNEL4.COM/50270/020|1WWW.CHANNEL4.COM/50270/021|1WWW.CHANNEL4.COM/50270/022|1WWW.CHANNEL4.COM/50270/023|1WWW.CHANNEL4.COM/50270/024|1WWW.CHANNEL4.COM/50270/025|
967    [nugget]: Sun Apr 30 10:51:49 2017:   Last Event: 0
966    [nugget]: Sun Apr 30 10:51:49 2017:   Recorded: 1www.channel4.com/50270/010|1www.channel4.com/50270/007|
965    [nugget]: Sun Apr 30 10:51:49 2017:   CRID: 2/[WWW.CHANNEL4.COM/4SEV0170417315016127]
964    [nugget]: Sun Apr 30 10:51:49 2017:    @ 1493645400 (Mon May  1 14:30:00 2017)
963    [nugget]: Sun Apr 30 10:51:49 2017:   Come Dine with Me
962    [nugget]: Sun Apr 30 10:51:49 2017: Processing slot +47 (47)
961    [nugget]: Sun Apr 30 10:51:49 2017: slots(48, +47,-46)
960    [nugget]: Sun Apr 30 10:51:49 2017: schedule reload complete (48).
959    [nugget]: Sun Apr 30 10:51:49 2017: Closing database.
958    [nugget]: Sun Apr 30 10:51:49 2017: Re-loading schedule database (48).
957    [nugget]: Sun Apr 30 10:51:49 2017: schedule save complete.
956    [nugget]: Sun Apr 30 10:51:49 2017: schedule save starting.
955    [nugget]: Sun Apr 30 10:51:49 2017: Persistent log starting, v0.97
954    +++++++++++++++++++++++++++++++++++++++++++++++++++++++

MymsMan · Apr 30, 2017

Skipping individual episodes allowing time for each to be processed seem to work OK, it is only when scheduling several skips at once via RS that causes problems,

I thought that the recorded episode list was limited to 5 but 9 episodes show in red in the EPG display, I'll see what happens tomorrow after the first recordings

A minor nit when skipping an episode all are show struck out in the RS schedule, not just the episode affected
Probably not worth the effort to fix

MymsMan · May 1, 2017

Despite what the schedule said it actually recorded 14:30, 15:00, 16:00, and 16:30 episode today only skipping 15:30.
As an episode records it effectively unskips the older skip requests

This limits the effectiveness of skipping to resolve conflicts with very frequent programmes.

af123 · May 2, 2017

Thanks for this MymsMan - I'm digesting the posts now!
Skips are done via CRID which can make the display confusing when there are multiple repeats of the same episode.
It certainly shouldn't unskip the older requests, I wonder if that's due to the capitalisation... the database column is not defined as case insensitive unfortunately.

af123 · May 2, 2017

Having changed the code to always use upper-case CRIDs, I've just done a test with Coronation Street on ITV2+1. Set it to record then checked the internal schedule:

Code:

humax# nugget schedule.epg 15 | egrep '(CRID|Start|Events):'
Past Events:
Upcoming Events:
    CRID:     /248484146
    Start:    1493729700 (Tue May  2 13:55:00 2017)
    CRID:     /248484150
    Start:    1493731800 (Tue May  2 14:30:00 2017)
    CRID:     /248484207
    Start:    1493902500 (Thu May  4 13:55:00 2017)
    CRID:     /248485434
    Start:    1494248100 (Mon May  8 13:55:00 2017)
    CRID:     /248485438
    Start:    1494250200 (Mon May  8 14:30:00 2017)
    CRID:     /249154177
    Start:    1494334500 (Tue May  9 13:55:00 2017)
    CRID:     /249154179
    Start:    1494336600 (Tue May  9 14:30:00 2017)

so it starts with 7 episodes and nothing in the 'past events' list which is where the skip entries get placed.

Through RS, I set both of the Monday episodes to skip.
Next, ran the first half of the RS process on the Humax which loads the entries into the local pending table and ended up with this:

Code:

humax# /mod/sbin/rs_process nocommit
Processing command 'skip 15952.13622'
*Skip 15952/13622 - 3/27/262225/1493729700/13326/1WWW.ITV.COM/248484146|1WWW.ITV.COM/248484150|1WWW.ITV.COM/248484207|1WWW.ITV.COM/248485434|1WWW.ITV.COM/248485438|1WWW.ITV.COM/249154177|1WWW.ITV.COM/249154179|
*No pending event
_Coronation Street
_Successfully scheduled skip for recording.
Processing command 'skip 15952.13623'
*Skip 15952/13623 - 3/27/262225/1493729700/13326/1WWW.ITV.COM/248484146|1WWW.ITV.COM/248484150|1WWW.ITV.COM/248484207|1WWW.ITV.COM/248485434|1WWW.ITV.COM/248485438|1WWW.ITV.COM/249154177|1WWW.ITV.COM/249154179|
_Coronation Street
_Successfully scheduled skip for recording.
Sending TBL_RESERVATION schedule information to remote server.
Already up-to-date.
Sending pending schedule information to remote server.
 Updating...
Already up-to-date.


humax# sqlite3 /var/lib/humaxtv/rsvp.db
sqlite> .mode line
sqlite> select * from pending;
              ulslot = 0
            ersvtype = 3
                hsvc = 262225
             nsttime = 1494250200
            szsttime = 00000000000000
           nduration = 1800
             erepeat = 0
             usevtid = 13326
           szevtname = i7Coronation Street
         ulPreOffset = 0
        ulPostOffset = 0
         ulProgramId = 0
          ulSeriesId = 0
            ucVolume = 0
         ucInputMode = 0
             usChNum = 0
           ucRecKind = 4
          ucCRIDType = 50
              szCRID = WWW.ITV.COM/31504171
        szFPBRecPath = Coronation Street
  szRecordedProgCrid = 1WWW.ITV.COM/248485438|1WWW.ITV.COM/248485434|
     szEventToRecord = 1WWW.ITV.COM/248484146|1WWW.ITV.COM/248484150|1WWW.ITV.COM/248484207|1WWW.ITV.COM/249154177|1WWW.ITV.COM/249154179|
aulEventToRecordInfo = Q
           bRecomRsv = 0
 usLastRecordedEvtId = 0
              eReady = 30
              action = 5

Next, committed the pending data:

Code:

humax# jimsh
Welcome to Jim version 0.77
. require rsv.class
. rsv commit

and checked the internal schedule again:

Code:

humax# nugget schedule.epg 15 | egrep '(CRID|Start|Events):'
Past Events:
    CRID:     /248485438
    CRID:     /248485434
Upcoming Events:
    CRID:     /248484146
    Start:    1493729700 (Tue May  2 13:55:00 2017)
    CRID:     /248484150
    Start:    1493731800 (Tue May  2 14:30:00 2017)
    CRID:     /248484207
    Start:    1493902500 (Thu May  4 13:55:00 2017)
    CRID:     /249154177
    Start:    1494334500 (Tue May  9 13:55:00 2017)
    CRID:     /249154179
    Start:    1494336600 (Tue May  9 14:30:00 2017)

So that looks right. I'll just wait for the 13:55 episode to record then check again.

MymsMan · May 2, 2017

af123 said:
Skips are done via CRID which can make the display confusing when there are multiple repeats of the same episode.

For GBRJ Yesterday used three different series Crids for the three repeats each day - I didn't see episodes being repeated on subsequent days
CDWM calls each days 5 related episode a series but uses the same SCRID every day - I haven't seen, but not really checked for, any duplication of episode CRID

af123 said:
It certainly shouldn't unskip the older requests, I wonder if that's due to the capitalisation... the database column is not defined as case insensitive unfortunately.

What I meant by that is that AFAIK szRecordedProgCrid is limited to5 entries and is used to skip the recordings by making them appear already recorded.
As new recordings are made the first entries will be removed from szRecordedProgCrid to maintain the 5 limit, if the removed entry is for a future skipped episode it will pop back into the recording schedule (when theszEventToRecord list is refreshed?) - capitalisation would not affect this

af123 · May 2, 2017

MymsMan said:
What I meant by that is that AFAIK szRecordedProgCrid is limited to5 entries and is used to skip the recordings by making them appear already recorded.
As new recordings are made the first entries will be removed from szRecordedProgCrid to maintain the 5 limit, if the removed entry is for a future skipped episode it will pop back into the recording schedule (when theszEventToRecord list is refreshed?) - capitalisation would not affect this

Ah, yes, right. We can't overcome that problem yet. You can only skip episodes that occur in the next 5.

MymsMan · May 2, 2017

af123 said:
Ah, yes, right. We can't overcome that problem yet. You can only skip episodes that occur in the next 5.

Possibly you could overcome that problem by storing the skip requests separately and only applying them at the end of a recording (recmon exit) when the recording is within 5 episodes. But at recording time you only have the information stored within the hmt which AFAIK does not include the CRIDs from the epg to perform matching and the whole task becomes a mess!
Perhaps in the interim the Skip option should not be offered on the visual menus if the series has no episode CRIDs or there are more than four episodes ahead in the epg so that we don't create the illusion of a skip being scheduled which wont actually work.

However this is a totally different issue from the one for which the thread was created and which I think still exists when skipping multiple episode within the first 5 so I shouldn't have confused the situation by raising the issue with skipping after the first 5 - sorry.

I am a bit confused by the command

Code:

Processing command 'skip 15952.13622'

How do the numbers 15952 and 13622 relate to the series and episode CRIDs needed for the skip - I would have expected the crids to be included in the command

[RS] Problems skipping F1 episodes.

Ye Olde Bowler

Attachments

The Dumb One

Ad detector

Attachments

Ad detector

Administrator

The Dumb One

Administrator

Administrator

Administrator

Ye Olde Bowler

Ad detector

Ad detector

Ad detector

Ad detector

Ad detector

Administrator

Administrator

Ad detector

Administrator

Ad detector